Wsus not updating status report

23-Aug-2016 16:38

What’s next in my post is nothing special that most of smart admins might not been knowing about, but I thought to make a step by step guide over WSUS from the resources already available over internet.

One of the endearing and annoying features of this ubiquitous OS is the monthly patch update process. It just kind of works in the background when you're not looking. I'll install the updates on a non-critical server during the week to test them. But for the workstations it does a pretty good job - most of the time.

So I do a Remote Desktop session to the machine in question and run the process manually. I used to spend hours looking up ways to get around these errors. This process of switching from the newer method to the older one and then back again seems to fix a host of registry errors and other wastes of time.

I know something is really messed up when I get a 0x8024001D error or some other stupid hex number. At one time I liked Scott Hanselman's method of renaming the c:\windows\Software Distribution\Download to c:\windows\Software Distribution\ Click on "Disable Microsoft Update software and let me use Windows Update only" and then click on "Apply changes now." After the silly thing asks if you are sure (duh! It is simple and fast and has almost always worked for me.

However, there are times when it rears its ugly head and demands attention. It pushes them out after I approve them and then installs them late at night, usually with an automatic reboot when completed.

In our company we run WSUS - Windows Server Update Services - to keep all our Windows desktops updated. I have trained my users over the years to ALWAYS leave their computers on to accommodate the patch process, the weekly AV scans and so that I can get into their workstations any time I need to work on them in the evening. Microsoft likes WSUS because it cuts down on the number of users hitting the Windows Update site. Microsoft has been slowly moving everyone over to Microsoft Update instead of Windows Update.

One of the endearing and annoying features of this ubiquitous OS is the monthly patch update process. It just kind of works in the background when you're not looking. I'll install the updates on a non-critical server during the week to test them. But for the workstations it does a pretty good job - most of the time.

So I do a Remote Desktop session to the machine in question and run the process manually. I used to spend hours looking up ways to get around these errors. This process of switching from the newer method to the older one and then back again seems to fix a host of registry errors and other wastes of time.

I know something is really messed up when I get a 0x8024001D error or some other stupid hex number. At one time I liked Scott Hanselman's method of renaming the c:\windows\Software Distribution\Download to c:\windows\Software Distribution\ Click on "Disable Microsoft Update software and let me use Windows Update only" and then click on "Apply changes now." After the silly thing asks if you are sure (duh! It is simple and fast and has almost always worked for me.

However, there are times when it rears its ugly head and demands attention. It pushes them out after I approve them and then installs them late at night, usually with an automatic reboot when completed.

In our company we run WSUS - Windows Server Update Services - to keep all our Windows desktops updated. I have trained my users over the years to ALWAYS leave their computers on to accommodate the patch process, the weekly AV scans and so that I can get into their workstations any time I need to work on them in the evening. Microsoft likes WSUS because it cuts down on the number of users hitting the Windows Update site. Microsoft has been slowly moving everyone over to Microsoft Update instead of Windows Update.

Windows Server Update Services (WSUS) is one of the best solution for your all such worries.