Hi I am trying to run extadsch.exe on my Windows 2008 R2 x64 server. This is prior to intall SCCM 2007 R3. I get error messages when trying I have tried to reboot and do the "regsvr32 schmgmt.dll" command as explained in another thread here on this forum. Any suggestions?

8202 translates to "The specified directory service attribute or value does not exist" and 8235 to "A referral was returned from the server" - whatever that may mean in that context ;-) Did you make sure that the user running extadsch.exe is a member of the schema admins (domain admins is not enough; but that would most likely result in another error message) and that you were not running into a UAC issue?Torsten Meringer | http://www.mssccmfaq.de

I think this issue has to do with that I'm not completely follwing the procedure according to microsoft. It says "unplug the network cable...". What I am doing is that I shut down the server and move it from the server room (cold and noisy). Then I place it on my desk and starts it up. What happens now when I start it up is that it's trying to reach it's "buddies" with no response. This generates a whole lot of warnings and errors in both event viewer and dcdiag. I shall now try this the correct way. This will cause (I think) the other servers to find out that the schema master is offline and then vote for a new temporary schemamaster. The actual schema master will then accept the update and when I reconnect it it will replicate the updates.

Please check if the Domain Admins has the permission to access the child objects of the System Managment Container in AD For additional viewing you might want to check out these sites: http://technet.microsoft.com/en-us/library/bb633121.aspx http://technet.microsoft.com/en-us/library/cc431377.aspx Hope it helps.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

There usually is no need to disconnect / isolate the DC before upgrading the schema. I've never heard about the ConfigMgr schema breaking anything.Torsten Meringer | http://www.mssccmfaq.de

Yes, maybe I'm a bit paranoid. But with so much errors I have had then I am doing it the "kosher"-way.

This issue is now solved after I went on a Microsoft-course. The thing is to unplug or disable the NIC and not to shut the server down. One must be 100% sure of that you have the correct FSMO-roles, logged on as a schema administrator and that the AD is in good shape. Also you need a system state backup. By the way. My teacher at the course told me specifically to have the DC unplugged since if you get an error it replicates the error.