Endpoint Protection

Hi folks, 

Ì'm part of an internation company and i'm looking for your expertise to merge two of our SEPM servers in the same views. 

First, we have a site which include more then 3,000 clients which use a Remote SQL database dedicated in our HeadOffice. Many sites connect to this SEPM and remote sites are using GUP to send Virus update content. We use a complexe Folder architecture. We sync most of our Symantec Folder whit our active directory. Which give us more than 20 root folders and a lot of subfolders in every root folders.

Default group

   Some computers in here

Site1

   Computers

   Servers

   Special computers

   and mote...

Site2

Computers

   Servers

   Special computers

   and mote...

On the other side, we have an other SEPM with 800 clients using a Local SQL Express. GUP is also use the same way on branch office. This server use no LDAP synchronisation and have a simple architecture Clients / servers / DC's quiet basic

Default group

Clients

   No FW

   Test

   Test2

   Update

Server

  update

My question is, what will happen to my servers once they will be Replication Partner ? Is the clients informations will be merge into my two SQL Servers ? Is the Clients folders architecture will merge and the content of "Default group" will now be common for both servers ?

What is we decide to roll back and remove the partnership between server. Will our Folders Architecture will need to be cleaned ?

I've went through lot of symantec HOWTO but this is more theorical than pratical for my situation. 

John

Hello,

What sep version are you using both site ?

Check some of link

https://www-secure.symantec.com/connect/forums/two-symantec-endpoint-environment-mergering-single

https://www-secure.symantec.com/connect/forums/merging-two-existing-sepm-servers-and-then-moving-new-sepm

https://www-secure.symantec.com/connect/forums/combining-two-sep-infrastructures

https://www-secure.symantec.com/connect/forums/merge-2-sepm-servers

The version is 12.1.2 in the HeadOffice 

12.1.1 in the other site

If you're going to setup replication, they should be on the same version

Ok I take note of that

Symantec does not support multi-version manager replication scenarios. Database schemas can change from version to version, and database corruption could occur if the schemas do not match. All Symantec Endpoint Protection sites that replicate should be running the same version

Does Symantec Endpoint Protection Manager support replication between sites running different versions?

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

My question is, what will happen to my servers once they will be Replication Partner ? Is the clients informations will be merge into my two SQL Servers ? Is the Clients folders architecture will merge and the content of "Default group" will now be common for both servers ?

--> Replication is not possible between already existing sites. It will overite the other. 

you first install a new Symantec Endpoint Protection Manager and database for replication with an existing manager. Second, you log on to the Symantec Endpoint Protection Manager and select and schedule the items to replicate.once replicated you will see the same contents on both the SEPMs

What is we decide to roll back and remove the partnership between server. Will our Folders Architecture will need to be cleaned ?

once your remove replication they wont talk to each other but whatever contents is in DB will be displayed in the console.

If the replication is not possible, is this possible to link both site in the same console as partner without replicating databases ?

That way we would have a common infrastructure, is this an option for us ?

Data replication is not necessary. After the partnership create we could create a second SEPM server on each site and create a database replication. Is this something possible ?

You would link different SEPMs to load balance or replicate.

Not possible to manager two or more sepms in a single console.  1 sepm and 1 database is called a site and each site is different in its own aspect.

you can have 2 sepms sharing a single database (replication) in your secondary region.

You could, in theory, look into the Symantec Protection Centre for unified loggin of both SEP Sites.  Management would still be separate, but at least you can obtain a higher level view of the whole lot.

Progressing a step further, you could also look at the SSIM the the External Logging options on the SEPMs (again only for unified reporting, not management).

I suppose my question is, which do you really want?  Is unified reporting enough, or must management all be from the same place as well?