Deploying the identity and vcac appliances sets their IP and FQDN.
That becomes the public fqdn for users to access the vcac - network1
But my VM to VM communication is on a internal only network - network2
So after I setup the vcac appliances and install iaas components, I try add the Windows AD identity store.
Problem is that vcac cannot find the AD domain because AD is on the internal only network2 and vcac is on the public network1.
This seems to me the vcac appliances need to have two NICs; one to for public FQDN and second for inter-VM communications in order to resolve the AD domain.
See attached screenshot:
The two Windows VMs are on the internal network, the IaaS VM is joined to the AD domain
The VMware appliances are on the external network.
Can I manually add a second NIC to the identity and vcac appliances in order for them to find the windows AD domain?
If not does this mean vcac only operates on one network for public and VM to VM communication?
