Validating that the servers contain only signed drivers

There are some new event channels for failover clustering to help with troubleshooting. Note that the events are specific to the node you're on.Knowing the purpose of each event channel can help you find the errors more quickly, which in turn will help you troubleshoot the problem more quickly.

Now I'll discuss some of the improvements made to the troubleshooting tools for failover clusters and show you how to take advantage of those tools.Here's an explanation of each channel: Because administrators often encounter problems when creating clusters and joining nodes, I want to show you how to use the Failover Clustering-Client/Diagnostic channel.This channel is disabled by default, so it won't be collecting any data.To enable it, you need to right-click the channel and choose Enable Log.The Diagnostic channel will then start collecting data relevant to a join or create operation. With the new features of Server 2012 Failover Clustering, the cluster will be created in the same organizational unit (OU) as the nodes.I'm using a Cypress FX3 controller over USB 3 and I've had success with it on Windows 7 by modifying Cypress's driver file to identify my device and then signing the driver package. We have a driver which passes the HLK and HCK tests.


Leave a Reply