• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2878
  • Last Modified:

Powershell script to inventory all servers that have IPv6 enabled/disabled

IPv6 PS Script
I want to inventory all computers in our AD environment and find out if IPv6 is enabled or not enabled.

I've attached a script and am stuck on disabled.
Can someone add to my script so the column  'disabled' outputs true/false.
Please keep in mind I'm trying to do it with a one-line command as I am learning PS.

thanks
0
techgenious
Asked:
techgenious
  • 7
  • 5
1 Solution
 
footechCommented:
Quick note - often one-liners are a lot more difficult to read and understand than multi-line scripts.
The closest I've seen for this is to use WMI to check what IP addresses are in use and examine them to see if they contain ":".  Possibly could make this a calculated property, but I haven't been able to pull it all together.
Honestly do not know if you can rely on the IPv6Address property from Get-ADComputers since it can return info even when IPv6 isn't enabled.
This the closest I've come up with, using a custom object:
Import-Module ActiveDirectory
$computers = Get-ADComputer -filter *
$out = @()
ForEach ($computer in $computers) 
{
	$custom = New-Object PSObject
	$custom | Add-Member -type NoteProperty -name ComputerName -value $computer.name
	$ipv6 = (gwmi Win32_NetworkAdapterConfiguration -computername "$($computer.name)" | Where {$_.IPEnabled -eq $True} ).IPAddress | Where {$_ -match ":"}
	$custom | Add-Member -type NoteProperty -name IPv6Address -value $ipv6
	$status = ($ipv6 -notmatch ":")
	$custom | Add-Member -type NoteProperty -name Disabled -value $status
	$out += $custom
}
$out

Open in new window

0
 
footechCommented:
This DOES NOT work (at least not completely), but it's where I was headed with calculated properties.  Just leaving it here to see if it sparks an idea for anyone else (and to show how ridiculous one-liners can get).
Import-Module ActiveDirectory
Get-ADComputer -filter * | Select Name,@{ name = "IPv6Address"; expression = { (gwmi Win32_NetworkAdapterConfiguration -computername "$($_.name)" | Where {$_.IPEnabled -eq $True} ).IPAddress | Where {$_ -match ":"} }}, @{ name = "Disabled"; expression =  { (gwmi Win32_NetworkAdapterConfiguration -computername "$($_.name)" | Where {$_.IPEnabled -eq $True}).Ipaddress | % {($_ -notmatch ":")} } }

Open in new window

0
 
techgeniousAuthor Commented:
Thanks but being a beginner, let me try your script and see what output I get.
Will it tell me if IPv6 is enabled?

thx
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
footechCommented:
I've never seen a property that you can query directly to determine whether IPv6 is enabled.  The best I know of is to look at a machine's IP addresses, and if one is an IPv6 address, infer that it is enabled.  Test it in your environment with hosts that you know are configured one way or another and see how it works for you.
0
 
techgeniousAuthor Commented:
Error messageThis is the error message when I run this on a DC and the RPC service is running
0
 
footechCommented:
You will see this when it can't connect via WMI to the remote machine(s).  What OSes are you running?  Does the firewall configuration on all the remote machines allow inbound WMI traffic?
0
 
techgeniousAuthor Commented:
Windows Server 2008 R2, the windows firewall is disabled on all machines.
0
 
footechCommented:
Hmmm... perhaps if the WMI service wasn't running; also, if DNS records are incorrect.
Here's another version to provide some feedback on current operations.  It may help you with determining what's going on.  Once you've determined a problem machine, best advice I can give is to run the commands individually and start breaking them down to see what might be happening.  For instance, taking (gwmi Win32_NetworkAdapterConfiguration -computername "NameOfProblemComputer" -ea "Stop" | Where {$_.IPEnabled -eq $True} ).IPAddress | Where {$_ -match ":"} and removing the last pipe, then removing the ".ipaddress" property call, and so on.
Import-Module ActiveDirectory
$computers = Get-ADComputer -filter *
$out = @()
ForEach ($computer in $computers) 
{
  $i++
  Write-Progress -activity "Progress Indicator" -status "Testing Connection" -currentOperation "Checking computer ""$($computer.name)"" ($i of $($computers.count))" -percentComplete (($i/$computers.count) * 100)
  If (Test-Connection $($computer.name) -count 2 -quiet )
  {
    Write-Progress -activity "Progress Indicator" -status "Gathering WMI Info" -currentOperation "Checking computer ""$($computer.name)"" ($i of $($computers.count))" -percentComplete (($i/$computers.count) * 100)
    try
    {
      $ipv6 = (gwmi Win32_NetworkAdapterConfiguration -computername "$($computer.name)" -ea "Stop" | Where {$_.IPEnabled -eq $True} ).IPAddress | Where {$_ -match ":"}
      $custom = New-Object PSObject
      $custom | Add-Member -type NoteProperty -name ComputerName -value $computer.name
      $custom | Add-Member -type NoteProperty -name IPv6Address -value $ipv6
      $status = ($ipv6 -notmatch ":")
      $custom | Add-Member -type NoteProperty -name Disabled -value $status
      $out += $custom
    }
    catch { Write-Host "Unable to retrieve info from ""$($computer.name)""" }
  }
  Else { Write-Output "Couldn't ping ""$($computer.name)""" }
}
$out

Open in new window

0
 
techgeniousAuthor Commented:
Thanks so much for this script:
When I run the script I get this:


  Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 933 argument is greater than the maximum allowed range of 100.
Supply an argument that is less than or equal to 100 and then try the command again.
At C:\IPV6.ps1:7 char:183
+ ... ercentComplete (($i/$computers.count) * 100)
+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
 
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 933 argument is greater than the maximum allowed range of 100.
Supply an argument that is less than or equal to 100 and then try the command again.
At C:\IPV6.ps1:10 char:185
+ ... ercentComplete (($i/$computers.count) * 100)
+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
 
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 967 argument is greater than the maximum allowed range of 100.
Supply an argument that is less than or equal to 100 and then try the command again.
At C:\IPV6.ps1:7 char:183
+ ... ercentComplete (($i/$computers.count) * 100)
+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
 
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 1000 argument is greater than the maximum allowed range of 100.
Supply an argument that is less than or equal to 100 and then try the command again.
At C:\IPV6.ps1:7 char:183
+ ... ercentComplete (($i/$computers.count) * 100)
+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
 
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 1000 argument is greater than the maximum allowed range of 100.
Supply an argument that is less than or equal to 100 and then try the command again.
At C:\IPV6.ps1:10 char:185
+ ... ercentComplete (($i/$computers.count) * 100)
+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
0
 
footechCommented:
Only way that could happen is if $i is greater than the number of computer accounts found by the Get-ADComputers cmdlet.  Add the statement $i = 0 anywhere before line 4 to make sure each time you run the script the count gets reset.
0
 
techgeniousAuthor Commented:
IPv6 ComponentsI really appreciate this I've learned alot being a complete beginner.

One other question, when it checks disable IPv6 I noticed the components which I need to see if they are enabled or disabled, which is components of IPV6:
-- Tunnel Adapter isatap
-- Tunnel Adapter 6to4 adapter
-- Tunnel adapter Teredo Tunneling Pseudo-Interface


How can I add that into the script to see if they are enabled/disabled?
I need to inventory those components.

many thanks
0
 
footechCommented:
Sorry, I'm not really sure what you're asking.  I'm not too familiar with the components you mentioned or how they're supposed to factor into the question here.  To my knowledge the components are present on a machine whether IPv6 is configured or not.  Perhaps if you could describe the situation better I could give you a better answer.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now