Environment Manager powered by AppSense

Profile Migration

For each Personalization Group, Profile Migration can be configured to either import user profile data into the database from a local profile or network profile or export user profile data from the database back into the local file system.

In this section:

Importing Profiles

Import Restrictions

During profile Import, files may fail to synchronize in the following scenarios:

  • The number of files within a specific profile sync exceeds the IIS MaxHttpCollectionKeys setting - the default value is 1000
  • The size of any single file exceeds the IIS maxAllowedContentLength setting - the default value is 30mb

In both scenarios, the profile import for Windows Settings or Application Groups fails and is reported as "failed to copy data to target" for the migration state. Profile Import continues to attempt to sync the remaining Profile settings.

If the issues above are addressed, the import automatically retries at the next logon if the user has not subsequently captured personalization for Windows Settings groups or that specific application group.

If personalization data has been captured subsequently by the user, after fixing the profile source, the captured data for the failed application group or Windows Settings Group must be deleted for it to be imported on next logon.

Files that cannot be read, such as those locked by another application, are not be imported.

Configure Profile Migration to Import Data from a Local Profile

User profile data is copied at logon from the logged on user’s local profile to the Environment Manager virtual cache. This data consists of included registry, folder and file paths for managed Application Groups and Windows Settings Groups.

  1. In the User Personalization navigation pane select Personalization Groups.
  2. Select a personalization group.
  3. Select the Profile Migration tab.
  4. Click Edit.

    The User Profile Migration Settings dialog displays.

  5. Select Import existing user settings to Personalization.
  6. Select Local from the Source drop-down.
  7. Click OK.

    If settings from a previous import operation exist for the Personalization Group, a dialog displays. The following options are available:

    • Resume the previous import - Existing settings are not replaced, but registry, folder or file inclusions which do not have data are imported.
    • Start a new import - Existing settings are overwritten with imported user profile data.

Profile Migration Import is enabled for users within the Personalization Group.

At logon, data from included registry, folder and file paths for managed Application Groups and Windows Settings Groups within the user profile is copied into the database.

Configure Profile Migration to Import Data from a Network Profile

User profile data is copied at logon from the profile at the specified network path to the Environment Manager virtual cache. This data consists of all included registry, folder and file paths for managed Application Groups and Windows Settings Groups. AppData can be imported from a separate network path if required.

Advanced Certificates, General Folder Options and Icons Windows Settings, cannot be imported from a network location.

  1. In the User Personalization navigation pane select Personalization Groups.
  2. Select a personalization group.
  3. Select the Profile Migration tab.
  4. Click Edit.

    The User Profile Migration Settings dialog displays.

  5. Select Import existing user settings to Personalization.
  6. Select Network from the Source drop-down.
  7. Enter a UNC path in the Network Path field. Environment Variables within the specified network path are expanded.

    The profile version number is appended to the specified network path where required. The following table shows the profile paths for each operating system if \\server\share\profiles\%USERNAME% is specified:

    Operating system Profile version Example profile path
    Windows 7 Windows Server 2008 R2 V2 \\server\share\profiles\%USERNAME%.V2
    Windows 8 Windows Server 2012 V3 \\server\share\profiles\%USERNAME%.V3
    Windows 8.1 Windows Server 2012 R2 V4 \\server\share\profiles\%USERNAME%.V4
    Windows 10 V5 \\server\share\profiles\%USERNAME%.V5
  8. If AppData is stored in a separate location, tick Enable AppData to be imported from a network location and specify a UNC path in the AppData Path field.
  9. Click OK.

    If settings from a previous import operation exist for the Personalization Group, a dialog displays. The following options are available:

    • Resume the previous import - Existing settings will not be replaced, but registry, folder or file inclusions which do not have data will be imported.
    • Start a new import - Existing settings will be overwritten with imported user profile data.

Profile Migration Import is enabled for users within the Personalization Group.

At logon, data from included registry, folder and file paths for managed Application Groups and Windows Settings Groups within the user profile is copied into the database.

Import Activity for Configuration Updates

After configuring Profile Migration in Import mode, a prompt displays if either:

  • Application Groups or Windows Settings Groups are added to the Personalization Group
  • Included registry, folder or file paths are added to a managed Application Group or Windows Settings Group.

Select from one of the options below.

Option Description
Commit the change and restart the Import for the affected groups The Application Group or Windows Settings Group is added to the Personalization Group or the included registry, folder or file path is added to the managed Application Group or Windows Settings Group. The import is restarted for all users within the Personalization Group, regardless of whether data has already been imported for the user.
Commit the change but only for new users The Application Group or Windows Settings Group is added to the Personalization Group or the included registry, folder or file path is added to the managed Application Group or Windows Settings Group. The import is started for users in the Personalization Group who do not have existing data.

Exporting Profiles

Export existing data from the Environment Manager Personalization database into user profiles.

Configure Profile Migration to Export Profiles

User profile data is copied at logon from the database to the logged on user’s local profile.

  1. In the User Personalization navigation pane select Personalization Groups.
  2. Select a personalization group.
  3. Select the Profile Migration tab.
  4. Click Edit.

    The User Profile Migration Settings dialog displays.

  5. Select Export user settings back to their User Profile.
  6. Click OK.

Profile Migration Export is enabled for users within the Personalization Group.

At logon, data from the database is copied into the user profile.

Changing Modes

The table below shows the behavior when changing Profile Migration modes.

Operating system Profile version Example profile path
Disabled Import If settings from a previous import operation exist for the Personalization Group, a dialog displays. The following options are available:
  • Resume the previous import - Existing settings will not be replaced, but registry, folder or file inclusions which do not have data will be imported.
  • Start a new import - Existing settings will be overwritten with imported user profile data.
At logon, settings from the logged on user’s profile are copied into the database.
Disabled Export At logon, settings from the database are copied into the logged on user’s profile.
Import Disabled The import operation is stopped. It can be resumed, however users who have not been migrated will have their user profile settings overwritten.
Import Export The import operation is stopped and cannot be resumed. At logon, settings from the database are copied into the logged on user’s profile.
Export Disabled The export operation is stopped and cannot be resumed.
Export Import The export operation is stopped and cannot be resumed. At logon, settings from the logged on user’s profile are copied into the database.

Related Topics


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other