Connect with experts and redefine what’s possible at work – join us at the Microsoft 365 Community Conference May 6-8. Learn more >

DHCP

29 Topics

How to Manage DHCP using PowerShell
Learn how to create and configure DHCP scopes, manage leases and reservations using PowerShell.
OrinThomas
Aug 01, 2019 Place ITOps Talk Blog
61KViews
6likes
0Comments
Edit subnet mask or scope in dhcp server running in windows server - Solved
it's not possible to directly change the subnet mask of an existing DHCP scope in a running Windows DHCP server. Here are the steps: 1. Export the Existing Scope Configuration: Open a command prompt with administrative privileges. Type the following command to export the scope configuration to a text file: netsh dhcp server \\<DHCP_Server_Name> scope <Scope_IP_Address> dump > C:\dhcp.txt 2. Modify the Configuration File: Open the dhcp.txt file in a text editor. Locate the line that specifies the subnet mask (e.g., SubnetMask 255.255.255.0). Change the subnet mask to the desired value. Save the changes to the file. 3. Delete the Old Scope: In the DHCP management console, right-click the scope you want to modify and select "Delete." 4. Import the New Scope: In the command prompt, type the following command to import the modified configuration: netsh exec c:\dhcp.txt 5. Verify the Changes: In the DHCP management console, check if the scope has been re-created with the new subnet mask. Right-click the scope and select "Properties" to confirm the subnet mask change. (Major Point - Ensure that your existing network address and subnet network address remain the same after making changes. If they are not the same, you need to modify the entire network address in the text file. For example, if the original subnet is 255.255.255.0 and the network address is 10.1.10.0, and you change it to 255.255.252.0, then the network address should also be updated to 10.1.8.0. Therefore, you must replace all instances of 10.1.10.0 with 10.1.8.0 in the entire text file (using Ctrl+H for the replacement). Thats it....
ARUNKRISHNARR
Jan 12, 2024 Place Windows Server for IT Pro
30KViews
2likes
2Comments
Upgrading 2012 R2 to 2019 Domain Controller / DFRS / DNS / DHCP
Hi All, Looking for some advice been a while since I have had to do an upgrade of the domain controllers but I just want to get people advice on the plan I have put in place to do this: Current setup is as follows: Domain Controller Operating System Functional Level FRS / DFRS Other Functions ROLE DC1 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP PDC / RID POOL MANAGER DC2 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP DC3 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP SCHEMA MASTER / DOMAIN NAMING MASTER DC4 Microsoft Windows Server 2012 (64-bit) Windows Server 2012 R2 FRS DNS / DHCP INFRASTRUCTURE MASTER The aim is to upgrade all servers to 2019 and upgrade their functional level to 2016R2 and also if possible or easier keep the existing IP's and Names. Things I need to try and avoid if possible: - No downtime (or minimal) - No impact on live services if possible i.e clients etc - In place upgrading So In terms of the high level plan it was as follows: - Upgrade/Migrate to DFRS on all existing DC's - Create 4 new servers running 2019 i.e DCNEW1, DCNEW2, DCNEW3, DCNEW4 install Active directory and add as a DC Member - Migrate the FSMO Roles to the corresponding new server i.e DC1 > DCNEW1 DC2 > DCNEW2 etc etc - Migrate DHCP / DNS to an other server - Demote the old DC's from AD - Rename / Re-IP the new DC's to the old DC's name and IP address. (I believe I will need to demote the new DCs i.e DCNEW1 and move the FSMO Roles to another server, rename and re-ip the DC to DC1 give it the same ip address, add it as a DC member and then move the FSMO roles back onto it and then repeat this process for each other DC) Some questions i have: Do I really need to upgrade to DFRS 1st ?? or can this be avoided? In a very high level plan, does this sound about right? or am I overthinking or missing anything. Is there a much slicker way to achieve my goal? In order to move a DHCP server I recall just exporting the DHCP scopes exporting/importing using "netsh dhcp server export C:\dhcp.txt all" If I want to move DNS is there anything else i need to consider other than installing the DNS Role? How would anyone else approach this? Help appreciated! Thanks
Solved
Samuel_Caunt
Oct 22, 2021 Place Windows Server for IT Pro
11KViews
1like
4Comments
Windows Server 2022 as Domain and DHCP Server
Hi, Windows Server 2022 announced. There are many IT Executives or Organizations who use Windows Server only for DNS Server, DHCP Server, managing network resources and implementing group policies. For this purpose, if we compare Windows Server 2012R2, Windows Server 2016, Windows Server 2019 and Windows Server 2022; can we find any differences? Moreover, for those executives or organizations, does it matter Windows Server 2022 announced? Please let us know differences in Windows Server from above perspectives. With Regards NndnG
NndnG
Aug 24, 2021 Place Windows Server for IT Pro
2.9KViews
1like
1Comment