Endpoint Protection

Hi,

I've just deploy the symantec endpoint and found a bit of issues.

Issue -
1.  I push down to the server, how do I know the server is running 64-bit or 32-bit. It doesn't display at all on the description?

2. When I deploy, it show sucessfully, but when I go one of of the servers, the symantec is not installed at all and I found out that the windows installer is not enabled.  Why does the system show sucessfully when it is not even deployed?

Thanks

It shows successful because the push from the SEPM to the client was successful but on the client the installation might not have completed so for that you can check if there is any previour version of symantec installed on your client.
the server is in your network hence you should know if its 64 bit or 32 bit before the installation.
You can go to the Start > Run prompt & type %temp% & search for return value 3 under the SEP_inst log & let me know your findings.

succecful because client package copied to remote machine. check the installation log on remote machine.

Thats why I say the best way o deploy is go to the client and install from their.

because there might be some other antivirus installed on it which may prevent sep installation. there might be some virus which also can prevent the installation. so for the first time just go to the client and install.

About first question, 64 Bit Client will only be installed on 64 Bit Operating system and same ways 32 bit goes only for 32 Bit. So that means if it got installed fine on 64 Bit machine that means it is installed as 64 Bit COmputer.

Seconds question, You see successfyl because the package was actually sent to the clietn computer but due to some problme on the remote machine it didn't got installed

As you said Windows Installer service was disabed(not enabled), try enabling that and install it again.

To further find the reason why it didn;t got installed, do the following

Start -- Run -- %temp%

Look for SEP_INST.log file and look for "Return Value 3", Check few lines above this line and you may be able to find the reason.

You can also upload the logs here, me or someone will look into that and guide you further

Dear All,

Its value is 'C:\WINDOWS\'.
Action ended 7:22:16: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (28:A0) [07:22:16:270]: Doing action: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
Action 7:22:16: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
Action start 7:22:16: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
MSI (c) (28:A0) [07:22:16:270]: PROPERTY CHANGE: Adding SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E property. Its value is 'C:\WINDOWS\system32\'.
Action ended 7:22:16: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.

 

Let say if I manually go to the Client and Install MANUALLY, in what situtation will I need to copy the  sylink.xml to the client?

 

Thanks

This portion of the log does not show Return Value 3. So can't say much about this.

About Manually goig to Client and installing there, the only situation to copy sylink is when you install unmanaged client.

Use SylinkReplacer to replace sylink file for unmanaged client.

Hi,

First of all, thanks for your help.

Are  I right to say that if the client has been installed as Unmanaged and I would like it to be managed,  I just copy the sylink to the client and it will automatically become managed ?

? Is there other steps that I need to perform to ensure it can communicate to the SEP. Do I need to restart the PC?

From the client point of view(workstation), how do I verify it can communicate with server and repot back?

Thanks

Hi Yobo,

Yes copying sylink will convert unmanaged client to Managed Client.

Replacing the Sylink file is the only steps there is no need to reboot the computer.

To check if the Clietn is communicating with SEPM Console, check if
-- Client Shield shows Green Dot
-- In Client GUI, go to Help and Support -- Troubleshooting, this should show you the SEPM Server name and also the Group in which client will show in SEPM Console
-- Client should have Green Dot in SEPM Console Client Tab as well.
-- Policy Serial number should be same on SEPM and SEP Client both.

Dear Partner,

Where can I download the SylinkReplacer  utility?

What is the difference by using the sylinkreplacer utily and manually copying the files ?

In addition, what does   a  Client Shield shows appear  means on the symantec endpoint projection manager but do not have a green icon?

How can I view Policy Serial number should be same on SEPM and SEP Client both?

Since sylink.xml is to convert from unmanaged to managed mode, how about if it is a new machine that has not been setup and if I export the client installation package, will I need to copy the sylink.xml file again?

Appreacitate your patience.


Thanks

Hi Yobo

You may find the Sylink replacer utility on the following forum link

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

Also you may get it from the file share account

To download this utility go to https://fileshare.symantec.com/, and use
the following login ID and password.

 

Login ID: sylinkreplacer
Password: Syl1nk0!

The password to extract the zip file is "symantec"

The difference between using the tool and manually replacing the sylink is that the tool can be run on the server and automatically it replaces the sylink file
You don't have to do it manually on all systems.

If the shield appears in the taskbar it means that the SEP client is installed however if there is no green dot it means that the client is not communicating with the SEP Manager

SylinkReplacer is intended for batch-mode Sylink updates to many remote machines. You have only one, so SylinkReplacer is overkill.

In your case, either click Import under Communication Settings in Help/Troubleshooting in SEP on the client, or use SylinkDrop in the Tools\NoSupport\SylinkDrop folder of SEP CD2. Or run SMC -STOP, copy the Sylink.xml file over the existing one on the SEP client, and run SMC -START. No machine restart is required for any of these techniques.

If you have an AD domain, you can make your SEPM installation more robust and never again risk having an unmanaged client with this tip that would have helped you here:

https://www-secure.symantec.com/connect/articles/startup-scripts-and-sylinkdrop-better-together