Hi again Ove,
Same comment as before - are you 100% sure this is the way to go with my old server out of comission?
Main Topics
Browse All TopicsI transferred FSMO's and closed down my old server. My new (and now unique) server is not the DC server - so it looks like something went wrong. (My modem/router is actually the DC server)
Q. How do I make this server the domain controller?
(idiots guide please!)
Do I leave the modem/router untouched as a secondary DC (It controlls our IP phone system).
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
OK to make your machine a DC then:
Run DCPROMO from the command prompt, if you are prompted to install DNS then allow this to be installed
If DNS is not installed on the machine, then add DNS manually from the "Configure my server" options
Make sure that the machine is a global catalog server, see http://support.microsoft.c
Make sure that all the clients point at the new machine as their DNS server
I've working from the presumption this is what happened: You had two DCs on your network and transferred the FSMOs from OldDC to NewDC, then powered down OldDC. NewDC is showing errors when you check the FSMO roles.
If - and only if - OldDC will never come back online, you need to seize those roles to NewDC. Follow the directions here: http://www.petri.co.il/sei
The old DC nead to be demoted and cleaned up from AD. If not possibly to take it online and do a normal demote using dcpromo, do a metadata cleanup as described in http://support.microsoft.c
If FSMOs are still on old DC, seize the roles to the DC that's alive by using ntdsutil
http://support.microsoft.c
Yes remove the old server & perform metadata cleanup of removed server.
http://support.micr
http://support.micr
Run dcdiag /v
You need the clients and servers to point to your Domain server for DNS.
You say your router/modem is the domain server.
Your router/modem may provide DHCP and if so will most likely provide DNS.
The problem with your router supplying DNS is that iit will not store the SRV records. The SRV records point the way for your clients to the Authentication server and they are also pointers to other domain services. How do you expect this to be a domain server if your clients and member servers are not pointed to the DNS SRV records???
I,ll bet the DC promotion went fine and your server is the domain server. But, I would be willing to bet your DHCP clients can't find the services your DC provides, (like authentication).
If you have a complete AD database, you have a complete domain. Just disable the router from providing DHCP and enable your Domain server to supply DHCP.
Hi ChiefIT
I think you have understood the problem (yes, one of the clients has to re-map the network drives every time it's booted up!). Otherwise, all clients access the server without problems.
However, the modem/router has to be the DHCP server as we have an IP phone system and the modem/router distributes the IP's to the phones and the clients, so I can't just move DHCP to the server.
Any suggestions for other solutions?
Aha, there's always a gotcha:
I assume your phones are on a different broadcast domain. In that case, they are on a different VLAN or a different router interface. You can support your phones via a Windows DHCP server by allowing your DHCP server to support multiple subnets. This is called a superscope:
Explanation of a superscope:
http://technet.microsoft.c
DHCP uses MAC address broadcasting:
You have probably seen the FF:FF:FF:FF MAC address. Data on these broadcasts are placed on the broadcast IP address this is the address you can't use in an IP space. So, instead of 192.168.1.1-254/24 , I am talking of the broadcast address of 192.168.1.255.
That is a broadcast MAC address. To set up a superscope, your VLANS will be set up as different broadcasts for each subnet. Your DHCP server can then administer both VLANS.
All of this depends upon your topology:
Can you provide it.
Business Accounts
Answer for Membership
by: OvePosted on 2009-11-07 at 02:49:05ID: 25765752
Start -> Run -> dcpromo