We currently run view 4.0.x. We have a number of pools with persistent desktops, built with composer (linked clones). As I understand from the 4.5 upgrade documentation the preferred (or only?) way of upgrading to 4.5 is by recomposing the pools. Our problem is that all these desktops have a couple of applications that require individual "hands on" configuration to work properly, and I would very much like to upgrade them without having to do all that work again. Is there a way to do this?
In our lab environment i tried to upgrade by doing the following:
1. Upgrade the Connection server
2. Upgrade VC + Composer, http://status at this stage = failed to communicate with Desktop View Agents (they are still 4.0.1)
3. Then I manually upgrade the View Agent on each desktop in the linked clone pools (without recomposing)
Result:The viewserver can now communicate with the view agents, but I get the infamous "Domain join failed: 1326". Dont know why they would need to join the domain again, since they havent really ever left the domain. I just upgraded the agent...
I tried applying the fixes for this issue (KB944043 + a couple of others), but they only seem to address the issues with 2008 r2 DC's.
Am I missing something here, or am I trying to do something impossible?
If the above can't be achieved, can I upgrade the Connectionserver, VC and Composer and still run the old pools with view 4.0? In that case i could gradually recompose pools (based on a new snapshot with View Agent 4.5) in a controlled fashion and handle one department at a time.
Hope there is help out there!