Endpoint Protection

I have just installed SEPM on a new server (the old one will be decommissioned), and I would like to scan and add all the clients on to the new server.

How do I do that?

Hello,

Could you please let us know -

1) What older Version of SEPM were you carrying?

2) What OS are you running on the SEPM server?

3) If you have Migrated from the Older Version of SEPM to the Latest Version of SEPM 12.1.1 by running the install over the older version OR by uninstalling older version of SEPM and then installing the SEPM 12.1.1?

4) How many SEP clients do you carry on your Environment?

1) The SEPM version was the same (v12), it's just the server that is being replaced.

2) Win 7 64 bit

3) There has been no migration, just a fresh install of SEPM on new server

4) Around 50 I think

Hi,

You can Replace Syslink.xml file or use Client Deployment Wizard - SEP 12.1.

Note :If issue is resolved then please mark this thread as a solved

Replacing the syslink file will do what exactly? I thought that handled just the communication settings. Will this put all the client machines in the right group as well?

You can Export Syslink file for partcular group and replace Syslink.xml file.

SEP Client Automatic Redirect that group.

Or

How to deploy clients in Symantec Endpoint Protection 12.1

The client deployment involves pushing out an install to the clients, however the clients already have endpoint installed.

When you say 'replace the syslink file', do you mean replace on the server or replace for each individual client?

I'm looking for a solution that doesn't involve any deployment or configuration per client. SEPM should have the functionality to add a large number of clients (without pushing out an install package) in one go. Is this possible?

The previous set up used an embedded DB. Should I try exporting it?

HI,

Do you have old SEPM database ?

Edit

Hello,

Here is it:

"With SEP12, we decided to merge the old clientremote tool and Find Unmanaged Computers into one.  The new version is called the Client Deployment Wizard.

You can find it in two places - first from the Home screen, choose "Install Protection Client to Computers" from the "Common Tasks" drop down at the top right, or alternatively, from the Clients tab, when you are in the client list, click "Add a Client" on the left hand side, just above "Add computer account"

Both will launch the CDW and allow you to search your network, find all your PC's and helps you deploy the right client to each one.

Give it a go and let us know what you think!

Currently which Databse you are using ?

Here is it:

"With SEP12, we decided to merge the old clientremote tool and Find Unmanaged Computers into one.  The new version is called the Client Deployment Wizard.

You can find it in two places - first from the Home screen, choose "Install Protection Client to Computers" from the "Common Tasks" drop down at the top right, or alternatively, from the Clients tab, when you are in the client list, click "Add a Client" on the left hand side, just above "Add computer account"

Both will launch the CDW and allow you to search your network, find all your PC's and helps you deploy the right client to each one.

Give it a go and let us know what you think!

Both setups use the embedded DB. which I'm guessing is some sort of SQL Server DB?

The Client deployment wizard involves pushing out packages, which ever way you launch it. The packages are already installed on the client machines. I just want to add the clients to the new server.

Yes you can add old DB to new SEPM

How to move Symantec Endpoint Protection Manager 12.1 from one machine to another

http://www.symantec.com/business/support/index?page=content&id=TECH171767

Edit.

But You can say you have only 50 client so you can use Client Deployment Wizard or syslink.xml file.

This is not a big task.

Edit.

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

http://www.symantec.com/business/support/index?page=content&id=TECH160736

That link doesn't lead to anything.

50 computers isn't a lot to a tech, but we are a very fast-paced office and cannot afford the downtime to each user (esp the boss)

You may set your installation package to "no restart"so you can control it but it does not mean you can avoid it and the SEPM just reflects it.

Migrating the SEPM would not require any reboots. However, when Migrating the SEP clients you may require a reboot of the SEP client machines. Network Threat Protection (firewall) drivers would require a restart of the machines to get themselves activated. However, these could be taken care off by creating custom package and avoiding the restart of machines.

Creating custom client installation packages in the Symantec Endpoint Protection Manager console version 12.1

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

Or,

you can replace syslink file there is no downtime required

follow this article except the restoring of database.

http://www.symantec.com/business/support/index?page=content&id=TECH160736

 the certificates needs to be restored for client to communicate back with the new SEPM.

Check this fourms

https://www-secure.symantec.com/connect/forums/clean-sepm-121-ru1-install-maintain-client-communication

With the syslink file, do you mean we have to replace it for each client, on their local machine?

Use the SylinkReplacer utility to replace Sylink.xml files in existing Symantec Endpoint Protection clients.

Note: The SylinkReplacer utility is only for use in Symantec Endpoint Protection environments. To obtain SylinkReplacer, contact Symantec Technical Support:
http://www.symantec.com/business/support/index.jsp

Once you have obtained the utility via Support, expand the archive (zip) file to a convenient location, such as the Desktop.
Note: This file is password protected. To unzip the file use the following password: symantec

Follow the instructions provided in the SylinkReplacer PDF.

Execute the tool by double clicking SylinkReplacer.exe and follow the on-screen instructions.

Please note that the DOS window should not be closed during any course of action while the tool is running.

Note: for SEP 12.1 environments, the SylinkReplacer Utility compatible with SEP 12.1 is required. It is also available from Support.

 How to point clients to a new SEPM after decommissioning or replacing the primary SEPM

http://www.symantec.com/business/support/index?page=content&id=TECH92556

I ended up putting faith in the users and showed them how to update their sylink file.

Thank you for your help!

If issue is resolved then please mark this thread as a solved

--