John,

You are never going to get to that level on *everything* that is migrated.

Your best bet will probably be to catalog the most important things to your 
users.  I worked with our desktop support teams to find out what was critical 
and what sort of things they had to manually do any time a user’s machine was 
rebuilt.  Then I made sure that USMT would migrate those things if possible.  
As they brought more, “Could USMT do this?” I would work to make sure that was 
included.

But to get to this kind of detail on all that USMT will and will not migrate 
would take forever.

Mike


From: [email protected] [mailto:[email protected]] On 
Behalf Of Marcum, John
Sent: Monday, August 25, 2014 11:47 AM
To: [email protected]
Subject: RE: [MDT-OSD] What does USMT migrate

Perfect example. The CIO was migrated to a new machine and USMT was not used. 
He just asked if we had used USMT would this checkbox have migrated because he 
had to manually go back and check it. AFAIK there's nothing documented to that 
level of detail. He'd like to know EVERYTHING that would migrate, not the 
registry keys but the settings inside the UI.


[cid:[email protected]]

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Monday, August 25, 2014 7:48 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [MDT-OSD] What does USMT migrate

I have to provide documentation on exactly what will and will not migrate. I'm 
not concerned that it won't get what I need, the bigger concern is that it will 
bring over garbage. Hence my using only migapp.xml and further reducing that 
subset by using a config.xml.

The config.xml is very vague. That's why I was asking what does it REALLY do. 
So I assume adding "Microsoft Office 2007" migrate="yes" in my config.xml will 
migrate anything Office 2007 related that is also in the migapp.xml? Maybe if I 
ONLY want Office settings I should just create myself a custom xml that has 
ONLY office settings in it?

Another thing is that I know one of the out of the box xml files migrates any 
folder on the root of C that was not put there by Windows. I can't remember 
which XML that is and I do not see that documented anywhere. I need to make 
sure that isn't going to happen.


Last thing that concerns me is that when I open migapp.xml in Notepad++ there 
are several sections that just don't look right as if maybe there's a typo in 
them. Is that the case? I have not edited the file at all. Here's an example of 
what I am talking about:

[cid:[email protected]]


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Niall Brady
Sent: Friday, August 22, 2014 2:59 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [MDT-OSD] What does USMT migrate

i'd say rather than get worried about what the docs say, do some thorough tests 
to see what your XML files have been setup to migrate and verify that they 
migrate the data you care about (or not)

that's the way I approached it, and in the process of doing so found flaws in 
the documentation for how usmt works on technet,

example: http://technet.microsoft.com/en-us/library/cc749023(v=ws.10).aspx

what is your main concern with USMT ? that your xml file won't migrate what you 
need ?

On Fri, Aug 22, 2014 at 9:43 PM, Marcum, John 
<[email protected]<mailto:[email protected]>> wrote:
There's an article here 
http://technet.microsoft.com/en-us/library/hh825238.aspx that describes what is 
migrated using the default manifests. However it doesn't go into detail about 
which settings are contained in which xml file. Is that documented anywhere?

Even more detailed, is it documented EXACTLY what individual lines in a 
config.xml migrate?

I need to know EXACTLY what this gets for instance.

<component displayname="Microsoft Office 2007" migrate="yes" 
ID="http://www.microsoft.com/migration/1.0/migxmlext/migapp/microsoft office 
2007/container">


or this:

<component displayname="Microsoft-Windows-themecpl" migrate="yes" 
ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-themecpl/microsoft-windows-themecpl/settings"/>

Or what happens if I set this to true and someone has pinned an shortcut to an 
app that's not installed on the target system?

<component displayname="Taskbar and Start Menu" migrate="no" 
ID="appearance_and_display\taskbar_and_start_menu">





________________________________
        John Marcum
            MCITP, MCTS, MCSA
              Desktop Architect
   Bradley Arant Boult Cummings LLP
________________________________
      [H_Logo]


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.
________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues 

Reply via email to