It is strongly recommended that you test your SMS site database upgrade before upgrading your production SMS site. If your live SMS site database upgrade fails, it leaves your SMS site in an inoperable state. If you have done any of the following, your database upgrade is more likely to require manual modification prior to a successful upgrade. In these circumstances, testing the database upgrade prior to upgrading SMS in your production environment is essential: 1. Any modifications to the SMS hardware inventory MOF 2. Any modifications to the SMS site database: a. Additional triggers b. Additional columns in tables c. Additional stored procedures 3. Any use of IDMIFS or NOIDMIFS in your SMS hierarchy 4. Any third party or internal tools that modify the SMS database Test Database Upgrade Procedure NOTE: Running Setup.exe /TestDBUpgrade is a destructive process. Do NOT run this test on a production SMS site database. You can test a database upgrade by using a copy of the SMS site database with the Setup /TestDBUpgrade switch. Perform this procedure on a copy of your SMS 2003 SP1 or later database. The procedure is as follows: 1. Back up the production SMS site database. (Refer to your SQL Server documentation for instructions on how to make a backup of a SQL Server database). 2. On a test computer that is running the same version and collation of SQL Server, restore the SMS site database. You do not have to install SMS on the test computer. 3. If you have been using SQL replication on your SMS Database, you must remove the extra columns added by replication prior to upgrade to this service pack. (Please refer to the following Knowledge Base Article for details: http://support.microsoft.com/?id=835860) 4. Put the Configuration Manager 2007 media into the DVD drive of the test computer 5. From the SMSSETUP\BIN\I386 folder on the Configuration Manager 2007 DVD, run: Setup.exe /TestDBUpgradeThe TestDBUpgrade command-line option runs the SQL portion of the Configuration Manager 2007 upgrade process. The results of this test indicate how successful the actual production database upgrade to Configuration Manager 2007 will be. If you do not see the message, "SMS Setup completed successfully" at the end of the log file, your SMS site database is not ready for upgrade, and you should not proceed with your SMS site upgrade.
It is recommended that you either exclude files that are encrypted, compressed or located in the Windows directory. Inventorying ...
It is recommended that you fill in all package properties for status Management Information Format (MIF) matching. If the ...
It is recommended that you fill in all status MIF matching fields. If the fields are empty, the source program for the status ...
It is recommended that you fill in the status MIF matching fields. If the fields are empty, the source program for the status ...
It is strongly recommended that you test your SMS site database upgrade before upgrading your production SMS site. If your ...
Join our Customer Experience Improvement Program and help improve the quality, reliability and performance of Configuration ...
licenses of "%2" (ProdRef="%3") were removed from the license store on the site server but could not be added to the software ...
licenses of "%2" (ProdRef="%3") were removed from the software metering server "%4" but could not be added to the site server ...
Local license balancing has stopped until "%1" license(s) of "%2" (ProdRef="%3") are placed back into the software metering ...