Im a work-study student at a community college working for the network admin. We run Netware 6.5 (its old old) and plan to migrate to AD over the summer. We have a very old box running Server 2k3 acting as the primary DNS server and sole DHCP lease agent. It also acts as the sophos AV enterprise console. Its slow.
We have a newer box he had me setup S2k3 on (all hardware here is old, he was concerned about driver issues on 2k8). In doing some searching I have created the forward and reverse lookup zones and had them transferred from the primary box. The idea is to lose the primary box and use this newer box as the primary dhcp/dns/sav server.
I was also instructed, during setup, to join the "new" S2k3 box to the DC we have running. The DC box has DNS and DHCP and File Server roles installed, but none are fully configured and the box is basically completely unused at this point.
Issue 1:
Im using the following link for DHCP migration.
http://support.microsoft.com/kb/325473
It appears to have worked fine and the new box has the proper DHCP scopes and such from the old DHCP box. I *cannot* "authorize" DHCP on the new box, however. Im sure theres a good, logical reason for this (probably haveing something to do with importing the data from the other box or some such), but I have no idea what it is or what to search for to find it.
While Im at it, is there a way to export the DHCP information into a readable format? Im also documenting the network and such for this place and thats obviously something that I want documented, so doing it easy instead of by hand would be nice
Issue 2:
Im going by this for DNS migration
http://articles.techrepublic.com.com/5100-10878_11-5084484.html
I have created the forward and reverse lookup zones and they have transfered fine from the old box. The new box is acting as a secondary DNS server now (under testing) and seems to be operating fine.
Im not sure of the best way to do the migration for the DNS to make the new box the primary and ditch the old box. The DHCP leases are for something like 3 days. Can I just drop the old box offline, bring up the new one with the same IP as the old box and expect things to work without a hitch? I cant see why not, but again, Ive never dealt with most of this before.
Also, what will be the difference between a standard primary zone and an AD-integrated zone? Again, the AD server isnt really....doing anything. It could be taken down and moved or outright replaced at some point before the migration is made in the summer. Considering the specs, I could just as well suggest that we decomission that box and make this one Im working on the DC *shrug*
Issue 3:
There is a box that was already a backup DNS server. He would like to keep it that way when we switch the old DNS/DHCP box out. He would also like to use this box as a backup DHCP server (with a different scope on all the lease ranges). What considerations do I need to make for this when I swap out the old DNS/DHCP box for the newer one?
Any input, suggestions, help or pointers are welcome. Sometimes Im just not sure exactly what to look or search for. Thanks.
We have a newer box he had me setup S2k3 on (all hardware here is old, he was concerned about driver issues on 2k8). In doing some searching I have created the forward and reverse lookup zones and had them transferred from the primary box. The idea is to lose the primary box and use this newer box as the primary dhcp/dns/sav server.
I was also instructed, during setup, to join the "new" S2k3 box to the DC we have running. The DC box has DNS and DHCP and File Server roles installed, but none are fully configured and the box is basically completely unused at this point.
Issue 1:
Im using the following link for DHCP migration.
http://support.microsoft.com/kb/325473
It appears to have worked fine and the new box has the proper DHCP scopes and such from the old DHCP box. I *cannot* "authorize" DHCP on the new box, however. Im sure theres a good, logical reason for this (probably haveing something to do with importing the data from the other box or some such), but I have no idea what it is or what to search for to find it.
While Im at it, is there a way to export the DHCP information into a readable format? Im also documenting the network and such for this place and thats obviously something that I want documented, so doing it easy instead of by hand would be nice
Issue 2:
Im going by this for DNS migration
http://articles.techrepublic.com.com/5100-10878_11-5084484.html
I have created the forward and reverse lookup zones and they have transfered fine from the old box. The new box is acting as a secondary DNS server now (under testing) and seems to be operating fine.
Im not sure of the best way to do the migration for the DNS to make the new box the primary and ditch the old box. The DHCP leases are for something like 3 days. Can I just drop the old box offline, bring up the new one with the same IP as the old box and expect things to work without a hitch? I cant see why not, but again, Ive never dealt with most of this before.
Also, what will be the difference between a standard primary zone and an AD-integrated zone? Again, the AD server isnt really....doing anything. It could be taken down and moved or outright replaced at some point before the migration is made in the summer. Considering the specs, I could just as well suggest that we decomission that box and make this one Im working on the DC *shrug*
Issue 3:
There is a box that was already a backup DNS server. He would like to keep it that way when we switch the old DNS/DHCP box out. He would also like to use this box as a backup DHCP server (with a different scope on all the lease ranges). What considerations do I need to make for this when I swap out the old DNS/DHCP box for the newer one?
Any input, suggestions, help or pointers are welcome. Sometimes Im just not sure exactly what to look or search for. Thanks.
Facebook
Twitter