Windows Server Limitations

Consider the following limitations if any RN is running Windows Server:

•	(Windows Server 2012 & R2) Any PN running XenTools 6.1 or later is not supported; in this case, the RN fails to boot. However, a PN running on XenServer 6.1 or later without XenTools installed is supported.

•

(Windows Server 2012 R2 Only) It is possible that the mouse may not be activated when an RN is running in test mode via Java console. Attempt to run the RN in production mode, and use an RDP session to access the RN. This bug will be resolved pending a XenServer release of a new BIOS or Microsoft fix.

•	(Windows Server 2012 & R2) When a REFS volume in Windows Server 2012 or R2 is protected, the Recovery Node for the same will be in standard NTFS. This is also true of a Bare Metal Restore.

•

(Windows Server 2012 & R2) When a deduplicated volume in Windows Server 2012 R2 is protected, the Recovery Node for the same will again be a standard NTFS. This is also true of a Bare Metal Restore. Additional caution should be used in allocating RN disk space as the Quorum agent on the Protected Node will report actual disk usage, which might be far less than when data is stored in its normal form.

•	(All Windows Server platforms) When onQ event log reports 3010 code for any Windows PNs, both 32-bit and 64-bit, the auto-upgrade fails. Perform one of the following workarounds in the order that they are listed:

•	Restart onQ Service on the PN.

•	Reboot the PN.

•	Uninstall and reinstall the last msi package at C:\Program Files\Quorum\installer.

v3.6 SP1