You can edit and extend the configuration script of vSphere PowerCLI to set up the environment, set vSphere PowerCLI startup actions, or define cmdlets aliases.

Creating a Custom Script Configuration File

If you want to load custom vSphere PowerCLI settings automatically, you can create a script configuration file named Initialize-PowerCLIEnvironment_Custom.ps1 in the Scripts folder. The application recognizes and loads the custom file after loading the default script configuration file.

Note

Changing the contents of the default configuration file Initialize-PowerCLIEnvironment.ps1 might cause vSphere PowerCLI to stop running properly.

Signing the Script Configuration File

When the execution policy of your system is set to Remote Signed, you do not need to sign the script configuration file after editing.

When the execution policy of your system is set to All Signed, you need to sign the script configuration file after editing. If you do not sign the file, vSphere PowerCLI will not load your modified configuration.

To learn more about setting the execution policy, see Set the Properties to Support Remote Signing.