Last month Barry Schiffer and I did a presentation on E2Evc, the subject? “Enterprise clients. when to use what and why?”
The last couple of meetings I had with customers this was a very hot topic, people are rethinking their client strategy with BYOD and CYO as alternatives to their traditional desktop strategy. I noticed that there still is a demand for a client strategy when using SBC/VDI but there are a lot of choices to be made when looking at enterprise clients:
With the upcoming release of Hyper-V 3.0 we see a lot of movement from both VMware and Microsoft on marketing level so all features are promoted, recently this type of marketing became a bit more ugly as VMware launched a ‘Get the facts‘ and older blogs from Microsoft on ‘Windows Server 8: Hyper-V 3.0 Evens the Odds with vSphere‘. Dan Brinkmann posted a very useful overview (from a Microsoft perspective) about the hypervisor on his blog.
During the last couple of projects I did I noticed that Microsoft Lync would prevent my session to log off normally, either on a Citrix XenApp/XenDestop or normal fat client deployment. Somehow running Lync stopped the logoff process and I would the error “This program is preventing Windows from logging off”:
The last couple of days there is a lot of positive but also some negative commotion in the twittersphere about the announcements made at Citrix Summit/Synergy in SF.
As the Customer Preview of Windows 8 was released yesterday and I had some additional time today I wanted to install the VDA in the Windows 8 CP. I already tried the VDA installation with the Windows 8 developers release but that wouldn’t work, it came up with the Windows 8 version of a BSOD. So with this new release and the release of VDA Version 5.5.100 I thought why not just try again.
Yesterday I was discussing the Mobility pack with a co-worker on a project and he told me his start menu was changed. After logging into the desktop with my iPad I recognized the mobility pack (which is a good step in new functionality). He was wondering how it got installed so after some investigation he found the reason, he had been installing hotfixes on his system and installed Hotfix XA650W2K8R2X64011 and the readme says:
