Hi there,

got a problem with Endpoint Protection 14.0.3929.1200 on Windows 10 (mixed from 1511 up to 1803), when we try to connect a unmanaged client to a management server

or are trying to relocate a client to another management server either by SEPM or by exported communications updater we get an error in the log located in c:\temp\clt-inst:

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

SEPM is running on Server 2012 R2, user account used to connect to the client is local admin, client password is submitted with package.

Deactivated tamper protection, but no change.

Dont know where to search further, somebody got the same problem? Just found a post with same problem, but SEP 12.1.

thanks in advance and best regards from germany

Marcel

Did you try from SEPM? See this KB article:

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

Hello Brian,

yes, this is our usual way as i wrote (...either by SEPM or by exported communications updater...), i tried the exported package just because my usual way was not funtioning anymore.

best regards
Marcel

Hi Marcel,

looks like its not taking the password

its just smc -importsylink from the error posted above, can you disable the password on the clinet and  try again?

or

Please try running the same cmd on the client machine manually after copying the sylink.xml manually on remote machine

start - run

smc -p "password " -importsylink pathtoSylink

here is the cmd

Endpoint Protection - Command-line options for smc.exe

https://support.symantec.com/en_US/article.TECH103048.html

Hi Rafeeq,

first to mention, problem also includes Windows 7 Prof computers. If i manually run the command it works on some machines and others not, some Win7 and some Win10. Didnt figured out yet whats special to those computers, as they all are rolled out by WDS from the same Win7 or Win10 image, are updated by WSUS, get same GPOs etc.

Are there any logs i could check? Is there a debug mode?

best regards
Marcel