Platform: WindowsProducts: Managed Backup (Agent)
Article ID: m2500Last Modified: 10-Dec-2024

Getting Started


First step before using our PowerShell Module is installing it in your system. Below you can find instructions for doing so.

You can find the current version of your Powershell by running this command:

Get-Host | Select version

For Powershell version 3.0 - 5.1 and above:

Open PS console with Administrator account and run this command.

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
iex ((New-Object System.Net.WebClient).DownloadString('https://git.io/JUSAA')+'Install-MSP360Module')

For Powershell version 2.0

For Powershell with version below we suggest updating to the most recent version.


Additional steps

At some step you also may be required to allow remotesigned execution policy by running

Set-ExecutionPolicy RemoteSigned

Use the following command to load module.

Import-Module -Name msp360


Examples

Here is an example of a couple popular requests to start working with our PowerShell module:

Get-Command -Module msp360

Get-Help Start-MBSBackupPlan


Troubleshooting

If you encounter errors during the installation of the PowerShell Module, refer to the Known Issues and Fixes chapter.

In March 2021, the support of the Transport Layer Security (TLS) versions 1.0 and 1.1 was discontinued: for more information, read the Deprecating TLS 1.0 and TLS 1.1 statement. TLS 1.2 is the only supported protocol version.

Check the TLS version with the following command:

https://tls-v1-2.badssl.com:1012/

If the PowerShell console runs under TLS 1.0 or 1.1, the following error message will be reported:

wget : The underlying connection was closed: An unexpected error occurred on a send
At line:1 char:1
+ wget https://tls-v1-2.badssl.com:1012/
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebE 
   xception
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Solution

To force PowerShell using TLS version 1.2 for the session, run PowerShell as administrator and execute the following command:

[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor "Tls12"

Contact Us

https://git.cloudberrylab.com/egor.m/doc-help-mbs.git