Add-DhcpServerv4Scope

Add-DhcpServerv4Scope is accessible with the help of DHCPServer module. To configure DHCPServer, go through this link.

Synopsis

Description

The Add-DhcpServerv4Scope cmdlet adds an IPv4 scope on the Dynamic Host Configuration Protocol (DHCP) server service with the specified parameters.

Parameters

-ActivatePolicies

Specifies the enabled state of the policy enforcement on the scope that is added.

-AsJob

Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell background jobs, see about_Jobs.

-CimSession

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.

-ComputerName

Specifies the DNS name, or IPv4 or IPv6 address, of the target computer that runs the DHCP server service.

-Confirm

Prompts you for confirmation before running the cmdlet.

-Delay

Specifies the number of milliseconds by which the DHCP server service should wait before responding to the client requests. Specify this parameter if the scope is part of a split scope deployment and this DHCP server service should act as a secondary DHCP server service for the scope being added.

-Description

Specifies the description string for the IPv4 scope that is added.

-EndRange

Specifies the ending IP address of the range in the subnet from which IP addresses should be leased by the DHCP server service.

-LeaseDuration

Specifies the time interval for which an IP address should be leased to a client in this scope. This should be specified in the format day.hrs:mins:secs.

-MaxBootpClients

Specifies, if the scope type is specified as Both to allow for both DHCP and BootP clients, the maximum number of BootP clients which should be leased an IP address from this scope.

-Name

Specifies the name of the IPv4 scope that is added.

-NapEnable

Specifies the enabled state of Network Access Protection (NAP) for this scope. If NAP is enabled, then the DHCP server service passes the statement of health (SoH) received from the client to the network policy server (NPS). Based on the NAP profile set, the NPS determines the network access to grant to the client.

-NapProfile

Specifies that the NAP profile should be set only if NAP is enabled on the scope. The NAP profile refers to the MS Service Class which is a condition used in network policies on NPS.

-PassThru

Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.

-StartRange

Specifies the starting IP address of the range in the subnet from which IP addresses should be leased by the DHCP server service.

-State

Specifies the state of the scope when it is created. The acceptable values for this parameter are: Active and Inactive. Only an active scope responds to client requests. The default value is Active.

-SubnetMask

Specifies the subnet mask for the scope specified in IP address format. For example: 255.255.255.0.

-SuperscopeName

Specifies the name of the superscope to which the scope is added.

-ThrottleLimit

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.

-Type

Specifies the type of clients to be serviced by the scope. The acceptable values for this parameter are: DHCP, BootP, or Both. The type of the scope determines whether the DHCP server service responds to only DHCP client requests, only BootP client requests, or Both types of clients.

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Syntax

————————EXAMPLE 1————————
PS C:>Add-DhcpServerv4Scope -Name “dev-jenk Net” -StartRange 192.168.10.1 -EndRange 192.168.10.254 -SubnetMask 255.255.255.0
This example adds a new scope for 192.168.10.0/24 subnet on the DHCP server service running on the local computer.

————————EXAMPLE 2————————
PS C:>Add-DhcpServerv4Scope -ComputerName dhcpsrv.TOSSolution.com -Name “dev-azure Net” -StartRange 192.168.11.1 -EndRange 192.168.11.254 -SubnetMask 255.255.255.0 -State InActive -NapEnable
This example adds the specified inactive scope for 192.168.11.0/24 subnet on the DHCP server service. The scope is enabled for NAP.

————————EXAMPLE 3————————
PS C:>Add-DhcpServerv4Scope -Name “2nd floor Network” -StartRange 192.168.12.1 -EndRange 192.168.12.254 -SubnetMask 255.255.255.0 -SuperScope “Expanded 2nd floor Network”
This example adds a new scope for 192.168.12.0/24 subnet on the DHCP server service running on the local computer. The scope is added as part of the superscope named Expanded 2nd floor Network.

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Add-DhcpServerv4Scope

You can also read about

To know more PowerShell cmdlets(Commands) on DHCPServer click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft