Article ID: 833179 - View products that this article applies to.
When you try to run the Hierarchy Maintenance Utility (the Preinst.exe tool) in Microsoft Systems Management Server (SMS) 2003 together with a user account that does not have explicitly defined rights, the command appears to run. However, there areno results.
If you run the Preinst.exe tool against a child site, you may receive the following error message:
Note child site code is the name of the SMS 2003 child site.
child site code not a known site
This behavior occurs when you try to run the Preinst.exe tool by using a user account that belongs to a group that has been granted permissions to the Site class in SMS. In this case, even though the user account is a member of a group that has permissions to the Site class, the user may require explicit permissions to the Site class. The Preinst.exe tool queries the SMS Security Rights table in Microsoft SQL Server to verify permissions. Group membership is not verified. Therefore, if the user account is not explicitly defined in the SMS Security Rights table, this problem may occur. For example, this problem may occur if rights are set at the group level.
To resolve this issue, explicitly grant administrator level rights for the SMS Site class to the user account. Alternatively, you may log on by using another account that is explicitly defined and has administrator level rights for the Site class.
To grant the user account that is used to run the Preinst.exe tool explicit permissions to the Site class in SMS 2003, follow these steps:
SMS security rights may be set for a user account through the SMS Administrator Console.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/199869/ )SMS: Assigning class and instance security rights with the SMS User Wizard
For more information about the Preinst.exe tool, search the SMS 2003 Online Library. To do this, follow these steps:
Article ID: 833179 - Last Review: October 27, 2006 - Revision: 2.1
Contact us for more help