Endpoint Protection

Hello!

SEP 12.1.5337.5000

I try to move the Clients to another SEPM.

With the new SEPM i made a SepCommunicationUpdater Package, which contains the SylinkDrop.exe, SyLink.xml and SylinkDropCommand.xml.

Now i made a simple startup script, to run SylinkDrop.exe on the Clients, but it generates the following error:

<Status ExitCode="14" Description="Error ( 3 ) in smc -importSylink."/>

When i run the script as Administrator, it works perfect.

In past i made this sometimes and it alway worked, but now i have this Problems.

What could i do, what means the errorcode?

I have also tried to export a Package, and used this SyLink.xml, same Problem.

The script needs to run with admin credentials. It sounds like it works fine when you do it that way.

Hi!

I wrote the script runs as startup script, so it has more than admin rights, it runs as System account!

1 of 20 times it works, but i don't know why. All the same PCs and OS Images.

I think it is an error in the actual sylinkdrop.exe, it always worked in the past.

Where can i download an older version, on fileconnect.symantec.com i only can get actual versions.

It's only on the install disc so you'd probably need to call support to get an older version.

I am having the same issue when trying to use it when deployed with system creds. It worked fine in our office windows domain, but our production domain isn't having it. Works fin when run as a Admin. 

Status ExitCode="14" Description="Error ( 3 ) in smc -importSylink."

So I am not the only one.

Getting exactly the same issue as Stoff.

If I RDP or VNC to the client PC, then while logged in I run the script works. 

But the client MUST have an admin logged in. Running over 20+ PC's I might get 1 or 2 that update, so does not help explaing it.

Also running the install client communicater direct from the SEPM also fails :(

AAARGH

Hi!

In my case, no Admin must be logged in, it will do it when a normal user is logged in. It seems the GUI of Symantec must run to execute the sylinkdrop sucessfully.

I opened a symantec support call, but they where not very interested to solve it. They had no solution for me, maybe because of bad knowhow of their own product. :-(

I had rewritten my script, so it runs the sylinkdrop command only, if a user is logged in.

Now it works, but the Symantec Support thinks it is a solution for the problem and is not interested in any help or solving the problem. But it is NOT a Solution for the problem, its a jump over the problem, but it still exists.

It seems symantec is not interested in resolving software errors. :-((

I will share the script, it waits until a User is logged in and then it executes the sylinkdrop.exe. If the state is not success, the script will run at the next system boot and try it again. It also reports to the sysvol Folder in a log file.

Maybe you need to change the line with "query user". The output is in german, so you need to change "BENUTZERNAME" to "USERNAME" or something in your language.

Run it as GPO startup script and it will work fine. :-)

Attachment(s)

SEPM-change_0.txt   1 KB 1 version

Hello,

There was a defect with 12.1 RU5 SEP client cersion where the Sylinkdrop would not be able to replace the Sylink if no user is logged in. This was Fixed with SEP 12.1 RU6 ( Fix ID - 3729729). Since this fix is a Client side fix you would need to upgrade your client to the 12.1 RU6 version first.