The DHCPserver module is not one that is backported - and certainly not to WMF3/PS3. If they're not currently AD-Integrated, and there is some reason that you are unable to tick that box, you can still easily migrate (without powershell) The process is detailed here, but the short thing is that you just export each of the zones using the dnscmd utility, and then you copy the resulting zone files to the root dns folder on the new server. and replicated among all Domain Controllers. If the zones are AD-Integrated, then - just like GPOs - all of the DNS data is contained in NTDS.dit. Well, if you're following best (and easiest) practices, you'll be running AD-Integrated Primary Zones (if you're not, its easy enough to switch them to AD-Integrated - assuming all DNS servers are DCs). The links and details of the GPO are contained in NTDS.dit - the Active Directory database - and is replicated automatically among all Domain Controllers. You simply add a domain controller, and the GPO gets replicated.
They live in AD and SYSVOL which is automatically replicated among all Domain Controllers in a domain by either FRS or DFS-R (likely the former in your case). I hate to break it to you, though, you really don't have that much work to do. So it was definitely smart to keep that in mind when planning this out. Well, in all honestly Powershell isn't going to do anything for you though, it is true that there are appropriate cmdlets on the latest OS that definitely can achieve these tasks. I also have to migrate DNS and DHCP for 4 different vlans.
I figured if I used PowerShell I would be easier.
0 kommentar(er)
