- Create (or modify) a GPO that targets the servers that will get the software package. In my case, I have an existing GPO called “Server Systems” I’ll be using that targets the “Server” OU as shown below.
- Edit the GPO and navigate to Computer Configuration -> Policies -> Software Settings -> Software Installation. Right click and select New -> Package
- Select the location of the “SolidFire_PowerShell_1_0_0_28-install.msi” file. This should be on a network share that is accessible to all the hosts that will receive the package. Select the “Assigned” radio button and click the OK button to finish adding the package.
- Group policy can take up to 90 minutes to refresh, but if you don’t want to wait that long you can force an update through GPMC by right clicking on the OU containing the servers and selecting Group Policy Update. This will speed things up a bit as the computers should get the updates within 10 minutes.
- To verify that the applicable GPO was applied a report with the output of gpresult can be run by login into a server and running gpresult /H %userprofile%\desktop\report.html In the example below, the policy was applied and the system is waiting for a reboot to complete.
- After the next reboot, the PSM should have installed.
- Enjoy some PowerShell!
As you may have heard, SolidFire released a PowerShell module earlier this week. Since I’m building up a new lab environment I decided it should be part of my standard server build. In the spirit of automation, I decided to use good old fashioned group policy to push it out to my designated server hosts. This is pretty simple to do if you haven’t done it previously.