That’s because “moving” usually implies transitioning to a server with a different name, which is not supported. What you essentially need to do is stage a disaster so you can recover to a different server that has the same name and domain membership ;)
-Phil From: [email protected] [mailto:[email protected]] On Behalf Of David Jones Sent: Tuesday, April 14, 2015 3:39 PM To: [email protected] Subject: Re: [mssms] Re: Moving Site to New Server Wow. I didn't even know that existed. I guess it didn't show up in my google searches because I wasn't using recovery or disaster. I was just googling 'SCCM 2012 move site server' Dave On Tue, Apr 14, 2015 at 3:23 PM, Russ Rimmerman <[email protected]<mailto:[email protected]>> wrote: This should be helpful in covering your bases http://www.microsoft.com/en-us/download/details.aspx?id=44295 From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David Jones Sent: Tuesday, April 14, 2015 8:11 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Re: Moving Site to New Server Duh. I forgot to mention that this is SCCM 2012 R2 CU4. On Tue, Apr 14, 2015 at 9:09 AM, David Jones <[email protected]<mailto:[email protected]>> wrote: We have a CAS and 2 Site Servers. I need to move one of the Site Servers to a new server. I am researching this but thought I would ask here and see what advice I could get. The new server has 5x the processor cores and 33% more RAM. We are running at 100% CPU most of the day now with the old server. The server I am moving it to is currently an MP/DP for the site server I am moving. I am hoping that having the CAS is not going to throw a wrench into things. Dave
