Users

Access

Resources

The Resources layer is the next stage of the blueprint.

Resources are the desktops and applications that we want to deliver to each user. This is also where many people get stuck because the perception is that there are a lot of options. There can be a lot of option until you start looking at it from a user group per user group perspective. Plus, when we look at the resources we want to deliver, we focus on a few core areas. If we look at our blueprint, we can break this down into 3 different user groups:

  • Road Warriors who we defined to use On-Demand Apps
  • Call Center users who will use the Shared (non-persistent) model
  • Engineers who use the Personal (persistent) model

Based on these groups, we define the following:

Road Warriors Call Center Engineers
Operating System Windows 2012 Windows 2012 Windows 7
Provisioning Method MCS MCS MCS
Corporate App Integration Installed into image Installed into image Installed into image
Personal App Integration Local App Access N/A Personal vDisk
Profile Citrix Profile Management
(standard config)
Citrix Profile Management
(standard config)
Citrix Profile Management
(standard config)
Policys(s) For users accessing through NetScaler Gateway: Optimized for WAN: Users Policy (Template)
For users NOT accessing through NetScaler Gateway: High-Definition User Experience Policy (Template)
For defined AD Groups: Mobile Experience policy (Custom)

And with this, we update our conceptual architecture as follows:

That’s all there is to the resource definition of the blueprint. Sure there are a lot of policies and profile settings you can manipulate, but why not start with the standard templates? These will cover a large percentage of use cases. If you need to customize then feel free to do so, but with the templates, you don’t have to start from the beginning.

Daniel – Lead Architect