Deploying the Now Micro Right Click Tools with ConfigMgr

Configuration Manager (ConfigMgr) console extensions have been a widely used tool for administrators to augment the functionality provided by ConfigMgr.  The Now Micro Right Click Tools (Right Click Tools) allow administrators to interact with their ConfigMgr clients in real time, enabling them to shortcut some of the wait times associated with an asynchronous client-based architecture.  This blog post will cover how to automate the deployment of the Now Micro Right Click Tools using the ConfigMgr application model.  The Right Click Tools require the .Net Framework 4.5 or higher, Windows Management Framework 3 or higher, and the Configuration Manager console as prerequisites.  See the linked blog posts for more information on how to create silent installations for these applications.

The Right Click Tools also have some requirements for the machines that they’re running against.  ICMP echo must be enabled in the firewall, as well as remote WMI and File and Print sharing.  Additionally, the user running the Right Click Tools must have sufficient permission on the computer that the action is running against to perform that action.  If using the tools to reset passwords, unlock accounts, or change group memberships, the user must have permissions to perform these actions in Active Directory.  Some of the tools use the Remote Registry service, so this service must be enabled on both the device running the Right Click Tools as well as the device being connected to.

 

Since the Now Micro Right Click Tools are an MSI based installation, creation of the ConfigMgr applications is relatively straight-forward.  For simple deployments, the default installation will provide the full set of functionality of the Right Click Tools.  Before creating the application, download the latest version of the  Right Click Tools from http://www.nowmicro.com/rct/ and copy it to a new folder in your ConfigMgr source folder.  Next, right click on the Applications node and choose New Application.  Use the Windows Installer type, and browse to the Right Click Tools.msi file in the ConfigMgr content source.

 

The Windows Installer type pulls some of the common metadata out of the MSI.  The following MSI properties are available to customize the installation:

 

Right Click Tools MSI Properties:

  • AUTOUPDATE – pull in updates from Now Micro automatically
  • WOLPORT –  port used to send WOL packets
  • WOLUNICAST – use unicast mode when sending WOL packets
  • PACKETSTOSEND – number of WOL packets to send

 

An example command line for the Now Micro Right Click Tools might be:

msiexec /i “Right Click Tools.msi” /q AUTOUPDATE=1 WOLPORT=7 WOLUNICAST=0 PACKETSTOSEND=5

 

Right Click Tools Enterprise MSI Properties:

  • RCTENTERPRISESERVER – the server that the enterprise tools will connect to

 

If deploying the Now Micro Right Click Tools Enterprise, RCTENTERPRISESERVER is a required MSI property.  An example command line for the Right Click Tools Enterprise would be:

msiexec /i “Right Click Tools Enterprise.msi” /q RCTENTERPRISESERVER=rct.domain.local

 

2

Once your customized install string is entered, click Next through the wizard.  Once the application object is created, we need to modify the dependencies of the application.  To do this, go to the Properties of the Deployment Type, and select the Dependencies tab.  Click Add to create a new Dependency Group. For a step by step instructions: Download This User Guide

The dependencies should look similar to this when finished.

 

3

 

The Right Click Tools are incredibly powerful, and sometimes we want to hide functionality that could cause issues in the environment.  The Now Micro Right Click Tools are customizable, enabling administrators to hide functionality from their users.  To customize the set of Right Click Tools available to users, we need to edit the template XML files that are installed with the tools.  To do this, we need to first install the Right Click Tools on a machine, edit the templates, and modify our installation to overwrite the template files that are installed by default.  The template XML files are located in the Default Menus folder inside the install folder (default is C:Program Files (x86)Now MicroRight Click ToolsDefault Menus).  If, for example, we wanted to remove the ability to shutdown or restart systems via the Right Click Tools, we would remove the following lines from the Device and Collection XML files:

 

<ActionDescription Class=”Separator”>

<ShowOn>

<string>ContextMenu</string>

</ShowOn>

</ActionDescription>

 

<ActionDescription Class=”Executable” DisplayName=”Cancel Pending Restart or Shutdown” MnemonicDisplayName=”Cancel Pending Restart or Shutdown” Description=”Cancel Pending Restart or Shutdown”>

<ShowOn>

<string>ContextMenu</string>

</ShowOn>

<Executable>

<FilePath>”wscript.exe”</FilePath>

<Parameters> “C:Program Files (x86)Now MicroRight Click ToolsSilentOpenPS.vbs” “C:Program Files (x86)Now MicroRight Click ToolsDevice – Tools.ps1” “##SUB:ResourceID##” ##SUB:__Server## ##SUB:__Namespace## “CancelPendRestart”</Parameters>

</Executable>

</ActionDescription>

 

<ActionDescription Class=”Executable” DisplayName=”Schedule Restart or Shutdown” MnemonicDisplayName=”Schedule Restart or Shutdown” Description=”Schedules Restart or Shutdown”>

<ShowOn>

<string>ContextMenu</string>

</ShowOn>

<Executable>

<FilePath>”wscript.exe”</FilePath>

<Parameters> “C:Program Files (x86)Now MicroRight Click ToolsSilentOpenPS.vbs” “C:Program Files (x86)Now MicroRight Click ToolsDevice – Schedule Shutdown.ps1” “##SUB:ResourceID##” ##SUB:__Server## ##SUB:__Namespace##</Parameters>

</Executable>

</ActionDescription>

 

<ActionDescription Class=”Executable” DisplayName=”Restart System” MnemonicDisplayName=”Restart System” Description=”Restarts system”>

<ShowOn>

<string>ContextMenu</string>

</ShowOn>

<Executable>

<FilePath>”wscript.exe”</FilePath>

<Parameters> “C:Program Files (x86)Now MicroRight Click ToolsSilentOpenPS.vbs” “C:Program Files (x86)Now MicroRight Click ToolsDevice – Shutdown Restart.ps1” “##SUB:ResourceID##” “Restart” ##SUB:__Server## ##SUB:__Namespace##</Parameters>

</Executable>

</ActionDescription>

 

<ActionDescription Class=”Executable” DisplayName=”Shutdown System” MnemonicDisplayName=”Shutdown System” Description=”Shutdown System”>

<ShowOn>

<string>ContextMenu</string>

</ShowOn>

<Executable>

<FilePath>”wscript.exe”</FilePath>

<Parameters> “C:Program Files (x86)Now MicroRight Click ToolsSilentOpenPS.vbs” “C:Program Files (x86)Now MicroRight Click ToolsDevice – Shutdown Restart.ps1” “##SUB:ResourceID##” “Shutdown” ##SUB:__Server## ##SUB:__Namespace##</Parameters>

</Executable>

</ActionDescription>

 

Once all of the customizations are made, copy the Default Menus folder up to the Right Click Tools install source and create a new .cmd file.

 

4

Edit the .cmd file and place the following text.  Replace the first line with the custom install string that was created as part of the Right Click Tools application.

 

msiexec /i “%~dp0Right Click Tools.msi” /q

 

XCOPY “%~dp0Default Menus” “%ProgramFiles%Now MicroRight Click ToolsDefault Menus” /E /Y

 

powershell.exe -ExecutionPolicy Bypass -File “%ProgramFiles%Now MicroRight Click Toolsinstall.ps1”

 

Next, go to the Properties of the Right Click Tools Deployment Type in ConfigMgr.  On the Programs tab, change the Installation Program to the batch file created in the previous step.  Check the box to “Run installation and uninstall program as 32-bit process on 64-bit clients” so that %ProgramFiles% maps to Program Files (x86) on 64-bit clients.

 

5

Click OK to save the changes.  Finally, update the content of the Deployment Type.