Environment: I'm running Service Center Essentials 2010 on a virtual Server 2008 R2 Server. We have one Domain Controller who provides the AD. We are testing SCE 2010 for software distribution and monitoring usage. Symptom description: I've just installed SCE2010 with all the relevant utilities a few days ago. Now I've started with the discovery of our clients. But unfortunately most of the clients don't get discovered by default. I've started a manual discovery and chose discovering by computer name. After scaning the network it gives me the message to control the admin rights of the user (this has enough rights for other clients in the domain though), the firewall (ports are all open) and if the client is in the AD (but still - he is). There is a link below this message to troubleshoot this issue. And I've followed the steps and tried to discover the client with net view. There is just a System Error 53. The clients who are discoverable have a printer or folder shared. Isn't there any way to discover clients who don't share anything? There are no recent configuration changes as it hasn't been working from beginning on. Additionnal information: I don't know if there is a problem with this. There is the WSUS service running on the DC. But for testing I've deleted a client from its list - but still the discovery won't work. There are no Log-Files in the Logging-folder recently. Yesterday for testing I've added one of the undiscovered clients to the GPO SCE Managed Computers Group Policy (SERVERNAME_MG), restarted the client but there was no change. Thank you for your assistance. Regards isehuet

Hello isehuet, Have you finished the Essentials Initial Configuration before the discovery? Before you can use System Center Essentials 2010 to manage your environment, you must complete the Configure System Center Essentials Wizard. This wizard walks you through configuring settings for Group Policy, firewall exceptions, remote assistance, computer discovery, notifications, proxy servers, monitoring, updates, and reports. Essentials Initial Configuration http://technet.microsoft.com/en-us/library/ff603601 If Essentials detects any policies that conflict with the settings required by Essentials, and you proceed without changing the settings to resolve these conflicts, Essentials might not operate correctly. Please also check if any related error message was logged in the OpsMgr Event Log on both the server or the client. Thanks,Yog Li TechNet Community Support

After struggling with this problem I've tried to install the SCOM instead. Therefore I've changed some major installations on the server. But unfortunately with SCOM the installation of the agent blocks as well. At least I can choose the client after scaning the network. Trying to install the agent afterwards I get the failure code 80070035 with the description "Network path could not be found". I think it must be the same error as with System Center Essentials but SCOM prompts it for troubleshooting. I've checked the internet already regarding this issue and couldn't find any helpful information. To ensure that the ports are open I've disabled my antivir program and the windows firewall of the monitored system. On the monitored system is runing Win7 and there is no printer or folder shared. I can imagine that Symantec Endpoint Protection is blocking some ports on my system... Will give you more information if I get further with testing.

Hello isehuet, Thanks for the information. I found this error code in the following article: Troubleshooting Issues When You Use the Discovery Wizard to Install an Agent http://technet.microsoft.com/en-us/library/ff358634 The remediation steps for the error code 80070035 are as follows: Verify that the management server can ping the computer on which you want to install the agent, using the fully qualified domain name (FQDN). If ping is successful, click Start, click Run, and then type the FQDN. If the management server cannot browse the target computer, check the firewall settings.Perform a manual agent installation. For instructions about agent installation, see Deploying Windows Agents (http://go.microsoft.com/fwlink/?LinkId=180383). Thanks, Yog Li TechNet Community Support

Hi Yog Li, Thank you for your help! Unfortunately the FQDN couldn't be resolved and it was impossible to establish any connection. From the local client it works but not from another client in the domain. I've rechecked the firewall and everything is configured as it should be... I haven't installed the Agent manually as it's nonsense to install the Agent and not getting any information afterwards for the SCOM monitoring. I don't see through this problem... From my point of view it shold be up and running. With my Domain Controller it works fine and even with a client that has a shared printer locally connected. Any other suggestions? Thanks, isehuet

What happens when you disable the SEP firewall? Check this article for Best Practices when installing a SEP client on servers. Best Practices for Installing Symantec Endpoint Protection (SEP) on Windows Servers

Hi Thomas, Thank you for your reply. I've already tried with disabeling the SEP firewall and all its services. I've also created some firewall policies in SEP regarding the SCOM management. Unfortunately it was not the fault. Thanks for further hints. I got stuck with this problem...