Understanding what the USMT 4.0 CONFIG manifests migrate (Part 3: XP Section B)
Published Apr 04 2019 06:19 PM 128 Views
Microsoft

First published on TechNet on Aug 15, 2011

This part covers the following config.xml components for Windows XP:

 

--------------------------------------------------------------------------------------------------

 

<component displayname="Microsoft-Windows-RasmanService-DL" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-rasmanservice-dl/microsoft-wi...>

<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="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-networkclien...>

<component displayname="Microsoft-Windows-Printing-Spooler-Core-DL" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-core-dl/micr...>

</component>

 

<component displayname="Phone and Modem" migrate="yes" ID="hardware\phone_and_modem">

<component displayname="Microsoft-Windows-TapiSetup-DL" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-tapisetup-dl/microsoft-window...>

</component>

</component>

 

--------------------------------------------------------------------------------------------------

 

Remote Access Connection Manager


Config Entry

<component displayname="Microsoft-Windows-RasmanService-DL" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-rasmanservice-dl/microsoft-wi...>


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="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-networkclien...>


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="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-printing-spooler-core-dl/micr...>


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="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-tapisetup-dl/microsoft-window...>


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

 



Ned “better than counting sheep” Pyle

Co-Authors
Version history
Last update:
‎Dec 13 2021 04:49 PM
Updated by: