I’ve run into this issue recently where software updates don’t deploy successfully to client machines in Configuration Manager but everything on the surface appears to be functioning correctly. I did some digging and found in the WUAhandler.log file there were entries like this:
OnSearchComplete – Failed to end search job. Error = 0x80244022.
Scan failed with error = 0x80244022
This repeated every handful of minutes. There are a few different issues that are tied to this but the one that impacted my situation was the WSUSPool in the IIS Application Pools. In my case the WsusPool was in a stopped state. Restarting it allowed it to run for a few minutes then fail again.
- Launch the Internet Information Services (IIS) console.
- Expand the default server, select Application Pools.
- Select WsusPool.
- Select Advanced Settings from the Actions pane.
- Scroll down to the Recycling section and select Private Memory Limit (KB).
- Change the default 1843200 to 4000000. Click Ok.
- From an elevated command prompt cycle IIS: iisreset
- Launch the Configuration Manager console and navigate to Assets and Compliance and select a sample device.
- Initiate the Software Updates Deployment Evaluation from the client.
- View the WAUhandler.log file for updated activity and confirm the error messages have stopped.
Private Memory Limit (KB)
Back in the “old days” when I was on a team supporting hundreds of servers we would occasionally encounter an issue that we just couldn’t figure out. We were lucky then to have a third level team we could call who had a direct link to Microsoft for support, no questions asked, no credit card required.
We would call them up, or fill in the form on the support website, and a triage tech would call to take some information and then a tech would call. The tech would send us a link and have us download a tool that we would run on the server. The Microsoft Product Support Report Tool would run and gather up, into one tidy package, all of the many logs and settings found on the server and wrap it up ready for delivery to the tech for analysis. We would then be provided with a temporary ftp address where we would send the package. The tech would take a look, stir with whatever magic diagnostic wands they had at their disposal, and provide us with a summary of what they had found. If the results didn’t tell us exactly what the problem was it would often give us a pointer to the direction we should be looking for a possible solution.
That’s gone now.
What you have now is something equally useful and interesting. The Microsoft Support Diagnostics portal gives you pages and pages of typical items that might require diagnosis ranging from Baseline analysis, Exchange Server, IIS diagnosis, Windows Server diagnosis and almost everything else under the Microsoft sun.
So it works like this. You browse to the portal and login with your Microsoft Live ID. Now that you’re logged in browse through the pages of options to find the diagnostics selection you need. You run through the diagnostic process and upload the results. The upload is analyzed and you get feedback that gives you an idea of what is wrong and how to go about fixing it. A handy resource.
I have a laser printer at home. It’s an HP LaserJet Professional CP1025NW. It’s a dandy colour printer. When I want to use it with my Windows 10 computers I go to the HP support webpage and download the appropriate driver and go from there. For some reason Windows wants to install the HP LaserJet Professional CP1020 series driver which must have something related to the CP1025NW driver. It never properly installed on my Windows 8.1 computers and it’s now doing the same thing with the Windows 10 computers I have. Every time new updates are released Windows 10 tries with all its might to install that CP1020 driver and every time it results in this:
What I would like to do is uncheck the requirement/option that insists on updating this particular driver. Sadly, this isn’t available to me. I can understand why that is. Microsoft is doing its best to protect people who run with scissors. Budding trapeze artists who use no safety net. I had a chat the other day with one of the smart people I work with about my printer driver dilemma and he pointed me to this support article KB3073930. There are a couple of excellent suggestions in the article but there’s also an actual work around to “make it stop” trying to install the driver.
When you download and run the wushowhide.diagcab file available on the support article page it does a quick scan of your machine and presents you with the option to Show or hide updates.
I selected Hide updates and was presented with a list of drivers including the “offending” driver.
I selected the driver and click next and the wizard begins “Resolving problems”. The wizard completes and resolves the problem. If the situation changes with that driver I can always rerun the wizard and Show hidden updates to allow Windows to update it successfully.
I’m dropping this here for future reference. It’s a lovely catchall of the many Microsoft tools for Windows deployment.
One of the consistent messages heard over the past few years, maybe more, regarding system administration and how things are done in the Microsoft world is that one must learn PowerShell. It’s how things are done and will be done into the future. I’ve never felt it to be that important or that urgent until recently. I find myself in a rut, without purpose. These are not good things. To want to go to work every day one must have purpose or one develops as dislike for the job and that’s just not good. How will I deal with this? PowerShell.
I bought a copy of Learn Windows PowerShell in a Month of Lunches written by a guy named Don Jones. I carried that book around with me for more than a month of lunches and only opened it a couple of times. Then the second edition came out. Ugh. Have I had that book for that long? Apparently so. Time to learn some PowerShell. As an extra motivator I work with a Microsoft PowerShell MVP so maybe I can put a dent in this book.