I have a deployment of SEP in a multi-site environment. I have two SEPM servers, one at each site. Replication is working and I've deployed the client out to multiple systems on my primary location without issue. Today, I began deploying clients out in my secondary location. The clients are in a separate group from those at my primary site with the communication settings configured to point to the secondary SEPM server.
The problem I'm having is when I deploy the SEP client to systems at the secondary location, the communication between the client and the secondary SEPM server does not appear to take place. When I go into troubleshooting and view the status, it reports "Server: Offline". It does show the correct information under "Group:" as far as where the client should be at, but looking at the SEPM server, it doesn't appear as a client and a search of unmanged clients with the client's name shows the computer with a "Deployment Status" of "No".
I have tried some solutions posted that suggest copying the sylink.xml file from the SEPM server to the client and pasting it into the SEP installation directory after stopping SMC, but that hasn't worked.
The client with the problem connecting to the SEPM server is a Windows Server 2003 R2 Domain Controller.
Any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Sorry,
You can download it from here:
http://service1.symantec.c
Turns out the communication issue had multiple sources. Because the management server is also a domain controller, the website was setup to run as a domain IUSR account for anonymous access. This caused problems with the SEPM service which would start and then fail. A recommendation I found was to enable Integrated Authentication on the website which enabled the SEPM service to start but effectively prevented the clients from accessing the SEPM server because they couldn't authenticate.
I switched the website over to a different domain account and that seems to have solved the client communication issue. I found the solution from one of the articles you linked and from using SylinkMonitor which reported the 401.1 error message from the webpage.
Now the problm I'm having is an inability to access the reporting console on the SEPM server, but that's a different issue.
Business Accounts
Answer for Membership
by: xmachinePosted on 2009-08-19 at 10:12:47ID: 25135001
Hi,
1)Download Sylinkmonitor (http://www.impassnet.org/
2) Enable Debug + SylinkMonitor debug feature
(http://service1.symantec.
Upload Sylinklog here to inspect it for you
3) Check the following communication troubleshooting guides:
http://service1.symantec.c
http://service1.symantec.c
http://service1.symantec.c
http://service1.symantec.c
http://service1.symantec.c
Symantec Certified Specialist