SMS 2003 SP1 Win2003 SP1 upgrade to SMS 2003 SP2 Schema issue...

SMS 2003 SP1 Win2003 SP1 upgrade to SMS 2003 SP2 Schema issue...

Post by TWF0d » Fri, 24 Feb 2006 06:39:26


I've just completed the upgrade to SMS 2k3 SP2 and worked my way through the
DCOM issues with no problems. I am seeing other issues, the schema update
adds support for the dNSHOSTNAME attribute, however I'm getting errors report
that they can not update the attribute. I have manually run the schema
extender with the following results:

ExtADsch.log

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

after this point the errors didn't go away on further investigation I
noticed that the schemaIDGUID didn't match what the upgrade should be and ran
the ldifde.exe with the file sms2003sp2_ad_schema.ldf

as per ldf file

# schemaIDGUID: 72e39547-7b18-11d1-adef-00c04fd8d5cd
schemaIDGUID:: R5Xjchh70RGt7wDAT9jVzQ==

Following error in the ldif.log

Importing directory from file "sms2003sp2_ad_schema.ldf"
Loading entries
1: cn=DNS-Host-Name,cn=Schema,cn=Configuration,dc=lzb,dc=hq
Entry DN: cn=DNS-Host-Name,cn=Schema,cn=Configuration,dc=lzb,dc=hq
Add error on line 22: Referral
The server side error is "A referral was returned from the server."
0 entries modified successfully.
An error has occurred in the program

On checking cn=MS-SMS-Management-Point,cn=Schema,cn=Configuration,dc=X The
[mayContain] attribute contains dNSHOSTNAME

What can I do to fix this?!

Would the following fix the issue in an import ldf file

dn: cn=DNS-Host-Name,cn=Schema,cn=Configuration,dc=X
changetype: modify
# schemaIDGUID: 72e39547-7b18-11d1-adef-00c04fd8d5cd
schemaIDGUID:: R5Xjchh70RGt7wDAT9jVzQ==

As all the other attributes read correctly....

Thanks in Advance!
 
 
 

SMS 2003 SP1 Win2003 SP1 upgrade to SMS 2003 SP2 Schema issue...

Post by Wonderboo » Fri, 24 Feb 2006 23:46:39

oes the server have rights to modify the AD objects?

"Matt" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...



 
 
 

SMS 2003 SP1 Win2003 SP1 upgrade to SMS 2003 SP2 Schema issue...

Post by Kim Oppalf » Tue, 28 Feb 2006 16:38:23

hat exactly is the issue you are describing?
I see an axtadsch.log that successfully exits, and that mentions that a lot
off the attributes already existed, which is quite normal.


--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Matt" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...