/cdupgrade <secondary site code>

This command, which you run from the parent site, upgrades a secondary site by using installation source files that are local to the secondary site (on a hard disk, network drive, or CD-ROM drive). It does not cause the parent site to send files to the secondary site because it assumes that the necessary files are available at the secondary site.

Use this option to upgrade failed sites if a global upgrade fails to upgrade all secondary sites. If a secondary site upgrade has failed, use the /deljob option (described later in this table) to prevent the parent site from trying to upgrade it.

/deinstall <secondary site code>

This command, which you run from the parent site, removes the specified secondary site from a site hierarchy.

If you want to remove a secondary site from a site hierarchy, first try to remove it by using the Configuration Manager console.

/deljob <site code>

This command, which you run from the source site, deletes all outbound traffic that is targeted to the destination site. This includes the deletion of all jobs, or commands, that are targeted to the specified site.

/delsite <removed child site code> <parent site code>

This command, which you run from the parent site, deletes incorrectly removed child sites from the site database of the parent site.

Use this option if you removed a site before you detached it from its parent. This transaction does not propagate up the site hierarchy to all parent sites of the current site.

Note
The /delsite command does not uninstall the site referred to by <removed child site code>. It merely removes the site information from the local Configuration Manager 2007 site database.

/dump <site code>

This command, which you run from the local site server, writes site control images to the root folder of the drive on which the site is installed.

/dump <site code> writes the site control image only for the specified site.

/dump writes the site control files for all sites.

An image is a binary representation of the site control file, which is stored in the Configuration Manager 2007 site database. The dumped site control file image is a sum of the base image plus the pending delta images.

After dumping a site control file image with the Hierarchy Maintenance tool, the file name is in the format sitectrl_<sitecode>.ct0.

/stopsite

This command, which you run from the local site server, initiates a shutdown cycle for the Configuration Manager 2007 Site Component Manager service, which partially resets the site.

When this shutdown cycle is run, some Configuration Manager 2007 services on a site server and its remote site systems are stopped. These services are flagged for reinstallation.

As a result of this shutdown cycle, some passwords are automatically changed when the services are reinstalled.

Note
If you want to see a record of shutdown, reinstallation, and password changes for Site Component Manager, enable logging for this component before using this command-line option.

After the shutdown cycle is started, it proceeds automatically, skipping any nonresponding components or computers. However, if the Site Component Manager service cannot access a remote site system during the shutdown cycle, the components that are installed on the remote site system are reinstalled when the Site Component Manager service is restarted.

When it is restarted, the Site Component Manager service repeatedly attempts reinstallation of all services that are flagged for reinstallation until it is successful.

You can restart the Site Component Manager service using Service Manager. After it is restarted, all affected services are uninstalled, reinstalled, and restarted. After you use the /stopsite option to initiate the shutdown cycle, you cannot avoid the reinstallation cycles after the Site Component Manager service is restarted.

/syncchild <site code>

This command, which you run from the parent site, synchronizes a child site with its parent site.

This command simulates a child site attachment so that all the components at the current site are triggered by a site attachment notification for the specified child site, thereby updating the child site.

For example, under this command, the Collection Evaluator sends all collection information and package definitions to the child site.

/syncparent

This command, which you run from the child site, forces all site control images in the site database to simultaneously propagate up to the parent site of the current site. This propagation includes the site control images of all child sites stored in the site database of the current site. Additionally, collected client discovery and inventory data is replicated to the parent site, and inventory resynchronization requests are triggered for any Systems Management Server (SMS) 2003 Advanced Clients assigned to the site.

Use this option when sites are out of synchronization due to time lags or other failures. Because secondary sites have no site database on which the Hierarchy Maintenance tool can operate, stop and restart the SMS Executive service instead of using the /syncparent command for a secondary site. This forces the current site control image for the secondary site to be forwarded to the parent site.

/upgrade <secondary site code>

This command, which you run from the parent site, upgrades a secondary site. Use this option to upgrade failed sites if a global upgrade fails to upgrade all secondary sites.

If a secondary site upgrade has failed, use the /deljob option to prevent the parent site from trying to upgrade it.

/keyforparent

This command, which you run on a site, is used to distribute the site's public key to a parent site.

The /keyforparent command places the public key of the site in the file <site code>.CT4 at the root of the program files drive.

After you run this command, manually copy the <site code>.CT4 file to the parent site's hman.box inbox (not hman.box\pubkey).

/keyforchild

This command, which you run on a site, is used to distribute the site's public key to a child site.

The /keyforchild command places the public key of the site in the file <site code>.CT5 at the root of the program files drive.

After you run this command, manually copy the <sitecode>.CT5 file to the child site's hman.box inbox (not hman.box\pubkey).

/childkeys

This command can be run on a recovering site's child sites. It is used to distribute public keys from multiple child sites to the recovering site.

The /childkeys command places the key from the site where the command is run, and all of that sites child sites public keys into the file <site code>.CT6.

After you run this command, manually copy the <site code>.CT6 file to the recovering site's "hman.box" inbox (not hman.box\pubkey).

/parentkeys

This command can be run on a recovering site's parent site. It is used to distribute public keys from all parent sites to the recovering site.

The /parentkeys command places the key from the site where the command is run, and the keys from each parent site above that site, moving up the hierarchy, into the file <site code>.CT7.

After you run this command, manually copy the <site code>.CT7 file to the recovering site's "hman.box" inbox (not hman.box\pubkey).