I am in the process of trying to deploy a Windows VM with 2 vNICs but cannot get past the Windows Setup following the initial vSphere Guest Customization. It basically hangs at this point because Windows appears to be unable to detect all component settings (I'm thinking here the 2nd Adapter is causing grief during the device setup phase??)...I am receiving errors similar to the following..("Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml].......A component or setting specified in the answer file does not exist"). My guess is sysprep'ing a Windows machine with 2 vNICs cannot be done in vCenter 5.5 but only speculating right now?? Just for info, we even modified the vSphere Guest Customization XML file by adding a 2nd Adapter but no luck there either.
Was wondering if anyone has a vRO Workflow they could share or suggest a method we could use in vRA/vRO 7 to add a 2nd vNIC to a VM either during or immediately following vRA Machine Provisioning?? Including this function during machine provisioning is required/preferred because we allocate IP addresses to network adapters using pre-configured vRA Network Profiles.
I realize this can be done using PowerCLI but was hoping to perhaps use a "Scriptable Task" in vRO as opposed to having to invoke an external script from a PowerShell host. The PowerCli method simply introduces additional routines, such as, connecting to vCenter using elevated User Accounts, Passwords...etc. and also makes IP allocation using predetermine Network Profiles a little more difficult or perhaps impractical afterwards.
I also recently discovered another source with actual vRO/vSphere native code that will allow me to perform the same routine. The link is pasted below for info. Although there were a few obstacles in compiling the code and navigating the process, the info was deemed excellent in allowing me to complete my task.
I'll update this post later with a copy of the vRO Workflow I created based on the input in the above link as a form of paying it forward to the Community. I'm guessing others may find it useful when performing similar automation routines.