Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.
Solved
SCE 2007 Management Server shows computer has not been contacted for most systems
Posted on 2009-06-27
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.
5-
5
10 Comments
OK, moved a step closer. It looks like our proxy server is impacting on the WSUS component in some way. Weird thing is that I don't have proxy enabled in IE on the management server or any of the other servers, only the XP workstations. WSUS Administration is now listing my servers but showing the IP of our proxy server???
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
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
Active today
This should be very helpful
Troubleshooting guide for issues where WSUS clients are not reporting in
Troubleshooting guide for issues where WSUS clients are not reporting in
Ran this on the management server. Let me know if you need it run on a client workstation
WSUSServerDiagnostic.jpg
WSUSServerDiagnostic.jpg
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
Featured Post
ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them.
Troubleshooting Steps:
Connect via h…
Note: You must have administrative privileges in order to configure lead or case queues.
Salesforce.com (http://www.Salesforce.com) is a cloud-based customer relationship management (CRM) system. It is widely used around the world by sales and ma…
If you are looking for an automated solution for backup single or multiple Office 365 user mailboxes to Outlook data file, then you can use Kernel Office 365 Backup & Restore tool. Go through the video to check out the steps to backup single or mult…
From store locators to asset tracking and route optimization, learn how leading companies are using Google Maps APIs throughout the customer journey to increase checkout conversions, boost user engagement, and optimize order fulfillment.
Powered …
Suggested Courses
Course of the Month5 days, left to enroll
579 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.