Endpoint Encryption

 View Only
  • 1.  Migrating & Upgrading SEE to a 2008 Server running SEPM

    Posted Jan 28, 2015 09:36 AM

    I'm currently running Symantec Endpoint Encryption management software on a Windows 2003 server (Server A). I want to migrate and upgrade the SEE software from the 2003 to a 2008 server that is also running SEPM. I think I found all the information I need on how to do this, but just want to double check and look for advice. 

    Changing the server name of the SEPM server: http://www.symantec.com/business/support/index?page=content&id=TECH196981

    Migrating and upgrading without losing clients: http://www.symantec.com/business/support/index?page=content&id=TECH157899&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1422455571340fHgso0v43UNP1G9v51lmzIood2QGdCGDAb0r8


    Aside from the steps from above, can anyone provide additional information or tips that we may need to know?



  • 2.  RE: Migrating & Upgrading SEE to a 2008 Server running SEPM

    Posted Jan 28, 2015 11:15 AM

    Are you concerned about conflicts between products? The recommendation is for each to have their own separate dedicated box. Are the hardware specs up to snuff as well?



  • 3.  RE: Migrating & Upgrading SEE to a 2008 Server running SEPM

    Posted Jan 29, 2015 09:30 AM

    Well I figured that Symantec Endpoint Encryption software was lightweight compared to SEPM, so I was thinking the additional software wouldn't be too intensive on the hardware resources.

     

    If the recommendation is to have the prodcuts on their own boxes, I understand and that would probably be the route to go, but I was just curious on any steps I may be missing if I decided to migrate SEE onto the same server as SEPM.



  • 4.  RE: Migrating & Upgrading SEE to a 2008 Server running SEPM

    Posted Jan 29, 2015 12:16 PM

    I haven't seen any issues reported while doing that, but since it is not really recommended, I don't know how many people are actually trying it.  The only thing I really have to base an opinion on is that I have seen it working in a couple customer environments, and they didn't seem to be having any trouble with it.

    As far as I know, there wouldn't need to be any special considerations or concerns apart from the obvious (i.e. not using the same port numbers between products).