New WSUS Server
-
Wednesday, September 12, 2012 1:35 AM
Hi There,
I have bulid a New WSUS server (Server 08 R2/ WSUS 3.0 SP2) as the old one(Server 03) had a lot of problems. i have given the same IP to the new server, and pointed using GPO. new clients who enter domain can communicated, but the existing domain PC do not appear in the console.
I think i have to update regestry keys or something else.
Appreciate Assistance.
Thanks Ashish
All Replies
-
Wednesday, September 12, 2012 1:50 AMModerator
So let's start by determining what these "existing" machines are actually doing. Post the latest detection event from the WindowsUpdate.log.but the existing domain PC do not appear in the console.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin -
Wednesday, September 12, 2012 4:37 AM
below is few line from the WindowsUpdate.log file
2012-09-12 16:25:18:018 1948 1e2c Misc =========== Logging initialized (build: 7.6.7600.256, tz: +1200) ===========
2012-09-12 16:25:18:018 1948 1e2c Misc = Process: C:\Windows\system32\wuauclt.exe
2012-09-12 16:25:18:018 1948 1e2c Misc = Module: C:\Windows\system32\wucltux.dll
2012-09-12 16:25:18:018 1948 1e2c CltUI AU client got new directive = 'Download Progress', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, return = 0
2012-09-12 16:25:48:343 1148 1d94 DnldMgr Error 0x80072efd occurred while downloading update; notifying dependent calls.
2012-09-12 16:25:55:597 1148 14cc DnldMgr Error 0x8024402c occurred while downloading update; notifying dependent calls.
2012-09-12 16:28:02:440 1148 1cd0 DnldMgr Error 0x80072efd occurred while downloading update; notifying dependent calls.
2012-09-12 16:30:08:457 1148 18b4 DnldMgr Error 0x80072efd occurred while downloading update; notifying dependent calls.
2012-09-12 16:30:08:459 1148 db8 AU AU checked download status and it changed: Downloading is paused
2012-09-12 16:30:08:462 1948 1e2c CltUI AU client got new directive = 'Shutdown', serviceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, return = 0
2012-09-12 16:30:08:473 1148 560 AU AU received handle eventabove is from client computer
- Edited by AshishNaidu Wednesday, September 12, 2012 4:50 AM
- Edited by AshishNaidu Wednesday, September 12, 2012 6:48 AM
-
Wednesday, September 12, 2012 7:45 PMModerator
Typically when we say post the latest detection event -- we mean the whole detection event... start to finish..
But in this case, there's a major clue here...
2012-09-12 16:25:48:343 1148 1d94 DnldMgr Error 0x80072efd occurred while downloading update; notifying dependent calls.
Pretty much says the client cannot talk to the WSUS server. Either it has an incorrect URL, or the configured URL is not resolvable, or not accessible, or is resolving to the wrong (or no) IP Address, or the IP pathway from the client is non-existent.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin- Edited by Lawrence GarvinMVP, Moderator Wednesday, September 12, 2012 7:46 PM
-
Thursday, September 13, 2012 3:35 AM
Thank Lawrence,
i have configured the wsus update using GPO, other options in the same policy seems to be applying to clients.
cant figure out where the isssue is.
-
Friday, September 14, 2012 9:16 AMModerator
Hi,
According to my understanding, you said that you have configured GPO to connect computers to the new WSUS, but those client could not.
I would like suggest you run gpresult/z to check the group policy result and make sure the setting has been applied to those client.
If the issue occured on all you client, please add another new client and try it.
Regards,
Yan Li
Yan Li
TechNet Community Support
- Marked As Answer by Yan Li_Microsoft Contingent Staff, Moderator Thursday, September 20, 2012 7:08 AM
-
Wednesday, March 06, 2013 1:35 AMthanks for support guys, i am now able to see about 200 computers in the console but have issues with about 60 computers.
when i run client diagnostic i get an error below
thinks i have done:
http://192.168.1.48/SimpleAuthWebService/SimpleAuth.asmx and http://192.168.1.48/selfupdate/wuident.cab- successful

