Today I’m going to investigate the cool new cmdlets for managing the DHCP server!<\/p>\n
Oh I wish I had these at my last job! We were deploying new workstations and imaging systems. For this to work, I needed to send a Wake on Lan to the workstations. The problem was that I didn’t have SCCM on the remote sites and the WAN wasn’t passing the packets.<\/p>\n
So I figured I could use Windows PowerShell and a cool Wake on Lan script from Marcus Van Orsow (\/\\\/\\0\\\/\\\/) running on the remote servers and my local one to do the trick. I combined this with a DHCP parsing trick from The Admin Guy. For the original post of this solution, see Powershell–Wake on LAN from \/\\\/\\o\\\/\\\/ and DHCP Parse from “The Admin Guy”–WHAT A COMBO!<\/a><\/p>\n I was happy with the solution, but at the time, I really wished that there was an easier way to work with DHCP. Now there is!<\/p>\n One of the challenges was to get a list of the available scopes in my original solution. In Windows Server 2012 R2, you can run the following cmdlet to get a list of available scopes in your DHCP server:<\/p>\n Get-DHCPServerv4Scope<\/p>\n As you can see, all of the details about this scope can be easily identified—even exported for documentation!<\/p>\n Get-DHCPServerv4Scope | Export-CSV C:\\Foo\\ContosoScopes.CSV<\/p>\n But here’s where Windows PowerShell rocks even more. What I can do now for modern day servers is use the cmdlets to build out a DHCP server.<\/p>\n First create a new scope. We’ll pick a pretty simple configuration:<\/p>\n Name ‘Sample’<\/p>\n Description ‘My Sample Scope Description’<\/p>\n Network 192.168.1.0<\/p>\n Subnet Mask 255.255.255.0 (24 bits)<\/p>\n Starting 192.168.1.100<\/p>\n Ending 192.168.1.200<\/p>\n We can do this in one line with Windows PowerShell:<\/p>\n Add-DhcpServerv4Scope -Name ‘Sample’ -StartRange 192.168.1.100 -EndRange 192.168.1.200 You can also edit the options for your scope with the same cmdlets. To make things easier, you can get a list of the available options defined in your DHCP server by using the Get-DHCPServerv4OptionDefinition<\/b> cmdlet:<\/p>\n Get-DHCPServerv4OptionDefinition<\/p>\n So I can find the names I can use for options pretty easily:<\/p>\n Get-DHCPServerv4OptionDefinition | where { $_.Name –like ‘*DNS*’ }<\/p>\n We can obtain the name we can use for the router option in the same manner:<\/p>\n Get-DHCPServerv4OptionDefinition | where { $_.Name –like ‘*Router*’ }<\/p>\n Now we can add options to our new scope by leveraging the Set-DHCPServerv4OptionValue<\/b> cmdlet. But instead of using the name, we need to use the OptionID<\/b> provided for the name. To add a router IP of 192.168.1.1 to our current scope called ‘Sample’, we’d do it like this in Windows PowerShell:<\/p>\n $id=(Get-DHCPServerv4Scope | Where { $_.Name –eq ‘Sample’ }).ScopeID<\/p>\n Set-DHCPServerv4ScopeOptionValue –Scope $Id –optionid 3 –value 192.168.1.1<\/p>\n Now that we have the ID, we can set up the DNS servers for this scope. We’ll use two internal servers 192.168.1.5 and 192.168.1.25:<\/p>\n Set-DHCPServerv4ScopeOptionValue –Scope $Id –optionid 6 –value 192.168.1.5,192.168.1.25<\/p>\n What’s interesting with this cmdlet is you can’t put in a false DHCP server. It will validate that it’s a live server first!<\/p>\n Now thinking back to my original problem with DHCP servers, I could have easily pulled out the current list of leased IP addresses from all of my scopes by doing something as simple as this and storing them into a CSV file:<\/p>\n Get-DHCPServerv4Scope | Get-DHCPServerv4Lease | Export-CSV CurrentIP.csv<\/p>\n Pretty cool, eh?<\/p>\n Pop back over tomorrow for our final day of Windows PowerShell Network Week, and we’ll play with going where no cmdlet has boldly gone before: Easily managing a DNS server!<\/p>\n I invite you to follow the Scripting Guys on Twitter<\/a> and Facebook<\/a>. If you have any questions, send an email to the Scripting Guys at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then just remember, the Power of Shell is in You.<\/p>\n Sean Kearney<\/b>, Windows PowerShell MVP, Honorary Scripting Guy<\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Manage DHCP server settings in Windows Server 2012 R2 with Windows PowerShell. Honorary Scripting Guy, Sean Kearney, is here. This weekend, I’m getting a little geeky. I’m going to continue with more of Windows PowerShell and the network cmdlets. This is the sixth part in a series called Windows PowerShell Network Week. You also […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[56,37,154,61,45],"class_list":["post-1622","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-guest-blogger","tag-networking","tag-sean-kearney","tag-weekend-scripter","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Manage DHCP server settings in Windows Server 2012 R2 with Windows PowerShell. Honorary Scripting Guy, Sean Kearney, is here. This weekend, I’m getting a little geeky. I’m going to continue with more of Windows PowerShell and the network cmdlets. This is the sixth part in a series called Windows PowerShell Network Week. You also […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1622","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=1622"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/1622\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=1622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=1622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=1622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/5277.1.png\" "\\"Image")
<\/a><\/p>\n
–Description ‘Sample for 192.168.1.0’ -SubnetMask 255.255.255.0<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/83060.2.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/0726.3.png\" "\\"Image")
<\/a>
<\/b><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/4760.4.png\" "\\"Image")
<\/a><\/p>\n