I currently have three traditional FCI SQL 2012 instances within WSFC configured between two physical servers. I am looking to add AlwaysOn Availability Groups functionality to one of these instances to be used for DR purposes. The new SQL server will be a virtual node located at a site remote to the current FCIs on the physical nodes. I am running into something which seem like it would be problematic but may just be making a mountain out of a mole hill.
Obviously the new virtual node needs to be added to the same WSFC containing the two physical nodes that run the three current FCIs. When I join the virtual node to the WSFC, the virtual node is added as a selected possible owner to most of the resources in the three current FCIs (e.g. SQL Server (INSTANCE), SQL Server Name and IP address, Cluster Name and IP Address, etc.) The virtual node is also added as an unselected possible owner on the shared disks, unselected obviously because it doesn't have access to the physical storage that presents those disks. For obvious reasons, this virtual node should never ever own any of the existing FCIs' resources. I just want the virtual node in the WSFC for AlwaysOn AG purposes. Should I go through all the existing FCI resources and deselect the virtual node as possible owner, even the Cluster Name and IP Address? It seems bad that a new node to a WSFC should automatically be added to resources of the existing FCI services when there is no way that the new node could ever own those services.