Wednesday, July 23, 2014

No mapping between account names and security IDs was done

Today, when i was working with the VM, so i need multiple VM for my LAB environment to test my Lync servers. I created one VM and create multiple VM from one VM.

Such as Lync frontend, SQL server etc.
When assigning the service accounts to the various SQL services the following error popped up when selecting the account to use:



The issue:
Since I created a single VM and used it as the base for both my domain controller and my SQL VM the machines has the same SID. Normally this is not a problem except in one case when a DC is involved. In the end, the fact that both machines had the same SID was the issue.
The resolution:
The domain controller should have it’s own SID. Everything else can have the same SID, but the DC needs to be unique. This can mean doing one of two things; run SYSPREP on each new VM you create on top of the differencing VM or just create two separate VMs (one for the DC and a separate image for everything else).
I chose to go option two. I have a single image I use for the DC and a second image that is the base image for all differencing disks that I may create. This way the DC SID is always guaranteed to be different from the other VMs I create and I don’t have to bother with running the annoying SYSPREP process every time I create a new VM.
If you do choose the SYSPREP route though here is what you need to do:
  1. From the Start Menu select Run
  2. Enter C:\Windows\System32\sysprep\sysprep.exe in the box and click OK
  3. Be sure that Enter System Out-of-Box Experience (OOBE) is selected
  4. Check the box next to Generalize (If this is not select the SID won’t get changed)
  5. Click OK and follow the prompts when the system reboots.

No comments:

Post a Comment