Client getting wrong WSUS server name
-
Mittwoch, 23. Januar 2013 17:05
Hello,
Since I migrated our WSUS server from 2003 to 2008 R2. All the clients are recorded on the new server, but I noticed after a few weeks that some of the clients did not communicate with the WSUS server any more.
The cause is that the old server name is referenced on the client in the following keys:
HKLM\SOFTWARE\Policies\Windows\WindowsUpdate\WUServer and HKLM\SOFTWARE\Policies\Windows\WindowsUpdate\WUStatusServer
I looked in the DNS database, the reverse DNS database, the WINS, but found nothing related with the old server name.
Does anyone have the solution to this problem ?
Thanks
Alle Antworten
-
Mittwoch, 23. Januar 2013 17:30
Am 23.01.2013 schrieb YELLOWDOG:
The cause is that the old server name is referenced on the client in the following keys:
HKLM\SOFTWARE\Policies\Windows\WindowsUpdate\WUServer and HKLM\SOFTWARE\Policies\Windows\WindowsUpdate\WUStatusServerDelete this Entries, GPUPDATE and Restart the Client. Comes the old
Servername back? If yes, run a gpresult /H >gpresult.html in a
administrative Commandline. You will find there a GPO with your old
wsus-name.Winfried
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
http://www.wsuswiki.com/Home -
Donnerstag, 24. Januar 2013 09:06
Thanks for the answer Winfried,
After running the gpresult /H command, I noticed indeed that the reference of the old server is in the GPRESULT, but if I edit the GPO applied to that machine the new server is correctly referenced.
I have about 15 different WSUS GPO and I believe that most of them are subject to the same phenomenon. I controlled all of them and the new server is correctly referenced, but 80% of the workstations are pointing on the old server.
How to explain that error ? Do I have to recreate the GPOs ?
-
Donnerstag, 24. Januar 2013 19:41
Am 24.01.2013 schrieb YELLOWDOG:
After running the gpresult /H command, I noticed indeed that the reference of the old server is in the GPRESULT, but if I edit the GPO applied to that machine the new server is correctly referenced.
Do you have more then one DC in your AD? If yes, is Replication
wokring without errors? In the Report you will see the Name of GPO, is
this a actual GPO?I have about 15 different WSUS GPO and I believe that most of them are subject to the same phenomenon. I controlled all of them and the new server is correctly referenced, but 80% of the workstations are pointing on the old server.
15 GPOs for WSUS?
Winfried
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
http://www.wsuswiki.com/Home- Als Antwort vorgeschlagen Winfried Sonntag [MVP]MVP Montag, 28. Januar 2013 18:27
- Als Antwort markiert Clarence ZhangModerator Donnerstag, 31. Januar 2013 02:55
-
Freitag, 25. Januar 2013 13:49No idea about it ?
-
Freitag, 25. Januar 2013 17:52
Am 25.01.2013 schrieb YELLOWDOG:
No idea about it ?
You can answer my questions:
http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/947492a7-054e-4f67-ae75-5fc27c0d939e#5ff864bd-f2b3-40b2-9081-f443b91f570eWinfried
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
http://www.wsuswiki.com/Home -
Samstag, 26. Januar 2013 12:54
What about cleaning SCCM client and then re-installing it? Does this works?
And what about client discovery after migration?
-
Montag, 28. Januar 2013 11:55
Winfried, the problem is a replication DC.
I solved it thanks to you.
Many thanks.
-
Montag, 28. Januar 2013 18:28
Am 28.01.2013 schrieb YELLOWDOG:
Winfried, the problem is a replication DC.
I solved it thanks to you.
Many thanks.Thanks for Answer. ;)
Winfried
http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
http://www.wsuswiki.com/Home
.png)
.png)
