SCE 2007 Management Server shows computer has not been contacted for most systems
I have installed SCE 2007 with SP1 and after 3 days the management server plus all local systems show "This computer has not been contacted yet" with an error on deployment and inventory and the Operating System is showing Windows 0.0
Laptops that are working over a VPN show the correct OS, software shows as up to date but updates are still showing unknown.
We do not use the XP firewall (we use Symantec Endpoint). I have tested RPC and fileshare connectivity by opening up eventviewer.msc from the management server to the affected workstations.
I found that the Selfupdate virtual directory was missing so I added it in manually as recommended on both the default web site (port 80) and the wsus administration site which operate on the custom port (8530 and 8531). I can connect from both the management server and from a local client. I have tried to force a reconnect using wuauclt detectnow but this makes no difference.
I also tried changing the group policy Windows Update settings (it is being applied OK) from https://managmentserver.domain.local:8531 to http://managmentserver.domain.local:8530 in case that was the issue.
I am now completely stumped as to what the problem may be. I'd like to get these basics functioning before moving on the the other errors that are now fillling up the alerts to do with performance counters.
Thanks very much in advance for any help given.
Laptops that are working over a VPN show the correct OS, software shows as up to date but updates are still showing unknown.
We do not use the XP firewall (we use Symantec Endpoint). I have tested RPC and fileshare connectivity by opening up eventviewer.msc from the management server to the affected workstations.
I found that the Selfupdate virtual directory was missing so I added it in manually as recommended on both the default web site (port 80) and the wsus administration site which operate on the custom port (8530 and 8531). I can connect from both the management server and from a local client. I have tried to force a reconnect using wuauclt detectnow but this makes no difference.
I also tried changing the group policy Windows Update settings (it is being applied OK) from https://managmentserver.domain.local:8531 to http://managmentserver.domain.local:8530 in case that was the issue.
I am now completely stumped as to what the problem may be. I'd like to get these basics functioning before moving on the the other errors that are now fillling up the alerts to do with performance counters.
Thanks very much in advance for any help given.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ran this on the management server. Let me know if you need it run on a client workstation
WSUSServerDiagnostic.jpg
WSUSServerDiagnostic.jpg
has to be run on clients ;-)
ASKER
DOh! :-)
FYI, although it was the management server the results in WSUS are the same. Both internal clients and servers, regardless of whether IE is set to use the proxy are showing the IP of the proxy server and are not updating their status. Weird?
WSUSClientDiagnostics2.jpg
WSUSScreenShot.jpg
FYI, although it was the management server the results in WSUS are the same. Both internal clients and servers, regardless of whether IE is set to use the proxy are showing the IP of the proxy server and are not updating their status. Weird?
WSUSClientDiagnostics2.jpg
WSUSScreenShot.jpg
Ok, go over the link above
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, this just got weirder, while reading through the procmon output one of the DCs just sync'd, while the other stubbornly refuses to play ball. Both are setup identically. I'm hoping that if one works that means the WSUS permissions must be OK.
ASKER
Cracked it. Turned out to be a setting on the proxy server. Needed to make sure that the local domain was added to the list of those that did not require authentication. Weird as you would have thought that if IE was set to not use a proxy it wouldn't matter. Hey ho!
ASKER
Updates are still showing as unknown so I guess we are looking at a WSUS/Proxy issue in some way.
The proxy server is the Smoothguardion module of Smoothwall Advanced Firewall