SCCM – Windows Update settings and errors

The last two weeks I was very busy deploying a specific update to several hundred servers. Besides the deployment I also spent some time answering questions about the process because some collegues didn’t understand why it took longer than expected.

Because I didn’t find the answers all in one place I decided to write this post. For myself, as a placeholder for recurring issues and for my collegues so they could understand the process a bit better.

Client Settings

When it comes to Software Update there are a few client settings that are important.

  • Computer Agent – Disable deadline randomization
    When you set this to Yes the client starts with the installation as soon as the deadline is reached.
    When you set this to No there will be a random wait time of up to two hours.
  • Computer Restart – Display notification/Display dialog box
    This specifies the restart behaviour. Your maintenance windows should be longer then those two periods combined.
  • Software Updates – Software update scan schedule
    This specifies at which interval the client checks for new updates.

More information can be found here.

Error Codes

During the deployment I experienced several errors. Some related to SCCM but others a bit more general.

  • 0x87D00692 – GPO conflict
    In some domains there were old WSUS GPO’s that conflicted with the WSUS settings that are generated by the SCCM client.
    Go to HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate and check your settings. There is a lot of information out there how you should configure your GPO’s.
  • 0x87D00669 – Unable to download content
    This could also be related to the 0x87D00692 error. Check your content distribution.
  • 0x87D0070C – Timeout
    When this error occurs the server took more then the default 10 minutes to install the update. Increase the maximum run time on the related update.
  • 0x87000070 – Not enough disk space
    This is more a general error. But when I had this error the server didn’t have enough free space on the system disk.

Upgrading to SCCM 1702

Yesterday was the day! The change request was approved so I could upgrade the site to the latest version 1702. In this post I will give you a quick walkthrough of that update.

The first step I performed was checking if all backups were ok. They were…

Updates and hotfixes are being managed from SCCM so no more searching for the latest hotfix or update. You can find them through Administration, Cloud Services, Updates and Servicing. BTW 1702 changes that location… So we’re on the 1610 version and 1702 is available. As you can see in the picture the prerequisite check was successful.

Select the update ‘Configuration Manager 1702’ and choose ‘Install Update Pack’ from the ribbon. The Updates Wizard will start…

You could select the ‘Ignore any prerequisite check’ option but I would only do that for a test environment. So click Next.

Enable the features you want to enable but for pre-release features you must give your consent up front… Click Next.

If you have a pre-production collection select the option ‘Validate in pre-production collection’ and browse to that collection. If you don’t have a pre-production collection just click Next. But be aware… The Client Installation package will be overwritten.

Accept the License Terms and Privacy Statement and click Next.

Check the summary and click Next. The update process will start.

When the wizard is done click Close. Now sit back and relax and wait for the upgrade to finish.

If you want to check the progress go to Monitoring, Updates and Servicing Status.

You could also check the file cmupdate.log on the site server.

During my upgrade I had one little issue. I had to restart both SMS_EXECUTIVE and SMS_DATABASE_NOTIFICATION_MONITOR service. For some reason they crashed which paused the upgrade process. After restarting the services the upgrade continued. If I can find the time I will investigate this issue.