Here's a little secret ... Most XenDesktop environments are extremely similar. In fact, if you ignore the many combinations of hardware out there, the similarities are increasing significantly.
Have user groups (some internal and some external) who need to access a resource type, be it a desktop or an application, which is managed by a set all controllers running on the hardware.
so why desktop virtualization is so complex? Because we have done it that way, believing that any deployment should start from scratch.
Think if you were going to have a house built. You start with a high-level plan. The first thing you do is determine what type of home you want to build: a rambler, split level, 2 floors, etc., but will have the same basic components (HVAC, electrical, plumbing, carpentry, roofing, etc. ). However, the first things that you think should not be wiring. It would be foolish to start here because you do not even know where the walls are to be located which contain son. So tell me why when you make desktop virtualization make people start with storage or servers?
This is why we have a XenDesktop plane 7. To guide you on your way to creating a desktop virtualization solution, XenDesktop 7 each solution has 5 parts:
1. user layer -. Defines the unique user groups and the general requirements of
2. Access Layer -. Defines how each group of users will have access to their resources by focusing on secure access policies and office stores / application
3. Line resources - defined positions virtual desktops and applications assigned to each user group
4. control Layer - Sets the underlying infrastructure required to support all users to access their resources
5 . physical layer - Sets the physical implementation of the overall solution
This is the framework for understanding how all the layers are based on the previous layer. When you start to develop the conceptual architecture of your solution, it begins to look like the following:
As we work through the layers in future blogs, we'll see how this structure will take shape and the decisions that you really need to do
Stay tuned ...
Daniel -. Lead Architect
Follow @djfeller
0 Komentar