Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

combining two endpoint protection managers to one

Created: 27 Nov 2012 | 19 comments

I have two servers currently that are not linked both taking care of enpoint management in different locations I would like ot either combine these into one server (ideal) or at least link the two if oossible to I have a master that will get the updates and issue them to the child server but I can get reports from one location that will include both.  the main server is RU7 and the other server is mr4, mp2 which creates another issue I tried to do the migration (tech article TECH104389) but because of the different versions it would not work.  also the older server I do not have the space on the hard drive to upgrade it to the same as the other.Looking for options the second server only has about 30 clients and if I could do it from the server I would not be opposed to deleteing the software and then pushing it from the other server, but need a process.

 

Thanks

Comments 19 CommentsJump to latest comment

pete_4u2002's picture

you need to add the server as replication, however note that since these are already existing as at different site the data might be lost from one site.

_Brian's picture

In this case, since you only have 30 clients, you can just create a new package from the newer server and push to the clients on the older box. They will upgrade and point to the new server.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

JoeCr's picture

 Pete, with your scenerio I would just create an additionla site for the second one and then it would re-install the clients ?

 

Brian if I re-push from the new site do I have to stop the other site first? or do I have to do an uninstall on those clients?

_Brian's picture

No, since they are on old versions, as long as you push a new RU7 package from the new server, it will upgrade right over the top and start pointing to the new server. Just make sure when you create the new package to uncheck the following:

This will clear all previous settings and point it to the new server

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Rafeeq's picture

Site A; upgrade to latest version

Site B: install new SEPM. and replicate with SiteA

Create a new package and push it to your 30 clients in Site B

 

Chetan Savade's picture

Hi.

It's important here to know available bandwidth between main site and remote site.

If bandwidth is limited then you need to setup Group Update Provider (GUP) on remote site.

New features and functionality in Symantec Endpoint Protection Release Update 5 (SEP RU 5) Group Update Provider (GUP)

http://www.symantec.com/business/support/index?pag...

From the main server (RU7) deploy new package on all the 30 clients by selecting an option stated by Brian81.

Now those 30 clients will start communication with main site. Promote one of the remote site machine as a GUP to save bandwidth so that all the 30 clients will not come over the WAN link to take updates.

Available disk space on the remote site is the major issue so you cannot go with replication.

 

 

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

JoeCr's picture

Brian states to uncheck but I believe I wnat to check the box that is circled which is a little different in ru7 but I understand to remove all of the older references.

as far as bandwidth we are pretty good we have two T1's tied together between the main site and the remote site.

I have the deployment package created but I need to create a new one I believe for the first time that will have that checkmarked and then the normal one that does not have that box checked, is that correct?  if so I am having a hard time getting a second install package created for the same version of the software. 

Thanks for the help I am a mcafee person from my other companies and now just learning symantec

Chetan Savade's picture

Hi,

I have the deployment package created but I need to create a new one I believe for the first time that will have that checkmarked and then the normal one that does not have that box checked, is that correct?

--> That's correct

You need to create new client install setting & select the same setting while exporting the package, check the following article to know more about it.

Managing client installation packages

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

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

_Brian's picture

If your deploying a client from the new server to clients connected to the old server, you will need to reset the communication otherwise it will still upgrade however it will still point to the old server.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

JoeCr's picture

Brian81 that is where I am having a problem trying to create a package that will overwrite the old information with the new infomation

Chetan Savade's picture

Hi,

Still you are not able to create custom package by selecting new client install settings?

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

JoeCr's picture

I created the new install settings now I need to get that into an install package that I can use

JoeCr's picture

I am still having issues is there a way in the mangement console that I cna uninstall it.  so that way it is unmnaged and then I can push the new one to it?

_Brian's picture

You can't uninstall from the SEPM console.

Is the upgrade not working? As long as it is a newer version, it should upgrade over the old version.. are you getting any error messages?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

JoeCr's picture

it is upgrading the client it is just not redirecting it to the new server it is still listed under the old server and I cna not get it to start looking at the new server.  I have not seen any error messages.  I push the client from the new server and it does upgrade the client but then it gets virus definitions and reports tot he old server still

_Brian's picture

Yes, because you need to check "remove all previous logs and policies, and reset the client-server communication settings" when you created the package from the new server.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

JoeCr's picture

I guess my problem is how to finish the package creation I have setup the install settings as shown above and named that then I thought that I created the package to use that but then when I deploy I can't tell if it is using that or not becasue it does not move the client.

_Brian's picture

If you open the GUI and select Help >> Troubleshooting, you can verify what SEPM server you're connected to.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SMLatCST's picture

I personally think you'd be better off just redirecting your 30 clients in the remote site to the main SEPM using the below article:

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

And taking a look at the upgrades as an optional step after they're talking and managed by the main server.