Public keys are not removed after you detach a child site in Systems Management Server 2003 (886012)
The information in this article applies to:
- Microsoft Systems Management Server 2003
SYMPTOMSAfter
you detach a child site in Microsoft Systems Management Server 2003, the
following conditions are true:
- On the child site, the file that contains the parent site's
public key is not removed from the SMS\inboxes\hman.box\pubkey folder. (This
file is Site_name.pkp.)
- On the parent site, the file that contains the child site's
public key is not removed from the SMS\inboxes\hman.box\pubkey folder. (This
file is Site_name.pkc.)
CAUSEThis problem occurs because the public key files,
Site_name.pkp and
Site_name.pkc, are
not deleted when you detach a child site. WORKAROUNDTo work around this problem, you can manually remove the
Site_name.pkp and
Site_name.pkc files from the
SMS\inboxes\hman.box\pubkey folders.
However, if the site hierarchy is
more than two levels deep, it becomes difficult to reliably clean up the keys
from grandparent or grandchild sites because of the lack of site hierarchy
information. In this case, you can keep these public key files on the
sites. The key files are harmless and use only 240 bytes per site.STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.REFERENCESFor more information about public keys, visit the following
Microsoft Web site:
Modification Type: | Minor | Last Reviewed: | 6/14/2005 |
---|
Keywords: | kbSMS2003spfix kbSMS2003bug kbsmsAdmin kbprb KB886012 kbAudITPRO |
---|
|