10. If the memory is not reduced : Restart the WSUS Administration Website

11. If the memory is not reduced : Restart the World Wide Web Publishing Service

Monitor, but eventually after a few days you should not see the “new normal” for the RAM required for the application pool to run

Then after a week reduce the memory to the new normal

]]>http://britv8.com/sccm-fixing-sup-memory-issues/feed/0SCCM – KB4457144 not installing Error 0x80070017 0x80240022[Solved]http://britv8.com/sccm-kb4457144-not-installing-error-0x80070017-0x80240022solved/
http://britv8.com/sccm-kb4457144-not-installing-error-0x80070017-0x80240022solved/#respondFri, 16 Nov 2018 09:29:25 +0000http://britv8.com/?p=935Continue reading...]]>Another weird one – KB4457144 was deployed to a collection of computers. On those that said it was still required, if you forced Software updates evaluation, it would error in the event log with

Package KB4457144 failed to be changed to the Installed state. Status: 0x80070017

]]>http://britv8.com/sccm-kb4457144-not-installing-error-0x80070017-0x80240022solved/feed/0SCCM – KB3114874 not installing [Solved]http://britv8.com/sccm-kb3114874-not-installing-solved/
http://britv8.com/sccm-kb3114874-not-installing-solved/#respondTue, 13 Nov 2018 10:36:04 +0000http://britv8.com/?p=925Continue reading...]]>A weird one – KB3114874 was deployed to a collection of computers. On those that said it was still required, if you forced Software updates evaluation, it would not show in the windows update log as being installed, or failing to install. Nothing, nada, zip! If you check what updates were installed , it was not listed. If I used my Get-UpdatesAvailableOnServer.ps1 script , it showed me what SCCM thought there was still outstanding.

Application updates are listed in the Application log under MSIInstaller provider

OS updates are via the setup event log

SCCM Client info can also be in the Configuration Manager Agent Provider

Check Windows Update Log

If you are seeing a history of errors there, then I run the WUSledgehammer over it.
This resets the windows Update Agent and resets the local group policy file.
A few manual runs of the Software Update actions on the SCCM Client , 15 minutes apart and a full cycle should be completed successfully.
If you are seeing installations fail in he log or other errors then we have two other places to look

Check the SCCM Client logs

Yeah/nah that will take forever , you seen how many there are!
Easiest thing to do is to hit it with my other sledgehammer the SCCM one.
Biggest issue with pushing a re-install from the SCCM console and forcing an uninstall first, is that not everything is cleaned up
With this one you need to look at the script closely. I am currently limited to psexec, which does not work for Windows 10.
The basic principles of the script are:

Uninstall SCCM Client.

Delete all 3 directories

Install SCCM Client

Component Based Servicing Health

OK this is a big one as this is the service that actually does the heavy lifting and what windows update calls to do the actual patch installation

If you are using Windows Update/WSUS/SCCM, the latest SSU will be offered to you automatically.

To get the stand-alone package for the latest SSU, go to the Microsoft Update Catalog.

This is a re-release servicing stack same KB , but its classification has changed

In October , Microsoft re-classified and re-released the servicing stack update (SSU) of each OS build.

What this means is they have superseded the existing KB binaries and updated the classification of the patch.

Some people were only applying Security patches and not applying Critical patches

Up to September 2018 the SSU was classified as a Critical patch.

Unfortunately a number of Security patches rely on the SSU being up to date, so patches were failing

Consequently, future SSU releases, from October 2018 onward, will get marked “security” not “Critical”

As an example you should now see in WUS and SCCM consoles multiple KB3177467 updates, but you will see all the updates marked Critical Updates have been superseded and new updates are now classified as “Security Updates”

ADK
ADK version 1809 releasedhttps://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
Note: Starting with Windows 10, version 1809, Windows Preinstallation Environment (PE) is released separately from the Assessment and Deployment Kit (ADK). To add Windows PE to your ADK installation, download the Windows PE Addon and run the included installer after installing the ADK. This change enables post-RTM updates to tools in the ADK. After you run the installer, the WinPE files will be in the same location as they were in previous ADK installs.

IMPORTANT: Starting with Windows 10 October 2018 Update, RSAT is included as a set of “Features on Demand” in Windows 10 itself. See “Install Instructions” below for details, and “Additional Information” for recommendations and notes. RSAT lets IT admins manage Windows Server roles and features from a Windows 10 PC

]]>http://britv8.com/security-pass-the-hash-mimikatz-and-credential-guard/feed/0Powershell – SCCM Client Sledgehammer aka Reset-CMClienthttp://britv8.com/powershell-sccm-client-sledgehammer-aka-reset-cmclient/
http://britv8.com/powershell-sccm-client-sledgehammer-aka-reset-cmclient/#respondFri, 27 Jul 2018 03:58:39 +0000http://britv8.com/?p=862Continue reading...]]>The following code forces a reset/repair of the SCCM Client on a device. It is very basic, but it succeeds where Install-CMClient fails even if you force the uninstall before installing

A few prerequisites:

PSExec from https://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Assumption that you are running a session that has the ability to PSEXEC to the remote Device AND is already setup to run the SCCMCmdlets

I have commented out the Install Client section , just because, for me it was easier to go into the SCCM Console and push the client when testing and additionally I have two sets of credentials, one for SCCM and one for Device Access.