How to stop Windows mounting read-only VVR volumes
If you kill a server and VVR does a takeover on another node, then when the node comes back, Windows assigns drive letters to the now read-only volumes when the diskgroup is imported. This means in VCS, after the VVR SG is onlined (and hence diskgroup imported), after a few minutes when the offline monitor runs for the MountV resources it detects these are online and you get a partially online application service group. You can't then fail back to that node until you manually offline the application service group. If there a formal way to stop this or technotes explaining this issue?
This is what I believe is happening:
When you online a MountV resource in VCS, when the drive letters gets assigned to a volume, this gets written to registry in \HKLM\SYSTEM\MountedDevices, so you will see something like:
This registy keys are there for all drives including the C:, so this includes partitions as well as volumes and these keys are present on XP clients too.
When you offline MountV resource, this registry entry is removed.
This makes sense so that with a server without VCS, if you reboot a server, then when the server returns the volume or partition receives the same drive letter that it had before.
With shared diskgroup failover, when a faulted node returns, the diskgroup is not imported as it is now imported on the failover node, so this does not cause a problem, it is only with VVR where diskgroup is imported on Seconday (or acting Secondary) as well as primary.
I wrote a quick postonline trigger for the VVR group to get offline Mounts when VVR is a secondary, but I figured there must be an official work-a-round or technote describing this issue.
Note, I see this more as a SFW problem rather than a VVR issue as this is not an issue for VVR on UNIX which is why I have started this forum under SFW rather than VVR.