Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Combining two SEP infrastructures

Updated: 21 May 2010 | 10 comments
Daniel_Allen's picture
+2 2 Votes
Login to vote
This issue has been solved. See solution.

I've just been informed that my company will be picking up a new company in the immediate future.  I understand that they are already running SEP 11.0.4 and presumably a SEPM server.  I will need to merge their existing infrastructure into mine, which is also 11.0.4.  Has anyone done this before?  Is there any documentation for this?

Thanks.

discussion Filed Under:

Comments

Vikram Kumar-SAV to SEP's picture
12
Jun
2009
2 Votes +2
Login to vote

Well...

Two diffrent databases can not be combined together.So one has to sacrifice.
Lets say Site A has 100 client and site B has 50 clients.
all are installed and working properly...now you decide to combine both these SEPMs.
So what you can do is.Export the list of IP address for the clients in site B ( only because they are less--so I wont consider this site as main site )
Then either Run Management server configuration wizard and select Add replication parter and connect to SEPM on Site A for replication.
Or Un-install SEPM on Site B ..install fresh and select Add a replication parter.
Once SEPM is installed and both Sites are replicating Use SylinkReplacer  Tool ( for this tool you will have to contact support --This tool remotely replaces sylink.xml files on client machines either by selecting list of IP address or by selecting a range of IP address ).
Use Sylinkreplacer to connect those 50 clients in SIte B to the SEPM.
Once this is done it will become centrally managed.then you can apply Management Server list on the clients groups ( Clients in which group will report to which SEPM ).

Note :As mentioned above even if you choose management server configuration wizard  it will wipe out the current database.

kavin's picture
12
Jun
2009
2 Votes +2
Login to vote

You can SETUP the replication

You can SETUP the replication between both the sites
The site that low number of machine make that site as the secondary partner
You can follow this document
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091703483748

once done with that you can Drop the sylink file on the client on the new location so thta they can restore the communiction

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008062412271448

NOTE:- In making the replication partner you will be loosing the database of the secondary server

Ajit Jha's picture
13
Jun
2009
0 Votes 0
Login to vote

Good Soltion Kavish  I will

Good Soltion Kavish
 I will work upon it as well.

Regards'

Ajit Jha

Technical Consultant

STS

Daniel_Allen's picture
12
Jun
2009
1 Vote +1
Login to vote

Thanks

Thanks guys.  This gives me an idea of what I need to do.

mon_raralio's picture
12
Jun
2009
2 Votes 0
Login to vote

Basically, you'll be

Basically, you'll be assigning the other clients to your SEPM server, and then use the other one as a replication and probably an update server.

“Your most unhappy customers are your greatest source of learning.”

Ghe21's picture
12
Jun
2009
2 Votes +2
Login to vote

how about the db of both

how about the db of both servers..
how would they be combined...
thanks

Ghe21's picture
12
Jun
2009
1 Vote -1
Login to vote

If they combined the db

If they combined the db server what will be the possible output..,

Sheila Marie's picture
12
Jun
2009
0 Votes 0
Login to vote

it is not an option to

it is not an option to sacrifice another db..
there must be something else aside from that..
thanks

Vikram Kumar-SAV to SEP's picture
12
Jun
2009
0 Votes 0
Login to vote

two DB

 you are not sacrificng the whole SEPM foreever but you are just sacrificing the DB and rebuilding it..

Two half-semi or full filled DBs can not combine.

mon_raralio's picture
14
Jun
2009
0 Votes 0
Login to vote

As soon as you added a client

As soon as you added a client from the other server, the new server would get all the info on that client, including the logs. If that's your concern.

“Your most unhappy customers are your greatest source of learning.”