Client getting wrong WSUS server name
-
Wednesday, January 23, 2013 5:05 PM
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
All Replies
-
Wednesday, January 23, 2013 5:30 PM
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 -
Thursday, January 24, 2013 9:06 AM
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 ?
-
Thursday, January 24, 2013 7:41 PM
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- Proposed As Answer by Winfried Sonntag [MVP]MVP Monday, January 28, 2013 6:27 PM
- Marked As Answer by Clarence ZhangModerator Thursday, January 31, 2013 2:55 AM
-
Friday, January 25, 2013 1:49 PMNo idea about it ?
-
Friday, January 25, 2013 5:52 PM
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 -
Saturday, January 26, 2013 12:54 PM
What about cleaning SCCM client and then re-installing it? Does this works?
And what about client discovery after migration?
-
Monday, January 28, 2013 11:55 AM
Winfried, the problem is a replication DC.
I solved it thanks to you.
Many thanks.
-
Monday, January 28, 2013 6:28 PM
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)
