IT Management Suite

I was watching some videos from the 7.5 User Summit on upgrading to 7.5 (http://www.symantec.com/connect/articles/75-summit-november-2013-implementing-cms-presentation) and it was mentioned that it was a best practice to run a custom SQL statement that disabled all policies/jobs/tasks prior to the upgrade and then to rerun a modified version of the SQL statement once the upgrade was complete to re-enable all of the previously disabled policies/jobs/tasks.

Can anyone tell me if this is still best practice for upgrading to 7.6?  Does anyone have this SQL statement, if it is, and help me know how to best use it?

I've asked Symantec but they don't know where to find this information any longer.

You can click on the hyper link "here" in the article which points to:

http://video.symantec.com/services/player/bcpid2947612088001?bckey=AQ~~,AAAACltotjE~,tv_QJdXkOoerwW8ezQ3qWkVdFUSVfdO4

The videos in question are on the Lessons Learned tab.

Publicis Experience 1:34

Q&A 1:10

Any help is appreciated.

Thanks,

Vaughn

Hi Vaughn,

Although you can do that, all I have usually done is isolate IIS so that it nly accepts traffic from localhost as well as its actual IP address, as this cuts out comms to all nodes except for the SMP's own SMA. 

If you did want to do this, you would need to target the ItemActive table I believe.  Best approach would be to copy its contents into a temp table, set all 1 entries to 0, and then after the upgrade simply copy the contents from the temp table back to the modified table.

Scott.