Microsoft
Software
Hardware
Network
Question : "The Directory Service was unable to allocate a relative identifier." when adding machines to AD
"The Directory Service was unable to allocate a relative identifier."
Oh jeepers I think I might have got a tad out of my depth with this one :( Seriously worried, about this one. Let me give you a bit of background history...
- I virtualised a Domain controller.
- Rebuilt the hardware with a fresh copy of Server 2008
- Imported the virtual machine and put it on line, everything was working great.
- I migrated the roles across as per advice below, Think I left both as writable DC's if its relevant I dont know?
http://www.experts-exchang
e.com/Soft
ware/Serve
r_Software
/
File_Serv
ers/Active
_Directory
/Q_2482694
3.html
- Performed a restore of the new DC using Symantec System restore and now...
"The Directory Service was unable to allocate a relative identifier."
I am unable to add at least one machine to the new domain, and I strongly suspect I wont be able to join any for that matter. I am also suddenly unable to join a Linux based NAS to which I suspect is related.
I might need a bit of hand holding with this one I am afraid
Answer : "The Directory Service was unable to allocate a relative identifier." when adding machines to AD
This has been resolved with a system restore. Bit of a sledge hammer to crack a wallnut but still :(
Random Solutions
Extract a CBitmap from a CImageList
How do you remotely access environment variables via Computer Management in Windows Vista?
sorting in views
List Box with multi columns
dbcc loginfo ( a details explaination )
SQL creating table relationship trouble
Visual Studio creates an error in my rc file every time I change a menu
OL 2003 - My macro causes "this outlook session contains macros" warning
DCPROMO fails when existing DC's are on different subnet / segment
Query over multiple fields