tolenmay
asked on
WSUS clients not reporting
I recently deployed new Windows 7 machines and configured them to report to a new WSUS server. Shortly after deployment, for some reason, WSUS was not showing as installed on the server - maybe another admin here removed it. In order to remedy the situation short term, I thought I should put the clients back on the original server, a Windows 2003 R2 Service pack 2 box. It has WSUS 3.0 SP1 (I think SP2 requires a 2008 server).
All I have done so far is modify the clients' reg key HKLM\SOFTWARE\Policies\Mic rosoft\Win dows\Windo wsUpdate\W uServer and HKLM\SOFTWARE\Policies\Mic rosoft\Win dows\Windo wsUpdate\W uStatusSer ver values to reflect the IP address of the Windows update server (they now just say http://10.1.1.28).
My clients now show up in the server, but show as not yet reported, as well as showing the OS as Windows 0.0.
The client utility output looks ok - and a reg query returns the following output:
HKEY_LOCAL_MACHINE\SOFTWAR E\Policies \Microsoft \Windows\W indowsUpda te
ElevateNonAdmins REG_DWORD 0x1
AcceptTrustedPublisherCert s REG_DWORD 0x1
WUServer REG_SZ http://10.1.1.28
WUStatusServer REG_SZ http://10.1.1.28
If I bring up 10.1.1.28 in a browser, I get an Under Construction page (which is correct, I believe) and if I do a http://10.1.1.28/selfupdate/wuident.cab it asks me to save the file so that's working correctly.
Will Windows 7 work with anything less than SP2 on WSUS?
Output of the client diagnostic tool is:
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://10.1.1.28
WUStatusServer = http://10.1.1.28
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Client is pointed to SUS 1.0 Server
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
All I have done so far is modify the clients' reg key HKLM\SOFTWARE\Policies\Mic
My clients now show up in the server, but show as not yet reported, as well as showing the OS as Windows 0.0.
The client utility output looks ok - and a reg query returns the following output:
HKEY_LOCAL_MACHINE\SOFTWAR
ElevateNonAdmins REG_DWORD 0x1
AcceptTrustedPublisherCert
WUServer REG_SZ http://10.1.1.28
WUStatusServer REG_SZ http://10.1.1.28
If I bring up 10.1.1.28 in a browser, I get an Under Construction page (which is correct, I believe) and if I do a http://10.1.1.28/selfupdate/wuident.cab it asks me to save the file so that's working correctly.
Will Windows 7 work with anything less than SP2 on WSUS?
Output of the client diagnostic tool is:
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://10.1.1.28
WUStatusServer = http://10.1.1.28
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Client is pointed to SUS 1.0 Server
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
ASKER
It's my understanding that you have to have 3.0 sp2 (aka 3.2) in order to support Windows 7 computers. http://support.microsoft.com/kb/972455
You are right that WSUS 3.2 is only supported on server 2008 R2 or 2008 with SP1. WSUS 3.2 release notes - http://www.microsoft.com/downloads/details.aspx?familyid=ba94a0d3-f22a-4e24-877e-6be6ce5da6d7&displaylang=en
Wish I could be of more help,
Jeff
You are right that WSUS 3.2 is only supported on server 2008 R2 or 2008 with SP1. WSUS 3.2 release notes - http://www.microsoft.com/downloads/details.aspx?familyid=ba94a0d3-f22a-4e24-877e-6be6ce5da6d7&displaylang=en
Wish I could be of more help,
Jeff
ASKER
That helps a lot Jeff! From what I can tell from the release notes, I'm going to have to install WSUS 3.0 SP2 on not only a 2008 server, but one with a 64-bit processor, is that correct? I have a 2008 R2 server on a 32-bit processor that I'd love to use, but it says IIS has to be running in 64-bit native mode. I guess that means I'll have to install it on the only 64-bit server available which is our SQL server and gets pretty heavy usage. Do you think there'd be any issues with putting WSUS there as well? How much of a resource hog is it? Our staff normally only works during the day and update check is at 3:00 am.
WSUS can be either 32-bit or 64-bit. My 2008 WSUS server is 32-bit and it updates our Windows 7 64-bit computers and 2008 32/64-bit servers no problem.
But I see where the release notes say;
If any IIS component is installed in 32-bit compatibility mode on a 64-bit platform, the WSUS 3.0 SP2 installation may fail. All IIS components should be installed in native mode on 64-bit platforms.
This only means if you do go 64bit, you have to go all the way, and not use any IIS 32-bit components.
-Jeff
But I see where the release notes say;
If any IIS component is installed in 32-bit compatibility mode on a 64-bit platform, the WSUS 3.0 SP2 installation may fail. All IIS components should be installed in native mode on 64-bit platforms.
This only means if you do go 64bit, you have to go all the way, and not use any IIS 32-bit components.
-Jeff
ASKER
The reason I'm asking all these follow-up questions (which might should be in another thread) is that when I go to install the file I downloaded from Microsoft (should I get the 32 or 64 bit one in my case?), it says I need IIS or additional IIS role services need to be installed. IIS is installed, and 25 role services:
The installed list is longer than the uninstalled list - Not installed features include:
ASP.net , .net extensibility, asp, isapi filters, server side includes, some of the security features aren't installed (such as basic, windows authentication etc... the only installed one is Request Filtering).
So, I'm not understanding what it's wanting and why it won't install.
The installed list is longer than the uninstalled list - Not installed features include:
ASP.net , .net extensibility, asp, isapi filters, server side includes, some of the security features aren't installed (such as basic, windows authentication etc... the only installed one is Request Filtering).
So, I'm not understanding what it's wanting and why it won't install.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@tolenmay - I still say 2008 is a better platform for WSUS
@dstewartjr
"Windows Server 2003 SP3 or later versions"
"Wrong!!! Did you read the release notes?"
Windows Server 2003 SP1 (NOT SP3) or later versions
http://www.microsoft.com/downloads/details.aspx?familyid=ba94a0d3-f22a-4e24-877e-6be6ce5da6d7&displaylang=en
@dstewartjr
"Windows Server 2003 SP3 or later versions"
"Wrong!!! Did you read the release notes?"
Windows Server 2003 SP1 (NOT SP3) or later versions
http://www.microsoft.com/downloads/details.aspx?familyid=ba94a0d3-f22a-4e24-877e-6be6ce5da6d7&displaylang=en
Your comment is still wrong >>> quote "You are right that WSUS 3.2 is only supported on server 2008 R2 or 2008 with SP1."
And "Windows Server 2003 SP3 or later versions" <<<Yes, I would hope that the server in question is fully patched
And "Windows Server 2003 SP3 or later versions" <<<Yes, I would hope that the server in question is fully patched
Please see attached image taken from the WSUS 3.0 SP2 release notes.
WSUS-Minimum-requirments.png
WSUS-Minimum-requirments.png
Pretty clear that it says" Windows Server 2003 SP1 or later versions"
ASKER
Thanks - I got WSUS 3.2 installed on my 2008 server (which, funny enough, turned out to be a 64-bit server after all - I didn't think it was). The discussion was really helpful, though, for me, as well as for future people who might encounter this.
tenaj-207 ???
What am I supposed to be seeing other than what I have been pointing out the whole time??
I was stating that your initial comment "....WSUS 3.2 is only supported on server 2008 R2 or 2008 with SP1" is wrong
What am I supposed to be seeing other than what I have been pointing out the whole time??
I was stating that your initial comment "....WSUS 3.2 is only supported on server 2008 R2 or 2008 with SP1" is wrong
dstewartjr
I don't know how to show you any clearer than I've already shown... It's all about the 2003 service pack. You wrote, "2003 SP3" when you should have written, "2003 SP1."
If you can't see it don't feel bad, just move on.
I don't know how to show you any clearer than I've already shown... It's all about the 2003 service pack. You wrote, "2003 SP3" when you should have written, "2003 SP1."
If you can't see it don't feel bad, just move on.
tenaj-207,
I am pretty well versed in all aspects of WSUS<<<my history here proves that.
For the third time now I wasnt commenting on the service pack.!!! I was commenting on your statement that it is only supported on 2008 R2 or 2008 with SP1 . which is untrue.
And as far as service packs go...like I said I would hope that the OP was updated to SP3 in the first place. Making "....It's all about the 2003 service pack." a moot point.
I am pretty well versed in all aspects of WSUS<<<my history here proves that.
For the third time now I wasnt commenting on the service pack.!!! I was commenting on your statement that it is only supported on 2008 R2 or 2008 with SP1 . which is untrue.
And as far as service packs go...like I said I would hope that the OP was updated to SP3 in the first place. Making "....It's all about the 2003 service pack." a moot point.
Thanks for all your hard work. Keep it up!
I was commenting on the 2003 service pack. Which you said WSUS is only supported on 2003 SP3 which is untrue, 2003 SP1 also supports it.
Yes this is a moot point.
Also thanks for your post on my article, I completely forgot I wrote that; the MS Fix it was a great addition.
I was commenting on the 2003 service pack. Which you said WSUS is only supported on 2003 SP3 which is untrue, 2003 SP1 also supports it.
Yes this is a moot point.
Also thanks for your post on my article, I completely forgot I wrote that; the MS Fix it was a great addition.
Thanks, It appears that the technet article(I posted) and the document that you download dont match in that respect(1 says SP1 and the other SP3). I only meant to point out that "Yes" you can install WSUS SP2 on Server 2003(without regard to service pack level). I like to make sure that all info is correct when it comes to WSUS.
Thanks guys, Updated to WSUS 3.2 and it fixed my problem.
ASKER
2010-08-18 10:58:57:453 936 688 PT WARNING: Cached cookie has expired or new PID is available
2010-08-18 10:58:57:453 936 688 PT Initializing simple targeting cookie, clientId = d74de380-593f-4c99-a775-47
2010-08-18 10:58:57:453 936 688 PT Server URL = http://10.1.1.28/SimpleAuthWebService/SimpleAuth.asmx
2010-08-18 10:58:57:500 936 688 PT WARNING: GetCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2010-08-18 10:58:57:500 936 688 PT WARNING: PTError: 0x80244019
2010-08-18 10:58:57:500 936 688 PT WARNING: GetCookie_WithRecovery failed : 0x80244019
2010-08-18 10:58:57:500 936 688 PT WARNING: RefreshCookie failed: 0x80244019
2010-08-18 10:58:57:500 936 688 PT WARNING: RefreshPTState failed: 0x80244019
2010-08-18 10:58:57:500 936 688 PT WARNING: PTError: 0x80244019
2010-08-18 10:58:57:500 936 688 Report WARNING: Reporter failed to upload events with hr = 80244019.