Changes to Hierarchy Design

  • Article

During the design phase it is important to understand what can later be changed in your hierarchy, after your SMS 2003 implementation. This section lists supported and unsupported post-deployment activities.

SMS 2003 does not support the following post-deployment activities:

  • Changing the disk drive letter on which SMS is installed

  • Moving the SMS site database from a remote location to the SMS site server

  • Important:

    • You can move the SMS site database from the site server to a remote server running SQL Server, or you can move the SMS site database from one remote server to another remote server. However, after you have moved the SMS site database from the site server, you cannot move it back.

  • Changing the site code

  • Changing the site name

  • Changing the computer name of the site server

  • Changing the parent site of a secondary site

  • Moving the SMS Provider from the site server to a remote server

  • Note:

    • The SMS Provider always stays where it was originally installed, either on the site server or on the computer running SQL Server. If the SMS Provider is first installed on a remote computer, and the SMS site database is later moved to a different remote computer running SQL Server, then the SMS Provider must move with it.

SMS 2003 supports the following post-deployment activities:

  • Moving the SMS site database from the site server to a remote server (the SMS Provider must remain on the site server)

  • Moving the SMS site database from a remote server to another remote server

For information about how to perform these moves, see the Microsoft Systems Management Server 2003 Operations Guide.

For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com