Windows PowerShell execution policies and profiles

To be able to run commandlets automatically from the Windows PowerShell command line, you must first set the execution policies to the correct level, as well as create administrator profiles on your local host. If you do not set the policies correctly, you might not be able to run the provisioning and cloning commandlets securely or at all.

The following lists the possible values for Windows PowerShell execution policies:

Restricted: Restricts any scripts to be run, downloaded, or installed.
AllSigned: Allows scripts to run that have been verified with security certificates.
RemoteSigned: Allows scripts to be run, downloaded, or installed. This policy is not secure and malicious code can easily exploit and damage any PowerShell .ps1 or VB script files.

By default, the Windows PowerShell execution policies are set to Restricted. To run the provisioning and cloning commandlets securely, you should set the Windows PowerShell execution policy to AllSigned.

For more information on how to set Windows PowerShell execution policies, see the Microsoft TechNet site.

You need to import the SCCmdlets module into your local Windows PowerShell profile, if you want them to be available from any Windows PowerShell session. This allows you to use SCCmdlets module through PowerShell sessions from Microsoft applications, such as System Center Virtual Machine Manager and System Center Operations Manager. For more information on Windows profiles, see the Windows PowerShell Owner's Manual on the Microsoft TechNet site.