Hi there,

I have been digging into Symantec forums and knowledge base articles regarding my upgrade scenario where I plan to have my latest SEP installed as a fresh copy on a new server and deactivating the current one once all the clients are connected to the new one. I am not sure if running 2 SEPM instances on different servers can pose any issues.

My plan is to install SEPM 12.1 to a Windows 2012 server then connect the clients to it and upgrade their version too. As soon as the new version has all the clients connecting to it, I'll remove the old one. While this could be straightforward, do I need to be aware of other pre-requisites?

Also, will it be possible to move SEP database to a full SQL server at a later stage?

Thanks and regards,
Trev

I suggest you can wait one month,Symantec new SEPM 12.1 RU5 (12.1.5), Will be released on October 6th 2014.

I am not sure if running 2 SEPM instances on different servers can pose any issues.

There is no issue

While this could be straightforward, do I need to be aware of other pre-requisites?

Upgrading or migrating to Symantec Endpoint Protection 12.1.4 (RU4)/12.1.4a (RU4a)

Best practices for upgrading to Symantec Endpoint Protection 12.1.x

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

Restoring client-server communications with Communication Update Package Deployment

Also, will it be possible to move SEP database to a full SQL server at a later stage?

Yes it's possible but If you will install Fresh SEPM,you can install SQL database.

Symantec Endpoint Protection Manager: Moving from the embedded database to Microsoft SQL Server

Thank you James for the quick reply.

I have checked the links you provided and I just want to know if these 2 items apply only to inline upgrades.

• WARNING: You must stop the Symantec Endpoint Protection Manager service before you upgrade, or you will corrupt your existing installation of Symantec Endpoint Protection Manager.
   
• Upgrade the Symantec Endpoint Protection Manager
  You do not need to uninstall management servers before you install the new version. The overinstall process saves your settings, and then upgrades to the latest version.

The links you provided are very helpful, especially you pointing out the installation of MS-SQL server during the fresh SEP install.

Cheers,

Trev

These 2 points are applied for the SEPM upgrade, no condition of online/offline.

In your scenario both of point not applicable because you will install fresh SEPM server.It's applicable only SEPM upgrade.

Thanks guys. I just wanted to be so sure :-)

This would also mean that on my new install I will have a fresh configuration. Or wil it be possible that during installation, the installer will pickup the configurations from my exisiting SEPM; i.e. the server groups, policies, users, etc? If not, what's the best way of importing them?

Regards.

There is some confusion.

What is your current SEPM and Server OS?

You want to shift in which SEPM and Server OS?

As per my understanding you are going to shift your SEPM in 2102 Server with Latest SEPM.

For this shifting you are require to install the same version of SEPM in 2012 server which are running your old Server.

Databse will be connect or shift in same version then after that you can be upgrade your SEPM in 12.1 RU4 MP1b.

This would also mean that on my new install I will have a fresh configuration. Or wil it be possible that during installation, the installer will pickup the configurations from my exisiting SEPM; i.e. the server groups, policies, users, etc? If not, what's the best way of importing them?

In that your scenario you will have below option.

1) You can Upgrade Latest SEPM 11.x than Intall NEW SEPM server and follow disaster recovery.

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

2) Use replication to install a new SEPM and keep the policy the same with old SEPM.

More info below articles

How to move Symantec Endpoint Protection Manager from one server to another server

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

Appreciate your inputs Sumit and James. While they are pretty similar, I think I will have to go with the option where I wouldn't need to immediately alter my existing installation. As per suggestions, I'm doing the following:

-Install SEPM v11.0.6 for replication on the new server.

-Move SEPM from the old to the new server whilst setting appropriate priority

-Once I confirm that all the clients are reporting to the new server, I will remove old server as a replication partner.

-Upgrade SEP on the new server to the latest version (12.1.4)

-Upgrade the clients via deployment tools

-If all things are in order, uninstall SEPM from the old server

I'll be making backups before carrying out these procedures. But in case something stuffs up, my concern is how will I be able to easily revert to my old server and make it as the manager again.

For the record, my current SEP has these details:

SEPM v11.0.6x ; SEPM Clients at v11.x (RU2 to RU7) ; Windows Server 2003

No of clients: 150+

The new installation will be:

SEPM v12.1.4 (MP1b); Windows Server 2012

Regards,
Trev

SEPM v11.0.6 does not support Windows 2012.

I suggest you can upgrade your SEPM v11.0.6 than install SEPM v12.1.4 (MP1b) and replication both server.

But My best suggestion you can wait till next month and upgrade Latest SEPM 12.1 RU5 (12.1.5),

May be that version will be resolved many problem and available New feature.

--Edit Words--

You can install the same version SEPM for the replication and after that set the new server as first priority

Installing Symantec Endpoint Protection Manager for replication

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

 After completed the replication successfully you can disconnect the old server.

Note - Replication is only be possible in same version.

As you are running with SEPM 11.0.6 and this version is not be supported for Server 2012.

Better is that you can upgrade your SEPM 11.x to 12.1 RU4 MP1b.

Side on you can prepare the new Server for the replication as ready the Server 2012 with 12.1 RU4 MP1b.

After the upgradation and completly fullfil the version requirement then create the replication and follow the bove comment steps.

I am now thinking of starting with a fresh install and just apply any customizations to the new SEPM manually. I reckon this will be a safer and shorter route rather than the upgrade-install-replicate method. I only have 4 client groups with a fair amount of policy modifications. I'll try to have both of these on my test environment though.

Thank you so much for your help guys. I'll probably wait for the 12.1.5 release if time permits.

Cheers,

Trev

Yes,It's Best bet for installed fresh SEPM.

You have only 150+ sep client,you can connect your all of SEP client to new server withthe help of below articles.

Restoring client-server communications with Communication Update Package Deployment

Also You can export Import SEPM policy OLD SEPM to New SEPM server.

How to export/import an existing Symantec Endpoint Protection policy