![]() You can do this with the Add-DhcpServerV4Scope cmdlet. Now that the DHCP server is authorized, you’ll need to add a scope. ![]() You can view a list of DHCP server that are authorized in AD by running the following command: Note that you don’t need to run this on the DHCP server, you can have someone else with the appropriate privileges run it on a DC.Īdd-DhcpServerInDC -DNSName -IPAddress 172.16.0.50 You can do this by running the PowerShell command (where you substitute in the appropriate FQDN and IP address of the DHCP server that you want to authorize). You’ll need to run the command with an account that has Enterprise Admin privileges in the forest, or is a Domain Admin account in the forest root domain. If you don’t do this, then the DHCP server won’t be able to lease addresses to clients. ![]() ![]() Once you’ve installed a DHCP server on a computer running Windows Server, you need to authorize that server in Active Directory. Install-WindowsFeature DHCP -IncludeManagementTools If you have a new server on which you want to deploy DHCP, just run the PowerShell command: ![]() Most organizations are already going to have DHCP deployed on their servers. This post has been republished via RSS it originally appeared at: ITOps Talk Blog articles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |