VMware VSHIELD MANAGER 4.1 - Bedienungsanleitung PDF herunterladen (Seite 21)

Note: Guest VMs are shown as UNPROTECTED on the vShield tab in the vSphere Client console.

This refers only to vShield App protection, not to Sophos protection provided by vShield Endpoint.

You should ignore this and follow the instructions in this section to check that VMs are protected.

9.1 Check the status in vSphere Client

You check the status of a security VM in vSphere Client as follows.

Important:

There can be a delay of up to 20 minutes between activating a security VM and seeing its status

in vSphere Client change.

In vSphere Client, on the vShield tab, Endpoint page, look for the security VM in the computer

list.

The Description should show “vShield Endpoint Solution, Sophos Anti-Virus for VMware

vShield, enabled” and there should be no critical errors under Endpoint Status.

2. If the Description does not show “enabled” and there is a critical error, perform the relevant

action according to this table:

ActionDescription

Ensure that the vShield Endpoint module and the

security VM have protocols that are compatible

with each other.

There is a protocol version mismatch with the

vShield Endpoint module.

Ensure that the security VM is powered on and

that the network is configured properly.

vShield Endpoint could not establish a connection

to the security VM.

Internal error. Contact your VMware support

representative.

The security VM is not reporting its status even

though guests are connected.

3. Look for the guest VMs in the computer list, displayed as “vm.”

The Description should show “Thin agent enabled”.

4. If the Description does not show “enabled”, turn on a guest VM that is turned off, or restart a

guest VM.

This should trigger the status to update.

startup guide

1 2 ... 16 17 18 19 20 21 22 23 24 25 26 ... 55 56

Keine Kommentare

VMware VSHIELD MANAGER 4.1 - Bedienungsanleitung Seite 21