Hi all I'm hoping to find some more info about this here, there doesn't seem to be much about this specifically, and I've already opened a case with MS, but there's a lot of knowledge here so, here goes.
On Monday, I upgraded from Windows Server 2088 R2, SQL Server 2008 R2, SCCM 2012 SP1 CU3 to Windows Server 2012 R2, SQL 2012 SP1, and SCCM 2012 R2 CU1. That whole process looked like this and was successful in both dev last week and prod on Monday: 1. Stop all Configuration Manager services at the site. 2. Upgrade SQL Server to SQL 2012 SP1. 3. Restart the Configuration Manager services. 4. Take CM Backup 5. Take SQL Backup. 6. back up SSRS encryption keys. 7. Reinstall Windows 2012 R2 on C partition using WDS 8. Install any patches required since last reference image. 9. Install SQL 2012 SP1 10. Install Prerequisites 11. Enroll for SCCM certificates and add them to IIS 12. Install SCCM 2012 SP1 CU3 choosing to site restore from back ups in steps 4 and 5. 13. install CU3 14. Upgrade to SCCM 2012 R2 15. install CU1 16. Clean up any lingering component issues in SCCM Trouble I've come across, only in production, of course, is that SUP syncs between SCCM and WSUS immediately crash the apppool for wsus and effectively disables wsus. Console doesn't open, application log on the server shows errors and all of the webservices under the WSUS Administration site in IIS are stopped. I was able to sync about 4000 updates successfully, all of the OS updates for XP, Vista, 7, 8, 8.1, 2003, 2008, 2008 R2, 2012, 2012 R2. I added Office to the Products list in the SUP config and another sync started. During the last bit of the sync last night something caused the wsus app pool to crash and stopped the sync. "Failed to sync update <GUID> 503 service unavailable" in wsyncmgr.log. I can get back into the wsus console if I start the pool, but as soon as I try to do anything with syncing in SCCM the app pool for wsus crashes. I don't much know where else to look for a cause, it feels very low level and bugish to me. Do any of you have any ideas? I'm waiting for a call back from MS as I type this. Todd
