OK (you said "(LOCAL)" so I didn't get that.

My question is why? How does it improve the process at all? To me, it would 
make things much more difficult to maintain and troubleshoot and be confusing 
for those running the TSes also.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Avery, James
Sent: Tuesday, September 24, 2013 1:05 PM
To: [email protected]
Subject: [mssms] RE: USMT - Side by Side Migration Question

I'm not thinking of a system refresh, but a side-by-side. Where I have computer 
A and computer B.

Computer A is the source
Computer B is the Destination


I send the TS to computer B for both capture and restore. But, the capture will 
see hopefully read the computer association and capture Computer A, then 
continue the TS and restore to Computer B.




From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Tuesday, September 24, 2013 12:27 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: USMT - Side by Side Migration Question

The default TSes already do this.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Avery, James
Sent: Tuesday, September 24, 2013 11:54 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] USMT - Side by Side Migration Question


Guys, I'm researching a way for a single Task Sequence to do both the Capture 
of a source computer and the Restore to the Destination (LOCAL) computer the TS 
is running from.

My thoughts are to run PSEXEC with the USMT command line...but I would like to 
have the user state stored at the SMP.

So it would look something like this.


1.       I create Computer Association for Source and Destination computer in 
SCCM

2.       TS is sent to Destination computer

3.       TS is started on Destination computer

4.       TS -

a.       Capture User State on Source (How to make this happen?)

                                                               i.      Request 
State Store

                                                             ii.      Set 
OSDMigrateAdditionalCapture

                                                            iii.      Capture 
User State

                                                           iv.      Release 
State Store

b.      Restore User State on Destination

                                                               i.      Request 
State Store

                                                             ii.      Set 
OSDMigrateAdditionalCapture

                                                            iii.      Restore 
User State

                                                           iv.      Release 
State Store



________________________________
This e-mail is intended solely for the person or entity to which it is 
addressed and may contain confidential and/or privileged information. Any 
review, dissemination, copying, printing or other use of this e-mail by persons 
or entities other than the addressee is prohibited. If you have received this 
e-mail in error, please contact the sender immediately and delete the material 
from any computer. To unsubscribe send an email to: 
[email protected]<mailto:[email protected]> 
Hitachi Consulting Corporation, 14643 Dallas Parkway, Suite 800, Dallas, Texas 
75254 (HCAD0411)
________________________________






Reply via email to