• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 460
  • Last Modified:

Symantec AV Upgrade -

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.  

OR

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.
0
fraunkd
Asked:
fraunkd
1 Solution
 
barryhiggins3Commented:
Hi,

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.
0
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

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now