This allows us to keep the original settings linked to the new Workspace Container and already apply the new settings as the default settings for all other (read: newly added) Agents. We did establish in our test environment that you can view the settings with the RES PowerFuse 2008 Management Console, but refrained from testing what would happen if we did use the old management console to make changes (no need for unneccessary havoc 😉 ).Īfter upgrading the database we also made some configuration changes, ensures all the original settings (and Agents) were linked to a new Workspace Container () and new settings we implemented as basis settings. RES Software has assured us that there is no problem connecting RES PowerFuse 2008 Agents to the upgraded database, as long as we are not using the RES PowerFuse 2008 Management Console to make configurational changes. Migrating to the latest version will take several days which creates a situation where we are running in a mixed mode configuration with both RES Workspace Manager 2012 and RES PowerFuse 2008 Agents connection to the upgraded database (based on RES Workspace Manager 2012).
RES WORKSPACE MANAGER 2012 UPGRADE
During the migration we are running a sort of mixed mode as we need to upgrade the Citrix XenApp servers in small batches to ensure users are not experiencing any downtime in the environment.
I’m currently performing a migration from RES PowerFuse 2008 to the latest RES Workspace Manager 2012 SR1 software for a large Citrix XenApp environment. I’m not sure if this particular situation will occur in many production environments, but here’s the case we ran into during our RES Workspace Manager 2012 upgrade process:
0 kommentar(er)
