Moving Symantec Endpoint Protection Manager server 11.0.4 to new hardware and IP address
Hi,
I have a couple of questions regarding moving Symantec Endpoint Proctection Manager to new server and IP.
Our network setup consists of 2 physical sites (main office in Melbourne which has about 500 clients and one in Sydney with 250 clients) We have two Symantec Endpoint Proctection Manager 11.0.5 servers installed in a failover config (one at each location) and a separate SQL database server also located on Melbourne. The SEP server contains one site.
We are planning to move the SEP Management servers to new hardware as there is a heavy load on the existing servers. We would then like to remove them.
How can I best achieve this?
Also should there be an additional database installed at our Sydney office to reduce netowrk traffic between sites?
Comments
Title: 'How to replace your
Title: 'Moving clients from site to site without manually replacing the Sylink.xml'
Document ID: 2009093012465148
> Web URL: http://service1.symantec.com/support/ent-security....
Title: 'How to replace your environment's only Symantec Endpoint Protection Manager (SEPM)'
Document ID: 2008012507573748
> Web URL: http://service1.symantec.com/support/ent-security....
Also should there be an additional database installed at our Sydney office to reduce netowrk traffic between sites?
--For this you can have replication , so that the clients will take updated from the Sydney site and only logs will be replicated
Or what you can do is have one SEPM and create 2 groups one for melbourne and other for sydney
And configure GUP at both the sites. The clients will not come to the SEPM for the update rather GUP will update them
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
You installed the second
You installed the second server as additional site or fail over site?
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
I think it is better to use
I think it is better to use GUP in your scenario .You may use the same server which you are using as SEPM in Syndney as GUP.First you shutdown the Sydney SEPM server and see.If all the clients are reporting to other server you can remove SEPM software from this server.For more about GUP refer this link
Symantec Endpoint Protection 11.0 Group Update Provider (GUP)
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Hi Avarind. To answer : You
Hi Avarind.
To answer : You installed the second server as additional site or fail over site?
The Sydney SEPM server was installed as a failover for melbourne. So would I be right in thinking that all clients are going to Melbourne for updates?
You mentioned that GUP is the best solution to reduce network traffic, however the link above states:
Using a GUP in a large group
We will have issues when the group gets large, i.e larger than 200. Certainly if a dedicated server is set as the proxy we can handle quite a bit of content. This is what secondary servers are today.
As we currently have 250+ cleints, wouldn't that make using GUP a problem?
Why I suggested to use GUP
Why I suggested to use GUP because if you add more servers the administration will be difficult.In your case you can install your Sydney SEPM as additional site.In this server you have to get the updates via replication .(If a SEPM has to receive updates from other this is the only way).If repliaction fails your second server will not receive the updates.Oher ways you have to install LUA in your main site and point the second server to download updates form it,or you have to configure the second server also to download the updates from Internet.
A GUP can handle up to 1000 clients.You can assign same LU policy to more that a group.So one GUP is possible for more than one group.
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
As an answer to your main
As an answer to your main concern, I would go ahead and install the new servers on new hardware as 3rd and 4th servers of the SEP site (with new IP adresses and everything).
Then I would arrange the Management Server List policies for every group (under Policy Components -> Management Server Lists).
Next, I'd assign the new server which will be responsible for database maintanance and backups (Admin -> Servers -> Site Properties etc). Then I would wait a couple days or weeks for clients to recieve the new Sylink.xml files. And finally I would uninstall the old servers and rearrange the Management Server Lists by removing the old entities.
On the other hand, you do not need to have another database at Sydney. Just keep the heartbeat intervals long and keep the communication in push mode. So that client's will not keep coming and doing stuff resulting in database activity.
I'd suggest 30 minutes with push mode.
You do not need GUP or anything else in Sydney since the SEP Manager console over ther will be handling it.
Liveupdate parts of the SEP Manager is mostly handled on the server itself and they are not database intensive.
Do you feel like the system is slowing down the link between Melbourne and Sydney?
Best regards,
Bekir Burak Durmaz
Have a look at this article
Have a look at this article also.You may get some useful information
Tips for installing SEP in Low Band width
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Would you like to reply?
Login or Register to post your comment.