Answered by:
SCCM 2012 Environment move

Question
-
Hi,
We have a SCCM2012 environment which is being moved to a new data center, does anyone have any opinions on shutdown/start up procedures (from shutting down the servers, moving and starting back up), see below environments:
1 x Primary Site Server - AppCatalog, Asset Intelligence, Component, Distribution Point, Management Point, Site Server and System.
1 x SQL Failover cluster (with 2 nodes) - Component, Site Database, Reporting
2 x SUP - Component, SUP
6 x Distribution points (at various sites) - Distribution Point
We are currently designing a plan for the move, so any opinions would be great.
Thanks
Thursday, March 14, 2013 2:59 PM
Answers
-
It really shouldn't matter at all. For my OCD I'd start up SQL first, the primary second then the DP's but CM is pretty good at self healing in such a situation.
John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/
- Proposed as answer by Jason Sandys [MSFT]MVP Thursday, March 14, 2013 6:15 PM
- Marked as answer by Jörgen NilssonMVP Tuesday, May 28, 2013 9:57 PM
Thursday, March 14, 2013 5:12 PM -
Yep, nothing special whatsoever but as John mentioned, since ConfigMgr relies on SQL Server, it should be last down, first up.
Unless you are changing the server -- which you actually can't do unless you want to break ConfigMgr -- there's nothing else to worry about except making sure the DNS records get updated for the IP addresses (assuming those are changing).
Jason | http://blog.configmgrftw.com
- Marked as answer by Jörgen NilssonMVP Tuesday, May 28, 2013 9:57 PM
Thursday, March 14, 2013 6:21 PM
All replies
-
It really shouldn't matter at all. For my OCD I'd start up SQL first, the primary second then the DP's but CM is pretty good at self healing in such a situation.
John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/
- Proposed as answer by Jason Sandys [MSFT]MVP Thursday, March 14, 2013 6:15 PM
- Marked as answer by Jörgen NilssonMVP Tuesday, May 28, 2013 9:57 PM
Thursday, March 14, 2013 5:12 PM -
Yep, nothing special whatsoever but as John mentioned, since ConfigMgr relies on SQL Server, it should be last down, first up.
Unless you are changing the server -- which you actually can't do unless you want to break ConfigMgr -- there's nothing else to worry about except making sure the DNS records get updated for the IP addresses (assuming those are changing).
Jason | http://blog.configmgrftw.com
- Marked as answer by Jörgen NilssonMVP Tuesday, May 28, 2013 9:57 PM
Thursday, March 14, 2013 6:21 PM