Preconditions:
- Core and Agent are installed.
- Agent protected by Core as a single machine.
Possible steps to reproduce:
- Go to agent server, delete 'v2' namespace from WMI repository ( in PowerShell: gwmi -Namespace root\virtualization -class __Namespace -Filter "name = 'v2'" | rwmi )
- Go to Core UI -> agent summary tab (wait for issue, it can take a few days to reproduce)
Some actions and metadata are unavailable because machine is unreachable.

From agent logs:
ERROR 2018-02-12T07:04:06 [15] - Replay.Common.Implementation.WmiApi.Wmi ()
Invalid WMI namespace: root\virtualization\v2
System.Management.ManagementException depth 0: Invalid namespace (0x80131501)
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) +0x3f 600008c
at System.Management.ManagementScope.InitializeGuts(Object o) +0x118 600025c
at System.Management.ManagementScope.Initialize() +0x52 600025b
at Replay.Common.Implementation.WmiApi.Wmi.Connect() +0xb 60020f4
WARN 2018-02-12T07:04:06 [15] - Replay.Agent.Implementation.HyperV.Metadata.HyperVMetadataService ()
Unable to establish Hyper-V WMI connection
Replay.Common.Contracts.WmiApi.WmiException depth 0: Invalid WMI namespace: root\virtualization\v2 (0x80131500) ---> System.Management.ManagementException depth 1: Invalid namespace (0x80131501)
Expected result:
Metadata is available.