Endpoint Protection

 View Only
  • 1.  SO upgrade on SEPM server

    Posted May 21, 2017 05:48 AM

    Hi all,

     

    I have a SEPM 12.1 server (latest version) running on a Windows 2012R2 server.

    I would like to upgrade the OS to windows 2016 on this machine, is this allowed?

    I am afraid SEPM 12.1 cannot run on windows 2016, in this case, would it be possible to upgrade the manager to v14 without upgrading the clients? I only have v12 licenses for my clients, and I am not eligible for upgrade to v14, so I don't want to upgrade the clients at the moment.



  • 2.  RE: SO upgrade on SEPM server

    Posted May 21, 2017 09:08 AM

    So your upgrading your SEPM server from 2012 R2 to 2016?

    You can follow the DR steps.

    Take a backup, remove SEPM, upgrade your server, install SEPM, apply DR procedure

    http://www.symantec.com/docs/TECH160736

    https://www-secure.symantec.com/connect/forums/move-sepm-upgrade-current-server-os-and-re-install

    Similar article for clients is here:

    http://www.symantec.com/docs/TECH197095

     

    There is no official confirmation of support for SEPM 12.16 MP 7 with windows 2016 in the below article but I assume it should work just fine.

    Upgrading To SEP 14 – What You Need To Know

    System requirements for Endpoint Protection 12.1.6 MP7

    Supported upgrade paths to Symantec Endpoint Protection 14.x

    Upgrade or migrate to Endpoint Protection 14

    Upgrade best practices for Endpoint Protection 14

    and to answer your question yes SEPM 14.1 will support SEP 12.1.x clients



  • 3.  RE: SO upgrade on SEPM server

    Posted May 21, 2017 09:08 AM

    The release notes for 12.1.6 MP7 do not list Server 2016 as supported.

    You would need to move to SEPM 14 to get full support for SEPM. If you move to 14 you would need the correct license type.



  • 4.  RE: SO upgrade on SEPM server

    Posted May 21, 2017 10:19 AM

    Hi all,

    thanks for your answers.

    If I move to 14, I would need the licenses only for the clients right? The manager doesn't need a license, although is not clear to me if I can upgrade it using the trialware version that one can freely download or if I would need to get at least one v14 license to get access to the download of SEMP. As I said, I was not planning to update any clients to v14 at the moment, just the manager, if necessary.

    In case I move to 14, should I first update SEMP and then perform the backup/remove SEMP/update OS/DR procedure, or first the backup/remove SEMP/update OS/install SEMP14 and perform DS procedure? 

     

    PS: I just read the DS procedure and there is no mentioning of the SQL database settings, is the document assuming the use of the internal database or ar the setttings saved in the DS recovery file and restored automatically? I am using a remote SQL server



  • 5.  RE: SO upgrade on SEPM server

    Posted May 21, 2017 10:56 AM

    You should upgrade to 14 and run DR. Typically, since you use 12.1. you should be entitled to 14. Did you get an upgrade email notification with a new serial. I don't know the specifics of your account so I'm only speculating.



  • 6.  RE: SO upgrade on SEPM server
    Best Answer

    Posted May 21, 2017 11:34 AM

    let me answer your question one by one marked in BOLD

     

    If I move to 14, I would need the licenses only for the clients right?

    Yes, SEPM is just a tool to control the clients and distrubute content and license and it doesn't consume any license

    The manager doesn't need a license, although is not clear to me if I can upgrade it using the trial ware version that one can freely download or if I would need to get at least one v14 license to get access to the download of SEMP. As I said, I was not planning to update any clients to v14 at the moment, just the manager, if necessary.

     Yes you can user the trial ware license or contact the support team to get your hands on SEP 14 serial number, I assume you have a valid entitlement so it should be relatively easy and free of cost. 

    In case I move to 14, should I first update SEMP and then perform the backup/remove SEMP/update OS/DR procedure, or first the backup/remove SEMP/update OS/install SEMP14 and perform DS procedure? 

     As a best practices in an enterprise its always recommended to follow the best practices document (taking the necessary backups) should you need them in case anything goes wrong. so to sum it up take backups of SEPM 12.1.6 and then upgrade to SEPM 14.1.x and then take backups of it as well. then uninstall SEPM and upgrade to win 2016. Then do DR with the backup taken in the SEPM 12.1x environment and see if SEPM 12.1.x works, if its not then you may have to uninstall the current SEPM and install SEPM 14.0 

    PS: I just read the DS procedure and there is no mentioning of the SQL database settings, is the document assuming the use of the internal database or ar the settings saved in the DS recovery file and restored automatically? I am using a remote SQL server

    since you are using a SQL server do a local backup and an SQL backup of both SEP 12.16 and 14 in your SQL studio and in the SEPM server as well and the DR needs to be done from the SEPM server the backup it uses is of its own wizards and it will work with both embedded and SQL.



  • 7.  RE: SO upgrade on SEPM server

    Posted May 31, 2017 06:13 PM

    I'm trying to follow the procedure outlined in your post, but I have one doublt.

    Following the guide you linked, I should:

    -Backup SQL Database (both in SQL and with symantec tool)

    -backup server key

    -uninstall

    -update OS

    -reinstall, at installation I'll be prompt for restoring server key

    -restore database using SQL tool

    Now, based on this, I presume during the reinstallation I should create a new SQL database, right? So, why I need to backup the old one also in SQL? Just for additional safety?



  • 8.  RE: SO upgrade on SEPM server

    Posted May 31, 2017 11:28 PM

    SQL back up is to restore the database with all the required information just in case something didn't go right.

    if things works smoothly, you would simply need to point it to the existing database in the Management server configuration wizard.