Post-Upgrade Tasks

[Previous] [Next]

Just as this chapter began by outlining some of the more important premigration tasks that need to be considered before upgrading an SMS 1.2 site to SMS 2.0, it now ends with a checklist of post-upgrade tasks that you should consider performing as part of your overall migration strategy:

• Revisit the converted database. Perform consistency checks, back up the database, and test the restore process.
• Configure site settings. Configure site boundaries, enable and configure discovery methods, enable and configure client installation methods, enable and configure the client agents, and identify site systems and assign appropriate roles.
• Check package and program configurations. Consider changing the conversion default of using a compressed version of the package to Always Obtain Files From Source Directory If Applicable. Verify the source directory path, identify distribution points for the package, and confirm program settings and make any changes that are necessary, keeping in mind that unattended command lines are converted to "disabled" programs.
• Create advertisements for your programs. Rebuild any recurring advertisements using the documentation you gathered prior to the upgrade.
• Confirm the membership of your collections created from converted machine groups. Consider changing the membership rules from direct membership (or static, the default after conversion) to membership based on a query in order to make the collection more dynamic and useful. Create new collections as appropriate.
• Re-create any queries you need for the new site. Use the documentation you gathered prior to the upgrade to create the new queries.
• Review your security needs. Configure appropriate object class and instance security for the upgraded site.

As with the premigration checklist, this post-upgrade list represents the more significant items to consider. You can modify this list to suit your own needs and migration strategy.