Page Comparison

Problem

Solution

This is generally caused by not following the requirements not being met for an ESXi scan . Make sure you are following all or due PowerCLI not being detected on the system. First, make sure the below requirements have been met:

• PowerShell installed

  • VMware.VimAutomation.Core module required as cmdlets for managing vSphere are needed

    • In the assessor-cli.log, search for Warning: VMware.VimAutomation.Core might not be imported, please check . If there is an occurrence, VMware.VimAutomation.Core module needs to be installed.

  • LanguageMode not configured to ConstrainedLanguage

• PowerCLI 6.5.1+ installed

• Assessed machine is a Microsoft Windows OS

Please ensure you have validated that you have PowerShell, the VMware.VimAutomation.Core module, PowerCLI 6.5.1+ installed, and the target machine is a Windows OS.

If the above requirements have been met and the issue is still present, the next step is to confirm the hasPowerCLI.ps1 script can be successfully run. The PowerShell Execution policy can prevent the hasPowerCLI.ps1 from running do to it being unsigned. To work around this follow the below steps:

1. Unzip the Assessor/scripts/scripts.zip file.

2. Run the command below to change the Execution Policy setting for the current PowerShell session:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

If this error occurs, the Execution Policy needs to be changed at the GPO level:

Image Added

3. After successfully setting the PowerShell Execution Policy to allow unsigned scripts, run the hasPowerCLI.ps1 script found in unzipped Assessor/scripts folder. It should return output similar to the below:

   Image Added

4. Once it is confirmed the hasPowerCLI.ps1 script can be run, re-run the assessment.

Keywords; ESXi unknown

Content by Label