Oh cool. Thanks. From: [email protected] [mailto:[email protected]] On Behalf Of Jimmy Martin Sent: Thursday, August 21, 2014 10:19 AM To: [email protected] Subject: RE: [MDT-OSD] Manual USMT
On scanstate, I will grab everything On loadstate, I usually will do something like /ue:* /ui:domain\* U don’t need the \ in it, the \ will make it only deal with domain stuff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Thursday, August 21, 2014 10:07 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Manual USMT Not following you… I am using ue*\*. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jimmy Martin Sent: Wednesday, August 20, 2014 7:18 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Manual USMT I believe you need to ue entries, ue:* and ue*\* Sent from my Windows Phone Jimmy Martin (901) 227-8209 ________________________________ From: Marcum, John Sent: 8/20/2014 16:17 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Manual USMT Thanks for the replies guys. I have a follow-up question. I am getting an error that says "unable to create local account because /lac was not specified" When I read my log it tells me that loadstate is trying to create a local account that was on the old machine. However I ONLY want to migrate a given user which I am specifying in both scanstate and loadstate. Why is loadstate trying to create the local user when I have explicitly told it not to? See attached log. I am using scanstate \\server\share\migration\mystore<file:///\\server\share\migration\mystore> /ue:*\* /ui:contoso\testuser1 /i:migapps.xml and Loadstate \\server\share\migration\mystore<file:///\\server\share\migration\mystore> /ue:*\* /ui:contoso\testuser1 /i:migapps.xml From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Wednesday, August 20, 2014 3:01 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Manual USMT 1. if the boot wim is x86 then use x86 scanstate if you are doing offline/hardlinking, if in windows, then use the x64 exe. 2. you could prompt for a username in a frontend hta like this one<http://www.windows-noob.com/forums/index.php?/topic/7294-the-cm12-bitlocker-frontend-hta> (the one I demo'd to you in Seattle) and use that variable elsewhere to migrate one username using TargetUser as a variable, you could try scanstate \\server\share\migration\mystore<file:///\\server\share\migration\mystore> /ue:*\* /ui:contoso\%targetuser% /i:migdocs.xml /i:migapp.xml /o On Wed, Aug 20, 2014 at 9:50 PM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: Two quick questions… 1. When manually migrating data from Win 7 x86 to Win 7 x64 would I use the x86 scanstate.exe and x74 loadstate.exe or both x86? (I only intend to migrate app settings) 2. In I build a batch file that contains the loadstate and scanstate commands and I only want to migrate a single given user can I use a variable in the command line and prompt for the user name? Like /ui: DomainName\%user%? ________________________________ 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. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... ________________________________ 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. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... ________________________________ 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.
