The users are first.
This is why we-have a blueprint for XenDesktop 7 Because We want to Avoid starting wrong. We want to make sour que le first thing we focus on are the users.
Think about it this way, When building a house, one of the first things you-have to figure it out is what kind of a house do you want / need (bungalow, cottage, mansion, split level, etc). Sometimes, you might determine That You do not need a house and end up with a condo or apartment. To make this decision, you-have to look at yourself and Understand Your needs (how much space, size of yard, number of bedrooms, etc.). When Defining your needs, you must not only look at today, goal aussi look at what you Anticipate the future to hold, Because MOST of us do not want to move houses every year.
The exact Sami thing takes up with a virtual desktop solution ... Figuring out what kind of resources you need (That notice I did not say "what kind of desktop you need" Because not everyone requires a desktop just like not everyone needs a house).
with So Many housing options, Many times people get stuck in simply try trying to figure it out what kind of house They need, or They Come up with 3-4 options and can not Make That final decision. Again, the Saami thing happens with desktop virtualization, do I need a non-persistent, persistent or applications.
The thing we tried to Accomplish with the blueprint is to Provide a starting spot based on Numerous successful implementations. For example, what if an organization Was try trying to better protect information through centralization for 3 user groups with The Following characteristics:
Call center users Focused on getting through a wide call volume as Quickly as possible, with as FEW distractions have possible.
Who Engineers need to do a lot of trial and error and are looking for alternatives to Often Their current tools are not optimal That
Who Road warriors are always on the go and sporadically need to enter or review a piece of information contained Within a small number of applications.
based on this scenario, we can start to create our conceptual architecture based on the framework we defined in The Earlier blog.
Simply understanding your user's high-level requirements and the overall goal of the organization helps us to start our Creating conceptual architecture. Based on thesis three user groups, we-have The Following:
- Because we want to centralize our data, we are looking at a hosted model for our three user groups:
- Road Warriors -> Apps On-Demand
- Call Center -> Shared (non-persistent model)
- Engineers -> Personal (persist model)
- We also know que la users will need to be presented with Their resources, qui est provided by StoreFront. ALTHOUGH we know we will need StoreFront, we do not know the details of it yet, which is better defined in the Access and Control layers.
- Because we-have thesis kinds of resources, we know this requires us to delivery infrastructure-have controller and controllers. . Purpose we do not know the details yet of These we reach up to the Control layer of the design
Stay tuned for the Access Layer ...
Daniel - Lead Architect
Follow @djfeller
0 Komentar