IT Management Suite

 View Only
Expand all | Collapse all

Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

  • 1.  Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Sep 07, 2022 06:28 PM
    My understanding is that in-place OS upgrades aren't supported so I'm looking to spin up all new servers to replace my existing Windows 2008 R2 servers (1 SMP and 1 task server) along with an off-box SQL 2008 and migrate data from my existing ITMS 8.1 RU7 infrastructure to 8.6 RU3.  Considering going with 3 new Windows 2022 Standard servers for SMP/NS, Task & SQL Server 2019.  Anyone see a problem with the OS/SQL versions that I've selected?

    Also wondering if anyone else was in this same situation before and went with Professional Services to do the migration for you as this seems like a rather daunting task if you ask me?


  • 2.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Sep 09, 2022 11:39 AM
    Hello Clint,

    Great questions.  There are no issues with your OS and SQL choices, as they are all supported in 8.6 RU3.  (Platform and OS Support Matrix)

    There is also upgrade documentation here: Upgrading ITMS.  Also check out the sub articles (Upgrade Checklist, Best Practices, Post-Upgrade Tasks, etc.)  That is all very good information to understand.

    The specific migration and upgrade steps for the SMP are in this KB (substitute 8.5 RU4 for 8.6 RU3): KB 204145

    If you would like to document the steps needed, Support would be happy to review your upgrade plan. 
    If you have any questions on the procedure, Support would also be happy to help you find the answer. 
    Please open a case the day before you're upgrade and let Support know that your upgrade is happening.  That way Support can be readily available for any issues or questions that may arise during or following the upgrade.

    Professional Services are available if you'd like their assistance: Contact Symantec Professional Services


  • 3.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Sep 09, 2022 02:34 PM
    Hi Roy,

    Appreciate the links to the migration documentation as I knew there'd be a decent amount to read.  Hopefully this is something I can tackle myself because I know management will get "sticker shock" for an engagement with ANY professional services.  We did have an authorized consultant come in to set up our first Altiris server years ago so maybe they'll stomach the cost for pro services if I ask nicely (hehe).


  • 4.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Sep 20, 2022 03:49 PM
    I found the following article on recommended system requirements.  Similar to my current environment, I'd like to combine the task & package site servers into a single VM so what specs am I using?  For example, am I choosing, say, the higher spec (CPU, RAM) under each task/package server section or perhaps combine the two; although thinking this might be overkill (except maybe for disk space).

    https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/it-management-suite/ITMS/Getting-Started/Hardware-recommendations/recommended-it-management-suite-hardware-v54421798-d780e4327.html


  • 5.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Oct 13, 2022 08:49 PM
    KB 204145 is redirecting existing task/package server to the new NS but what if I'm instead bringing up a new task/package server as well?  My existing task/package server is running Windows 2008 R2 so it has to go too.  Thanks in advance!


  • 6.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Oct 13, 2022 10:13 PM
    Edited by Igor Perevozchikov Oct 13, 2022 10:20 PM

    Hello Clint!

    Sure you can add a new Site Servers on new Windows OS (Consider IIS features requirements for new PS or TS Required IIS features for the Task Server and the Package Server to build HTTP code bases )
    (Check that all packages are ready with published codebases on new PS and new Task Server is active and clients are registered)

    If you are using CEM, then need to add new Site Server in CEM Gateway. Verify that CEM clients can download packages from PS.
    If old Site Servers aren't needed any more (And these old Site Server machines will be turned off and never powered on), then you can delete them from NS and from CEM Gateway

    Or your question was about migration of all packages from old PS to a new PS machine to avoid downloading them from new NS?

    Best regards,
    IP.





  • 7.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Oct 14, 2022 03:51 PM
    Hi Igor,

    Yes...I was wondering if data had to be migrated from my old task/package server to the new one or just define a new PS/TS on the new NS then it'll copy over whatever it needs (in time, of course)?  Step 6 in KB 204145 seems to instead be using an existing PS/TS server but I've already spun up a new VM for this purpose.  OSes are old on all of my existing servers so I'm planning to replace everything with 3 new VMs (1 NS, 1 SQL & 1 PS/TS).

    Clint


  • 8.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Oct 17, 2022 09:01 PM
    I just noticed another "monkey wrench" for me in KB 204145.  When migrating Software Management Solution data in Step 3, there's a note that says it does not export "Software Library" (among some others) as a source which makes up the bulk of my software packages.  I always thought "Library" source locations had their files on the ITMS server so am I mistaken on this?


  • 9.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Oct 18, 2022 12:19 AM

    Hi Clint!

    "Software Library Configuration" settings accepts only UNC path locations, no matter if there is a local ITMS UNC share is specified or remote UNC path. (I think that you have ITMS local UNC share as SW Library, therefore it seems like packages stored locally)

    Therefore Migration Wizard doesn't export Software packages with "Source" locations like "UNC", "SW Library" or "URL"



    Exports packages only with "Local" Source location


    To update Source location for existing packages which were imported "SW Library" source, need to change SW Library location and choose to migrate existing package and update their source


    Best regards,
    IP.



    ------------------------------
    [JobTitle]
    [CompanyName]
    [State]
    ------------------------------



  • 10.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Oct 18, 2022 04:20 PM
    Hi Igor,

    My existing server seems to have the software delivery packages at \\{altiris_server}\Software Library in different folders of this share.  For this Package Source change, I'm assuming that I'll need to select "Automatically delete old package files after migration" or else disk usage on the NS and PS could become a problem?

    So guess I've been importing software incorrectly all these years for Migration Wizard to not be able to handle the Software Library?  Don't know if "Software Library" was something I selected from the get-go so when I import s/w, it defaults to this now or if it's an actual default.  Would've been nice if the developers accounted for the Software Library but I know some things are easier said than done.

    BTW, by following KB 204145, will all of my filters get migrated over as well?  Thanks!

    Clint


  • 11.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Oct 19, 2022 01:57 AM

    Hi Clint!

    1. This is user own choice whether to delete packages from old SW Library (better to keep them while they aren't yet copied to a new SMP Server library)
    If you are going to use "Software Library" on new SMP Server using \\{altiris_NEW_server}\Software Library, then you can manually copy \\{altiris_server}\Software Library folder from old SMP to new SMP \\{altiris_NEW_server}\

    After this specify \\{altiris_NEW_server}\Software Library location for "Software Library Configuration" and choose "Change existing packages" option


    Or do not manually copy SW library folder with packages and just change old \\{altiris_server}\Software Library to a new \\{altiris_NEW_server}\Software Library and choose option "Migrate existing packages"

    In case if during migration of packages some error will appear, then UI will show which package is affected and offer to solve this problem

    As example if package doesn't exist in SW library

    Clint: So guess I've been importing software incorrectly all these years for Migration Wizard to not be able to handle the Software Library? 
    IP: No, You are not wrong to use a SW library for packages import. Because all physical packages can be migrated from old SMP to a new SMP via changing SW Library UNC path (if it required to be changed)

    Migration wizard is a tool to export all existing packages only from SMP local drives (not UNC path) of Software management and Patch management solutions and copy/import them all in single "Store.adb" file to a new SMP.

    Clint: BTW, by following KB 204145, will all of my filters get migrated over as well?
    IP: All filters, reports, folder, policies, etc will be preserved, because we are talking about migration of existing "Symantec_CMDB" database as well, so new SMP will be using previous existing database.

    ("Migration wizard" tool doesn't export/import Filters, reports, policies, etc)

    Best regards,
    IP.



    ------------------------------
    [JobTitle]
    [CompanyName]
    [State]
    ------------------------------



  • 12.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Posted Oct 27, 2022 02:43 PM
    A consultant set up our Altiris server years ago so I'm a newbie when it comes to fresh installs.  I'm looking at my Entitlements where one is for ITMS and the two others are for CMS.  When installing 8.6 RU3 via SIM, am I supposed to select both suites?

    Another thing is that my patch/software delivery packages currently all go to the D: drive of the NS (even does this on my task/package server) which I want to do on the new servers as well since these files can potentially take up a huge chunk of disk real estate.  I presume I have to change the path to D: during the install or is this something that's specified after the fact?


  • 13.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Oct 27, 2022 03:03 PM
    Hi Clint,

    You should be able to install just ITMS.  ITMS includes everything included in CMS.  If you have separate license files for both ITMS and CMS, you will want to load both of them.


  • 14.  RE: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements

    Broadcom Employee
    Posted Oct 27, 2022 10:26 PM

    Hi Clint!

    Need to keep same install directory on new Notification Server if you are going to use existing (old) database

    1. Check what install dir is for Symantec Installation Manager on old NS and install SIM in same location on new NS


    2. Check what install directory is for NS it self on old NS server and then install NS in same directory on new NS machine


    3. For remote Package Servers, you can use global settings to set where to store all packages 
    (Of course if Symantec Management agent is already installed in D:\ drive then no need to change these settings, since packages will be stored on D:\ drive automatically)


    Or if there are separate Package Servers which need to use D:\ drive then there is a "Override global policy" for every single Package Server.

    Best regards,
    IP.



    ------------------------------
    [JobTitle]
    [CompanyName]
    [State]
    ------------------------------