jackson321 Posted February 3, 2016 Report post Posted February 3, 2016 Hello, I'm in the planning process to upgrade a SCCM 2012 sp1 on OS 2008r2 (single site). We would like to migrate the OS from 2008r2 to 2012r2 and move SQL off box to SQL 2014. From what I've been reading I need to do a Backup and Recovery in Configuration Manager as referenced in the following links listed below. WSUS was installed on the on the same server using sql express, non of us has access to the DB and the person that originally installed it has left the company. So I'm stuck with a dilemma. Uninstall WSUS from the SCCM before performing a backup. On reinstall of SCCM go ahead an install WSUS as a new server. http://blogs.msdn.com/b/scstr/archive/2014/06/13/configmgr-2012-site-recovery-scenario-stand-alone-site-server-os-or-hardware-migration-change.aspx https://technet.microsoft.com/en-us/library/gg712697.aspx The high levels steps Backup Config Manager and package source location Backup SCCM Database Build new SQL server, reattached DB, give permissions Build new SCCM server (same hostname, IP) Copy package location to new sccm server Perform a recovery of Site Server Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 3, 2016 Report post Posted February 3, 2016 I would keep sql on the same server as SCCM, having it remote just causes problems. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted February 7, 2016 Report post Posted February 7, 2016 How so? Why keep on same server when one can have it on an SQL cluster? Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 8, 2016 Report post Posted February 8, 2016 having the database remote only opens you up to more possibilities of failure, (eg: replication), keeping it local minimizes those problems. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted February 9, 2016 Report post Posted February 9, 2016 One could say that to every product using SQL. In that case we would have every second server (or more) with its own local SQL server... Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted February 9, 2016 Report post Posted February 9, 2016 You are welcome to have a remote SQL server but as a consultant I always add 15 days to any project with remote SQL server. Remote SQL servers always give you headaches. Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted February 9, 2016 Report post Posted February 9, 2016 I think I need to become a consultant... Quote Share this post Link to post Share on other sites More sharing options...
jackson321 Posted February 17, 2016 Report post Posted February 17, 2016 This is such a small environment < 300 so I'm not worried about replication. I'm actually a DBA too and recommended to management to leave it local. There isn't much CPU, IO utilization for the instance. Fun times Quote Share this post Link to post Share on other sites More sharing options...
