12/02/2021 | News release | Distributed by Public on 12/02/2021 04:17
The screenshot below shows the full complement of options available for script deployment using MEM (Intune).
PolicyPak Scripts Manager offers your four times the choice that Intune has, which means you can leverage more power over any of your Windows 10 machines, regardless of whether they are MDM-enrolled, domain-joined, or non-domain-joined. What's more, the PolicyPak editors are built inside the Group Policy Management Editor, a tool that admins already use. You can take those scripts and use them on-prem with Group Policy or export them for use within Intune.
Creating a policy in PolicyPak Scripts manager is easy (see image below).
The power of choice that PolicyPak Scripts Manager delivers isn't restricted to just its selection of script formats. It also provides you the ability to revert scripts when a policy doesn't apply. For instance, in the previous screenshot we mapped a shared printer. Let's say we want to delete all network printers should the user ever fall out of scope of the designated policy. If we want to use a VB script this time instead of a Batch file, it's no problem. Just create the reverted action script using a VB Script as shown below.
Of course, if you prefer PowerShell, you can also select it as your choice. Let's say we wanted to map a network drive. In this case we will run it interactively as "Get-Credential" will prompt the user to enter a password as shown below.
The final step in this example is to decide how often you want the script to run. You can choose to run it on every policy processing and log in with the "Always" flag, as shown below.
If you really want super admin-like powers for script deployment then look at the various trigger options available with PolicyPak Scripts Manager. Triggering is nothing new. Group Policy has allowed you to utilize logon and logoff triggers since the beginning. However, it's a different world today than it was 20 years ago, and PolicyPak is constantly evolving in order to adapt to the dynamic, ever-changing world of tomorrow. PolicyPak Scripts Manager offers you to a variety of trigger points to choose from.
Have you been trying to figure out how to continue to deploy your arsenal of on-premise scripts to users in your newly VPN-connected world? With PolicyPak Scripts Manager you can initiate scripts when a user connects with VPN regardless of your VPN solution. This means you can map that drive when connected and then delete the mapping once disconnected. You can also trigger scripts based on the start or closing of a designated process, a session lock, an assigned schedule, or the traditional logon and logoff actions as shown below.
Microsoft Intune doesn't enable you to granularly select where your scripts should apply. But using Intune with PolicyPak is different.
If we want to accurately deploy our script policy by VPN triggering, we could choose only members of a select user group that use Windows 10 portable machines. We can even add an IP range so that the policy only applies when the computer is located off of the corporate network. You can see all of these conditions in the screenshot below.
PolicyPak can accentuate your Intune scripting abilities. As we've seen, Intune's scripting isn't bad, but it is limited to:
Here are a few videos to help you see the full picture of what we've gone over here:
If choice is power, PolicyPak delivers it.