Endpoint Protection

Hello,

         I'm completely re-structuring my company's SEPM enviornment.  I'm building a new SEPM that I want to bring online using the same site license and site name.  Management does not wish to have this new SEPM replicate with the old one.  I will re-structure the polices and groups on the new SEPM and then push out a client re-direct to point the current clients to the new SEPM.

Can anyone elaborate to the concerns/problems of this approach?  Any advice would be greatly appreciated.  Thank you!

It's a lot of manual work to setup policies, etc. Once you push out an upgrade from the new SEPM, the clients should all than connect to it.

Replicating the two would be easiest if you can.

Are you moving to a new server with different hostname/IP?

The advantages/disadvantages are listed here:

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

Thanks Brian.  Just to add, I'm essentially building a "new" SEP enviornment for my organization.  The current one was just stood up with the default groups/policies in place. 

If I build this new SEPM and stand it up using the same license and site name, can this cause any problems with the current SEP enviornment in place?  My plan is to build the new SEPM and conduct some initial testing on a few dedicated machines, with regard to cutting them over to the new SEPM.

Please note I will be building the embedded database from scratch and will not use the current one in place.  Hope that clarifies.  Thanks!

Export the policy from old server and import it in to new one is also east way for policy.

http://www.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication

It shouldn't be a problem. They will operate independantly of one another. If only default policies were in place than you won't have much manual work as I thought.

I would suggest starting with the latest version of SEP 12.1 which is RU3.