I am migrating test to live and live to test but in the same domain. Sadly I 
haven't had any problems yet... makes me a bit nervous. :)

Von: [email protected] [mailto:[email protected]] Im 
Auftrag von Jason Wallace
Gesendet: Dienstag, 24. September 2013 14:24
An: [email protected]
Betreff: RE: AW: [mssms] Migrating Objects from 2012 to 2012

Fab - and thank you for your help in this from the other week.

I know that you are doing exactly what we are doing here.  Just wondering if 
you have separate domains from which you are migrating and any gotchas on that? 
 I'm guessing the respective answers are Ja and Nein :)

Now if only we had the ability to mark UAT objects as approved and keep the 
admins right out of PROD :) . . . .

________________________________
From: [email protected]
To: [email protected]
Date: Tue, 24 Sep 2013 13:36:40 +0200
Subject: AW: [mssms] Migrating Objects from 2012 to 2012
To your first point:

The following items are new for migration in Configuration Manager SP1:
*         Beginning with System Center 2012 Configuration Manager SP1, you can 
merge data from other hierarchies that run the same version of Configuration 
Manager as your hierarchy. This includes migrating data from a test environment 
into your production environment.

Not just supported but as of SP1, recommended, I would say.

Von: [email protected] [mailto:[email protected]] Im 
Auftrag von Jason Wallace
Gesendet: Dienstag, 24. September 2013 13:14
An: [email protected]
Betreff: [mssms] Migrating Objects from 2012 to 2012

Hello folks

I am writing a process document on migrating objects from Test to UAT and UAT 
to PROD in SCCM 2012 SP1.  I am planning to use the migration tool included in 
2012 as this appears to work & some very kind folks on here have confirmed that 
it does.  My testing also shows that this is the case.

So, Diolch, Danke, Merci and Thanks so far.  Just a couple of questions which I 
have so far though:

1. Support.  As is often the case we need to provide a solution that is 
"supported" by Microsoft.  Yes, I know that Microsoft would never not support a 
Premier customer etc. and can justify the use of the tool but I know that I 
shall be asked why the tool is a 2007 to 2012 tool and whether the use in 2012 
to 2012 is supported.  Has anyone managed to get a support statement on this 
please?

2. Other Objects.  A couple of things won't be migrated - the SUP categories 
etc.  Is there a kind soul who would be prepared to share an extract / import 
pair of scripts for this please?

Thanks very much
Jason






Reply via email to