Completely decommission SCCM and associated DB, etc.

Question

Hi all,
Just joined a company, and we have a SCCM 2012 RTM server which I'm sure they installed and managed learning as they went, and not following best practices, etc. It has a lot of what I believe is redundant data, reporting is broken, I can't locate the PXE logs
anywhere, and a few other things. Talking to my Infrastructure manager we believe it may take less time decommissioning it and starting from scratch, one piece at a time (first making sure it can deploy windows updates, then OSD, then software distribution,
etc.), instead of trying to fix it (handover documentation is not also that good).
I'm quite of a SCCM newbie, although I had some exposure in the past to SCCM 2007. We basically have a SCCM server using an external SQL server. SCCM is integrated with AD. There is a number of SCCM clients deployed in our network.
Like I said, what we would like is to make it like we ever had SCCM installed and start from scratch. Can you share links that might be useful, advice, etc? I will start with these:
http://anoopcnair.com/2012/08/09/sccm-configmgr-2012-uninstall-cas-primary-secondary-server/
http://technet.microsoft.com/en-us/library/gg712320.aspx#BKMK_DecommissionSites
I guess the workflow should be something like this, but I'm sure I'm missing steps in between.
Uninstall the primary site using Configuration Manager Setup
Remove DBs
Decommission server (format it, or whatever)
Deal with the computers with the client already installed
Install WSUS, SCCM, DBs, etc.
Point out computers to the new WSUS
Some extra questions:
- Can we reuse the old site name?
- What about the computers with the SCCM client installed? Is best practice to uninstall it (maybe via AD GPO?)? Can we just reconfigure them? What if it's possible to reuse the site name?
Thanks a lot.

Answer 1

Remember to also clean the System Management container under System in Active Directory. Regarding the clients, I'd not bother you could use any of the installations method to just reinstall it, or re-assign it with a script. Also, I'd consider coming up
with a good naming standard for the new site codes, as I assume that the previous setup may not have had the best names (CAS, PRI, SEC etc may not always be a good thing).
Once you've installed the OS, have a look at my ConfigMgr 2012 R2 prerequisites installation tool:
Some other notes:
- Consider installing ConfigMgr 2012 R2 and SQL on the same machine, depending on the number of clients.
- When you install a new environment, always go for the latest and greatest (CM CU's, SQL SP's and CU's).
Other than that, if you havn't yet seen Nial's excellent guides. I strongly urge you to check them out.
Regards,
Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja
 Thanks Nickola. Why do you suggest installing SQL server in the same machine instead of using a dedicated SQL Server? I could think of making sure that high usage on that server doesn't impact SCCM, but I don't know if you mean something as simple
as that. My environment is currently 70 clients, but it may grow in the future.