Andre P
asked on
How do I migrate DNS from SBS2k8 to Server 2k12 Step by step .
I have an SBS server in production and a Server 2012 on the network as a DC . I have already migrated dhcp to the 2012 server .
The next step I would like to accomplish is to have the 2012 server be the DNS server for computers on the network .
It is bascally one network with a satellite office which connects via site to site vpn How do I make this happen and transfer the information and the function to the Server 2012 ?
I have already installed the dns role on the 2012 server .
Step by step please ?
Thanks !
The next step I would like to accomplish is to have the 2012 server be the DNS server for computers on the network .
It is bascally one network with a satellite office which connects via site to site vpn How do I make this happen and transfer the information and the function to the Server 2012 ?
I have already installed the dns role on the 2012 server .
Step by step please ?
Thanks !
ASKER
"You just update clients and DHCP."
How do I do that ?
How do I do that ?
That depends on your clients. Updating a network printer with a static IP is different for each brand and model. Plus computers. Plus OSes. Same with DHCP.
These are *basic* IT skills. If you need a walk you through that level of detail, you should hire someone. Trying to do it yourself is a food way to break your production network in very bad ways.
These are *basic* IT skills. If you need a walk you through that level of detail, you should hire someone. Trying to do it yourself is a food way to break your production network in very bad ways.
ASKER
Oh i know how to do that but shouldnt the DHCP update the clients settings when they get a new lease ?
I was asking how to have the clients know that the server 2012 is the DNS and not the SBS server .. Where do I change that ?
I was asking how to have the clients know that the server 2012 is the DNS and not the SBS server .. Where do I change that ?
If the clients have DNS staticly configured then you change it on the client. If they have DNS dynamically assigned then you change the DNS Server Option in the DHCP scope.
ASKER
nothing is statically configured except the server
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A few things aren't clear...
1. Did you install the 2012 Server as a DC? If you did then DNS is already installed and configured on the DC.
2. If #1 is done, then you just add it to your DHCP scope - or modify the DHCP scope. This is BASIC server administration. If you're not familiar with it, then you must not understand, truly what DHCP does. Because you would go to your DHCP server and just change the scope properties.
If you don't understand this stuff, you can choose to take offense or you can spend some time learning Windows Administration and Networking/Network administration. Neither should be done in a post or two on a forum, but rather, using lab environments, research, and asking questions about your test environment that won't potentially shut down your production environment if someone here provided the wrong information or you misunderstood.
Sorry, I know I can be blunt at times... the number of times I walk into messed up network because the technician who may understand Windows 7,8,10 great, doesn't understand servers or networks and has messed things up is too numerous for me to count.
1. Did you install the 2012 Server as a DC? If you did then DNS is already installed and configured on the DC.
2. If #1 is done, then you just add it to your DHCP scope - or modify the DHCP scope. This is BASIC server administration. If you're not familiar with it, then you must not understand, truly what DHCP does. Because you would go to your DHCP server and just change the scope properties.
If you don't understand this stuff, you can choose to take offense or you can spend some time learning Windows Administration and Networking/Network administration. Neither should be done in a post or two on a forum, but rather, using lab environments, research, and asking questions about your test environment that won't potentially shut down your production environment if someone here provided the wrong information or you misunderstood.
Sorry, I know I can be blunt at times... the number of times I walk into messed up network because the technician who may understand Windows 7,8,10 great, doesn't understand servers or networks and has messed things up is too numerous for me to count.
If you've stick to defaults.