Rebuild site servers without redistributing content over the WAN:
In order to support the Windows 10 Migration project for this customer the hierarchy needed to be upgraded to a level to support deploying/managing of windows 10v1607. The current level of the environment is 2012 R2 SP1 and we will move to CB1606 and upgrade to CB1610. During this time I took the opportunity to simplify the architecture as there were dozens of unnecessary secondary sites. These locations would have the site replaced with a single distribution point. There was no getting around these secondary sites as the pre-req check would fail due to the unsupported version of SQL server express installed on the systems. SCCM does support in place upgrade of SQL on a site server but that is limited to full SQL and not the express version. The best practice would be to spin up the new servers, configure them as Pull Distribution Points, pull the content from the old servers, and then smoothly transition between the two. In this environment, however, we were not provided with new servers to use, and we were faced with the added difficulty of prohibitively slow WAN connections, requiring us to come up with an alternative solution.
WARNING: WHEN REMOVING A SECONDARY SERVER AND YOU HAVE OTHER DPs THAT ARE ASSIGNED TO THAT SITE WILL BE REMOVED. THIS WILL OCCUR WHEN THE HIERARCHY MANANGER COMPONENT RECIEVES NOTIFICATION THAT XXX SITE IS NO LONGER PART OF THE HIEARCHY. SO KEEP THAT IN MIND WHEN DOING A SECONDARY SITE SERVER CONVERSTION. WHEN YOU LOOK IN THE CONSOLE YOU WILL EVENTUALLY SEE THE DPs HAVE BEEN REMOVED. THE ONLY WAY TO CHANGE THE SITE CODE FOR A DP IS DURING THE SETUP OF DP. WHEN THIS ROLE IS REMOVED BY HIEARCHY MANANGER BELIEVING IT IS NO LONGER PART OF SCCM IT WILL STILL RETAIN THE CONTENT LIBRARY. YOU WILL HAVE TO ADD BACK THE ROLE AND REDISTRIBUTE CONTENT WHICH THE HASH WILL STILL BE CURRENT (PENDING YOU DO CONTENT VALIDATION).
- Validated via the distmgr.log on the primary site server
- Validated by no longer being seen in distribution point configuration status in the console
1. ConfigMgr2012 Setup is started by system with command line options /deinstall / msg2parent /nouserinput
2. Information is checked, this will be things such as the following. FQDN, OS is verified, Checks for existing setup information, existing SQL information, existing configmgr installation and version number, etc.
3. removes SQL alias for sccm
4. Starts uninstallation of secondary site by first cleaning up SQl server replication data, start uninstallation of local dp (if applicable) Remove content SCCMContentLib, SMSPKG, SMSPKGF$, SMSSIG$ directories from the server. The process will also move through list of all SCCM Services and stop/uninstall them if present and then stop WMI
NOTE: After services/connections are removed you will see a number of redlines in the log file. This is only b/c connection can not be established which is expected right after stopping WMI
since we uninstalled SQL this freed up two extra drives on the machine that stored the database and the log files. These were then reclaimed by the storage team. For the entire project this allowed 1200 GB to be reclaimed. Uninstall the sccm console as it is no longer needed.
- Completely uninstall SCCM Client
- Remove the following registry HIVE “HKEY_Local_MachineSoftwareMicrosoftSMS”
- Reinstall SCCM client