Opening the PowerShell Console
Opening the PowerShell Console
Log on to your administrative workstation (we assume the PowerShell Extensions for Ivanti DSM are already installed on that machine). Use an account that is already imported into your DSM 2022.2 environment and that has the Supervisor role assigned. As an alternative you can directly log on to your DSM 2022.2 Business Logic Server using an account with the Supervisor role assigned. In this case the PowerShell Extensions for Ivanti DSM have to be installed on the Business Logic Server.
Open the PowerShell console window by clicking on the shortcut that was created during the installation phase of the PowerShell Extensions for Ivanti DSM (the shortcut is only available if the feature Shortcut had been selected during the installation phase. Do not hesitate to restart the setup application and add that feature if required).
|
Hint: If you prefer a different approach to open the PowerShell console window (e.g. using the shortcut created during the installation of the PowerShell itself) the PSX7 Snap-In might not be loaded automatically and therefore it is not available without manual loading. Alternative ways to load the Snap-In are described in the section Loading the Snap-In. |
In the default configuration the PowerShell is very restrictive and does not allow the execution of scripts. Using the defaults and starting PowerShell with the PowerShell Extensions for Ivanti DSM for the very first time you might experience the following warning:
|
Do you want to run software from this untrusted publisher? File C:\Program Files\NWC Services\PSX7\NwcServices.BlsAdministration.TypeData.ps1xml is published by E=dev@nwc-services.de, CN=NWC Services GmbH, O=NWC Services GmbH, C=DE and is not trusted on your system. Only run scripts from trusted publishers. [V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is "D"): |
We suggest to select option "[A] Always run" to load the Snap-In in subsequent sessions without further manual interaction. If you follow the suggestion the public part of the certificate used to sign the scripts and the Snap-In is imported into the list of trusted publishers of your certificate store.
Furthermore we suggested to change the PowerShell's default execution policy with the command
|
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned |
This configuration allows you to execute your own scripts (that might have not been digitally signed). More information about execution policies and their consequences can be found at http://www.microsoft.com/technet/scriptcenter/topics/msh/cmdlets/set-executionpolicy.mspx.
|
Hint: Using Windows Vista (or higher) with User Account Control enabled, requires the above command to be executed from a console started as an administrator. |
After successfully starting the PowerShell console execute the following command
|
Get-Module |
or
|
Get-PSSnapin |
at the prompt to ensure the Module or Snap-In was loaded. On success the following output should occur (among other). Note: the value of the PSVersion entry will be displayed as 2.0 (or higher), if you are using Windows PowerShell 2.0 (or higher):
|
ModuleType Name ExportedCommands ---------- ---- ---------------- Binary psx7 {New-EmdbVirtualizationManagementServer, Get-EmdbPolicyInst... |
or
|
Name : NwcServices.BlsAdministration PSVersion : 5.0.10586.51 Description : Windows PowerShell Snap-In for Ivanti Client Management BLS administration |
The absence of this output indicates a problem. In such a case please refer to the section Troubleshooting.