Endpoint Protection

I will be upgrading from SAV 10.1.8 to SEP 11 at 6 different locations.  Each site has it's own SAV 10.1.8 server.   I have the Reporting Server installed on a separate server from my SAV 10 servers which they all report too.   I was going to upgrade to SEP 11 one location at a time.  From reading some documentation, it said to remove the Reporting Server first.  Is that only if the Reporting Server is installed on the same server as the SAV server? 

  As I said, I was going to upgrade one site at a time.  My plan was to move the clients at a one site to another 10.1.8 site temporarily, update that site to SEP 11 and then upgrade the clients to SEP 11.  Does that sound like a good plan?  Is there an easier way?

Reporing component is now integrated with SEPM

Install the manager SEPM on new server . then create package then install it on clients

once all your clients are migrated to SEP, you can then uninstall SSC, primary server, and reporting server

AFAIK you need to remove Reporting Server only when installed on the same machine where you plan to put your SEPM.

You plan sounds fine. How many clients do you have in eanch site? Installin SEPM server, exporting client installation package will take you like 30 min so I do not know if it make sense to move the clients temporarily to another SAV server?

Moreover, you do not need to remove SAV clients - SEP installation will overwrite SAV :-)

Uninstalling Reporting Server would be required as when installing SEP Client on the machine that has Reporting Server would fail the installation of SEP Client.

Also there is no need to point SAV client to another SSC while you are installing SEP. As SSC(Symantec System Center) and SEPM(Symantec Endpoint Protection Manager) can stay on the same machine or in the same network. You can install SEP over SAV 9.x or 10.x Client.

During the installation SEP Client will first remove SAV and then install SEP on the machine.

Below are 2 articles those you can refer for migration

Title: 'How To Migrate From Symantec Antivirus System Center Console To Symantec Endpoint Protection Manager'
Web URL: http://www.symantec.com/business/support/index?page=content&id=TECH106485&locale=en_US


Title: 'Symantec Endpoint Protection Manager reference guide for Symantec System Center users'
Web URL: http://www.symantec.com/business/support/index?page=content&id=TECH116729&locale=en_US

I have 6 sites, some sites have as many as 800 clients and some as few as 60.   The network connection between sites is a little slow which is why we have a server at each site.  With 10.1.8, I have the SAV server and the System Center console installed on each SAV server and can manage each site for the other site servers if needed.  We also use Ghost to image workstations and each new machine initially connects to the same SAV server.  After deskside completes the local configuration I drag and drop it to it's local SAV server.   I don't know if that is the best way to do it, but it has worked well for 5 years using that method using both 10.1.5 and 10.1.8.   I would like to continue using that same process when we move to SEP 11 unless there is a better method.  

You can have ; SAV, SEPM installed on the same server, 

Uninstall SAV server and SSC at the end and then install SEP on this server, 

Please go with the method u r comfortable with....

It is a good plan im my view. Please mind that SAV clients will not download definitions from SEPM. So it is ok to move them to a second SAV server, install SEP console and then deploy SEP clients pointing them to a new SEPM server. Please make sure you know how to create SEP installation package which will change communication settings on a client (if you have SAV pointing to srver A and you want to install on the machine SEP which is going to be connected to server B you wanna make sure that the client "forgets" about old server A). If you do know how to export such a package, let me know :-)

After updating the server to SEP 11, my plan was to push a new SEP 11 package via my Software Distribution tool to upgrade the clients with the SyLink.XML file from the new server included in the package.  I assume that will work.  I only have a 4 hour window each night for updates to the client machines, so managing it with Software Distribution tool is the best for me.  My one question is will I be still able to drag and drop clients from one site to another or will I need to push a new SYLINK.XML file to each client to move it to is primary site server.

BTW, thanks for all the info so far.

Different manager will have different Sylink file

so if you are having 1 for each site; then it will all be different.

You can use the sylink replacer to move the sylink file to clients

http://www.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm