VCAP-DTD | Objective 6.1 | Create a Physical View Client Design

Determine the number and types of access endpoints required for the design (e.g., zero client, thin client, fat client, etc.)

You will normally be presented this type of information during the initial design workshops. In most cases, one of your requirements will be, “the solution must support x users” or “the solution must support x concurrent sessions”. If in the rare situation a business doesn’t know how many users/desktops the infrastructure will be required to support, then you can use capacity planning tools to assist in information gathering.

It is worth clarifying from the start the expected growth required from the design so that these factors can be accounted for.

Each type of endpoint has it’s benefits and drawbacks.

Thin Clients

  • Power on and present the View desktop seamlessly
  • Lower cost and reduced support requirement
Zero Clients
  • No operating system
  • No local storage
Thick Clients
  • Repurpose traditional PCs or laptops (no cost outlay)
  • Apple Mac systems (BYOD)

It’s not mentioned in the blueprint, however tablets should also be considered:

Tablets

  • Apple iPAD
  • Android
For each device the following should be investigated against the design:
  • What OS version is installed, will it require AV and patching?
  • Will it require firmware updates?
  • Will it support multiple monitors?
  • What are the multimedia requirements?
  • Is there a need for local permanent storage?
  • What are the peripheral port access requirements?
  • Are there any special network requirements such as VPN?
  • Where will the device be located, will there be any support and access constraints?
  • Are the user devices mobile?
  • What is the end user capabilities and profile?
  • Will local mode desktops be used?

Identify security requirements for the View Clients

Generally security requirements will already be governed and the View solution will need to fit those requirements. The main considerations client wise, will be if there is a requirement for VPN  and smart card authentication as these will limit the choices of end clients available to use.

Items such as security servers, two factor authentication etc aren’t really an issue for client devices.

Determine connectivity requirements for the View Clients

At this stage we should already be aware of where our users will be connecting from and specifically (for client selection) have a looked at the protocol they will be using, PCoIP or RDP?

Establish multimedia capabilities

If our design determines the requirements for multimedia then we need to ensure that the end clients will support it too!

Multimedia redirection (MMR) redirects the output of multimedia codecs that are running on the remote desktop tot he local client. The local client system renders the full motion video and audio. Windows XP and Vista support MMR, Windows 7 does not.

If there is a requirement for HD video within a Windows 7 desktop, then typically 2vCPUs and 1GB RAM will be required for PCoIP to play 420p and 720p formatted videos. For 1080p, the windows may need to be smaller to get HD quality.

Network latency will be critical for acceptable multimedia performance, and on some links may prove challenging.

Establish peripheral requirements

USB redirection is provided with the View Client running on Windows 7, Windows XP and Windows XP embedded. VMware recommends that an assessment is carried out capturing the USB requirements for all users. Include all USB devices, including:

  • Blackberrys
  • iPhones
  • USB drives
  • USB printers
  • USB Webcams
  • USB headsets
  • etc etc etc etc

During the PoC phase all of these devices should be tested and verified as working.

Printer redirection is key and often overlooked. Ensure the client device supports print redirection and meets the location awareness requirements.

The client device that gets selected will need to supply enough ports. Support for some peripherals may require drivers to be installed on the desktop.

Speak Your Mind

*