- When scanning a Hosted Virtual Machine in a Machine Group, the scan fails with error: Invalid credential for 'IP ADDRESS' (HYPERVISOR NAME) in Machine Group 'MACHINE GROUP NAME'
- Example: Invalid credential for '10.10.200.100' (VMware vCenter Server) in Machine Group 'Test'
- ST.Protect.managed log shows the following entry: Virtual Server '10.10.200.100' with null credentials is unsupported.
- A scheduled deployment fails.
- ST.TaskHost.Managed log shows the following: Virtual server not found for HostedVirtualSystem with managedMachineId (1) and scanId (18). Ensure the server has been added for this user (multi-user scenario).
- A scheduled scan fails. The Results/Scan Summary shows: Warning: No machines were found in this scan
- SCHF log shows the following entry: No machines to scan - resolved xml has no entries for machines
When Admin1 adds a Hosted Virtual Machine to a Machine Group, that machine group is visible to all other Protect users. However, because credentials are user specific, the Browse Credentials necessary to access the hypervisor and subsequently the Hosted Virtual Machine, are missing for other users.
The first Symptom listed is caused by running a scan logged in as a user who does not have the Browse Credential Assigned to the hosted VM.
Scheduled symptoms are caused by setting the Default Credential as a user who does not have a Browse Credential Assigned.
Hosted VM Missing Browse Credentials
Hosted VM With Browse Credentials
Add the vCenter Server or ESXi Hypervisor into Virtual Inventory.
- Click New> Add vCenter Server/ESXi Hypervisor...
- Enter the Server details and select credentials to access the Hypervisor and click Add.
- Reopen the existing Machine Group and verify that the machine now has Browse Credentials.
In the event the Hosted VM still does not show Browse Credentials, go through adding the Hosted VM into the existing Machine Group again. This will assign it the Browse Credentials.
Shavlik Protect All