Parent Site Change

The Parent Site Change flowchart describes the actions that take place when an administrator attaches a site to a parent site. The effect of the described activity in the “Discovery Data Manager: Parent Site Change” flowchart is to pass all information in a primary site’s database to its new parent site.

The described activity in this flowchart takes place on the primary site server after an administrator has used the SMS Administrator console to attach the primary site to a parent site. The flowchart is the same whether the site had a different parent site before the change or never had a parent site before.

Tracing Information

You can trace the activity described in this flowchart by studying the status messages for the server components listed in the table below. Or, you can enable the log files for these components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about viewing status messages and enabling logging, see “Status Messages Versus Logging” in Chapter 16, “Introducing the SMS 2.0 Flowcharts.”

Table 17.6 Status Message Components and Log Files for Discovery Data Manager: Parent Site Change

Troubleshooting Tips

If DDRs and inventory from clients are not being reported to a new parent site:

• Verify that the parent site information and address are correct. To do so, navigate to <site code - site name> in the SMS Administrator console:

  Systems Management Server   Site Database (site code - site name)      Site Hierarchy         site code - site name

  Right click site code - site name in the console tree and click Properties.

• Verify that the account (under Site Settings, Addresses in the SMS Administrator console) used to access the site has the appropriate permissions.
• Verify that the parent site has adequate disk space to store the data.
• Examine the status messages for Discovery Data Manager and Inventory Data Loader to verify that they have attempted to send the data to the parent site.
• Examine the Ddm.log file on the client site to determine whether:
  • Discovery Data Manager started the evaluation process on all DDRs in the database, based on the new parent assignment.
  • Discovery Data Manager created DDRs for each discovered resource in the database.
  • The DDRs created by Discovery Data Manager were passed to Replication Manager to send to the new parent site.
• Verify that Discovery Data Manager created notification files (*.sha) and placed them in the following directories:

Table 17.7 Directories for Discovery Data Manager Notification Manager

These notification files tell the respective processes that a new parent site has been assigned and that it should forward inventory data, after it is processed locally, to the new parent site.

• Verify that the parent site is processing the DDRs properly.