Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Sylink issue

Created: 03 Feb 2013 | 3 comments
Jaredirk's picture

Hi Guys,

We have a current deployment of SEP from one of our clients using SNAC 11.0.6

Here is what we have done so far:

1. Created a virtual machine similar to their production environment.

2. On the VM, we installed 11.0.6 SNAC SEPM and then used replication from their production SNAC.

3. After replication, we upgraded the VM with the 12.1 RU2 SEP and SNAC version.

Here is my dilemma,

I deployed a package to 5 workstations with SEP/SNAC and was successfully installed.

But the problem is, they did not report to the new server but instead connected to the production server.

Is that because the sylink I used from the new server was a replicate of the sylink from the production server?

Or I need to turn my replication off?

Comments 3 CommentsJump to latest comment

.Brian's picture

If replication is turned on, you should see it show up in both SEPMs. Force a replication to see if it shows up. From there, you need to set the new server as a Priority 1in the Management Server List

 

Configuring a management server list

Article:HOWTO81154  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL http://www.symantec.com/docs/HOWTO81154

 

Assigning a management server list to a group and location

Article:HOWTO80735  |  Created: 2012-10-24  |  Updated: 2013-01-30  |  Article URL http://www.symantec.com/docs/HOWTO80735

 

The other thing you need to check is when you create the package from the new server, make sure the below is checked when creating the package:

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

pete_4u2002's picture

where were the clients communicating earlier?
are they able to communicate to replication ( newly added) server?

SMLatCST's picture

I'm curious, at which point was the client install package created for your test machines?  Do they report into the old SEPM?

If they are successfully reporting to the old SEPM, then the MSL changes suggested by Brian ("Thumbs Up" BTW) should do the trick.

In theory (as long as they were created after replication was established) they should hold the certificates required to communicate with your test SEPM.  Take a look at the below articles for troubleshooting client communications:

http://www.symantec.com/docs/HOWTO80740
http://www.symantec.com/docs/TECH102682
http://www.symantec.com/docs/TECH105894
 

If the test described in the second article returns an "OK", the communications are possible, but the client doesn't haev the right details.  In which case, I'd suggest replacing the communications file on your test clients with one from your test SEPM:

http://www.symantec.com/docs/TECH157585

I know these are for SEP, the steps should be the same for SNAC....

On a final note, replication should ideally have been broken before the upgrade was performed on your test SEPM.  Replication should effectively be broken now anyway as the SEPMs are on different versions.