Get-DhcpServerv4Policy

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

Synopsis

Gets one or more policies at the server level or the scope level.

Description

The Get-DhcpServerv4Policy cmdlet gets one or more policies at the server level or the scope level.

If the Name and ScopeId parameters are specified, then the policy from the specified scope is retrieved.

If only the ScopeId parameter is specified, then all of the policies in the specified scope are retrieved.

If only the Name parameter is specified, then that specific server level policy is retrieved.

If neither the Name nor the ScopeId parameter is specified, then all of the server level policies are retrieved.

Parameters

-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 Dynamic Host Configuration Protocol (DHCP) server service.

-Name

Specifies one or more names of the policies to return.

-ScopeId

Specifies the scope identifier, in IPv4 address format, from which the policies are retrieved. If you do not specify this parameter, the server level policies are retrieved.

-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.

Syntax

Get-DhcpServerv4Policy [-ComputerName <String>] [[-Name] <String[]>] [[-ScopeId] <IPAddress>] [-CimSession <CimSession[]>] [-ThrottleLimit <Int32>] [-AsJob] [<CommonParameters>]

—————–EXAMPLE 1—————–
PS C:>Get-DhcpServerv4Policy -ComputerName dhcpsrv.TOSSolution.com -Name PrinterPolicy
This example gets the policy properties for the policy named PrinterPolicy that is defined as a server level, or server-wide, policy.

—————–EXAMPLE 2—————–
PS C:>Get-DhcpServerv4Policy -ComputerName dhcpsrv.TOSSolution.com -Name AdminPolicy -ScopeId 192.168.1.0
This example gets the policy properties for the policy named AdminPolicy that is defined inside the scope 192.168.1.0.

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

Get-Command Get-DhcpServerv4Policy

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