How to allow a virtual test lab using VMware ESX 3.5 and Windows Server 2003 to mingle with physical network?
Posted on 2009-07-14
Using VMware ESX 3.5 and Converter 4, we have virtualized clones of four of our production servers to use for a performance test outside of production hours. All servers have Windows Server 2003 and are members of a domain: one is a domain controller, one is our ERP database server using SQL Server 2005, and the other two run middle tier services for the ERP. No SYSPREP or other SID modifier was run. All four systems work well when connected to an isolated virtual switch, and the ERP client runs.
We need to move the ERP systems over to a virtual switch that is connected to our production environment (shutting down the physical servers that were cloned) to allow for a wider-scale performance test of the ERP. One of the servers comes up fine, but the other two (including the SQL box) will not log in to the production network. If we authenticate them on the virtual network then point their NICs to the virtual switch connected to the production network, we can ping them from clients, and ping clients from them, but they still generate authentication errors on our production DCs, and the ERP doesn't work.
We are considering using Reset Account on the computer accounts in Active Directory for these three systems then rejoin them to the production network. We anticipate that our actual production systems might then experience the same problems, and we'd have to reset the accounts again. We need 2-3 rounds of performance testing, so the accounts would get reset quite a bit.
Is anyone aware of problems all this computer account resetting will cause?
Have any other suggestions as to how we can get the virtual clones (same computer name, IP, SID) to work on the production network?