I thought the whole time i knew what I was doing when it came to building templates. I think this is a very important step to NEVER forget if you plan on using Windows Server 2008 R2 or Windows 7 (have not tried this with 2012 or 8 and all documentation does not exist for it yet).
This bug bit me hard this week. I'm planning out multiple SRM testing environments. My goal was to build a single vApp, and clone it a few times. Each clone will keep the same IP addresses and I will only have one environment on at a time to do testing. Of course, this would all be fine within vCD, but I took the old school route.
I have my vCenter/SQL/SRM server all on a single 2008 R2 VM. When I cloned this VM, the IP address didn't stay the same. in fact, a new vmxnet3 adapter was added to the VM and the old one was never found. No big deal, right? I'll go ahead and assign the same IP address to the new adapter. Once I did that I ended up with the dreaded error message "The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?" as seen in Microsoft KB 269155.
Add a comment