sms: sms 2003 sp2 schema extension

so you ran the schema extension you say, and it ran so fast that you didn't notice it had finished? if you're upgrading from SMS 2003 to SP2, the included schema "extension" doesn't do very much at all. in fact, from a practical standpoint, nothing is extended. an existing attribute is linked to an existing class. if you're a sms administrator and can't convince your ad administrators to run it, just show them this. here's a log of a proper run:

<03-30-2006> Modifying Active Directory Schema - with SMS extensions.
<03-30-2006> DS Root:CN=Schema,CN=Configuration,DC=bladerunner,DC=int
<03-30-2006> Attribute cn=MS-SMS-Site-Code already exists.
<03-30-2006> Attribute cn=mS-SMS-Assignment-Site-Code already exists.
<03-30-2006> Attribute cn=MS-SMS-Site-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Roaming-Boundaries already exists.
<03-30-2006> Attribute cn=MS-SMS-Default-MP already exists.
<03-30-2006> Attribute cn=mS-SMS-Device-Management-Point already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Name already exists.
<03-30-2006> Attribute cn=MS-SMS-MP-Address already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
<03-30-2006> Attribute cn=MS-SMS-Ranged-IP-High already exists.
<03-30-2006> Class cn=MS-SMS-Management-Point already exists.
<03-30-2006> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=bladerunner,DC=int.
<03-30-2006> Class cn=MS-SMS-Server-Locator-Point already exists.
<03-30-2006> Class cn=MS-SMS-Site already exists.
<03-30-2006> Class cn=MS-SMS-Roaming-Boundary-Range already exists.
<03-30-2006> Successfully extended the Active Directory schema.

i've marked the relevant lines you need to look for in your schema log. you can check this manually too with the active directory schema snap in (schmmgmt.msc). under classes, locate mSSMSManagementPoint. take a look at the optional attributes. you should see dNSHostName now.