Client Management Suite

Hello,

I'm trying to migrate my Software Update Packages from 7.0 to 7.1 and I read:

About migrating Patch Management Solution data

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

I used NSUpgradeWizard installation package that is on my 7.1 and ran it on my 7.0 server.

I exported everything in a .adb datastore.

When I imported that datastore on my 7.1, all packages are copied and not downloaded which is fine but SU tasks are not created.

Is this normal?

Anyone has any info on that please help.

RJ

SU tasks are migrated during the DB reconfiguration process (not through the migration wizard). Check the "About migrating to Symantec Management Platform 7.1" chapter of "ITMS 7.0 migration guide" for details (http://www.symantec.com/business/support/index?page=content&id=DOC3550).

Thanks for your quick reply.

So since we are not doing a DB upgrade I guess that we will have to recreate all the SU Tasks by hand.

RJ

Did you run the PMImport task first?  This needs to be done before you migrate anything patch related.

Why did you choose not to migrate the database, but to still use the Migration Wizard?  I could understand starting clean (new DB new server), or migrating (migrated DB, new server, Migration Wizard for non-DB content), but why do a "mixed" migration of sorts?

You can migrate the DB, just point your SIM to the CMDB, then you can run the PMImport task.

What i did was, migrate the db, pmimport, then i moved the files from the old server c:\Program Files\Altiris\Patch Management\Packages\Updates to the new server, same path.

Did a full resource membership update and it all worked fine.

Regards,

Daniel

Hi,

We are still at CMS 6.0 in production but I had started to recreate our settings on a SMP7 that was supposed to go in production. Since the 7.1 is released, our plans changed. The 7.0 has served a bit as a test bench that is why I only wanted to keep the SU Tasks that we had already created in 7.0.

Because server admins don't want to stage their servers with patches already installed, they count on Altiris to do that for them (I won't comment that...), we have all SU patches still enabled which that makes a lot.

I tought that I would save time by doing "garbage in - garbage out" but I will re-think the whole story.

RJ

Andrew,

It's a shame but I tried to make it in so many ways that I don't even remember if I did a PMImport first...

I think that just for the benefit of the test, I will try it again. :-|

RJ

I imagine it would be less pain to migrate the traditional way, upgrading the database, then remove what you do not want (either pre-migration or post-migration), then to do a mixed migration.