Now, let’s get a better safety net in place!
I’ve got a good, reliable PowerEdge 2650 that was donated by another IT guy (thanks Jim!) It’s been humming right along, waiting for
something to break an opportunity to take on some further roles.
My PE2650 is a Windows Server 2003 R2 box. ‘Dorothy’ is a tired old Windows Server 2003 SP2 box (as are my other servers). To make the PE2650 a domain controller, I need to:
- Extend the AD Schema to accomodate 2003 R2’s new functionality
- Add the PE2650 as a Domain Controller
Step 1: Extend the schema
- Log onto ‘Dorothy’ as a schema admin
- Use this excellent TechNet article to extend the schema. Read carefully and follow every step
note: I had no issues extending the schema, and the directions were spot-on. Why re-invent the wheel?
Step 2: Add the PE2650 as a Domain Controller
- Log onto the PE2650 (w/ admin rights)
- Follow this excellent Petri article to add the PE2650 as a domain controller
note: I did not have to restart the netlogon service