ITScripts Requirements

Setup Requirements

For information on configuring the console for use with ITScripts, see ITScripts Options.

License Requirements

The following ITScripts features are available to you with a standard license key.

  • Access to free scripts created by Ivanti
  • Execute scripts against target machines
  • Execute scripts from the console
  • Create PowerShell Templates
  • Access all predefined scripts provided by Ivanti
  • Import your own custom scripts
  • Import scripts that use custom PowerShell modules
  • Execute custom scripts on the console (target type = Console)
  • Execute custom scripts on the console against target machines (target type = Any)
  • Execute predefined and custom scripts against ESXi Servers and vCenter Servers (target type = ESXi Hypervisor)
  • Schedule scripts

Script Requirements

There are two basic requirements for using a script within Security Controls:

  • The script must contain metadata that uniquely identifies it and describes its functionality and input parameters
  • The script must be signed by an authority that is trusted by the machine that the console is running on

See Creating a Custom Script for more information on these and other script requirements.

Console Requirements

  • Microsoft .NET Framework 4.6.1 or later
  • Windows PowerShell 4.0 or later: Windows PowerShell is a command-line shell and scripting language that is designed for system administration and automation
  • Operating System: All operating systems that support the Security Controls console will also support PowerShell 4.0

Target Machine Requirements

You do not need to install any additional software on the target machines. Scripts of type Any or Console are run against the selected target machines or machine groups without the services of WinRM (PowerShell remoting). The PowerShell client on the console will communicate with the target machines by using other Windows remoting services such as remote registry service, remote Windows file sharing, WMI services, etc. The actual service used will depend on the script. The only ports required are the ports required by the Windows services being used.

Scripts with a target type of WinRM Remoting are slightly different. They are implemented by creating a custom ITScript and specifying remote as the metadata type.