the attribute cannot be modified because its owned by the system
finally i have found how to modify a setting, but after doing this in ADSIEDIT, the message shows up:
"the attribute cannot be modified because its owned by the system"
what could be here the reason now?
"the attribute cannot be modified because its owned by the system"
what could be here the reason now?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
are you sure about the correct path in the registry? i cannot find NTDS in services...
This method I found on the Internet, regarding yur problem.
Hope this helps.
Login as a member of Schema Admins (preferably on the Schema Master FSMO)
Launch LDP.EXE
Connect to the Schema Master FSMO using LDP.EXE
Bind to the Schema Master using an account with Schema Admin permissions.
From the Browse menu, choose Modify
In the Modify dialog box, leave the DN field blank, and type schemaUpgradeInProgress in the Attribute field. In the Value field, enter the number 1. Click the Enter button, then click the Run button.
Close the Modify dialog box.
Launch ADSIEDIT.MSC and modify the mAPIID values for the necessary attributes. (You may need to wait for the Active Directory to replicate.)
Run LDP again, and change the value of schemaUpgradeInProgress from 1 to 0.
From the Active Directory Schema console, right click on the console and choose "Reload the Schema"
Hope this helps.
Login as a member of Schema Admins (preferably on the Schema Master FSMO)
Launch LDP.EXE
Connect to the Schema Master FSMO using LDP.EXE
Bind to the Schema Master using an account with Schema Admin permissions.
From the Browse menu, choose Modify
In the Modify dialog box, leave the DN field blank, and type schemaUpgradeInProgress in the Attribute field. In the Value field, enter the number 1. Click the Enter button, then click the Run button.
Close the Modify dialog box.
Launch ADSIEDIT.MSC and modify the mAPIID values for the necessary attributes. (You may need to wait for the Active Directory to replicate.)
Run LDP again, and change the value of schemaUpgradeInProgress from 1 to 0.
From the Active Directory Schema console, right click on the console and choose "Reload the Schema"
Hi,
Sorry, there was a typo omit. The setting should be changed on your DC most preferably on your schema master.
Regards,
Sekhar
Sorry, there was a typo omit. The setting should be changed on your DC most preferably on your schema master.
Regards,
Sekhar
ASKER
ill check quick if it works. really curious...
ASKER
not working. i rebootet teh schema master DC,but still cannot modify that setting
ASKER
very frustrating,it still damn doesnt work...i cannot edit that setting
engeltje's suggestion works 100% perfect. Thanks Mate!!
This worked Great for us, adding the regkey and than adding the LDP command in resolved our 2003 > 2008 R2 Migration issues.
Thankyou engeltje
Thankyou engeltje
ASKER