Understanding what the USMT 4.0 CONFIG manifests migrate (Part 3: XP Section B)
This part covers the following config.xml components for Windows XP:
--------------------------------------------------------------------------------------------------
<component displayname="Microsoft-Windows-RasmanService-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-rasmanservice-dl/microsoft-windows-rasmanservice-dl/settings"/>
<component displayname="Hardware" migrate="yes" ID="hardware">
<component displayname="Printers and Faxes" migrate="yes" ID="hardware\printers_and_faxes">
<component displayname="Microsoft-Windows-Printing-Spooler-Networkclient-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-networkclient-dl/microsoft-windows-printing-spooler-networkclient-dl/settings"/>
<component displayname="Microsoft-Windows-Printing-Spooler-Core-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-core-dl/microsoft-windows-printing-spooler-core-dl/settings"/>
</component>
<component displayname="Phone and Modem" migrate="yes" ID="hardware\phone_and_modem">
<component displayname="Microsoft-Windows-TapiSetup-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-tapisetup-dl/microsoft-windows-tapisetup-dl/settings"/>
</component>
</component>
--------------------------------------------------------------------------------------------------
Remote Access Connection Manager
Config Entry
<component displayname="Microsoft-Windows-RasmanService-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-rasmanservice-dl/microsoft-windows-rasmanservice-dl/settings"/>
Config Manifest
"\USMT\x86\DlManifests\rasmanservice-dl.man"
Behavior Synopsis
Migrates custom DLL autodial entries for Remote Access Connection Manager settings for the computer, does not migrate per-user. Only useful if the custom DLLs are installed on the destination.
Special Consequences: probably has no value in migration unless same third party remote access software used on destination.
No screenshot possible. AOL and MSN are example clients.
Mapped Printers
Config Entry
<component displayname="Microsoft-Windows-Printing-Spooler-Networkclient-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-networkclient-dl/microsoft-windows-printing-spooler-networkclient-dl/settings"/>
Config Manifest
"\USMT\x86\DlManifests\printing-spooler-networkclient-dl.man"
Behavior Synopsis
Migrates mapped network printer settings, per-user settings. Per-computer settings are for non-useful stuff. These settings have no effect on local printers or printers shared out this computer.
Print Spooler
Config Entry
<component displayname="Microsoft-Windows-Printing-Spooler-Core-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-core-dl/microsoft-windows-printing-spooler-core-dl/settings"/>
Config Manifest
"\USMT\x86\DlManifests\printing-spooler-core-dl.man"
Behavior Synopsis
Migrates computer’s Spooler settings.
Telephony
Config Entry
<component displayname="Microsoft-Windows-TapiSetup-DL" migrate="yes" ID="https://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-tapisetup-dl/microsoft-windows-tapisetup-dl/settings"/>
Config Manifest
"\USMT\x86\DlManifests\microsoft-windows-tapisetup-dl.man"
Behavior Synopsis
Migrates telephony settings, both per-user and –per-computer (as XP TAPI settings are mainly stored as computer settings, then referenced by user registry).
The Complete List and Downloadable Versions
- Understanding the USMT Config.xml Windows XP Downlevel Manifest Behaviors 1.0.docx (download)
- Understanding the USMT Config.xml Windows Vista Manifest Behaviors 1.0.docx (download)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 1: Introduction)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 2: XP Section A)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 3: XP Section B)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 4: XP Section C)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 5: XP Section D)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 6: XP Section E)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 7: XP Section F)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 8: XP Section G)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 9: XP Section H)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 10: Vista Section A)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 11: Vista Section B)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 12: Vista Section C)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 13: Vista Section D)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 14: Vista Section E)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 15: Vista Section F)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 16: Vista Section G)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 17: Vista Section H)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 18: Vista Section I)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 19: Vista Section J)
- Understanding what the USMT 4.0 CONFIG manifests migrate (Part 20: Vista Section K)
Ned “better than counting sheep” Pyle