Jump to page sections

• Used Registry Keys
• End Result CSV Displayed In Excel
• Module Parameters
• Script Parameters
• Example Use
• Test Run
• Looking At The CSV Data
• Inspecting Computers With Errors
• Filtering On A Certain Installed .NET Version
• Summary Of .NET Versions
• Download
• Version history
• Get the latest .NET version
• Enabling the Remote Registry Service

I'm not rewriting all of the documentation, so some of it could be partially outdated if you use the latest v2.x module - but I do recommend that.

The CSV has one field for errors, one for each .NET version from 1.1 till 4.0 (client/full differentiated for v4) and one field with the computer/host name. In v1.1 and later versions of the script there's also a field for 4.x which differentiates between the different 4.x versions above 4.0, from 4.5 and up.

I didn't add detection of .NET v1.0, so you're on your own if you need to look for that. You will also have to rewrite the script if you need to detect service pack levels.

Here's what the latest version looks like with the -LocalHost parameter in use:

In Excel 2010 the default delimiter appears to be a tab, not a comma, so you need to go to the ribbon "Data", choose "From Text" under "Get External Data" and specify the correct options when importing. Using either the default encoding ANSI or UTF-8 works for me with the lab data. You need to specify that the data is delimited, and that the delimiter is a comma.

ipcsv file1.csv | epcsv -not -enc utf8 -delim ';' file1semicolon.csv

I've learned this depends on culture settings, so instead of -Delimiter ";" # you can use the parameter -UseCulture, this should make it open magically in Excel on ''that'' computer with current culture/locale settings.

For computers where there are no errors, the error field will contain a hyphen/dash ("-"), so you can use -eq '-' or -ne '-' to filter on that using Where-Object. You will get "No ping reply" in the error field for computers that do not respond to ICMP echo / ping - and also for computers which do not resolve via DNS or WINS/NetBIOS.

PS C:\> Import-Csv .\DotNet-Versions-2012-03-18.csv | Select -First 1

Computer   : esxi
v4\Client  : Unknown
v4\Full    : Unknown
v3.5       : Unknown
v3.0       : Unknown
v2.0.50727 : Unknown
v1.1.4322  : Unknown
Error      : No ping reply


PS C:\> Import-Csv .\DotNet-Versions-2012-03-18.csv | Select -Skip 1 -First 1

Computer   : SRV2003R2ESXI
v4\Client  : Installed
v4\Full    : Installed
v3.5       : Installed
v3.0       : Installed
v2.0.50727 : Installed
v1.1.4322  : Not installed (no key)
Error      : -

PS C:\> Import-Csv .\DotNet-Versions-2012-03-18.csv | Where { $_.Error -ne '-' } | ft -auto

Computer    v4\Client v4\Full v3.5    v3.0    v2.0.50727 v1.1.4322 Error
--------    --------- ------- ----    ----    ---------- --------- -----
esxi        Unknown   Unknown Unknown Unknown Unknown    Unknown   No ping reply
WIN2K       Unknown   Unknown Unknown Unknown Unknown    Unknown   No ping reply
SERVER2003  Unknown   Unknown Unknown Unknown Unknown    Unknown   No ping reply
VISTA64ESXI Unknown   Unknown Unknown Unknown Unknown    Unknown   Unable to open remote registry: Exception calling...
WINXPESXI   Unknown   Unknown Unknown Unknown Unknown    Unknown   Unable to open remote registry: Exception calling...
WIN7ESXI    Unknown   Unknown Unknown Unknown Unknown    Unknown   Unable to open remote registry: Exception calling...
SERVER2008  Unknown   Unknown Unknown Unknown Unknown    Unknown   No ping reply
XPTANKET    Unknown   Unknown Unknown Unknown Unknown    Unknown   No ping reply

PS C:\> Import-Csv .\DotNet-Versions-2012-03-18.csv |
  Where { $_.'v4\Full' -eq 'Installed' } |
  Select 'v4\Full', Computer | ft -auto

v4\Full   Computer
-------   --------
Installed SRV2003R2ESXI
Installed SIEMENS
Installed 2008R2ESXI2
Installed 2008R2ESXI

You can use "$_.'v4\Full' -ne 'Installed'" to see which clients or servers don't have it installed.

I started the remote registry service on the Vista client and now I got the data from that too:

PS C:\> Import-Csv .\DotNet-Versions-2012-03-18.csv | Where { $_.Computer -ieq 'vista64esxi' }

Computer   : VISTA64ESXI
v4\Client  : Installed
v4\Full    : Not installed (no key)
v3.5       : Installed
v3.0       : Installed
v2.0.50727 : Installed
v1.1.4322  : Not installed (no key)
Error      : -

It's on GitHub here: https://github.com/EliteLoser/DotNetVersionLister

If you have Windows Management Framework 5 or higher (WMF 5 is available for Windows 7 and up), you can install my DotNetVersionLister module from the PowerShell gallery, a Microsoft project and online repository for scripts.

Install-Module -Name DotNetVersionLister

Or for your user only (does not require elevation / administrator privileges):

Install-Module -Name DotNetVersionLister -Scope CurrentUser

#$ComputerName = Get-ADGroupMember -Identity SomeComputerObjectGroup | Select-Object -ExpandProperty Name
$ComputerName = Get-ADComputer -Filter * -Propert Name | Select-Object -ExpandProperty Name
Import-Module -Name DotNetVersionLister -ErrorAction Stop
$DotNetVersionsHash = @{}
foreach ($Computer in $ComputerName) {
    $DotNetVersion = Get-DotNetVersion -ComputerName $Computer -PSRemoting -ContinueOnPingFail -NoSummary
    if ($DotNetVersion -and -not $DotNetVersion.Error) {
        if ($DotNetVersion.'>=4.x' -match '\S' -and $DotNetVersion.'>=4.x' -notmatch 'error|not installed|universe') {
            $DotNetVersionsHash[$Computer] = $DotNetVersion.'>=4.x'
        }
        elseif ($DotNetVersion.'v4\Client' -eq 'Installed' -or $DotNetVersion.'v4\Full' -eq 'Installed') {
            $DotNetVersionsHash[$Computer] = '4.0'
        }
        elseif ($DotNetVersion.'v3.5' -eq 'Installed') {
            $DotNetVersionsHash[$Computer] = '3.5'
        }
        elseif ($DotNetVersion.'v3.0' -eq 'Installed') {
            $DotNetVersionsHash[$Computer] = '3.0'
        }
        elseif ($DotNetVersion.'v2.0.50727' -eq 'Installed') {
            $DotNetVersionsHash[$Computer] = '2.0'
        }
        else {
            $DotNetVersionsHash[$Computer] = '<2.0'
        }
    }
    else {
        $DotNetVersionsHash[$Computer] = 'Error'
    }
}
$DotNetVersionsHash.GetEnumerator() | Format-Table -AutoSize

To enable the remote registry service, and set the startup type to automatic, you would ideally use an AD Group Policy (GPO/GP), but if you ghetto it (temporarily), you can use a simple foreach loop that iterates a list of computers, checks the status of the service with Get-Service, and if it's not running, it tries to set the startup type to automatic and then to start it (it seems to get a start signal immediately when you set it to auto).

The results will look like this for disabling and enabling:

Enable-RemoteRegistryService.ps1.txt code. Read it, understand it, and adapt as you see fit, or just run it (you will need to populate the $ComputerName variable).

PS C:\temp> C:\temp\Enable-RemoteRegistryService.ps1
server2012: The RemoteRegistry service is already running.
vista64esxi: The RemoteRegistry service is already running.
server2008: The RemoteRegistry service is already running.

Here's a similar, but reversed script, for disabling the RemoteRegistry service, if you want to do that after enabling it and then processing the computers with Get-DotNet-Version.ps1: Disable-RemoteRegistryService.ps1.txt.

Google custom search of this website only

Minimum cookies is the standard setting. This website uses Google Analytics and Google Ads, and these products may set cookies. By continuing to use this website, you accept this.

If you want to reward my efforts