In this lesson we will have a look on PowerShell built in security features and how it differs from e.g. BAT files. We will then have a look how execution policy can help to control on what basis the PowerShell scripts can be executed. At the end, we will configure some GPOs to control the execution and transcription of scripts.
In this lesson we learn how to use PowerShell to access WMI (Windows Management Instrumentation), so that we can gain often hidden or obscure information. We will then use WMI Explorer graphical tool to ease discovering all possible classes and instances that WMI provides. Finally, we will use WMI queries to add another level of granularity in GPO so that we can target very specific computers in it. Exercises There’s a WMI class that lists all the installed software – find it and list all currently installed software with PowerShell....
Having software consistently deployed across the fleet of computers is one of the key points that can be automated. If I have a choice (and it makes sense), I will always choose GPO over any other solution because it’s embedded into Active Directory thus not requiring installation, learning and maintenance of additional management tool. MSI – Software Installation One of the main advantages of MSI installers is that in 99% of cases you can just use the “Software Installation” option in GPO, and GPO will take care of the silent installation....