While I’ve blogged on the mechanics of upgrading from UPM 2.x to UPM 3.x, I’ve not yet addressed the other aspects of planning and configuration. This came up recently in-house, where we’d decided to upgrade an XD4 farm to XD5.
The original request came in as:
“We are creating a new CPM environment for XD5 Pooled in Showcase. We would like to take the contents of the existing user profiles in XD4 Pooled, being managed by an older version of CPM, and migrate them to a new folder share and then attach them to the new CPM environment.
Is this possible? Is it as simple as a robocopy command preserving permissions and pointing the new CPM to this directory?
Any guidance you can offer would be appreciated.
We are using UPM 2.1 currently – is it safe to move the profile folders to a new share and point UPM 3 at them (after the templates have been normalized)?”
So skipping the mechanics (for which, see How do you migrate from Profile Management 2.x to 3.x? )…
From the description, I assumed there was no co-existence phase. (If there is, then start with the above reference). So in essence you just switch off the old UPM 2.1 , copy the profiles to a new file share and turn on the new UPM 3.2.2 (the latest UPM). We recommend this version because the driver has been rewritten for improved coexistence with antivirus software.
So next: “is it safe to move the profile folders to a new share and point UPM 3 at them” – yes, this can be a simple robocopy operation. Please bear in mind the security (ACL) recommendations for the new share – Security Recommendations for Roaming User Profiles Shared Folders
Your existing configuration will form a good basis for the new XD farm. If you update the ADM template, then you will need to configure very little:
- Path to user store – should point at the new file share. If the old Path to user store was something like \\oldserver\oldshare#sAMAccountName#%ProfVer% (where ProfVer is a system environment variable to differentiate between v1 (XP) and v2 (Vista/Win7) profiles – see here for how to set these up), then you will need to ensure the new farm has an identical environment variable set up. Note that the \\server\share part of the path can now refer to a DFS namespace – supported configurations and use cases are described at High Availability and Disaster Recovery with Profile Management
- Active write back – this is enabled by default in version 3. It is designed to write back file changes to a profile without waiting for the user to log off. It may be valuable in XD setups using virtual machines, to avoid data loss following an outage.
- Profile streaming – this is disabled by default in version 3, but is the “flagship” feature. It is designed to speed up logins, by only copying files from the network user store “on demand”. Its use is strongly recommended.
- Always cache – this setting is only effective if Profile streaming has been enabled, and if set to zero, will cause the whole of the profile to be trickled down to the XD machine in the background after the logon completes.
Finally, assuming that you are planning to support local Internet Explorer on the XD desktop, then you should also read To manage cookie folders and other transactional folders. In order to maintain the integrity of the cookie folder, the supported configuration is to set both Folders to mirror and Process Internet cookie files on logoff policies.