Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Unsynchronized offline files are not migrated when you use USMT 5.0


View products that this article applies to.

Symptoms

When you try to migrate offline files data by using Windows User State Migration Tool (USMT) 5.0, unsynchronized data may be ignored in the migration. Additionally, when you examine the scanstate debug logs, you notice the following plug-in errors. (Error text is wrapped for readability.)

Windows XP source computer
2012-07-17 15:05:32, Error [0x0808ff] COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\usmt5\x86\dlmanifests\Microsoft-Windows-OfflineFiles-DL\CscMigDl.dll, {0DB12CCB-7CFD-46B6-B4D1-DAA6FF0FBCF7}, 0) failed, hr=[0x80070003].

2012-07-17 15:05:32, Warning [0x080386] Failure while instantiating IDiscovery for Plugin={ServerPath="Microsoft-Windows-OfflineFiles-DL\CscMigDl.dll", CLSID={0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}, ThreadingModel=Apartment}. Error: 0x80070003

Windows 7 source computer
2012-07-17 08:54:35, Error [0x0808ff] COutOfProcPluginFactory::CreateInstance: m_currentHostSurrogate->LoadDllServer(C:\usmt5\amd64\ReplacementManifests\Microsoft-Windows-OfflineFiles-Core\Cscmig.dll, {0DB12CCB-7CFD-46B6-B4D1-DAA6FF0FBCF7}, 0) failed, hr=[0x80070003].

2012-07-17 08:54:35, Warning [0x080386] Failure while instantiating IDiscovery for Plugin={ServerPath="Microsoft-Windows-OfflineFiles-Core\Cscmig.dll", CLSID={0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}, ThreadingModel=Apartment}. Error: 0x80070003

↑ Back to the top


Cause

Note The following functionalities and limitations apply to online USMT migration of offline files (also known as client-side caching or CSC):
  • USMT 5.0 does migrate CSC settings and the "dirty" (unsynchronized to server) file cache from Windows 8 source computers.
  • USMT 5.0 does migrate CSC settings from Windows Vista, Windows 7, or Windows XP source computers However, USMT 5.0 does not migrate the "dirty" (unsynchronized to server) file cache from these operating systems because the cscmig.dll and cscmigdl.dll plug-ins are not included with USMT.
  • USMT 4.0 does not migrate CSC settings or the "dirty" (unsynchronized to server) file cache from Windows XP source computers.
  • USMT 4.0 does migrate CSC settings and the "dirty" (unsynchronized to server) file cache from Windows Vista and Windows 7 source computers.
In order to migrate the CSC dirty cache, USMT must have plug-in DLLs that are provided by Offline Files. USMT 5.0 does not include the plug-ins in the USMT installation package, even though it does include the necessary XML manifests. If you migrate without capturing the CSC dirty cache, the offline data is permanently lost after the source computer is gone. (Dirty cache CSC data is the local changes that have not yet synchronized back to the file server.)

USMT does not support offline migration of CSC files because plug-ins cannot be used in /offlinewinold or /offlinewindir migrations.

↑ Back to the top


Workaround

Outside USMT

To work around this issue outside USMT, have end-users manually synchronize so that all offline files are up to date on the file server. This can also be automated by using the Synchronize method of the Win32_OfflineFilesCache class. For example, go to the following websites:
Using USMT

To work around this issue by using USMT, use the migration DLLs that are included with the destination OS to correctly migrate CSC cache data by using USMT 5.0 (only) from any source operating system that is supported by USMT to any destination operating system that is supported by USMT. These files are already tested and supported through Windows Upgrade and Windows Easy Transfer (also known as WET or File And Settings Transfer Wizard).

Important
  • In the following examples, USMT 5.0 is installed in C:\usmt. Your path may differ.
  • In the following examples , the C:\windows\winsxs folders are specific to the operating system service pack, build, and hotfixes. Your path may vary. Always use the latest file from the appropriate operating system and architecture.

How to fix 32-bit Windows XP migrating to Windows 7

  1. Locate a computer that is running a 32-bit version of Windows 7 or a 64-bit version of Windows 7 Service Pack 1 (SP1).
  2. Copy the following file:
    C:\Windows\winsxs\x86_microsoft-windows-m..-downlevelmanifests_31bf3856ad364e35_6.1.7601.17514_none_04801f69e1dbd8e6\cscmigdl.dll
  3. Save the file as follows on the source computer, and then migrate by using scanstate:
    C:\Usmt\x86\DlManifests\Microsoft-Windows-Offlinefiles-DL\cscmigdl.dll

    Note
    If you are using /targetwindows7, you must change the path to use "DlManifests7" instead of "DIManifests."

     
  4. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a computer that is running a 32-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\x86_microsoft-windows-m..eplacementmanifests_31bf3856ad364e35_6.1.7601.17514_none_fdfbc5f949b9a49e\cscmig.dll
      2. Save the file as follows on destination computer, and then migrate by using loadstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
    2. If you are migrating to a computer that is running a 64-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_fc6e4e567286d457\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

How to fix 32-bit Windows XP migrating to Windows 8

  1. Locate a computer that is running a 32-bit or 64-bit version of Windows 8.
  2. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a computer that is running a 32-bit version of Windows 8, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\x86_microsoft-windows-m..levelmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_54e92e02157b8aae\cscmigdl.dll
      2. Save the file as follows on the source computer, and then migrate by using scanstate:
        C:\usmt\x86\DlManifests\Microsoft-Windows-Offlinefiles-DL\cscmigdl.dll
    2. If you are migrating to a computer that is running a 64-bit version of Windows 8, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\wow64_microsoft-windows-m..levelmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_bb5c73d80239bddf\cscmigdl.dll
      2. Save the file as follows to the source computer, and then migrate by using scanstate:
        C:\usmt\x64\DlManifests\Microsoft-Windows-Offlinefiles-DL\cscmigdl.dll
  3. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a computer that is running a 32-bit version of Windows 8, follow these steps:
      1. copy the following file:
        C:\Windows\WinSxS\x86_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_c2a4714b6b7f23c6\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
    2. If you are migrating to a computer that is running a 64-bit version of Windows 8, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\amd64_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_1ec30ccf23dc94fc\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

How to fix 32-bit Windows 7 or Windows Vista migrating to Windows 8

  1. Locate a computer that is running a 32-bit or 64-bit version of Windows 8.
  2. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a 32-bit version of Windows 8, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\x86_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_c2a4714b6b7f23c6\cscmig.dll
      2. Save the file as follows on the source computer, and then migrate by using scanstate:
        to"c:\usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll"
    2. If you are migrating to a computer that is running a 64-bit version of Windows 8 computer, follow these steps:
        1. Copy the following file:
          C:\Windows\WinSxS\wow64_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_2917b721583d56f7\cscmig.dll
        2. Save the file as follows on the source computer, and then migrate by using scanstate:
          C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
  3. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a 32-bit version of Windows 8, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\x86_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_c2a4714b6b7f23c6\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
    2. If migrating to an x64 OS Windows 8 computer, follow these steps:
      1. Copy the following file:
        C:\Windows\WinSxS\amd64_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_1ec30ccf23dc94fc\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

How to fix 64-bit Windows 7 or Windows Vista migrating to Windows 8

  1. Locate a computer that is running a 64-bit version of Windows 8.
  2. Copy the following file:
    C:\Windows\WinSxS\amd64_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_1ec30ccf23dc94fc\cscmig.dll
  3. Save the file as follows on the source computer, and then migrate by using scanstate:
    C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
  4. Copy the following file:
    C:\Windows\WinSxS\amd64_microsoft-windows-m..ementmanifests-base_31bf3856ad364e35_6.2.9200.16384_none_1ec30ccf23dc94fc\cscmig.dll
  5. Save the file as follows on the destination computer, and then migrate by using loadstate:
    C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

How to fix 32-bit Windows Vista or Windows 7 migrating to Windows 7

  1. Locate a computer that is running a 32-bit or 64-bit version of Windows 7.
  2. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a computer that is running a 32-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\x86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_a04fb2d2ba296321\cscmig.dll
      2. Save the file as follows on the source computer, and then migrate by using scanstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

        Note If you are using /targetwindows7, you must change the path to use "ReplacementManifests7" instead of "ReplacementManifests."
    2. If you are migrating to a computer that is running a 64-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\x86_microsoft-windows-m..eplacementmanifests_31bf3856ad364e35_6.1.7601.17514_none_fdfbc5f949b9a49e\cscmig.dll
      2. Save the file as follows on the source computer, and then migrate by using scanstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

        Note If you are using /targetwindows7, you must change the path to use "ReplacementManifests7" instead of "ReplacementManifests."
  3. Take one of the following actions, depending on your operating system:
    1. If you are migrating to a computer that is running a 32-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\x86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_a04fb2d2ba296321\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x86\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
    2. If you are migrating to a computer that is running a 64-bit version of Windows 7, follow these steps:
      1. Copy the following file:
        C:\Windows\winsxs\amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_fc6e4e567286d457\cscmig.dll
      2. Save the file as follows on the destination computer, and then migrate by using loadstate:
        C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

How to fix 64-bit Windows Vista or Windows 7 migrating to Windows 7

  1. Locate a computer that is running a 64-bit version of Windows 7.
  2. Copy the following file:
    C:\Windows\winsxs\amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_fc6e4e567286d457\cscmig.dll
  3. Save the file as follows on the source computer, and then migrate by using scanstate:
    C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll
  4. Copy the following file:
    C:\Windows\winsxs\amd64_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_fc6e4e567286d457\cscmig.dll
  5. Save the file as follows on the destination computer, and then migrate by using loadstate:
    C:\Usmt\x64\ReplacementManifests\Microsoft-Windows-Offlinefiles-Core\cscmig.dll

↑ Back to the top


More information

The inability to migrate offline files in these scenarios and not having the migration DLLs in the USMT package represent a code defect and are not a result of product design.

USMT does not support or use plug-ins when it performs offline migrations of any kind (/offlinewinold or /offlinewindir). This behavior is by design.

↑ Back to the top


Keywords: KB2736596

↑ Back to the top

Article Info
Article ID : 2736596
Revision : 9
Created on : 10/19/2012
Published on : 10/19/2012
Exists online : False
Views : 554