DHCP - Report for all DHCP scopes with detail

-

Script for DHCP scope report:


$DHCP_Scopes = Get-DhcpServerv4Scope –ComputerName FQDN -ErrorAction Stop

           #$DHCP_Scopes = $Null

    $output = Foreach ($DHCP_Scope in $DHCP_Scopes) {

        # Going through the scopes returned in a given server

        $DHCP_Scope_Stats = Get-DhcpServerv4ScopeStatistics -ComputerName FQDN -ScopeId $DHCP_Scope.ScopeId

        [PSCustomObject] @{

            'DHCP Server'    = $DHCP_Server.DNSName

            'DHCP IP'        = $DHCP_Server.IPAddress

            'Scope ID'       = $DHCP_Scope.ScopeId.IPAddressToString

            'Scope Name'     = $DHCP_Scope.Name

            'Scope State'    = $DHCP_Scope.State

            'In Use'         = $DHCP_Scope_Stats.InUse

            'Free'           = $DHCP_Scope_Stats.Free

            '% In Use'       = ([math]::Round($DHCP_Scope_Stats.PercentageInUse, 0))

            'Reserved'       = $DHCP_Scope_Stats.Reserved

            'Subnet Mask'    = $DHCP_Scope.SubnetMask

            'Start Range'    = $DHCP_Scope.StartRange

            'End Range'      = $DHCP_Scope.EndRange

            'Lease Duration' = $DHCP_Scope.LeaseDuration

        }

    }

    $output | export-csv $env:userprofile\desktop\DHCP-REPORT.csv


Comments

Post a Comment

Popular posts from this blog

Service Principal Names (SPNs) SetSPN Syntax (Setspn.exe)

-
Image
Service Principal Names (SPNs) SetSPN Syntax (Setspn.exe) Table of Contents SPN Purpose SPN Format SetSPN Viewing or Checking SPN Registrations SPN Registration Errors Related to SPN Registration or Configuration Manually Registering SPNs Troubleshooting SPN Issues Resolving SPN Registration Issues SPN Lookup Errors Delegation External Articles SPN Purpose A service principal name (SPN) is the name by which a Kerberos client uniquely identifies an instance of a service for a given Kerberos target computer. If you install multiple instances of a service on computers throughout a forest, each instance must have its own SPN. A given service instance can have multiple SPNs if there are multiple names that clients might use for authentication. For example, an SPN always includes the name of the host computer on which the service instance is running, so a service instance might register an SPN for each name or alias of its host. ↑  Return to Top
Read more

Azure Fix for "the VM is generalized" start-up error in Microsoft Azure

-
Image
How to fix the below error, it works for when followed the below steps. 1) Go to the "Disks" page in the Azure Portal: 2) Click on the disk that is attached to the generalized VM. 3) Then click "Create Snapshot", and fill in the form: 4) After the snapshot is generated, go to the Disks page, and click "Add". 5) Fill in the "Create managed disk" form, and make sure to select your newly created Snapshot as Source: 6) After the new disk is created, click on it to see details. Then click the button "Create VM": 7) Create the VM as you would normally do. Done!
Read more

Troubleshooting SCEP certificate profile deployment to Android devices in Microsoft Intune

-
Image
Introduction This guide provides an architectural overview of SCEP certificate profile deployment to Android devices in Microsoft Intune, including how to verify that each step is successful. It also provides troubleshooting suggestions for some of the most common issues that you may encounter during the deployment process. It's assumed that you have configured the NDES server, the Trusted Root profile and SCEP profile. In the example in this guide, the Trusted Root and SCEP profiles are named as follows: Trusted Root Profile: AndroidNorthEndRootCert SCEP profile: AndroidSCEP Overview of SCEP communication flow NDES and SCEP issues are some of the most challenging problems that may be encountered when you use Microsoft Intune. Having a basic understanding of the architecture and the communication flow of the SCEP process helps you identify or narrow the scope of the issue. It's important to understand how to collect logs, what logs to collect
Read more