Awesome, thanks! Are there any object types I should stay away from if moving between sites?
On Thu, Oct 10, 2013 at 2:52 PM, Chris Nackers <[email protected]>wrote: > I’d say they are portable, I move stuff ALL THE TIME between my lab and > client’s production systems or vice-versa… **** > > ** ** > > *Chris Nackers* > > *Microsoft MVP – Enterprise Client Management* > > Email: [email protected]**** > > *Nackers Consulting Services, LLC* > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Andrew Berges > *Sent:* Thursday, October 10, 2013 1:35 PM > *To:* SMS Mailing List > > *Subject:* Re: [mssms] Creating a replica of production in a lab**** > > ** ** > > Thanks everyone for the replies!**** > > > Yeah, I'm doing an RTM lab because we're currently at 2012 RTM. I plan to > move to SP1, test, then move to R2 at the same time and get it all out of > the way at once.**** > > I can use the existing lab we have, but for the purpose of saving time > instead of waiting for others to prep our typical lab environment and make > sure it is up-to-date, I figured I'd build one using Johan's scripts from > the ground up and just import the content, collections, deployments, task > sequences, etc if possible, which it sounds like it is.**** > > So if I take that approach (exporting and importing), is everything tied > to our primary site code or server name or anything like that? Or are the > exports truly portable (can be imported into a "clean" server with another > site code, server name, etc?**** > > Regards, > > Andrew**** > > ** ** > > On Thu, Oct 10, 2013 at 2:12 PM, Chris Nackers < > [email protected]> wrote:**** > > As for moving content export/import with 2012…. Collections packages, > etc… **** > > **** > > Plus shouldn’t you be building a SP1 lab? Or wait until next week Friday > and built a R2 lab J**** > > **** > > *Chris Nackers***** > > *Microsoft MVP – Enterprise Client Management***** > > Email: [email protected]**** > > *Nackers Consulting Services, LLC***** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Andrew Berges > *Sent:* Thursday, October 10, 2013 11:56 AM > *To:* SMS Mailing List**** > > > *Subject:* Re: [mssms] Creating a replica of production in a lab**** > > **** > > Thanks for the reply Mark.**** > > > Revisiting this, as I'm now building my lab with CM 2012 RTM currently. I > suppose I already know the answer to this, but I can't restore a backup to > my lab that was from a different server & domain correct?**** > > I'm trying to figure out how people that have both a lab and production CM > environment are transferring configurations between the two with a minimum > of effort. I'm assuming that most people are not using the same domain > name in production as they are in the lab, but perhaps I'm mistaken on that > assumption... ?**** > > Thanks Again, > > Andrew**** > > **** > > On Thu, Oct 3, 2013 at 2:06 PM, Mark Mears <[email protected]> wrote: > **** > > Restoring a site backup would be the best alternative to ensure you got > all objects replicated correctly. **** > > **** > > Thanks,**** > ------------------------------ > > * ***** > > *Mark Mears***** > > [email protected] <[email protected]%0d>**** > > Phone: (757) 945-2651**** > > **** > > [image: cid:[email protected]] <http://www.cireson.com/>**** > > **** > > [image: cid:[email protected]]<http://twitter.com/teamcireson> > Check out our System Center App Store: www.cireson.com/app-store**** > > **** > ------------------------------ > > **** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Andrew Berges > *Sent:* Thursday, October 3, 2013 12:47 PM > *To:* SMS Mailing List > *Subject:* [mssms] Creating a replica of production in a lab**** > > **** > > Hello All,**** > > With the final version of CM2012 R2 on the verge of release, I'm preparing > to add SP1 and R2 to my current CM2012 production environment.**** > > In the past moving from 2003 to 2007, I built new hardware in the lab and > restored the prod database from backup, (which was far from optimal, given > that the file structure for source locations wasn't the same, all clients > were missing, etc), then ran an in-place upgrade. Pretty much the same for > service pack testing.**** > > With 2007 to 2012, it was a non-issue for the most part as I just migrated > when possible and recreated what couldn't/wouldn't migrate.**** > > But with SP1's tendency to break things, R2 not being out the door yet, > and the previous issues with SP1 being re-released to fix issues, I'm > apprehensive about breaking my environment applying it (especially OSD with > the changes to WinPE and ADK underneath).**** > > So I'm curious: what approach do list members use for replicating their > production CM environment to a lab environment for testing service packs > etc before "pulling the trigger" in prod? Restoring a site backup? > Exporting the objects as MOF's and importing them in the lab? Just use a > "vanilla" stripped-down CM lab environment to test the SP's etc without > regard for your actual prod deployments? Something else entirely?**** > > Thanks in advance,**** > > Andrew**** > > **** > > **** > > **** > > **** > > ** ** > > ** ** > > ** ** > >
<<image001.png>>
<<image002.jpg>>
