Parent and child sites cannot communicate after you upgrade to SMS 2003 (832107)


The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

After you upgrade a Microsoft Systems Management Server (SMS) 2.0 child site to SMS 2003, an SMS 2003 central site may no longer accept package data from the upgraded child site. For example, this behavior occurs in the following scenario:
  1. You have two SMS 2.0 Service Pack 4 (SP4) sites. Site A01 is the central site, and site A02 is the child primary site.
  2. You upgrade the A01 central site to SMS 2003. In the A01 Site Properties dialog box, you click to select the Require secure key exchange between sites check box on the Advanced tab. You also make sure that the Do not accept unsigned data from sites running SMS 2.0 SP4 and earlier check box is cleared.

    After the upgrade, the child site (A02) can still communicate with A01, because A01 is configured to accept unsigned data.
  3. You then upgrade child site A02 to SMS 2003. After the upgrade, A02 cannot communicate with A01.

CAUSE

This issue occurs because the child site does not automatically transfer its security key to the parent central site.

WORKAROUND

To work around this issue, manually transfer the key file from the child site to the parent site. To do this, follow these steps:
  1. On the child primary site, click Start, and then click My Computer.
  2. Double-click the drive where SMS is installed.
  3. Open the SMS\Inboxes\Hman.box\pubkey folder.
  4. Copy the public key file in this folder to a different location. For example, copy the public key file to the SMS\Inboxes\Hman.box folder on the central site.

STATUS

This behavior is by design.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbUpgrade kbsetup kbinterop kbSecurity kbnofix kbBug KB832107 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.