July 21st, 2010 
Simon Seagrave 
Are you managing or thinking of implementing a VMware View environment? If so here’s a potential gotcha to look out for. As you may or may not have heard with the introduction of VMware vSphere 4.1 the vCenter Server has now gone 64bit which is good news in the interests of moving towards pure 64bit environments though the catch is that VMware View Composer 2.0.x unfortunately does not support 64bit operating systems.
The solution or workaround? That’s simple, as per VMware’s Knowledge Base article here just don’t upgrade to VMware vSphere 4.1. Admittedly this is a simple workaround though obviously will have implications for those of you running a VMware View environment who are also wanting to upgrade to and take advantage of the exciting new features found in vSphere 4.1.
No related posts.
Posted in 
My name is Simon Seagrave and I am a London (UK) based Senior Technology Consultant and vSpecialist working for EMC. 
Loading ...
The issue is slightly more complex and annoying than this.
The composer service (as part of View 4.01) works perfectly with Server 2008 x64/2008 R2 x64 and vSphere 4.0 (update 1 and 2). I have been using it this way since late 2009
vCenter 4.1 seems to be the breaking point now. The View connection servers can no longer contact and use the Composer service running on the vCenter 4.1 server.
This is another PR and image issue that View did not need after recent news of View 4.5 problems
It really seems from the outside as if View 4.01 did not even get tested or QA against vSphere 4.1 until after release.
Do the internal teams and beta testers talk and test or not?
I guess we now wait for the mythical View 4.5 (September timeframe?)
[...] This post was mentioned on Twitter by VMware Planet V12n, TechHead.co.uk (Simo. TechHead.co.uk (Simo said: New TechHead Post: "VMware View 2.0.x and vSphere 4.1 Gotcha" http://tinyurl.com/37glw2y [...]