Can I do that, or do I need to shutdown my perfectly working WSUS Server? I can contact 3-4 out of 90 computers. ALL of them have management status errors. too bad I can't embed a screenshot. The details panel, at the top, has a box, which states that "the computer has not yet been contacted" Yet the agent is up and running on all the machines. Thoughts?

You can keep your WSUS server, you are not forced to do anything to it. However, you can't use it for any of your machines thatSCE manages. If you have any GPOs pointing to the old WSUS server you will need to ensure that those GPOs do not apply to your SCE computers. HTH, Tim

well, I am using it, I change the policy to point back to the original one. If the WSUS element is critical to SCE working correctly, then I need to know that., so I can transition updates over to SCE. It doesnt make sense to run 2 wsus servers.

Hi, I agree with Tim. A. Run Essentials2007 in parallel with WSUS. A computer can be managed either by WSUS or by Essentials2007, but not by both. GPOs especially setting on Specify intranet Microsoft update service location for SCE and WSUS are different. So if you want to run Essentials2007 in parallel with WSUS, you may have to separate the computers in your domain to different OU so that different GPOs can apply to the different target computers. You may run RSOP.msc from CMD prompt on client computer to see which group policy it has applied, especially setting on Specify intranet Microsoft update service location, it should be the Http://SCEServerName(FQDN):8531 if it is the client to SCE Server. By the way, you may run wuauclt /detectnow on client computer to force it to connect to the Sever. There will be a few minutes' delay between running the command and seeing the results on the server. After forcing the client to contact the server, you can get its status with an update status report. B. Migrating WSUS 3.0 to SCE2007 For your scenario, both GPOs for SCE and WSUS exist. So if you decide to only run SCE, then you may delete the GPOs for WSUS and shut down the WSUS Server or uninstall it. Then you may run Gpupdate /force on client computer to force it to apply the GPOs for SCE. Hope it helps. Best regards, Xiu Zhang - MSFT Microsoft Online Community Support

I'm having some problems with updating unmanaged workstation with WSUS. What your saying about Http://SCEServerName(FQDN):8531, is this the correct? I believe that it's Https://SCEServerName(FQDN):8531 for managed workstations and Http://SCEServerName(FQDN):8530 for unmanaged workstations. So, what's the right answer?Greetings,

The WSUS element is critical to SCE working correctly. You will not get management information for your managed machines until they are pointed to the SCE server for updates.

mheijkant, It is not recommended that you use a SCE version of WSUS to supply non-managed computers with updates. This is bad if for no ither reason than it causes you to have to use the WSUs console on your SCE server, and you can do damage requiring complete removal and re-installation of SCE quite easily from the WSUS console. Tim

Hi mheijkant, I agree with Tim. Also, SCE does not support to deploy update to un-managed computers. Https://SCEServerName(FQDN):8531 is just the right address for client to connect to SCE Server to detect and download updates. Best regards, Xiu Zhang - MSFT Microsoft Online Community Support

Maybe there is some misunderstanding. I don't wan't SCE to support unmanaged updates. I just expected that WSUS could still be used for the windows updates, after the installation of SCE. So I expected that the unmanaged workstations could be windows-updated through the same WSUS server as before.I read somewere, might have been the microsoft documentation, that port http://<wsus-server>:8530 could be used for this purpose. And at the same time https://<wsus-server>:8531 could is used for SCE functionality.Are you telling me that updates through 8530 just aren't supported, because of your own field experience?Can you tell me were exactly, I can find this information that confirm's, that ordinary windows updates aren't supported for a SCE-upgraded, WSUS server.Hopefully this will end my quest, to find a working sollution. Otherwise a second WSUS server has to be the final answer.Thank's

Hi, It is not recommended or supported to use WSUS console within SCE to distribute update. It will damage the SCE installation from WSUS console. So in this scenario, you need to set up another WSUS for those unmanaged clients. Hope it helps.

Hi, It is not recommended or supported to use WSUS console within SCE to distribute update. It will damage the SCE installation from WSUS console. So in this scenario, you need to set up another WSUS for those unmanaged clients. Hope it helps. Does this still apply to System Center Essentials 2010? Obviously the ideal solution is for the Windows Update functionallity in SCE 2010 to provide updates to UNMANGED/AGENTLESS clients.