I have multiple severs set up for clients where they have two servers and VM’s are replicated across for backup purposes and so downtime is reduced if the main server has hardware faults.

For whatever reason, sometimes the replication fails and needs to be reset and re synced manually from scratch with a few clicks. In these instances, you need to be notified so you can manually enable the replication to start again.

Step 1. Open up Task Scheduler
Step 2 – Created a New task, name it something like Email Alert For VM Replication Fail
Step 3 – Make sure it runs whether user is logged on or not see below screenshot:

Step 4 – Set the trigger to on event. Fill in the details as per below screenshot:

Step 5 – Set an Action to email yourself via powerscript. Make sure you select the clients ISP SMTP gateway that does not need authentication.
For the argument you need to edit this line to suit your needs.

-command &{send-mailmessage -from [email protected] -to [email protected] -subject ‘VM Replication issue on HyperV’ -body ‘Go Gix It!’ -smtpserver x.x.x.x}

The Event ID I have used gives me emails when the replication is critical and manually needs to be reset. If you want more alerts for even warnings you will need to add more schedules for more ID’s The following ID’s if you search in even log will give you the main ones. This article here mentions the main ones also.

http://www.altaro.com/hyper-v/how-to-check-hyper-v-replica-health-part-2/

Recently, during a mass construction of ASrock Z87 Extreme 4 motherboards with Corsair H100i water cooling units, an issue occurred where a couple of the H100i were failing to be detected in Corsair Link (A program used to control the speed of the fans) upon booting up. However, physically unplugging the H100i from the USB socket it was currently in and moving it to another nearby USB socket in the Z87 Extreme 4 Motherboard instantly caused the H100i to be detected in the system and the fans/LED/Temps all appeared in Corsair Link. That is, until next boot where the problem occurred once again. We attempted a few simple solutions (such as: Driver updates, Software updates, etc) and none of these were successful for our issue.

Browsing the Corsair Forums we discovered a post by the user Scotty_Two (link below) who (through another user – Thatualle1970) suggested a neat, fairly simple and reversible workaround for Windows 8.1 that went as follows:

1. Pressing the windows key + r (bring up the run

   command) and run “regedit“. This will open you up to the registry editor window

2. Find and navigate through “HKEY_LOCAL_MACHINE” > “SYSTEM” > “CurrentControlSet” > “Enum” > “USB” > “VID_1B1C&PID_0C04“
3. You should find one or possibly more folders of random numbers, letters, and ampersands (in our case there were 3 folders and all of them were just random numbers)
4. In each of these folders contained another folder named, “Device Parameters” containing 4 important

   DeviceSelectiveSuspended“, “EnhancedPowerManagementEnabled” and “SelectiveSuspendEnabled“

5. By double clicking each of those 4 entries listed above we edited the value data from 1 (on) to 0 (off)

After applying this fix we rebooted the computers and relaunched Corsair Link. To find that all our fans/LED/temp control are there without the need to (constantly) move the USB socket we currently have the H100i plugged in to.

Multiple reboots later; we still have no need to swap the USB socket it is currently plugged in to.

To reverse this change, one

would simply navigate back through the registry (steps 1-4 above) and at step 5 instead of changing the value data to 0 for the 4 strings (“AllowIdleIrpInD3“, “DeviceSelectiveSuspended“, “EnhancedPowerManagementEnabled” and “SelectiveSuspendEnabled“), switch them back to 1.

For more information visit: http://forum.corsair.com/v3/showthread.php?t=120962