Hello all,
This is my first question that I'm posting and it really got me going for days now. I'm pretty new at Systems Management Server 2003 and I'm trying to do some tests with a client.
First of all, I'm using Advanced Security. We have a domaincontroller up and running and a second server (lets call it SMS1) where SMS2003 en MSSQL is running. On the client and the SMS server all firewalls are disabled for the moment. First a quick summary of the options:
- The site is called "VLK" with Site Bounderies my domain (test.company.be), "Publish to Active Directory" is enabled.
- Client Push Installation is enabled for workstations (advanced client), with the SMSSITECODE=AUTO option.
- SMS1 has following roles: SMS Client Access Point; SMS Component Server; SMS Distribution Point; SMS Management Point; SMS Reporting Point; SMS SQL Server; SMS Server Locator Point; SMS Site Server.
- Site System Status is marked as OK.
- Component Status is marked as OK.
Now, I installed the Advanced Client on my testmachine via the Client Push Installation Wizard (right-clicked the testmachine in the All Systems collection). The client is installed on the testmachine but now starts the trouble.
In the list of the "All Systems" collection, the testclient appears as not assigned and not installed. So I double checked on the client, went to the Systems management properties and there I noticed that the SMS Site is empty. I pressed the "Discover" button and then I get the error: "Automatic site code discovery was unsuccesful".
I started searching on the internet and found some possible sollutions, but nothing helps:
- From
http://support.microsoft.com/kb/925282Troubleshooting post-installation issues
The SMS Advanced Client is installed successfully, but does not appear as installed or assigned
1. You must verify that the SMS Agent Host service is running on the client. If the SMS Agent Host service is not running, the client may not send a heartbeat discovery record to report that the client is installed and assigned.
I checked it and the SMS Agent Host is started.
2. Double-click the SMS Client Control Panel item on the SMS Advanced Client computer, and then click the Advanced tab in the Systems Management Properties box. If no site code is listed, click Automatically Discover. If the discovery fails, it may be because of one or more of the following reasons:
" The Active Directory schema has not been extended for SMS 2003. If you ran ExtADSch.exe manually to extend the Active Directory schema, the ExtADSch.log file will contain information about the Active Directory update and whether Active Directory was extended successfully. This log file is located in the root of the system drive.
I reran the ExcADSch.exe file and got following output in my log:
<11-09-2007 10:03:46> Modifying Active Directory Schema - with SMS extensions.
<11-09-2007 10:03:46> DS Root:CN=Schema,CN=Configur
ation,DC=t
est,DC=com
pany,DC=be
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Site-Code already exists.
<11-09-2007 10:03:46> Attribute cn=mS-SMS-Assignment-Site-
Code already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Site-Boundaries already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Roaming-Boundari
es already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Default-MP already exists.
<11-09-2007 10:03:46> Attribute cn=mS-SMS-Device-Managemen
t-Point already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-MP-Name already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-MP-Address already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
<11-09-2007 10:03:46> Attribute cn=MS-SMS-Ranged-IP-High already exists.
<11-09-2007 10:03:46> Class cn=MS-SMS-Management-Point
already exists.
<11-09-2007 10:03:46> Located LDAP://cn=MS-SMS-Managemen
t-Point,CN
=Schema,CN
=Configura
tion,DC=te
st,DC=comp
any,DC=be
<11-09-2007 10:03:46> Successfully updated class LDAP://cn=MS-SMS-Managemen
t-Point,CN
=Schema,CN
=Configura
tion,DC=te
st,DC=comp
any,DC=be.
<11-09-2007 10:03:46> Class cn=MS-SMS-Server-Locator-P
oint already exists.
<11-09-2007 10:03:46> Class cn=MS-SMS-Site already exists.
<11-09-2007 10:03:46> Class cn=MS-SMS-Roaming-Boundary
-Range already exists.
<11-09-2007 10:03:46> Successfully extended the Active Directory schema.
I checked the permissions ans SMS1 has full control over the System and System Management container. So this seems OK in my eyes?
" SMS site systems have not been published in Active Directory. You can view \SMS\Logs\Sitecomp.log on the SMS Server to see whether the SMS site systems have been published. For more information about how to grant permissions on the System Management container in Active Directory, click the following article number to view the article in the Microsoft Knowledge Base:
830022 (
http://support.microsoft.com/kb/830022/) Status message 4909, 4912, 4913, or 4915, or error code 8202 after you install Systems Management Server 2003
To verify the Active Directory Publication I followed the steps in the "Active Directory Schema Modification and Publishing for Systems Management Server 2003" white paper on page 11-12.
.
" The server locator point cannot be located. The SLP must be published in Active Directory or registered in WINS in non-Active Directory environments.
This is in the same document as the Active Directory Publication info.
All the attributes are in place. So there no problem I hope?
So now I'm here, hoping someone with more experience could point me in the right direction. If you have any more questions sure ask them. I hope my explenation was clear enough.
Greetings,
Steven Bruneel
Start Free Trial
