SmallPrint
asked on
Adding clients Computers to WSUS 3.0
I have configured WSUS 3.0 SP2 on my 2003 R2 server. I am able to open the console on the server. I am still testing WSUS, and only downloaded and approved Win7 SP1.
I do not want to modify our global GPO yet, so I only locally modified the policy on my desktop. I enabled Specify Intranet Microsoft update Service Location, and I set it to http://servername:8530 (i installed on post 8530).
After enabling this setting, and running wuauclt.exe /detectnow on my desktop, I still see 0 computers in the WSUS admin console.
Am i doing something wrong?!
I do not want to modify our global GPO yet, so I only locally modified the policy on my desktop. I enabled Specify Intranet Microsoft update Service Location, and I set it to http://servername:8530 (i installed on post 8530).
After enabling this setting, and running wuauclt.exe /detectnow on my desktop, I still see 0 computers in the WSUS admin console.
Am i doing something wrong?!
ASKER
ASKER
permission wise, everything looks fine.
Can this be related to WSUS being installed on a DC? I have read nothing that states this can't be installed on a DC, but maybe you have heard different.
Can this be related to WSUS being installed on a DC? I have read nothing that states this can't be installed on a DC, but maybe you have heard different.
People install WSUS on DC's all the time, it's just not recommended/preferred.
Are you sure that you have "anonymous access" enabled where appropriate as described in the article ?
Are you sure that you have "anonymous access" enabled where appropriate as described in the article ?
ASKER
Just double checked all IIS settings. They all have anonymous access enabled.
I want to confirm, I should be looking only at the WSUS Administration site, not the default, correct?
"WSUSAdmin" entry does not exist.
I want to confirm, I should be looking only at the WSUS Administration site, not the default, correct?
"WSUSAdmin" entry does not exist.
NO! You should be looking at the "Default" and it should also be started
ASKER
from my WindowsUpdate.log.
WARNING: SendRequest failed with hr = 800710dd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://fpsvrsko01:8530/selfupdate/wuident.cab>. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x800710dd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x800710dd
WARNING: SendRequest failed with hr = 800710dd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://fpsvrsko01:8530/selfupdate/wuident.cab>. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x800710dd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x800710dd
WARNING: SendRequest failed with hr = 800710dd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://fpsvrsko01:8530/selfupdate/wuident.cab>. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x800710dd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x800710dd
WARNING: SendRequest failed with hr = 800710dd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://fpsvrsko01:8530/selfupdate/wuident.cab>. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x800710dd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x800710dd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x800710dd
WARNING: DownloadFileInternal failed for http://fpsvrsko01:8530/selfupdate/wuident.cab: error 0x800710dd
WARNING: SelfUpdate check failed to download package information, error = 0x800710DD
13c4 Setup FATAL: SelfUpdate check failed, err = 0x800710DDASKER
i thought that it should be started yesterday, but when i try to start it i get error: The process cannot access the file because it is being used by another process.
just tried to start again..same error.
just tried to start again..same error.
Even though you setup WSUS to use port 8530, WSUS still needs to use a selfupdate virtual directory under port 80 as you see under "Default" <<<so the permissions need to be correct there as well
ASKER
looking into this now...this should be fun. I'll report back once i get this thing going.
ASKER
i assume I should only be looking at port 80? Net state gave me the following about 80...
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1452
TCP 192.168.67.229:80 192.168.67.229:2674 TIME_WAIT 0
There is no listenonly port reg key listed.
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1452
TCP 192.168.67.229:80 192.168.67.229:2674 TIME_WAIT 0
There is no listenonly port reg key listed.
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING 2736
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1452
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 748
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING 748
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:705 0.0.0.0:0 LISTENING 3800
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:1031 0.0.0.0:0 LISTENING 1348
TCP 0.0.0.0:1041 0.0.0.0:0 LISTENING 2912
TCP 0.0.0.0:1042 0.0.0.0:0 LISTENING 2912
TCP 0.0.0.0:1049 0.0.0.0:0 LISTENING 2912
TCP 0.0.0.0:1097 0.0.0.0:0 LISTENING 3560
TCP 0.0.0.0:1154 0.0.0.0:0 LISTENING 2736
TCP 0.0.0.0:1311 0.0.0.0:0 LISTENING 3896
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING 444
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 5424
TCP 0.0.0.0:5049 0.0.0.0:0 LISTENING 1508
TCP 0.0.0.0:6051 0.0.0.0:0 LISTENING 2788
TCP 0.0.0.0:6150 0.0.0.0:0 LISTENING 1484
TCP 0.0.0.0:8400 0.0.0.0:0 LISTENING 2912
TCP 0.0.0.0:8402 0.0.0.0:0 LISTENING 4216
TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING 4
TCP 127.0.0.1:389 127.0.0.1:1053 ESTABLISHED 444
TCP 127.0.0.1:389 127.0.0.1:1054 ESTABLISHED 444
TCP 127.0.0.1:389 127.0.0.1:1055 ESTABLISHED 444
TCP 127.0.0.1:389 127.0.0.1:4098 ESTABLISHED 444
TCP 127.0.0.1:1051 127.0.0.1:1052 ESTABLISHED 2912
TCP 127.0.0.1:1052 127.0.0.1:1051 ESTABLISHED 2912
TCP 127.0.0.1:1053 127.0.0.1:389 ESTABLISHED 3256
TCP 127.0.0.1:1054 127.0.0.1:389 ESTABLISHED 3256
TCP 127.0.0.1:1055 127.0.0.1:389 ESTABLISHED 3256
TCP 127.0.0.1:4098 127.0.0.1:389 ESTABLISHED 2736
TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING 3280
TCP 127.0.0.1:5152 127.0.0.1:2590 CLOSE_WAIT 3280
TCP 192.168.67.229:80 192.168.67.229:2674 TIME_WAIT 0
Do you have a website running on this DC ? Sharepoint ?
ASKER
Nothing. Sharepoint is on another physical server.
When I go to http://servername/, i get the "it works" message....doesnt that mean nothing is really running on 80?
When I go to http://servername/, i get the "it works" message....doesnt that mean nothing is really running on 80?
You should get a "Under Construction" page
ASKER
would reinstalling IIS help us exclude any other sites working on port 80?
ASKER
this DC is also a DNS server....
It looks as if you have Frontpage or Dreamweaver on this server.
Try uninstalling/reinstalling IIS so that you can get the "Default Website" started
ASKER
We are getting VERY close to fixing this.
SubVersion was installed. I uninstalled it, and now when I visit http://servername/, I get "you are not authorized to view this page" 401.1
. The default website is now running. My local machine still wont update though.
SubVersion was installed. I uninstalled it, and now when I visit http://servername/, I get "you are not authorized to view this page" 401.1
. The default website is now running. My local machine still wont update though.
ASKER
uninstall/reinstall IIS and WSUS ?
You need to see "Under Construction" so it looks like permissions
"uninstall/reinstall IIS and WSUS ? "
Well you got the default website running, so not quite yet
Well you got the default website running, so not quite yet
Why dont you go ahead and reinstall IIS and make sure ASP.NET gets installed as well.
ASKER
removing and reinstalling now.
If there are still problems, I would also reinstall WSUS. Hopefully you wont have to.
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
ASKER
just reinstalled IIS...same permission error (401.1).
ASKER
reinstalling WSUS now.
ASKER
i reinstalled WSUS...still get 401 error.
When i try to update my client, i now get error 80072EFD
When i try to update my client, i now get error 80072EFD
ASKER
i also reinstalled WSUS all under port 80...so now there is just the default site in IIS.
When you uninstalled WSUS, did you follow the article above or just use add/remove?
Check....
http://social.technet.microsoft.com/wiki/contents/articles/wsus-troubleshooting-survival-guide.aspx
Check....
http://social.technet.microsoft.com/wiki/contents/articles/wsus-troubleshooting-survival-guide.aspx
ASKER
Add/remove. I'll read the article.
Regardless if wsus is installed or not, shouldnt http://servername still show an under construction page?
Regardless if wsus is installed or not, shouldnt http://servername still show an under construction page?
Yes
ASKER
when we talk about permission for IIS, do you mean the section titled "IIS Settings" in bold @ http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well there you go, you should be set
ASKER
Going against Microsoft documentation, adding Windows Integrated permission actually fixed my issue
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
WSUS Troubleshooting Survival Guide
http://social.technet.microsoft.com/wiki/contents/articles/wsus-troubleshooting-survival-guide.aspx