<div>
There is a GPO object associated with the WSUS update location in domains.. &nbsp;Maybe te old server is referenced there?<br />
<br />
<a href="http://www.microsoft.com/technet/community/columns/sectip/st0506.mspx" rel="ugc nofollow">http://www.microsoft.com/technet/community/columns/sectip/st0506.mspx</a><br />
<br />
-D-
</div>


There is a GPO object associated with the WSUS update location in domains..  Maybe te old server is referenced there?

http://www.microsoft.com/technet/community/columns/sectip/st0506.mspx [http://www.microsoft.com/technet/community/columns/sectip/st0506.mspx]

-D-

<div>
A Group Policy does point the servers correctly to fhserver08, but when I run rsop.msc on one of the affected servers, it shows the WSUS server incorrectly as fhserver05.
</div>


A Group Policy does point the servers correctly to fhserver08, but when I run rsop.msc on one of the affected servers, it shows the WSUS server incorrectly as fhserver05.

<div>
<div class="content wysiwyg-content">
I'm running WSUS to update ten Windows 2003 servers and ninety Windows XP clients. &nbsp;Three of the servers are not reporting. &nbsp;I have run cliendiag.exe on these three servers, and they all pass. &nbsp;However, when looking at the WindowsUpdate.log files on these servers, they wrongly point to an old decommissioned WSUS server - <br />
<br />
2008-06-10 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;14:12:57:688 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;828 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4b4 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PT &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server URL = <a href="http://fhserver05/SimpleAuthWebService/SimpleAuth.asmx" rel="ugc">http://fhserver05/SimpleAuthWebService/SimpleAuth.asmx</a><br />
<br />
instead of the current WSUS server which is fhserver08.<br />
<br />
The WSUS server is correctly shown as fhserver08 in the registry of each of these servers, and I can find no trace in the registry of the old server, fhserver05.<br />
<br />
Can anyone help please?
</div>
</div>


I'm running WSUS to update ten Windows 2003 servers and ninety Windows XP clients.  Three of the servers are not reporting.  I have run cliendiag.exe on these three servers, and they all pass.  However, when looking at the WindowsUpdate.log files on these servers, they wrongly point to an old decommissioned WSUS server - 

2008-06-10	14:12:57:688	 828	4b4	PT	  Server URL = http://fhserver05/SimpleAuthWebService/SimpleAuth.asmx

instead of the current WSUS server which is fhserver08.

The WSUS server is correctly shown as fhserver08 in the registry of each of these servers, and I can find no trace in the registry of the old server, fhserver05.

Can anyone help please?

Clients not reporting

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.