SCCM2012 DB Migration

This guide works great but it is missing one important step. Before using CM Setup to reconnect to the new DB server restart the SQL server. This way the Cert on CM server will be recreated for the new SQL server (assuming SQL is using Domain Service Account). After migration connection port in SUP config changed to the default 80, needed to change it back to 8530 (WSUS on 2012 sp1)


SCCM 2012: Access Denied while trying to download updates

Works great, remember that the computer from which you use SCCM console to create deployment need to have the SCUP cert

IT Consultant Everyday Notes

I tried to download monthly updates to my Deployment Package. The attempt failed with Access Denied for all updates. It turned out that even my account is a local admin on the SCCM server I need to add it with Full rights to the source share (both NTFS and Share permissions) where my Deployment Package is located.

As soon as I added the account implicitly and granted rights to it SCCM successfully downloaded necessary updates to the Deployment package.

View original post

SCUP 2011 + WSUS + SCCM 2012


Implementing SCUP 2011 into existing SCCM infrastructure


CM Server Windows 2012 STD:

  • SCCM 2012 SP1
  • WSUS role local
  • SCUP local

Process Overview:

  1. Add WSUS role
  2. Add Software Update Point role to CM
  3. Install SCUP 2011
  4. Configure SCUP 2011
  5. Distribute SCUP Certificates
  6. Publish Updates
  7. Add SCUP Catalogs in SUP configuration
  8. Change GPO


1.Add WSUS role

No special requirements except adding after installation of the role to group “WSUS Administrators” local administrator. If you fail to do this publishing of updates will not work

2. Add Software Update Point role

1 2 3 4 5 6 7 8 9 10 11 133. Install SCUP 2011

follow this works fine no comments needed

4. Configure SCUP 2011

follow this but remember to start SCUP console always by Run as Administrator if you fail to do that almost every configuration will not be succesfull.

5. Distribute SCUP Certificates

follow this works fine no comments needed

6. Publish Updates

follow this works fine no comments needed

7. Add SCUP Catalogs in SUP configuration

Now we have to refresh the configuration in SUP by adding new catalogs that are visible after configuring and publishing updates from SCUP


The last part is to change the GPO to not point at any WSUS (if it was configured before) and add “Allow signed content from intranet Microsoft update service location”

Now what  remains is to sync SUP with WSUS. Do not try to find published updates from SCUP in WSUS they only appear in SUP.


SCCM Logs CM side:

WSUSCtrl.log – Records details about the configuration, database connectivity, and health of the WSUS server for the site.

wsyncmgr.log – Records details about the software updates synchronization process.

SUPSetup.log – Records details about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.

WCM.log – Records details about the software update point configuration and connections to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.

SCCM Logs Client side:

WUAHandler.log -shows exactly what is updated and if the process ended with success or not


WindowsUpdate.log – system log regarding windows update located in c:\Windows