Be advised though there are some things that don’t migrate as smoothly. If you have MDT-integrated Task Sequences in particular, you may hit some snags.
-Phil From: [email protected] [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Monday, March 16, 2015 1:51 PM To: [email protected] Subject: Re: [mssms] Splitting Domain and SCCM I did not know that :-) I think I will use the migration wizard. Thanks On Mon, Mar 16, 2015 at 12:29 PM, Marcum, John <[email protected]<mailto:[email protected]>> wrote: Couldn't you just use the built in migration wizard? It does 2012 to 2012 now. After that just run a script to change the package source locations. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Todd Hemsell Sent: Monday, March 16, 2015 10:42 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Splitting Domain and SCCM Our company is splitting up so I need to create a new SCCM server and copy all of the applications over to it. Also need to migrate SCEP polices and such. I am planning on using PS to export and import the applications. Was wondering what the other opinions might be? /Todd ________________________________ 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.
