|8/20/2008||You recevied the error "cannot be loaded because the execution of scripts is disabled on this system"||When executing scripts, you need to change the default security policy of PowerShell.
To do this, execute the following command:
|8/20/2008||Running script manually returns "The term '...' is not recognized as a cmdlet..."||This means PowerShell can not locate your script. PowerShell wants absolute paths, not relative. Unlike a regular Command Prompt, where you can change to the directory and type a filename to use, PowerShell wants you to enter the full-path.
In a regular command prompt, you could:
In PowerShell, you must enter the full path:
|8/20/2008||How do I debug script execution issues?||You can run scripts manually at a PowerShell Command Prompt to see if they work.
For example, to run the BIOS script manually, type the command using the following format:
|8/20/2008||LCCPowerShellGUI runs, shows scripts, but the results are blank.||A good chance is that the PowerShell foundation is not authorizing the scripts to run. These things are required for scripts to run through the LCCPowerShell GUI.
|8/20/2008||Unhandled exception: Could not load file or assembly
|This error occurs if the requirements have not been installed. To run LCCPowerShellGUI, you will need to install the requirements listed in the Whitepaper.|