Just to piggy-back on this. What if the previous Systems Administrator named the server something stupid. How would one then migrate to a new Server with a new naming convention?
On Wed, Mar 29, 2017 at 8:41 PM, Jason Sandys <ja...@sandys.us> wrote: > I’ve never had an issue with it rebuilding – it’s a lot faster to simply > copy the content library over though which is another reason to keep the > old server online though (with a new name and services shutdown). As a note > here, you need to **update** all of your content; redistributing it is not > sufficient as that has nothing to do with the content library. > > > > J > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Andrew Sanders > *Sent:* Wednesday, March 29, 2017 9:53 AM > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] Recommended process for moving SCCM CB to new > server? > > > > Jason- > > > > If I may ask, what do you do about the SCCMContentLib directory that is on > the primary site server? I tried this migration a few weeks ago and did not > move that directory. I found documentation/blog posts online that said you > didn't have to move it, and that you could redistribute all of your content > and it would rebuild. I tried that, and it did not rebuild. The system > could not refresh content that was already in ConfigMgr. I used the content > library explorer tool to look in the content library on my DP's, and almost > all of the content was marked as invalid. I ended up punting and going back > to my old primary site server. > > > > On Tue, Mar 28, 2017 at 5:16 PM, Jason Sandys <ja...@sandys.us> wrote: > > IMO, yes. > > > > Except, I don’t typically shut down the old, server, I shutdown the SQL > and ConfigMgr services and rename it so then when (not if) I need something > off of it, it’s still on the network. > > > > J > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Steve Whitcher > *Sent:* Tuesday, March 28, 2017 2:29 PM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] Recommended process for moving SCCM CB to new server? > > > > It looks like I need to make some changes in order to install CB v1702. > Both the SQL server version and the OS version it's running on are no > longer supported. > > > > The primary site server is also getting low on disk space, and could stand > to be upgraded to server 2016, so I'm thinking that this might be a good > time to build up a new server and migrate SCCM over to it. For 2012R2, I > understand that the process boiled down to: > > > > Backup the Site DB > > Shut down the server > > Build a new server using the same IP, hostname, etc > > Install the same version of SCCM > > Recover the DB to the new server > > > > Is that still the way to go? > > > > Rather than upgrading the current SQL server, I'd like to install SQL on > the primary site server and use that for the configmgr db instead. Does > that need to be done separately? As in, first move the site server as > above, then after SCCM is functional on the new server install SQL and move > the db? > > > > Anything else I need to watch out for? > > > > Thanks! > > Steve > > > > > > > > > > -- > > *Andrew Sanders* | *IT Manager, Client Computing **Architecture* > > Systems & Networks | Information Technology Services | The University of > North Carolina at Greensboro > > (336) 334-5028 (p) | (336) 334-5932 (f) > > 107A McNutt Center | 1400 Spring Garden Street | Greensboro, NC | 27403 > > apsan...@uncg.edu | http://its.uncg.edu > > Microsoft Certified IT Professional | Microsoft Certified Technical > Specialist > > > > > >
