Solved

WSUS Clients

Posted on 2013-05-28
7
373 Views
Last Modified: 2016-02-20
I have a few WSUS clients that aren't reporting/connecting to WSUS and when i run rsop.msc on the clients I see they're pointing to an old WSUS server that has since been decomissioned, I've updated the Group Policy and yet say 8 of the 9 clients in that group are fine and 1 still gets the old server....

I've tried regedit but soon as i run gpupdate its resets to the old server....

any help with this is much appreciated.
0
Comment
Question by:antrimbc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 4

Expert Comment

by:EddyvanOpdorp
ID: 39200747
How did you update the group policy ?
did you try gpupdate /force on the client ?
0
 
LVL 22

Accepted Solution

by:
Haresh Nikumbh earned 500 total points
ID: 39200756
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

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/947492a7-054e-4f67-ae75-5fc27c0d939e
0
 

Author Comment

by:antrimbc
ID: 39200782
EddyvanOpdorp - I updated the GP to point to new server and yes both normal reboot and gpupdate /force...

The problem with editing the registry is soon as i run gpupdate it resets it back to older server...
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 22

Expert Comment

by:Haresh Nikumbh
ID: 39200811
refer my link, where other ppls also mention same thing after running gpupdate it create old entry.
0
 

Author Comment

by:antrimbc
ID: 39200818
Winfried, the problem is a replication DC.
I solved it thanks to you.
Many thanks.

What does he/she mean by that?
0
 
LVL 5

Expert Comment

by:joyofsharing
ID: 39205723
Referring to comment ID: 39200818

Its means that if your AD (Active Directory) have more than one DC (domain controller) then replication must be working ok between them.
If replication is not working as expected then that also could be the issue.
0
 

Author Closing Comment

by:antrimbc
ID: 39246978
Good answer
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question