All TKB Articles in Horizon

Starting at version 4.6, View has the ability to support PCoIP remote access through the View Security Server. See View 4.6 Announcement. I posted an article back in December 2010 in the End User Computing CTO site about this forthcoming View release and described how it works. See Secure Remote Access with View and PCoIP. Some people report that when they setup PCoIP remote access with View 4.6 and try a PCoIP connection from the View Client, they just get a black screen for a few seconds and then an error indicating that the session has ended. On the iPad View Client this problem shows as a message saying "your desktop is loading too slowly". In the vast majority of cases, this was caused because one of the 3 setup steps shown below was not done or not done properly. If you're getting these symptoms, then check very carefully that these 3 simple steps have been done correctly. When View Connection Servers and Security Servers are running 4.6 or newer, you can enable this functionality by following these three steps: 1. Enable PCoIP Gateway functionality on each Connection Server. By default, PCoIP connections are direct from the View Client to the View virtual desktop as they were in View 4.0 and 4.5. If you have some Connection Servers for remote access and some for local access then just do this for the remote access ones. That way local access PCoIP can still be direct to the View virtual desktop. Using View Administrator, go to the Configuration Servers section. Select a Connection Server, select Edit and tick the box "Use PCoIP Secure Gateway for PCoIP connections to desktop". Then for all users of this Connection Server and any Security Servers attached, PCoIP will gateway through either the attached Security Servers or this Connection Server. The server used for the PCoIP gateway (usually the Security Servers) must be running View 4.6 or newer on Windows Server 2008 R2. 2. On every attached Security Server, set up the “External URL” and the new "PCoIP External URL". These URLs are used by the View Clients to connect to the particular View server. These names and addresses must be resolvable and usable by the clients. If remote connections are made directly to the Connection Server then the External URLs must also be setup on the Connection Server. 3. Update the firewall to allow PCoIP to pass through. This is: PCoIP between View Client and Security Server TCP destination port 4172 from Client to Security Server UDP destination port 4172 from Client to Security Server UDP source port 4172 from Security Server to Client (this is the reply UDP data) PCoIP between Security Server and virtual desktop TCP destination port 4172 from Security Server to virtual desktop UDP destination port 4172 from Security Server to virtual desktop UDP source port 4172 from virtual desktop to Security Server (this is the reply UDP data) This is in addition to the firewall rules used in View 4.5. For further details, refer to the View 4.6 Architecture and Planning Guide and the View Administrator Guide here View Documentation. For a more detailed examination of this, take a look at this video. It goes into details on the deployment and architecture for PCoIP remote access with View 4.6 and goes through a worked example involving remote and local access, load balancing, the n+1 VIP model, the external URLs etc. and shows how it is all configured through View Administrator. Mark Benson - VMware - View Architect - End User Computing CTO Office

Has someone been able to deploy a View 4.5 Connection Server (Standard) with a vCenter 4.1 Update 1 server ? I'm getting a "Error saving vCenter entry" error. I did clear out like the VMware KB says the vShield licenses from my vCenter. My View 4.5 has no issues connecting to a vCenter 4.0 or vCenter 4.1, but it's stuborn with my vCenter 4.1 Update 1 Regards, Erik Bussink

During the installation vCenter server, there is an option two choose a DSN which points to en external database or we can make use of the SQLExpress which is buntled with vCenter Server. This Document describes installation of View Composer keeping database on the SQLExpress instance which is configured automatically during vCenter installation. Firstly login to the server where VMware vCenter Server is running. Install SQL Server management Studio Express.This software can be downloaded from Microsoft Website. Now open SQL Server Managemet Studio Express (MS SSMSE) login as below. Now object explorer for the database will be opened. Here you can create a new database but however, view composer does not support windows integrated authentication. Hence new user (SQL user ) need to be defined and map with a new database. Typically such SQL express instance should not have a production DB role. So here I am going to explain creating a new DB and mapping it to the inbuilt SQL admin account named "sa". In our case, by default the "sa" account will be in disabled mode. So as the first step we will enable the account and set a password. On the SQL object explorer  - Under 'Security' select the 'Logins'. Right click on 'sa' and go to properties. set password hereand make necessary password enforce policy if required (else uncheck). On the properties window left side click on the status, and grant the permission to connect to database and enable the login. refer below Right click on the server , go to properties and Change the authentication type to Mixed Modeas below. Restart the SQL Service Now the SA account has been enabled for the SQL instance. Disconnect the object explorer and connect to the SQL again using sa account Now the oject explorer is connected to database using sa credentials. as the final step we need to create a new database that need to use with composer. righ click on the database inventory , and select 'New Database' name the database , and click OK This will create new database, and since it si created using 'sa' account 'sa' will have complete permission on this DB. So no need to configure tha database permission and user mapping for this DB. If you are creating a new user other than 'sa' then the User should have the permissions and db ownership to the database. We are now done with the database configuration. the left out part is DSN configuration. From the control panel , open ODBC configuration and select system DSN. One DSN would be already available for virtual center. Click "Add" to create one for View Composer. Select 'SQL Native Client' and click finish. On the next page fill in the DSN name , Decription, and Server. Name can be of any choice. Description is optional and Server should be in the syndax <Hostname>\SQLEXP_VIM Click next, and choose the authentication and SQL authentication and provide sa credentials. In case new user is defined and mapped database , provide that here. Chage the default DB to the newly created database. proceed the wizard through next page with default options and finaly test the data source. The test should give a successful result as below. Click OK and finish teh wizard. This will return to the DSN configuration page of ODBC, and both VC and newly cretaed DSN will be lister here as below Now install View composer, and when it asks for databse, Give the DSN name as 'View Composer' and username as 'sa' and its password. Proceed the wizard and complete the installation

My customer wants to minimize the number of View member servers to monitor and maintenance. They attempted to install Connection Server service on Active Directory server, but failedwith the attached warning : `This product cannnot be installed on Domain controller'. I know that this is not a recommended configuration at all for a number of reasons, but I'd like to know why the connection server installer is not allowing us to install connection server on Active Directory server to convince the customer.

The big difference between VMware View 3 and 4 is that View 4 adds a new display protocol – PCoIP – that provides an optimized desktop experience for the delivery of the entire desktop environment specially across WANs with high latency and low bandwidth. From a user experience perspective View 4 offers a big improvement over its former release, but for the VMware View Administrator nothing much changes on a day-to-day basis besides few bits and pieces, and off course, the added support for vSphere 4 that enables improved virtual machine scalability and performance. The installation of all VMware View 4 components is pretty much the same – For VMware View Agent only an additional option to install a PCoIP Server when deploying to the template. See original post at [http://myvirtualcloud.net/?p=403|http://myvirtualcloud.net/wp-content/uploads/2009/12/viewagent_install.png] There is another difference during installation of VMware View Client. A feature called Log in as current user that provides enhanced single sign-on – this feature integrates with Active Directory and smart cards to help simplify the process of logging in to a VMware View desktop. If you want to require all users to provide identity and credential information to log in to a View Connection Server and again to access a View desktop, deselect the Log in as current user component. [http://myvirtualcloud.net/?p=403|http://myvirtualcloud.net/wp-content/uploads/2009/12/viewclient_install.png] Most of the new features related do administration or management can be found in the Desktop/Pool Settings and View Server Settings pages. Connection server restrictions: When you assign a tag to a View desktop or desktop pool, only users who connect to a View Connection Server instance that has a matching tag can access that desktop or desktop pool. You can assign a tag when you add or edit a desktop or desktop pool. See View Server Settings for configuration of the tags. Default display protocol: The new option here is PCoIP, however RDP and HP RGS are still available. Max number of monitors: Support for up to four monitors. (PCoIP only) Resolution on each monitor: Support for resolutions up to 1920×1200 and pivot orientation to each monitor independently. (PCoIP only) [http://myvirtualcloud.net/?p=403|http://myvirtualcloud.net/wp-content/uploads/2009/12/add_desktop.png] Tags: In View Server Settings administrators now can control user access to virtual desktops based on the View Connection Server being used for authentication. When you assign a tag to a View Connection Server instance, users who connect to that View Connection Server can access only those View desktops and desktop pools that have a matching tag or no tags. [http://myvirtualcloud.net/?p=403|http://myvirtualcloud.net/wp-content/uploads/2009/12/viewserver_settings.png] From View 4 release notes it is possible to read the following additional features: Smart card policies – Administrators can set group policies to force desktop disconnection and require reconnection when users remove smart cards. Domain filtering – You can use vdmadmin.exe to control the accessibility of domains and traverse trust relationships more quickly. You can cleanly delete View desktops using scripts. I haven’t seen any additional information about this, not even in the manual. The only link with a script to clean orphaned replicas comes from Duncan Epping. http://www.yellow-bricks.com/2009/12/16/cleaning-up-orphaned-replicas-in-view/ You can log in to View desktops using user principal names (UPN). You can explicitly configure IP addresses to override those supplied by the View Agent when accessing a desktop. Mixed Active Directory and Kerberos authentication is supported. Conclusion Besides some obscure new features that are not even properly documented in the manual, the upgrade and management of VMware View 4 should be no hard work for an experienced View 3 administrator. PCoIP greatly enhances the user experience however due to the lack of new features, in my opinion VMware View 4 had an early market release as a result of the obvious competition with XenDesktop. One of the features I would like to see for a next release is a agnostic connection protocol such as http/https to be able to access the desktop from anywhere. For some organisations multimedia and audio are not the most important when delivering virtual desktops but I will let this discussion for another opportunity. See original post at (Virtual Cloud) Andre Leibovici

This document describes the process of configuring a Wyse V10L to work with TCX. This is an open Wiki for the community to evolve and improve. What is TCX TCX are enrichment extensions to allow additional features to your remote sessions. There are currently three extensions and more planned. Multimedia - TCX Multimedia is a software layer on the server that intelligently redirects the multimedia processing tasks dynamically between the client and server. The multimedia stream decodes locally on the client using the local processing power of the device thereby providing complete multimedia playback capabilities overcoming any limitations that are inherent in traditional thin computing architectures. USB Virtualisation - Enables the sharing and discovery of local USB devices as if they were connected directly on the Virtualized Desktop environment. Solves the USB peripheral issues when it comes to deploying thin clients. No more compromise on limited local drivers. The Wyse thin clients now can seamlessly access their USB-based printers, scanners, storage devices, Palm, BlackBerry, and Pocket PC hand­helds over VDI environment. What do I need? You will need : a terminal, a license key for the component of TCX you are enabling (either multi-media or USB redirection) the Wyse software for the virtual machine an FTP server to place the config files a DHCP server to place some options string in Step 1 - Get your V10L working and pulling its config off the central FTP servers wnos.ini file. An example entry into your wnos.ini file. SignOn=yes autoload=1 EnableKeyboardMouseSettings=no SessionConfig=ALL MapDisks=yes DomainList=YOURDOMAIN VDIBroker=https://192.168.1.100/ Timeserver=192.168.12.40 TimeZone='GMT + 10:00' ManualOverride=yes Daylight=yes Start=100107 End=040107 TimeZoneName="AUS Eastern Standard Time" DayLightName="AUS Eastern Daylight Time" Language=Au Step 2 - Add the settings for TCX to your wnos.ini file Put your license code for TCX into the wnos.ini file. If you have multiple separate by a comma. TCXLicense=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE,FFFFF-GGGGG-HHHHH-IIIII-JJJJJ Step 3 - Install the Wyse software into your VM Get the latest extensions from the Wyse website. You then need to install them inside the virtual machine that the terminals will be connected to. You are going to want to make them part of your SOE or template which drives your pools. Step 4 - Test Now you can do your testing to make sure it all works. For multimedia you just need to play video of a supported format. Try it full screen and see if the sound is in sync. You can also look on the log file in your client and you will see an entry showing that decoding has started. Another way to see if video is working if you have dual screens is sit the video across the two screens, you will see that only half the video plays, depending which screen has the greater view of the video. A current limitation is spanning two monitors. To test the USB attach a simple USB device such as a storage device. Again you should see the entries on the clients log showing a new device has been inserted. You virtual machine should report new hardware detected and load the driver or the device will just start working. It does not work. What now? If USB is not working you may need to set the terminal to map through the USB device. Put an entry of "unmapusb=no" into your wnos.ini file. Further reading and helpful links The ThinOS Admin guide has the details of the configuration options, especially for the important ones for the wnos.ini file. The next thing your will want to do is get it working with VDM, see Using the Wyse V10L and S10 Thin Clients with VDM.