• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 7 - Server domain connection question...

Scarpozzi

Scarpozzi

Lifer
I have a virtual machine where I installed with Windows 7. I copied the virtual machine to a second system. Both of them join the domain without an issue....but I think because they are the same virtual image, the licensing is getting screwed up somehow when it validates with the Windows domain licensing server.

So...my question....are there particular settings or registry keys I need to hack on one of these boxes so it doesn't collide with the other...or am I crazy and these errors have nothing to do with licensing.

When I logout/login to a system after joining the other VM to the domain, I get trust errors on the login screen and have to auth as the local admin account instead of the domain user/admin....then I have to leave the domain/reboot and rejoin/reboot to fix it.

Thanks.
 
did you sysprep the vm before copying it? sounds like SID problem. Using the same image is fine, but it has to be prepped to allow multiple VMs to be spun up off it.
 
When you clone a VM, doesn't some info (like the MAC address) change, so the SID is different?

When I clone a VM that's already been bound to AD, I usually have to unbind/rebind it, or I will have issues. But the SIDs don't conflict.
 
Because you cloned the VM both Win7 installs have the same computer name. You can't join two computers to a domain using the same name.
 
dave_the_nerd said:
When you clone a VM, doesn't some info (like the MAC address) change, so the SID is different?

When I clone a VM that's already been bound to AD, I usually have to unbind/rebind it, or I will have issues. But the SIDs don't conflict.
Click to expand...

Only a sysprep changes the SID (at least from the 'MS tools' side). If you are just cloning VM's then you have SID mapping issues. It would be very obvious is you used WSUS as the duplicate SID machines would constantly replace each other in the reports.
 
It's a virtual box VM. I did no sysprep on it.

The copy was a total afterthought. I can check the virtual Mac and SID next time I boot my laptop. I just couldn't remember what all was registered when it signed in to the domain.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top