Symantec AV Upgrade -

Posted on 2009-05-13
Medium Priority
Last Modified: 2013-12-09
Currently, we are running Symantec Enterprise 10.1.7.  

We will be moving to Symantec Endpoint Protection 11 this month.  Symantec 10 and 11 will run on separate hardware but will be live on the network together as clients are removed from 10 and then installed from 11.  

We will also be migrating to a new domain in three months (project due to end in three months).

In preparation to migrate to the new domain, we have one DC already migrated over as a first step as we begin migrating more servers over.

New servers added to the network are being joined to the new domain so that we will not have to deal with migration issues later in the next three months.

That being said:

Would it be better to build the Symantec 11 server on the new domain, and have it service computers on the old domain as systems are being migrated over?

Would be nice to know the pros and cons of this decision.  


Would it be better to build the Symantec 11 server on the present (old) domain and then migrate the server to the new domain as the clients are migrated over to the new domain.

Would be nice to know the pros and cons of this decision.

Any advise on this would be greatly appreciated.
Question by:fraunkd
1 Comment

Accepted Solution

barryhiggins3 earned 2000 total points
ID: 24379058

I would advice putting the Endpoint Server in the new domain and making sure you have a trust setup between the old and new domain. That way when your deploying clients you can authenticate using admin credentials from the new domain to deploy to computers in both the old and new domain.

There isnt really any point in setting the server up in the old domain as you will only have to migrate it, a simple service account in the new domain with local admin privalges on p.c's in both domains should do the trick (and would be needed anyway).

You can deploy the Endpoint cleints to P.C's by scanning IP ranges so there's nothing to stop you deploying to both domains at once.

Another tip- If you are planning on running your Endpoint database on a seperate MS SQL server DO NOT use anything pre MSSQL 2005 as there is a know issue that we have spent weeks working with Symantec trying to resolve. If you can get away with it just use the Endpoint server's built in Database instance as it will save you alot of hassle.

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

UPDATE - 6/15/2011 Added support for Release Update 6 Maintenance Patch 2 Point Patch 1 (RU6 MP2 PP1). Fixed a defect in the username field that was hard-coded to look for a specific domain (left over code from testing). This release will be the …
If you are like me and like multiple layers of protection, read on!
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

607 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question