Migrating Hardware Inventory Customizations
SMS and Configuration Manager use Managed Object
Format (MOF) files for hardware inventory. These files are substantially
different in Configuration Manager from those in SMS 2003. The data classes defined by
ConfigMgr 2007 are now defined in the configuration.mof file, whereas
the reporting classes are specified in the SMS_Def.mof file. This means
that you will need to separate out any custom classes defined in your
SMS 2003 SMS_Def.mof or mini-MOF files and then add the appropriate MOF
language to each of the ConfigMgr .mof files.
Before the upgrade, copy your SMS_Def.mof file
and any mini-MOF files you are using to a separate location to avoid
them being overwritten. After the upgrade completes, use a text editor
to open and edit the .mof files.
If you have custom classes defined in your SMS 2003 SMS_Def.mof file or in mini-MOF files, you can use the #pragma namespace
compiler directives in the file to locate the data and reporting
classes for these definitions. The SMS 2003 SMS_Def.mof file uses a #pragma
namespace
compiler directive to instruct the compiler to use a particular
namespace. Most custom data classes extract data from the root\CINV2 WMI
(Windows Management Instrumentation) namespace.
In general, you can locate data classes in the SMS_Def.mof or mini-MOF by searching for the #pragma namespace root\CINV2 directive. You should append the block of text following this directive to the end of the configuration.mof file (without the #pragma namespace directive itself). You will find the corresponding reporting class definitions under the #pragma namespace root\CINV2\sms. These should be copied to the SMS_Def.mof file.
Interoperability Considerations
Although you can upgrade SMS 2003 SP 2 sites
directly to ConfigMgr 2007, you should upgrade them to SP 3 if you plan
to maintain SMS 2003 sites for a significant period. ConfigMgr clients
running Windows Vista will not function correctly if they roam to SMS
2003 SP 2 sites. In addition, SMS 2003 SP 2 clients cannot roam to
ConfigMgr sites in native mode.
SMS 2003 SP 2 is no longer supported based on the
Microsoft support life cycle. You should therefore upgrade any SP 2
sites and clients to SP 3 or ConfigMgr 2007 as soon as possible to
continue to receive support and software updates.
In a mixed environment, you will use the SMS 2003
Administrator console to administer SMS 2003 primary sites and the
ConfigMgr console to administer ConfigMgr primary sites. If you have
secondary sites running SMS 2003, you will be able to administer them
through the parent primary site; however, you will not be able to change
the accounts or passwords used by these secondary sites. You will also
not be able to create or configure Remote Access Service (RAS) senders
or configure Active Directory Security Group Discovery on SMS 2003
secondary sites with ConfigMgr parent sites.
Troubleshooting Upgrade Issues
If you encounter any failures during the setup
process, you should check the setup log at c:\ConfigMgrSetup.log for any
error messages. Some common upgrade issues include the following:
You receive the following error message:
Cannot insert the default site control image to the database.
ConfigMgrSetup.log contains the entry “error xp_SMS_notification not
found.”
This generally occurs when you have
reinstalled SQL Server on the site database server and the
xp_SMS_notification extended stored procedure was removed during setup.
To correct this problem, use the procedure described in http://support.microsoft.com/kb/556084 to re-create the extended stored procedure.
Setup
fails while attempting to install the SMS Provider. ConfigMgrSetup.log
contains the entry “CompileMOFFile: Failed to compile MOF.”
This generally results from an incorrect AD Service Principal Name (SPN) registration.
Upgrading
a secondary site may fail when using local source files if the
bootstrap process is unable to locate the installation files in the
correct path or if there is a version mismatch.
SMS_Bootstrap.log will show errors locating the install.map file or an incorrect build number in install.map.
Setup fails to correctly detect the type of site you have installed.
This may be the result of previous failed upgrade attempts or incorrect information in the site server registry.
The
SMS SQL Monitor service is no longer required in Configuration Manager
2007 SP 1. You should disable or delete this service after the upgrade
to avoid misleading error messages at logon, in the system event log,
and in the ConfigMgr status message system.
One way to delete the service is to use the SC.EXE Windows Resource Kit tool with command line SC delete SMS_SQL_Monitor. For information about SC.EXE, see http://technet.microsoft.com/en-us/library/bb490995.aspx. After you delete the service, you can manually remove the following Registry keys:
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\COMPONENTS\SMS_SITE_COMPONENT_MANAGER\Component Servers\<servername> \Components\SMS_SQL_MONITOR
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Tracing\SMS_SQL_MONITOR
If Setup completes successfully, you should
review the site status to make sure all systems and components have an
OK status, or investigate any errors or warnings that have occurred.
