Trying to update Windows 2003 AD schema to Windows 2008 r2 and get this:

Entry DN: CN=PosixAccount,CN=Schema,CN=Configuration,DC=xxxx,DC=xxx
Add error on line 1519: Unwilling To Perform

The server side error is "Schema update failed: Rdn-Att-Id has wrong
syntax."

An error has occurred in the program

If I edit sch31.ldf and remove the PosixAccount section, it next fails at:

Entry DN: CN=ShadowAccount,CN=Schema,CN=Configuration,DC=xxxxx,DC=xxx
Add error on line 1519: Unwilling To Perform

The server side error is "Schema update failed: Rdn-Att-Id has wrong
syntax."

An error has occurred in the program

If I edit out the ShadowAccount section, the update fails at:

Entry DN: CN=User,CN=Schema,CN=Configuration,DC=xxxx,DC=xxx
Add error on line 2013: Unwilling To Perform

The server side error is "Schema update failed: class in aux-class list does
not exist or is not an auxiliary class."

An error has occurred in the program

And finally here:

Entry DN: CN=User,CN=Schema,CN=Configuration,DC=xxxx,DC=xxx
Add error on line 2013: Unwilling To Perform

The server side error is "Schema update failed: class in aux-class list does
not exist or is not an auxiliary class."

An error has occurred in the program

The two latter sections are tied to the first two, it seems


So, If I remove the 4 failing sections from sch31.ldf and run adprep
/forestprep, it completes successfully and I am able to upgrade my windows
2003 domain controller to windows 2008. My question is what am I breaking by
doing this? The google hits I have followed point to SFU being installed,
and though it isn't installed on any domain controllers now, I can't be sure
that it never was. There is no indication in the schema that it's there
anyway. Any way to fix the error, so I can adprep correctly?

Thanks




~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to