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]
------------------------------
Original Message:
Sent: Oct 18, 2022 04:19 PM
From: Clinton Watarai
Subject: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements
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
Original Message:
Sent: Oct 18, 2022 12:19 AM
From: Igor Perevozchikov
Subject: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements
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]
Original Message:
Sent: Oct 17, 2022 09:00 PM
From: Clinton Watarai
Subject: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements
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?
Original Message:
Sent: Sep 09, 2022 11:39 AM
From: Roy Brooksby
Subject: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements
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
Original Message:
Sent: Sep 07, 2022 06:27 PM
From: Clinton Watarai
Subject: Upgrade 8.1 RU7 to 8.6 RU3 System Requirements
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?