Is it possible configure VIN to discover dependencies across multiple vCenter Servers?  It looks like each instance of VIN is associated with just one vCenter Server.  Neither linked mode nor SSO multi-site mode seems to integrate discovery across vCenter Servers.  If this is not possible in current version of VIN, is it something in the pipeline for next release?  May be some sort of integration of lookup/inventory services to gain visibility across VCs? 

Even in liked mode, each VIN instance is displaying VMs from second vCenter Server as external VMs and stops discovering any further dependencies.  I didn't find any reference to specific instructions for VIN setup in linked mode.  Can you please provide link to the section you referred to?  thanks