IT Management Suite

We have a client that will be migrating their AMS and CMS to a new location.

Their naming convention is based per location (e.g. PHL-L001 for Philippines and SG-L001 for Singapore) as well as they have different subnets per location.

I have already called the support and been advise that I cannot restore the Symantec_CMDB if i will not use same hostname and IP for the new server.

Any advise guys on how can I preserve the data especially on AMS (asset status tagging, location, etc.) as well as other modules of CMS?

Thank you in advance!

Hi Marilou,

a few questions here:

1. From which version of AMS and CMS you are going to migrate them to a 7.6?
2. Migration in your case means that current AMS and CMS will be working while you are restoring previous AMS and CMS databases backup on a new SQL Server hardware and install AMS and CMS 7.6 on a new hardware as well?

Regards,

IP.

Hi IP,

1. No version change will be done, client is using version 7.6. We will retain same version on new Notification Server.

2. Will it be possible for us to restore the database of old NS DB to a new NS DB that has different name and IP? 

We need to have the old NS and new NS both up and running as we will do the migration (moving of clients) by sites (client have 5 sites). Main goal of activity is to have exact replica of old NS (content and functionality).

Regards,

Marilou

Hi Marilou,

some other questions:

1. You want to preserve same GUID of managed clients after their redirection from old NS to a new NS?
2. Do you a have a "Cloud Enabled Management" functionality enabled on old NS?
3. Do you know that asset status, locations, etc aren't replicable by stand-alone replication rules? You already have another way how to migrate all asset related data from old NS to a new NS?

Thanks,

IP.

Hi IP,

1. Can you share with me what will be the effect if GUID remains or changed? I think as long as the solutions for CMS and AMS is working we are good. Base on this article http://www.symantec.com/docs/HOWTO10372 it will change (UniqueID (generated by the Notification Server)).

2. CEM is not enabled.

3. I don't have a knowledge on how we will retain the data on AMS. It's one of the main reason that we would like to preserve the data as the client already put in tons of effort to tag the status and information on their assets.

Below are the proposed tasks that I have for the migration activity after installing same solution and versions on new NS:

Let me know your thoughts on this.

Thank you,

Marilou

Hi Marilou,

in case of new installation of 7.6 release on a new hardware with new database creation, it will requires all necessary data migration from existing 7.6 environment to a new 7.6 environment, using different methods, such as stand-alone replications or export/import, DS drivers adding and re-creation of WinPE, NS and Site Servers settings chaging, migration of packages using "SWD replicator" tool and physical packages migration using "Migration Wizard"

Asset Management Solution data with their associations should be also migrated but there were problems that Data Connector wasn't able to do this - You can check this discussion about similar case: https://www-secure.symantec.com/connect/forums/partial-migrate-data-old-ns-new  . And stand-alone replication rule will not be able to replicate asset data, since asset resources aren't replicable.

******************************************************************************************

Seems like a better way will be to just take backup of currently running "Symantec_CMDB" database from both 7.6 servers and use them for a new 7.6 installation on a new hardware, to avoid manual migration of asset management data as well as for software packages, reports, tasks, etc.

1. Take "Symantec_CMDB" databases backup from current SQL Servers - 7.6 environment and download these backups on a new SQL Server(s) - Hardware

This KB has information about "Symantec_CMDB" database backup/restore from SQL Server to SQL Server

• https://support.symantec.com/en_US/article.HOWTO109671.html

Notes:

• Make sure that a new SQL Server has supported version for 7.6 release and it's version isn't lower than SQL Server where you took "Symantec_CMDB" database backup.
• Make sure that a new SQL Server has same SQL Collation as previous SQL Server where you took "Symantec_CMDB" database backup, otherwise if SQL Collation is different between new SQL Server and database backup, then you will not be able to use it for 7.6 installation.

2. Install "Symantec Installation Manager" on new NS - hardware and choose 7.6 release for installation.

• On step of "Install Readiness Check" you will MigrationPackage (If you don't have it, then please ask tech support to provide it for you)
• On step where to specify SQL Server and database name, choose your new SQL Server instance where you've restored "Symantec_CMDB" database backup and choose "Use existing Database" ⇒ start 7.6 installation.

Once 7.6 will be installed/configured on new NS hardware and using existing "Symantec_CMDB" database 7.6 on a new SQL Server hardware, then install required 7.6 Hot Fix.

3. Now you will have all same data available with their asset associations, etc on a new hardware. Just don't forget to configure/modify other things, like:

• Pay attention that now on new 7.6 NS you have "old" Package Server(s) and Task Server(s) which are connected and working with an old 7.6 NS! So you have to remove unnecessary Site Server(s) from new 7.6 NS and install a new Package Server(s) and Task Server(s) which will be working with a new 7.6 NS and will serve managed client computers. Otherwise, if you will have "non-existing" Site Server(s) available on Site Server Management page of new 7.6 NS, then other new Site Servers and managed clients will try to communicate with them with no success.

• Once you have new Package Server(s) installed for new 7.6 NS, you have to copy all physical packages/images from previous 7.6 NS to a new 7.6 NS environment (You can use "Migration Wizard" to get all physical packages from "Software Management Solution" and "Patch Management Solution" and export them into a "Store.adb" file, which can be delivered to a new 7.6 NS and imported there). Make sure that when all physical packages are downloaded on a new 7.6 NS, you have run "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" and "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}" scheduled tasks to update their information in database.

• Review and modify "Site Server(s)" and their settings, because in a new location you have different subnets, etc so otherwise setup required Site Services to manage/serve client computers from a new 7.6 environment. Don't forget that if you will don't remove Site Servers
• Check that your NS settings, such as proxy, mail smtp, etc are correct.

Note:

Check that you have correct "Communication Profile" specified in "Agent install" page! If there is a "Communication Profile" of previous 7.6 NS, then change it to a new profile of a new 7.6 NS, otherwise all push installation of SMA will redirect clients to an old NS 7.6 server.

4. For existing managed client computers redirection, you can export "Communication Profile" of new 7.6 NS and import it on old 7.6 NS machine, then create separate "Targeted Agent Settings" and choose there a new 7.6 NS communication profile ⇒ once managed clients will receive new settings, they will try to connect and register with a new 7.6 NS machine.

Thanks,

IP.

Hi IP,

Thank you for the detailed response on my query.

A few clarifications:

May I confirm that the new hardware/NS and database you are discussing have different hostname and IP to the old/existing setup?

Will the database can be safely use even though the tables/information in it have already been tagged/used the hostname and IP address of old NS and DB in most of its content?

For the migration wizard, I have read that this tool is applicable to migrate lower version of ITMS to the newer version. Can we also use this in migrating ITMS with same version?

Thank you,
Malou

Hi Marilou,

1. Yes. New CMS/AMS 7.6 will be running on a new hardware with new IPv4 as well as their new SQL Server.

Don't forget that this is not a new installation with new "Symantec_CMDB" database creation, but just restoring of existing "Symantec_CMDB" database backup on a new SQL Servers and CMS/AMS 7.6 installation using existing database in SIM option.

2. Owner of all resources in database will be changed from old CMS/AMS 7.6 to a new CMS/AMS 7.6 hostname.

• As example, you will see there your new CMS/AMS 7.6 hostname as "Source" of all resources, instead of old CMS/AMS 7.6 hostname, otherwise this will be a new NSOwner of resources in DB.

3. Yes, you can use "Migration Wizard" to export/import appropriate data (data which is supported for export/import by MigrationWizard tool) between same version of 7.6.x servers

4. Please pay attention to use a same installation directory path as it is on old CMS/AMS 7.6 servers.

• For example if old CMS/AMS 7.6 is installed in C:\Program Files\Altiris\     then use the same installation path on a new CMS/AMS 7.6 server, when you will be installing a "Symantec Installation Manager" there.

Thanks,

IP.

Hi IP,

Thank you very much for your effort and guidance.
Will give you an update as soon as we have successfully done the migration.
Thank you once more for your help in this matter.

Regards,
Malou
 

Hi IP,

An update for this:

- Client have a open discussion that they will be replacing AMS with ServiceNow.

- The initial scope of work will be reduce. No backup will be needed from the existing setup.

I appreciate the assistance support you’ve given me.

Regards,
Malou