Home
  •  

Microsoft Windows Server 2016 and 1709+ Network Load Balancing

Microsoft.Windows.NetworkLoadBalancing.2016 :: 10.0.2.1 (Management Pack)

This management pack contains logic to discover and monitor Windows Server 2016 and 1709+ NLB clusters.

Management Pack Elements

Classes (3)

 DisplayNameIDBase ClassAbstractHostedSingletonGroupExtensionAccessibility
Microsoft.Windows.NetworkLoadBalancing.10.0.ComputersWindows Server 2016 and 1709+ NLB Computers GroupMicrosoft.Windows.NetworkLoadBalancing.10.0.ComputersMicrosoft.SystemCenter.ComputerGroupFalseFalseTrueTrueFalsePublic
Microsoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterWindows Server 2016 and 1709+ NLB Network AdapterMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterMicrosoft.Windows.Server.10.0.NetworkAdapterFalseTrueFalseFalseFalsePublic
Microsoft.Windows.NetworkLoadBalancing.10.0.ServerRoleWindows Server 2016 and 1709+ NLB Server RoleMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleMicrosoft.Windows.NetworkLoadBalancing.ServerRoleFalseTrueFalseFalseFalsePublic

DataSource Modules (2)

 DisplayNameIDIsolationAccessibility
Microsoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.DataSourceWindows Server 2016 and 1709+ NLB Cluster Discovery Data SourceMicrosoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.DataSourceAnyPublic
Microsoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.EventBasedDataSourceWindows Server 2016 and 1709+ NLB Cluster Discovery Event-Based Data SourceMicrosoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.EventBasedDataSourceAnyPublic

ProbeAction Modules (1)

 DisplayNameIDIsolationAccessibility
Microsoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.ProbeWindows Server 2016 and 1709+ Cluster Discovery ProbeMicrosoft.Windows.NetworkLoadBalancing.10.0.ClusterDiscovery.ProbeAnyPublic

WriteAction Modules (2)

 DisplayNameIDIsolationAccessibility
Microsoft.Windows.NetworkLoadBalancing.10.0.CollectEventCollect Event Write ActionMicrosoft.Windows.NetworkLoadBalancing.10.0.CollectEventAnyPublic
Microsoft.Windows.NetworkLoadBalancing.10.0.GenerateAlert.SuppressByDescriptionGenerate Alert Write ActionMicrosoft.Windows.NetworkLoadBalancing.10.0.GenerateAlert.SuppressByDescriptionAnyPublic

Unit Monitor Types (2)

 DisplayNameIDAccessibilitySupport Monitor Recalculate
Microsoft.Windows.NetworkLoadBalancing.10.0.DriverInitializationFailureMonitorTypeDriver initialization problem monitor typeMicrosoft.Windows.NetworkLoadBalancing.10.0.DriverInitializationFailureMonitorTypePublicFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.RepeatedEventLogManualReset2StateMonitorTypeRepeated event monitor typeMicrosoft.Windows.NetworkLoadBalancing.10.0.RepeatedEventLogManualReset2StateMonitorTypePublicFalse

Discoveries (3)

 DisplayNameIDTargetEnabled
Microsoft.Windows.NetworkLoadBalancing.10.0.Cluster.DiscoveryWindows Server 2016 and 1709+ NLB cluster discoveryMicrosoft.Windows.NetworkLoadBalancing.10.0.Cluster.DiscoveryMicrosoft.Windows.Server.10.0.ComputerTrue
Microsoft.Windows.NetworkLoadBalancing.10.0.Cluster.EventBasedDiscoveryWindows Server 2016 and 1709+ NLB cluster discovery (event based)Microsoft.Windows.NetworkLoadBalancing.10.0.Cluster.EventBasedDiscoveryMicrosoft.Windows.Server.10.0.ComputerTrue
Microsoft.Windows.NetworkLoadBalancing.10.0.ComputerGroupDiscoveryPopulate Windows Server 2016 and 1709+ NLB Computers group discovery ruleMicrosoft.Windows.NetworkLoadBalancing.10.0.ComputerGroupDiscoveryMicrosoft.Windows.NetworkLoadBalancing.10.0.ComputersTrue

Unit Monitors (3)

 DisplayNameIDTargetCategoryEnabledAlert GenerateAccessibility
Microsoft.Windows.NetworkLoadBalancing.10.0.FrequentConvergence.MonitorFrequent node convergenceMicrosoft.Windows.NetworkLoadBalancing.10.0.FrequentConvergence.MonitorMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAvailabilityHealthTrueTruePublic
Microsoft.Windows.NetworkLoadBalancing.10.0.SynAttackSYN AttackMicrosoft.Windows.NetworkLoadBalancing.10.0.SynAttackMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleSecurityHealthTrueTruePublic
Microsoft.Windows.NetworkLoadBalancing.10.0.TimerStarvationTimer starvationMicrosoft.Windows.NetworkLoadBalancing.10.0.TimerStarvationMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAvailabilityHealthTrueTruePublic

Rules (48)

 DisplayNameIDTargetCategoryEnabledAlert Generate
Microsoft.Windows.NetworkLoadBalancing.10.0..Client.stickiness.conflictMore than one node claims an IP address to be on the client affinity listsMicrosoft.Windows.NetworkLoadBalancing.10.0..Client.stickiness.conflictMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0..Client.stickiness.descriptors.exceededThe maximum number of IP addresses with stickiness to this node that could be tracked by NLB is reachedMicrosoft.Windows.NetworkLoadBalancing.10.0..Client.stickiness.descriptors.exceededMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0..Extended.affinity.configuration.is.inconsistentExtended affinity configuration is inconsistentMicrosoft.Windows.NetworkLoadBalancing.10.0..Extended.affinity.configuration.is.inconsistentMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.A.load.distribution.error.was.detected.during.convergenceA load distribution error was detected during convergenceMicrosoft.Windows.NetworkLoadBalancing.10.0.A.load.distribution.error.was.detected.during.convergenceMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.A.port.rule.operation.was.issued.but.there.is.no.port.rule.that.contains.this.portA port rule operation was issued but there is no port rule that contains this portMicrosoft.Windows.NetworkLoadBalancing.10.0.A.port.rule.operation.was.issued.but.there.is.no.port.rule.that.contains.this.portMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.An.unsupported.legacy.host.was.discovered.on.the.networkAn unsupported legacy host was discovered on the networkMicrosoft.Windows.NetworkLoadBalancing.10.0.An.unsupported.legacy.host.was.discovered.on.the.networkMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.BiDirectional.affinity.team.configuration.problem.detectedBi-Directional affinity (BDA) team configuration problem detectedMicrosoft.Windows.NetworkLoadBalancing.10.0.BiDirectional.affinity.team.configuration.problem.detectedMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.BiDirectional.affinity.team.configuration.warningBi-Directional affinity (BDA) team configuration warningMicrosoft.Windows.NetworkLoadBalancing.10.0.BiDirectional.affinity.team.configuration.warningMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Duplicate.dedicated.IP.address.was.detected.on.the.networkDuplicate dedicated IP address was detected on the networkMicrosoft.Windows.NetworkLoadBalancing.10.0.Duplicate.dedicated.IP.address.was.detected.on.the.networkMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Maximum.transfer.unit.reported.by.the.adapter.is.too.small.to.contain.an.NLB.heartbeat.messageMaximum transfer unit (MTU) reported by the adapter is too small to contain an NLB heartbeat messageMicrosoft.Windows.NetworkLoadBalancing.10.0.Maximum.transfer.unit.reported.by.the.adapter.is.too.small.to.contain.an.NLB.heartbeat.messageMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NetworkInterface.PacketsReceivedPerSecond.CollectionNetwork Adapter\Packets Received/sec Performance RuleMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkInterface.PacketsReceivedPerSecond.CollectionMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterPerformanceCollectionTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NetworkInterface.PacketsSentPerSecond.CollectionNetwork Adapter\Packets Sent/sec Performance RuleMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkInterface.PacketsSentPerSecond.CollectionMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterPerformanceCollectionTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.cant.track.TCP.connections.because.it.was.unable.to.open.the.TCP.connection.callback.objectNLB can't track TCP connections because it was unable to open the TCP connection callback objectMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.cant.track.TCP.connections.because.it.was.unable.to.open.the.TCP.connection.callback.objectMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.cluster.IGMP.multicast.IP.address.is.invalidNLB cluster IGMP multicast IP address is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.cluster.IGMP.multicast.IP.address.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.a.duplicate.host.priority.that.is.shared.between.cluster.hostsNLB detected a duplicate host priority that is shared between cluster hostsMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.a.duplicate.host.priority.that.is.shared.between.cluster.hostsMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.an.unequal.number.of.dedicated.IP.addresses.and.network.masksNLB detected an unequal number of dedicated IP (DIP) addresses and network masksMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.an.unequal.number.of.dedicated.IP.addresses.and.network.masksMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.an.unequal.number.of.virtual.IP.addresses.and.network.masksNLB detected an unequal number of virtual IP (VIP) addresses and network masksMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.an.unequal.number.of.virtual.IP.addresses.and.network.masksMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.duplicate.cluster.subnetsNLB detected duplicate cluster subnetsMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.detected.duplicate.cluster.subnetsMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.attach.to.network.adapterNLB driver failed to attach to network adapterMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.attach.to.network.adapterMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.bind.to.the.adapterNLB driver failed to bind to the adapterMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.bind.to.the.adapterMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.IP.address.is.invalidNLB cluster IP address is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.IP.address.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.network.address.is.invalidNLB cluster network address is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.network.address.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.network.mask.is.invalidNLB cluster network mask is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.cluster.network.mask.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.number.of.port.rules.exceeds.the.configured.maximumNumber of port rules exceeds the configured maximumMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.initialize.because.the.number.of.port.rules.exceeds.the.configured.maximumMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.for.notifications.with.the.IPv4.NSI.providerNLB driver failed to register for notifications with the IPv4 NSI providerMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.for.notifications.with.the.IPv4.NSI.providerMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.for.notifications.with.the.IPv6.NSI.providerNLB driver failed to register for notifications with the IPv6 NSI providerMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.for.notifications.with.the.IPv6.NSI.providerMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.the.device.objectNLB driver failed to register the device objectMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.the.device.objectMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.unregister.the.hook.interfaceNLB driver failed to register/unregister the hook interfaceMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.failed.to.register.unregister.the.hook.interfaceMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.has.detected.one.or.more.sessions.corresponding.to.a.port.rule.that.is.improperly.configuredNLB driver has detected one or more sessions corresponding to a port rule that is improperly configuredMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.driver.has.detected.one.or.more.sessions.corresponding.to.a.port.rule.that.is.improperly.configuredMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.add.a.multicast.MAC.address.to.the.network.adapter.it.is.bound.toNLB failed to add a multicast MAC address to the network adapterMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.add.a.multicast.MAC.address.to.the.network.adapter.it.is.bound.toMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.add.all.the.dedicated.IP.addresses.to.this.hostNLB failed to add all the dedicated IP (DIP) addresses to this hostMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.add.all.the.dedicated.IP.addresses.to.this.hostMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.converge.due.to.inconsistencies.in.the.port.rules.between.this.host.and.another.cluster.hostNLB failed to converge due to inconsistencies in the port rules between this host and another cluster hostMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.converge.due.to.inconsistencies.in.the.port.rules.between.this.host.and.another.cluster.hostMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.converge.due.to.port.rules.with.a.duplicate.single.host.priority.in.the.clusterNLB failed to converge due to port rules with a duplicate single host priority in the clusterMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.converge.due.to.port.rules.with.a.duplicate.single.host.priority.in.the.clusterMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.read.or.verify.the.configuration.parametersNLB failed to read or verify the configuration parametersMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.read.or.verify.the.configuration.parametersMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.register.as.a.WMI.providerNLB failed to register as a WMI providerMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.register.as.a.WMI.providerMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.update.the.adapter.multicast.listNLB failed to update the adapter multicast listMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.update.the.adapter.multicast.listMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.update.the.NLB.host.state.in.the.registryNLB failed to update the NLB host state in the registryMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.failed.to.update.the.NLB.host.state.in.the.registryMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.Host.converged.with.legacy.hostNLB Host converged with legacy host(s)Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.Host.converged.with.legacy.hostMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.received.a.heartbeat.from.a.host.with.an.invalid.IDNLB received a heartbeat from a host with an invalid IDMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.received.a.heartbeat.from.a.host.with.an.invalid.IDMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.NLB.will.not.attach.to.adapter.because.it.does.not.support.dynamic.changing.of.its.MAC.addressNLB will not attach to adapter because it does not support dynamic changing of its MAC addressMicrosoft.Windows.NetworkLoadBalancing.10.0.NLB.will.not.attach.to.adapter.because.it.does.not.support.dynamic.changing.of.its.MAC.addressMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.The.dedicated.IP.address.is.invalidDedicated IP (DIP) address is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.The.dedicated.IP.address.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.The.dedicated.network.mask.is.invalidDedicated network mask is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.The.dedicated.network.mask.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.The.maximum.number.of.actively.serviced.connections.that.could.be.tracked.by.NLB.is.reachedThe maximum number of actively serviced connections that could be tracked by NLB is reachedMicrosoft.Windows.NetworkLoadBalancing.10.0.The.maximum.number.of.actively.serviced.connections.that.could.be.tracked.by.NLB.is.reachedMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.The.NLB.driver.could.not.allocate.enough.memory.resources.to.perform.driver.operationsNLB driver could not allocate enough memory resources to perform driver operationsMicrosoft.Windows.NetworkLoadBalancing.10.0.The.NLB.driver.could.not.allocate.enough.memory.resources.to.perform.driver.operationsMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Version.mismatch.between.the.NLB.driver.and.control.programsVersion mismatch between the NLB driver and control programsMicrosoft.Windows.NetworkLoadBalancing.10.0.Version.mismatch.between.the.NLB.driver.and.control.programsMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Virtual.IP.address.in.a.port.rule.is.invalidVirtual IP address in a port rule is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.Virtual.IP.address.in.a.port.rule.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Virtual.IP.address.is.invalidVirtual IP (VIP) address is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.Virtual.IP.address.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse
Microsoft.Windows.NetworkLoadBalancing.10.0.Virtual.network.mask.is.invalidVirtual network mask is invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.Virtual.network.mask.is.invalidMicrosoft.Windows.NetworkLoadBalancing.10.0.ServerRoleAlertTrueFalse

Discovery Property Overrides (1)

 DisplayNameIDContextTarget
Microsoft.Windows.NetworkLoadBalancing.10.0.NLBClusterDiscovery.DisableOnNanoDisable Windows Server 2016 and 1709+ NLB clusters discovery on Nano serversMicrosoft.Windows.NetworkLoadBalancing.10.0.NLBClusterDiscovery.DisableOnNanoMicrosoft.Windows.Server.10.0.Nano.ComputerMicrosoft.Windows.NetworkLoadBalancing.10.0.Cluster.Discovery

Monitor Property Overrides (1)

 DisplayNameIDContextTarget
EnableNetworkAdapter.10.0.StateMonitorForNLBNetworkAdaptersEnable network adapter state monitor for NLB 2016 and 1709+ network adaptersEnableNetworkAdapter.10.0.StateMonitorForNLBNetworkAdaptersMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterMicrosoft.Windows.Server.10.0.NetworkAdapter.NetworkAdapterConnectionHealth

Folder Items (1)

 DisplayNameIDFolderNameElementID
Microsoft.Windows.NetworkLoadBalancing.10.0.LoadDistributionPerformanceViewWindows Server 2016 and 1709+ - Load distribution across nodesMicrosoft.Windows.NetworkLoadBalancing.10.0.LoadDistributionPerformanceViewMicrosoft.Windows.NetworkLoadBalancing.PerformanceFolderMicrosoft.Windows.NetworkLoadBalancing.10.0.LoadDistributionPerformanceView

Views (1)

 DisplayNameIDTargetTypeAccessibilityVisible
Microsoft.Windows.NetworkLoadBalancing.10.0.LoadDistributionPerformanceViewWindows Server 2016 and 1709+ - Load distribution across nodesMicrosoft.Windows.NetworkLoadBalancing.10.0.LoadDistributionPerformanceViewMicrosoft.Windows.NetworkLoadBalancing.10.0.NetworkAdapterMicrosoft.SystemCenter.PerformanceViewTypePublicTrue