If you’re a Windows administrator, you know that it’s easy to install software on remote Windows systems. But what if you want to install software on a system that’s not connected to the network? Or if you want to use a different operating system on a remote Windows system? There are two ways to do this: using PowerShell and using the Remote Desktop Protocol. Using PowerShell To use PowerShell, first create a new instance of the PowerShell cmdlet. Then type the following command to install the Microsoft .NET Framework 4.5 on an unnamed remote Windows system: $env:COMPUTERNAME\WINDOWS\system32\Microsoft.NETFramework4.5 $ env:USERNAME\WINDOWS\system32\Microsoft.NETFramework4.5 The first argument is the computer name or name of the local computer on which you want to run PowerShell; the second argument is the user name or login name for that computer. The third argument is an environment variable that contains information about how to run PowerShell on this computer (for example, COMPUTERNAME). The fourth argument is a pathname for a file that contains instructions about how to run PowerShell on this computer (for example, C:\windowspowershell.exe). The fifth and last argument are two parameters—the command and its arguments—that will be passed along when the command is executed.
If you’re an IT admin, chances are high that you’ve had to install software for others. Endpoint management is big business these days, and maintaining software across hundreds or thousands of computers is common in large organizations. Big business usually means big $$, though.
What if you’re in an organization with little-to-no budget? Maybe yourself or someone on your team has gotten into using PowerShell to automate various tasks? In that case, using PowerShell to manage software across many endpoints at once may be beneficial.
The PowerShell scripting language is a powerful flexible language that seems to handle just about anything in a Windows environment. Working with software on remote computers is a piece of cake!
In this article, you’re going to learn how you can use PowerShell to build installed software reports. Although PowerShell is capable of installing software as well, you’ll focus on querying software that’s been installed via other means.
Where Software Is Registered
The term “software” is a vague term, especially on Windows. When a software package is installed, it’s entirely up to the software developer to determine what changes on the user’s computer. Software installers copy files, create registry keys, add WMI instances, and more. The key to building an accurate software inventory report, regardless of the method, is first understanding what to look for.
Although installed software is registered in WMI, a more reliable way to find this information is to use the registry.
Every modern version of Windows stores installed software information in the three registry keys below. Depending on how the software was installed, it always is stored as a registry key under one of these parent keys.
HKEY_LOCAL_MACHINE(32-bit path) HKEY_LOCAL_MACHINE6432Node(64-bit path) HKEY_CURRENT_USER(for every user profile)
Each child registry key in these parent keys is typically named for the software’s globally unique identifier (GUID). Inside of that key, you can find registry values for software title, version, and more.
Remote PC Requirements
To use the code covered in this article, I’m assuming you have PowerShell Remoting enabled and available on your remote computers. You can test PowerShell Remoting by attempting to execute a simple command like Invoke-Command -ComputerName REMOTEPCNAME -ScriptBlock {1}. If this fails, the rest of the information covered in this article won’t work either.
Using the PSSoftware Community Module
To prevent recreating the wheel and building your own PowerShell tool, let’s use an existing one. I created a PowerShell module called PSSoftware a while back that solves this problem well.
First, in an administrative PowerShell console, download and install the PSSoftware PowerShell module from the PowerShell Gallery by running Install-Module PSSoftware.
Once you have the module installed, inspect the commands available to you by running Get-Command -Module PSSoftware -Noun Software. You’ll see a few commands like Get-InstalledSoftware, Install-Software ,and Remove-Software. These commands are the main functions to manage software. In this article, I focus on the Get-InstalledSoftware function.
Test out the Get-InstalledSoftware command by first running it locally with no parameters. You immediately see many different software packages fly by.
You can limit that output down to just the title and version using the Select-Object cmdlet.
To query a remote computer, use the ComputerName parameter. The same software packages are returned.
Perhaps you’d rather not see all installed software but just software matching a specific title. You can filter this information using the Where-Object cmdlet. The following example finds all the software that starts with SQL on the remote computer.
Summary
Once you understand where installed software is stored and can access it with PowerShell, the world is your oyster. From here, you can quickly expand this code to multiple computers, looking for numerous packages and more.
Using free community PowerShell modules is a great way to build software inventor reports on the cheap!
