Follow

Application Data migration from Portability to Folder Redirection

Product: ProfileUnity

Product Version: 5.5

Expires on: 365 days from publish date

Updated: November 26, 2013

 

Problem:

This is general guidance how to configure ProfileUnity to migrate Application Data and Local Application data from portability rule to folder redirection.

 

Symptoms:

After migration it is not recommended to make AppData or Local App Data stay using portability rule because it significantly extends logon time creates extra traffic on the network and makes some impact on available memory and CPU cycles.  The redirection is always the desired end solution.

 

Possible Resolution(s):

Note: Following steps are only compatible with windows 7 or above. If you are running PU with windows XP please create "Windows 7" filter.

Note2: This is for one time migration and not Windows XP and Windows 7 co-existence. 

 

Chain of events which will happen after making configuration changes:

1) User logs in with new configuration 

2) Portability rule is run and files are written to "Application Data and Local Application Data" on to local system drive.

3) Folder Redirection rule is executed and "Copy to new location" takes place (Files are migrated to new redirected location)

Configuration:

Step 1) Create folder redirection of AppData and/or Local App Data with setting "Copy to new location"

Note: We use "Copy to new location" because "sync" might not have enough time to complete before user log off. 

Application Data examples:

    • If you are redirecting to a path use "\\servername.domain.com\Sharename\%username%\AppData\Roaming"
    • If you are redirecting to a mapped drive use I:\AppData\Roaming -  (This requires configured "Mapped Drive")
    • If you are redirecting to a Virtual VHD, use: "%userprofile%\Profile-VHD\AppData\Roaming" - (This requires configured "Virtual Disk")

For more information on how to configure Virtual Disk go here: How to create Virtual Disk (VHD) and mount to a path or drive letter?

Example of redirecting to VHD which is mounted to a path:

appdata.jpg

 

Local Application Data Examples:

    • If you are redirecting to a path use "\\servername.domain.com\Sharename\%username%\AppData\Local"
    • If you are redirecting to a mapped drive use I:\AppData\Local - (This requires configured "Mapped Drive")
    • If you are redirecting to a Virtual VHD, use: "%userprofile%\Profile-VHD\AppData\Local" - (This requires configured "Virtual Disk")

For more information on how to configure Virtual Disk go here: How to create Virtual Disk (VHD) and mount to a path or drive letter?

Example of redirecting to VHD which is mounted to a path:

localapp.jpg

Note: To test the setting on a specific user before making this change global create a "user" filter and use it instead of "Windows 7" filter to test this setting. Once the test is sucessfull and some extensive testing of the applications the change can be made global by changing the filter on folder redirection from "user" filter to "windows 7'"filter.

 

Step 2) Select "Update" in ProfileUnity console and download your new default configuration ini file to your netlogon\profileunity folder.

 

Step 3) Users can start to log in.

When the user logs in with those settings and portability setting on the AppData than following list of events (listed only relevant items) happen:

1) Virtual Disk is mounted

2) ProfileUnity Portability rule is executed and AppData is copied from AppData.7z to your local AppData folder

3) ProfileUnity finished running other portability rules

4) ProfileUnity folder redirection takes place and PU recognizes it needs to copy AppData folder located on local disk to new redirected location

5) After copy registry is modified pointing AppData and Local AppData to new redirected location.

Note: Because the AppData and/or Local AppData is copied twice this logon is usually 2x time longer than usual logon first time with above scenario.

Note2: To verify who is redirected and who is not, enable inventory setting within ProfileUnity.

Note3: To verify manually folder redirection took place, verify at this registry location: HCKU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders.

 

Step 4) Once it is verified that all users are migrated, to clean up follow those 3 simple steps.:

  • Pause/Delete Application Data Portability rule
  • Pause/Delete Local Application Data Portability rule
  • (Update and download default.ini file)

Note: If you would like to accomplish opposite task, follow this KB: How to migrate users from Folder Redirected Application Data to Portability

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.