View 4.6 has been released
Same days ago VMware has released the new version of View. It include several bugfix, it fully supported the new vSphere 4.1 U1 and has some enanchments.
The most valuable new feature is that now the security server can accommodate PCoIP connections... So no more VPN (or public IP addresses for virtual desktops) is required to use PCoIP over Internet.
Other features like a Client Hypervisor or new tools specific for profiles and GPO management are still missing.
VMware View 4.6 Release Notes:
The upgrade take
I've tested the upgrade without read the upgrade guide (it's not a recomenended practice, but was a way to test how easy or difficult was the upgrade).
The vSphere 4.1 was already upgrade last week (with still old VMware Tools on virtual desktop to avoid problem with View Agent 4.5), so only the View part was interested.
The upgrade is very simple and fast and it most case does not require any reboot. To be honest the enviroment was simple with only one Connection Server and one Secure Server and some pools.
For VMware Composer, only warning to keep the existing certificate (by default it prompt to create a new one)... no need to reboot the vCenter Server, so it's very clean and simple.
For the Connection Brokers (both Connection Server and Secure Server) the upgrade is more simple and still no reboot is required. For the Secure Server the new parameter for PCoIP is asked (a public IP address).
For the View Client a reboot is prompted, but seems that the new client works also without it. The client (as also in the 4.5 version) can be simple download from a Connection Broker.
For the virtual desktop, in order to use PCoIP with the Secure Server the new View Agent is required. For other operation (for example RDP with a Secure Server) also the old 4.5 agent works fine.
Upgrading the agend require a reboot, but could be the right time to also upgrade the VMware Tools or apply latest Windows Updates.
To upgrade the desktop pool, a simple recompose operation can be applied using the new snapshot from the "master desktops".
Note from my enviroment:
- all Windows servers virtual with Windows Server 2008 R2
- desktop pools are some with Windows XP Pro and others with Windows 7 Ent, in both cases with 32 bit architecture
- I've tested only with a Windows XP (32 bit) and Windows 7 (64 bit) clients
- desktops are in my local language, servers are all in english language
Windows 7 SP1 Support
Officially there is only an experimental support for Microsoft Windows 7 SP1 RC operating systems.
But I've also tried to create a pool with Windows 7 SP1 and seems that there aren't big issues.
As written the big news is the support of PCoIP though a Secure Server... this finally can open the usage of this protocol in a simple way also of WAN connection where the RDP solution was not efficient.
I've tested with the new client and it works like a charm, it's easy, it's works and also performance are quite good.
IMHO this is the right approach, instead of require VPN client and connections. Also the client can be unmanaged so have VPN connections on it may be a potential security hole (although several solutions can be used to mitigate this problem, but they require more complexity).
Note that a new port (4172) is required to use PCoIP with a Secure Server and also a public IP (strange but it require an IP, not a DNS FQDN). IMHO a pure tunneled solution with only the port 443 was a better solution... But at least it only require two ports (443 and 4172) and the public IP can also be owned by firewall that natted the secure server.
VMware View 4.6 PCoIP Software Gateway (PSG) from Andrelei Bovici
Security server vs VPN thread (it's shot but interesting)
When use RDP?
Also if now PCoIP can be used with a Secure Server, there are some cases where the RDP protocol must be used (so could be used to keed each pool with the dual protocol option):
- old client version: for example from thin client or from special software (I've tested with the Dell Latidune On option, but of course actually can not use PCoIP with the Secure Server)
- client without PCoIP support: like smartphone, Mac Client or most Linux Client
- tablet: actually most are without PCoIP support (but seems that the iPad View Client will have this support)
- Aero Theme requirements: with RDP and Windows 7 client is possible use Aero, with PCoIP no