I had a working Server 2008 R2 system running SQL Server 2012 Enterprise all on one 8G/4CPU VM and did a "copy to" vApp clone.
The new vApp was put onto a separate VLAN. Durring the copy process, guest customization was preselected and I gave the new VM a new machine name. I access both VLANs via OpenVPN from my WIndows 7 x64 desktop client.
So far so good, I could use the vDC console to log onto the new vApp machine using my previous admin credentials.
I ended up with two problems however...
1) none of my previous logins will work with SQL Server when I try to launch SQL Server Management Studio. I get a message saying "Login failed for user 'newmachine\user'" so maybe the usr SIDs for the cloned users are not the same as the original user SIDs? I would think it could not tell the difference if everything was cloned and only the machine name changed.
2) my Windows 7 RDP client will not connect unless I configure the new server to allow "any RDP" instead of only "Network Level Authentication" that was configured on the original server I cloned from. When I enable "any RDP" I can RDP in to the cloned system just fine.
The cloned machine had the new machine name and a new SID assigned by the cloning process. The original and clone are on isolated VLANs and cannot see each other. Both are using workgroups and not domains.
If I leave the cloned server RDP set to "NLA only" like the original server, my Windows 7 client gets a message complaining that RDP does not support NLA for the cloned machine. RDP works fine connecting to the original server that still has NLA only specified. The RDP instance that says I need NLA enabled, shows NLA is enabled in the about box.
Anyone seen either of these issues? Any suggestions?
Thanks, Dave