Patch for Windows, powered by Shavlik

ITScripts Requirements

License Requirements

The ITScripts features that are available to you depend on your license key. To determine your license level, select Help > About Ivanti Patch for Windows.

ITScripts features available with a Ivanti Patch for Windows Standard license

Access to free scripts created by Ivanti

Execute scripts against target machines

Execute scripts from the console

Create PowerShell Templates

ITScripts features available with a Ivanti Patch for Windows Advanced license

Access all predefined scripts provided by Ivanti

Import your own custom scripts

Import custom scripts written by others, such as those on the ITScripts Community Site

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 on the target machine (target type = WinRM Remoting)

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 Ivanti Patch for Windows:

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 Ivanti Patch for Windows console will also support PowerShell 4.0

A Ivanti Patch for Windows Advanced license must be available in order to access the more advanced features of the ITScripts function

When using PowerShell Remoting: On the Tools > Options > ITScripts tab you should verify the TCP port to use, and you should select the credential to use if it is necessary for Ivanti Patch for Windows to temporarily add a target machine to the console's TrustedHosts list when executing a WinRM script.

Target Machine Requirements When Using PowerShell Remoting or Opening a PowerShell Prompt

For additional details see about_Remote_Requirements in the PowerShell Help system.

Windows PowerShell 3.0 or later

The Microsoft .NET Framework 2.0 SP2

Windows Remote Management 2.0 (WinRM 2.0) or later: Working in conjunction with Windows PowerShell, WinRM allows scripts to be invoked on remote machines.

Although WinRM is automatically included in Windows 7, Windows Server 2008 R2, and Windows Server 2008 R2 - Core, it is not enabled by default on any of these operating systems.

TIP: The winrm quickconfig command is an easy method for enabling the protocol and setting up the default configuration.

Windows Server 2008 SP2, Windows Server 2003 SP2, Windows Vista SP2, and Windows XP SP3: You must download and install WinRM 2.0 on target machines using these operating systems (see KB968929 for information).

TCP port 5985: This is the default port that must be configured on your organization's firewall to allow the WinRM protocol. You can use a different port if it is defined in the WinRM listener.

Credentials must be provided for the target machines. You cannot execute scripts using your current logon credentials.

Administrator Requirements: Administrator privileges (Run As Administrator) are required in order to perform some remoting operations.

User Requirements: To establish a remote connection and run remote commands, the current user must be a member of the Administrators group on the remote computer. Or, the current user must be able to provide the credentials of an administrator.

Windows Network Location: To enable remoting on client versions of Windows, such as Windows 7, the current Windows network location must be Domain or Private ("Home" or "Work"). If the network location is Public, Windows PowerShell cannot create the required firewall exception for WS-Management communication.

Configuration Requirements: To configure Windows PowerShell to receive remote commands, at a PowerShell command prompt type enable-psremoting.

Secure Connection Requirements: If you want to use a secure connection you must do the following on the console and on each target machine:

Console: Enable the Use SSL check box on the Tools > Options > ITScripts tab. On that same tab you should also choose the secure TCP port to use.

Target machine: Each target machine must contain a signed certificate and a WinRM HTTPS Listener.

Target Machine Requirements When NOT Using PowerShell Remoting

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

Was this article useful?    

The topic was:



Not what I expected