Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.
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.
[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
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
Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Exception Handling is in the core of any application that is able to dignify its name.
In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.
These days socially coordinated efforts have turned into a critical requirement for enterprises.
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB.
How Percona can help
Percona can help you determine if Percona Server for MongoDB is the right solution for …
Suggested Courses
Course of the Month8 days, 16 hours left to enroll
721 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.