PowerShell Extensions for Ivanti DSM

Further Options

To gain access to your DSM 2022.2 environment, you must first create a PowerShell drive. The basic command

can be parametrised with several mandatory and optional parameters.

Mandatory parameters are:

• -Name <string>
  The name of the new drive. You can choose any name. But we recommend to use a name that links to the connected DSM 2022.2 environment. Throughout this documentation we use the name "emdb".
  
  
• -PsProvider <string>
  The name of the provider that make the data for the drive available. The fixed provider name used by the PowerShell Extensions for Ivanti DSM is "BlsEmdb". 

• -Root <string>
  The internal root directory of the provider resp. the directory that should act as a root directory of the PowerShell drive. For instance you can create a PowerShell drive that has its root directory mapped to the path "rootDSE\Managed Users & Computers".
  
  

Establishing connections using alternate credentials

Similar to the way you connect to the file system of a remote server using a different user context ("Connect as...") you can use alternative credentials to connect to your DSM 2022.2 environment. Therefore provide the parameter "-credential" followed by an object of type PSCredential or a user account name to the cmdlet New-PSDrive.

• -Credential <PSCredential-object>
  The PSCredential object is used to authenticate the connection. An object created by a call to Get-Credential is used directly for authentication. If you provide only a user account name you are requested to type in the password.

Examples:

or

Accessing a remote Business Logic Server

As a default, the PowerShell Extensions for Ivanti DSM assume that the Business Logic Server is installed on the local computer. More likely the PowerShell Extensions for Ivanti DSM are installed on an administrative computer and you want to connect to a remote server. In this case you have to specify the computer that hosts the Administration Webservice. Therefore the cmdlet  New-PSDrive supports additional optional parameters: 

• -Url <string> | -BlsUrl <string>
  The URL describing the BLS. This parameter overrides the parameters -Root, -BlsHost and -BlsPort.
  
  
• -Root \\<blshost>[:<blsport>][\<emdbroot>]
  The root path formatted as an UNC path. If <blsport> is omitted, port 8080 is assumed. This parameter overrides the parameters -BlsHost and -BlsPort. 

• -BlsHost <string> 
  The Business Logic Server. The host name can be given as a NetBIOS name, a full qualified domain name or as an IP address. If this parameter is omitted the Administration Webservice is assumed running on the local computer.

• -BlsPort <integer>
  The port on which the Administration Webservice is listening. If this parameter is omitted, port 8080 is assumed.

Examples:

or

or

or

Using encrypted communication for accessing DSM

Typically the BLS is accessed via the http-protocol. For some time, it is possible to use https as the access-protocol instead of http, as http's payload is transferred in plain text via the network. This results in an encrypted communication between the DSM Console and the BLS or - when using PSX - the communication between PowerShell and the BLS and the data can't be easily captured and read by a third party while travelling the network.

In order to use the encrypted communication, the BLS has to be configured accordingly, which is beyond the scope of this online help. To initiate a secure channel with the Business Logic Server via https, please use the following parameter:

• -UseTLS
  The BLS is accessed via https instead of http. The Internet Information Server hosting the Administration Service has to be correctly configured. When choosing a https-connection, the SSL-port 443 is used as the default-port. Should you need to specify an alternative port, provide its port-number via the -Root-parameter or by adding the optional -BlsPort parameter.

Examples:

or

       
or