In case BlueParq not starts and you receive the following message:
Why does this happen
This occurs when the group policy on your computer that defines whether you can execute PowerShell code is set to disabled (by either you or your local administrator).
Check PowerShell Execution Policy
- Press WindowsKey + R
- Enter the following: powershell
- The Windows PowerShell console will open.
- Execute Get-ExecutionPolicy -List
- If UserPolicy is RemoteSigned BlueParq will not start (this is because we cache all of the available cmdlets and modules).
Solution
- Press WindowsKey + R
- Enter the following: gpedit.msc
- Press OK.
- The Local Group Policy Editor opens.
- Navigate to User Configuration -> Administrative Templates -> Windows Components.
- Open Windows PowerShell.
- Double click on Turn on Script Execution.
- Select Not Configured in the dialog.
- Press OK and close the Local Group Policy Editor.
- Restart your computer and the next time you start BlueParq it should go without any issues.
Domain Policy
If your machine is part of an Active Directory domain, you have to check if there is a Domain Policy which prohibits you to executes scripts.