VCAP-DTD | Objective 6.2 | Determine Session Connectivity Requirements for a View Client Design

Establish session mobility requirements (e.g., Follow Me, etc)

Does the business already have an investment in a follow me solution?

How do people print now?

Will that solution integrate with the built-in ThinPrint features of VMware View, or will a further investment be required?

Print jobs can severely affect bandwidth and responsiveness, if possible, use follow me/location based printing to avoid transferring bits over the RDP or PCoIP remote display channels.

Some consideration here, should also be given as to what will happen when a user disconnects from an active session. For example, a user is in a client meeting at a remote location, connected to their View desktop via an iPad. They have made various notes throughout the meeting and at the end simply disconnect. They then travel home or back to a corporate office and login again, will their disconnected session take them to where they left off?

If this is required you need to carefully think about how long you leave ‘disconnected’ sessions available for, as potentially, these desktops could just be sat there for a number of hours or day consuming resource when they don’t need to be.

Establish remote access requirements

The requirements for remote access should come from the business. It will be up to you to determine the number of security servers, the connection protocols, and consider using tags for remote access.

In most cases not all users will require remote access, therefore they could potentially be a separate use case, but that would probably be too easy. If  remote access is required, will the business be happy with the users getting the full feature desktop they have when residing on the corporate LAN or will a different restricted desktop be made available (where tags will come in to play).  I’ve seen people struggle with tags so here area few snippets that you should be aware of when using tags.

  • The tags are applicable to Connection Servers only and not Security Servers
  • Any Security Servers paired to a Connection Server works exactly like the Connection Server
  • If a load balancer is used in front of a group of Security Servers or Connection Servers they must be tagged in the exact same way
  • A single Connection Server or single Desktop Pool can have multiple tags
  • Multiple Connection Servers and Desktop Pools can have the same tag
  • Desktop Pools that do not have any tags can be accessed through any Connection Server
  • View Connection Servers that do not have any tags can only access the desktop pools that also do not have any tags
  • Tags have a higher priority to user entitlement pools
Depending on the remote location, thought will need to be given as to which connection protocol will be used, and therefore will you give users the ability to choose their own protocol?
VMware and Teradici have provided the following guidelines for remote access:

Determine applicable session behaviour requirements for the design (e.g., disconnect, logoff, timeout)

This type of information should be given to you again from the business, else you will need to probe for the answers in the design workshops. As briefly mentioned earlier, if disconnected machines are never logged off, sessions can (but not in the same way as with old terminal server sessions) become stale, and consume resource for no reason.

It is likely you will use different policies for different pools. For example, a dedicated assignment pool may not have any disconnect sessions, or potentially they logoff times will only be once a week to keep inline with company policy. Floating desktops or kiosk style may have a much shorter policy and perhaps could be logged off every evening or at the end of every business day. Discuss the options with the business to make suitable plan.

Identify display protocol requirements to satisfy the design

VMware have worked hard with Teradici to promote the PCoIP protocol and will try to push this over RDP where possible. Refer to the above table to determine which protocol is suitable for your desktop pool assignments. Perhaps with more IT savvy users you let them choose their type of protocol instead of forcing the users to use one desktop internally and potentially another externally.

Is multimedia required within the desktops? If so, you will want to try and ensure that all desktops requiring multimedia content are using the PCoIP protocol for improved performance. If the desktop is a simple task worker desktop with a few applications on then you will probably find that RDP is sufficient and will allow for users connecting in.

Ensure GPO is reviewed to make the most out of your chosen connection protocol. For example, disable the build to lossless feature in limited bandwidth situations etc.