Windows

The following modules can be used on Windows for monitoring:

  • Bare Metal

  • Microsoft Hyper-V

  • Storage Spaces

  • Microsoft IIS Server

  • Microsoft SQL Server

Requirements

The following Windows components are required on Windows Servers for monitoring:

  • Microsoft PowerShell v2 or later

  • .NET Framework 2.0 or later

Remote Management Requirements for Windows Servers

Remote Management is enabled by default for Windows Server 2012 R2 and later versions. If you want to monitor earlier versions of Windows, you should enable Remote Management to allow agentless monitoring.

To enable Remote Management, start a PowerShell with Administrator rights and execute the following commands.

1. Enable PSRemoting. You should enter Y for all questions.

Enable-PSRemoting

2. Configure WinRM Max Envelope Size. (Optional)

Set-Item WSMan:\localhost\MaxEnvelopeSizekb 1024

3. Configure WinRM Max Memory Per Shell. (Optional)

Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 2048

Remote Management Requirements for Windows Desktop Clients

If you want to monitor Desktop versions of Windows, you should enable Remote Management to allow agentless monitoring.

To enable Remote Management, start a PowerShell with Administrator rights and execute the following commands.

1. Enable PSRemoting. You should enter Y for all questions.

Enable-PSRemoting -SkipNetworkProfileCheck -Force

2. Configure Windows Firewall Rule. (Optional)

Set-NetFirewallRule –Name "WINRM-HTTP-In-TCP-PUBLIC" –RemoteAddress Any

Supported Versions

VirtualMetric supports the following versions of Windows:

Windows Server 2003 R2
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows Server Core 2008 R2
Windows Server Core 2012
Windows Server Core 2012 R2
Windows Server 2016
Windows Server Core 2016
Windows Server 2019
Windows Server Core 2019
Windows Nano Server
Windows 7
Windows 8
Windows 10

Sizing

Hardware requirements for VirtualMetric depends on the total number of monitored objects (Hyper-V VM, Microsoft IIS WebSite, Microsoft SQL Server Database, etc.) and intervals used. The following values are provided as reference for typical usage (based on 20 seconds interval). Inventory collections are not included in this calculation.

Bare Metal

  • Per Server a. 50 MB of memory (VirtualMetric Trigger) b. 4 Kbps of bandwidth (VirtualMetric API) c. 15 MB of disk space per month (VirtualMetric Database)

Microsoft Hyper-V

  • Per Host a. 50 MB of memory (VirtualMetric Trigger) b. 4 Kbps of bandwidth (VirtualMetric API) c. 15 MB of disk space per month (VirtualMetric Database)

  • Per Virtual Machine a. 5 KB of memory (VirtualMetric Database) b. 4 Kbps of bandwidth (VirtualMetric API) c. 20 MB of disk space per month (VirtualMetric Database)

Microsoft IIS Server

  • Per Server a. 50 MB of memory (VirtualMetric Trigger) b. 8 Kbps of bandwidth (VirtualMetric API) c. 20 MB of disk space per month (VirtualMetric Database)

  • Per Web Site a. 5 KB of memory (VirtualMetric Database) b. 16 Kbps of bandwidth (VirtualMetric API) c. 30 MB of disk space per month (VirtualMetric Database)

Microsoft SQL Server

  • Per Server a. 50 MB of memory (VirtualMetric Trigger) b. 32 Kbps of bandwidth (VirtualMetric API) c. 50 MB of disk space per month (VirtualMetric Database)

  • Per Database a. 10 KB of memory (VirtualMetric Database) b. 24 Kbps of bandwidth (VirtualMetric API) c. 40 MB of disk space per month (VirtualMetric Database)

Proxy Configuration

If you use a proxy configuration on Windows Server, you may need to add an exception for VirtualMetric.

1. Go to the Notification Center and click All Settings.

2. To edit the proxy exception list, click Proxy and type your VirtualMetric API address. Then, click the Save button to apply the changes.

Double Hop Configuration

You may see the following error when you try to monitor a Hyper-V Cluster or Standalone Server that uses Storage Spaces Scale Out File Server as storage.

Cannot find path '\\S2DSMB\Gold\Test.vhdx' because it does not exist.
    + CategoryInfo          : ObjectNotFound: (\\S2DSMB\Gold\Test.vhdx:String)
    [Get-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetIt
   emCommand
    + PSComputerName        : vmetric-s2d-hv.virtualmetric.com

Due to the Double-Hop issue, VirtualMetric is not able reach the Storage Spaces File Share.

1. To fix this issue, you should use delegation on the S2DSMB File-Share account with PowerShell.

$SOFSSMB = Get-ADComputer "S2DSMB" # This is your Scale Out File Server
$SOFSHV = Get-ADComputer "vmetric-s2d-hv" # This is your Hyper-V Host
Set-ADComputer -Identity $SOFSSMB -PrincipalsAllowedToDelegateToAccount @($SOFSHV) # Set delegation for Hyper-V host on SMB file share account

You don't need to do this operation on all SOFS Cluster Members, but only for SOFS File Share.

2. After this, you may need to clear the Kerberos cache to apply the changes immediately.

klist purge -li 0x3e7

3. You should clear the Kerberos cache on all Hyper-V Hosts and SOFS Cluster members. Otherwise, you may have to wait 15 minutes.

4. You may still have Access Denied messages after clearing the Kerberos Cache. If your user account has no privileges on the SOFS Cluster nodes, you should give it permission on the nodes.

5. Make sure that your user account has Local Administrator privileges on the SOFS Nodes.

PreviousVersion 8.0.3NextVMware

Last updated