Thursday, August 27, 2009

SBS 2008 UR3 and the WSUS 3.0 SP2 Update

As I reported earlier, Windows Small Business Server Update Rollup 3 was making its way to a WU/MU/WSUS near you. Well, it has finally arrived and so far, seems to work.

I can't, unfortunately, say the same about the WSUS 3.0 SP2 release that was also recently released. I chose to install it via WU/MU and it got to the point where it successfully removed the previous version then died complaining that it didn't have adequate rights to install WSUS 3.0 SP2 on the server. of course, it was running as an Administrator. But don't let that get in the way of a good bug! :)

I'd strongly suggest that until a few of us have done further testing, you steer clear of this update for non-test environments.


The Ouspoken Wookie


ThePrutser said...

Firstly the SP2 update also broke down the WSUS 3.0 installation completely on my SBS 2008 server: Updates were no longer downloaded, SBS console could not retrieve any information (generated errors) and the event log showed some Update errors especially
HRESULT: 0x80244019. I fixed this using and the following "Extra's"

* Uninstall WSUS 3.0 SP2, and remove everything. You can leave the WSUS dir in place, as it will give an "in use error" when you try to delete it.

* Install WSUS 3.0. SP2 using the settings/parameters provided from step 4. in the section "To manually recover Windows Server Update Services" in the guide above.

NOTE1: you'll notice that you can skip a lot of steps, or use them to check the settings currently/already applied.

NOTE2: It will perform a new synchronisation, meaning it will download all needed updates again.

Hilton Travis said...

Thanks for the info - I've performed a few WSUS 3.0 SP2 updates in a test environment here and they have worked - I don't have a test Migration SBS here right now, however I have a funny feeling (and not one of those good funny feelings) that this is another remnant of the Microsoft SBS Migration method.

I've also installed WSUS 3.0 SP2 here on a client server that I'm in the process of building and had no issues whatsoever. is definitely a good article to keep in your "So, an update broke my SBS 2008" list as it contains the entire process needed to remove and reinstall WSUS 3.0 if it becomes non-functional (due to a Microsoft Update or some other failure).

Anonymous said...

Hi There

Well I find myself in a similar state – yet worse. I too received an error message after aplying the WSUS 3.0 SP2 patch, however instead of being able to reboot, my SBS server is in an endless loop.

Upon Rebooting, after an unusually long time ‘Applying Computer Settings’ an error message is displayed saying “Updates were not configured correctly. Reverting changes. Do not turn off your computer.”

I am not able to get to a logon screen, in order to do any kind of further troubleshooting.

Safe Mode, and Last known good yeild the same results – before being presented with a logon screen – the system falls back to attempting to ‘revert changes’ but it is abviously failing.

Furthermore, when I boot to the SBS Disk 1, and choose the ‘Repair my Computer’ option, the “Restore from Backup” does not see my WD MyBook, that I have been using for backups.

So for options, I have been thinking about [1]System Restore, or [2]Disabling a service form startup, or [3]somehow clearing the state of the failed updates. Not much on google for this error on SBS.

So, [1]Is there a way that I can do a system restore from the command line?
[2]If I was thinking that disabling WSUS from starting may also allow me to boot into SBS and troublehsoot from there. How do you disable a service from starting, from the Repair environment’s command prompt?
[3]Lastly, I was wondering if there is a way to ‘clear’ the error state that seems to be triggering this looping ‘reverting changes’ error.

Any help is appreciated.


Hilton Travis said...

G'day Ed,

Since an update caused the issue, call Microsoft PSS and let them know that this is a) Business Critical/Business Down and b) that this issue was caused by an update being applied and you will be able to receive PSS support at no charge.

They broke it - let them walk you through fixing it.

Then report back in here what the ultimate fix was for others to learn from. :)