After working on updating my View 4.5 environment to 4.6, I came to the conclusion that the documentation is not exactly complete. I have listed out a few tips to take note of during your update process.
•All of the base images must have the upgraded View Agent installed. ◦You can install over the existing 4.5 agent, however it might fail if the View Composer Guest Server Agent can’t be stopped. To get around this, disable the service, reboot and reinstall the 4.6 agent
◦Once you install the agent, make sure you check the video card driver version. It should be the VMware SVGA 3D (Microsoft Corporation – WDDM) version 220.127.116.11
•Easiest way to upgrade the connection broker is by adding a replica server. ◦If you are running Windows 2003 32-bit the easiest upgrade path is to add a new server. Simply create a 2008 R2 server and install View as a replica server.
◦If you want to keep your Connection Server as 2003 then you can simply click the option “Use PCoIP Secure Gateway for PCoIP connections to desktop”
◦If you want to have a security server, I found it easiest to create another new server and set the pairing password. If your security server is already 2008 r2 then you could also reinstall the security server and set the password, but that would stop access temporarily from the outside world.
•On the View Admin console, make sure to set the external url on both the Security Server and the Connection Server. This is not needed or possible if you keep a 2003 connection server.
•If you want PCoIP over the WAN you will need to open a few more ports in addition to 443 ◦TCP 4172 Security Server -> Virtual Desktop
◦UDP 4172 Security Server Virtual Desktop
◦TCP 4172 View Client External -> Security Server
◦UDP 4172 View Client External Security Server
•If you think you have all the ports open, but still get a time out when using the Ipad client or through PCoIP, but RDP works fine and you are using a Cisco ASA (and possibly some other firewalls); we have found that you may need to separate the firewall rules. One rule for the UDP 4172, one for TCP 4172, and one for TCP 80 and 443. Having a single rule with all the ports seems to have problems when connecting through an ASA.
Hopefully these few tips will allow your upgrade or deployment to go just a little bit smoother.