Just wanted to let you know - today is the day two updates will be available to you to assist in your management and deployment of WSUS 3.0.
First ,we are making an update available for WSUS 2.0 SP1, which will create a 3.0 "self update tree" on your WSUS 2.0 /SP1 servers. The self-update tree update contains the code for the WSUS 3.0 client. That means, once this update is approved and installed on your WSUS 2.0 SP1 server, 2.0 clients "mapped" to that server will be "self updated" to the 3.0 client the next time the client 'checks in' with the WSUS 2.0 SP1 server. The server remains WSUS 2.0 SP1, while the clients are able to update themselves from the server, to the 3.0 version. We did this to ensure customers had a distributable method to update their clients and realize new performance optimizations, but still manage the plan and timing to upgrade the servers to WSUS 3.0. This update is classified as a critical update for all server categories on which WSUS 2.0 SP1 is supported, with the exception of SBS R2.
Additionally, WSUS 3.0 will available via WSUS today, classified as an "update" and targeted at Windows 2003 SP1 for WSUS 2.0, WSUS 2.0 SP1 products. There will be 2 updates since 3.0 now natively supports x64bit. They are:
Windows Server Update Services 3.0 (KB935524)Windows Server Update Services 3.0 for x64-based Systems (KB935524)
Again, this update will be classified as an “update” targeted at Windows 2003 SP1 for WSUS 2.0 and WSUS 2.0 SP1. Also the update will be used to upgrade WSUS 3.0 RC to RTM on the Windows 2003 server.
Hope this helps and happy updating!
http://support.microsoft.com/kb/936301 - is this applicable to WSUS 2.0 (no SP1)? Do I need to manually install it on WSUS 2.0 (no SP1)? Please clarify.
I'm lost. Is this update shown here: http://support.microsoft.com/kb/936301 supposed to be applied to all workstations in our org?
The blog mentions an update for wsus server which will create the tree so clients can self update.
So are we pushing the update or are we creating the tree?
Okay. wsus is showing that only the wsus server itself needs this update (936301)
However, after running this update on the WSUS server, the client is still reporting ver. 220.127.116.1107.
If I manually run this update on the CLIENT, the version shows ver. 7.0.6000.374.
What am I missing?
I'm in the same boat as John. I installed the update described in KB936301 (WindowsUpdteAgent30-x86.exe) three days ago. I check the WUAUENG version number today on some random client and they still show 18.104.22.16807. I thought that 936301 added a 3.0 self update tree to WSUS 2.0 SP1 so my clients could go to 3.0 while my server stayed @ 2.0 SP1?
I delivered the 927891 MSI update to about 150 clients which immediately went berserk with 100% CPU issues. I thought that the combination of the 3.0 client and MSI update was supposed to solve this so I've been freaking. Turns out the clients haven't self updated yet.
What's the solution WSUS guys?
Previously, I had run the executable manually in our test environment on our wsus server. This did not work.
I just applied the update to our prod wsus server via wsus, (not manually) and now the clients are downloading the latest 3.0 client.
Should I install the update on WSUS 2.0 (NO SP1). I can't find any information on this.
症状 SVCHOST CPU 占用率过高，如果停止 Automatic Update 服务， CPU 占用率高的问题消失。 或者用下面的方法确认是否 AU 引起 SVCHOST CPU 占用率过高的问题：
Symptom SVCHOST high CPU. If stopping the Automatic Update service, the high CPU issue disappears. You
it good i have updated my wsus 2.0 to 3 .0 every , its better before the version . here i have some problems , i am facing
in wsus server its showing a pc requires some updates , but in the pc its not showing any downloaded and ready to install popup.( i have run the command like wuauclt.exe /detectnow)
this is not for a pc iam facing for more than 10 pc's.
so plz any one plz suggest.
any way like to puch the patches for a particular group of machine.
症状（ Symptom ） SVCHOST CPU 占用率过高，如果停止 Automatic Update 服务， CPU 占用率高的问题消失。 或者用下面的方法确认是否 AU 引起 SVCHOST CPU
---Quoting the article---
The self-update tree update contains the code for the WSUS 3.0 client. That means, once this update is approved and installed on your WSUS 2.0 SP1 server, 2.0 clients "mapped" to that server will be "self updated" to the 3.0 client the next time the client 'checks in' with the WSUS 2.0 SP1 server. The server remains WSUS 2.0 SP1, while the clients are able to update themselves from the server, to the 3.0 version.
Will the client automatically reboot when it receives this self-update? If so, can the update be rolled out to servers and PCs in a controlled fashion, like other updates (Detect Only, Mixed, etc)?
Can someone help identify the order in which the updates are to be done. In our WSUS I currently see the KB927891 for servers and desktops; KB936301 for the WSUS server; and of course, the WSUS update (the 3.0 upgrade) KB935524 to take the server from 2.0 to 3.0. I understand that KB935524 should be the last thing done, but I do not know the order of the first two installs to be done. I want to ensure the order is correct to prevent any potential negative impact to our systems. Thanks!
According to my update history on the 24th May, KB927891 was installed first and then KB936301 successfully. Hope this helps.
Thanks for the its much appreciated
Very interesting writeup thank you....................................