When you are trying to run the VM on your previously stored VHDX, And when you try that machine to join the DC and your domain controller also uses the same copy of your VHDX file, then you get the SID Error, do the following to ignore the error:
- At the command prompt, change to the root folder of drive C, Type C: then type CD %SystemRoot%\System32\Sysprep
- and then run sysprep
I was trying to make a fail over cluster using the following settings
VM 1= SQLA, Domain Controller
VM2= SQLP, Domain computer
Moreover I have created three iscsi drives on the SQLA machine. the idea was to use these disks while creating the fail over Cluster. The Drives were created successfully on SQLA machine and even the SQLP machine initiator machine was able to connect to the drives.
After running the Validation before creating the cluster I received the Following Warning
Solution: First of all a cluster can not be created on domain controller machine. both the machine needs to be in the same organization unit.
however when we try creating the cluster we receive the following errors:
the “cluster service” stops responding and even the iscsi Drive created in the target doesn’t shows up.
so in order to resolve this issue, turn the Cluster Service to disable and restart the Microsoft ISCSI target service. this will at least bring back your iscsi drives on target.
Once again the cluster will not be created on domain controller machine. and the cluster service will only be enabled once the cluster is setup between at least two computers.
Moreover in order to remove the node from the failed cluster you need to run the power shell command:
For Removing the Cluster nodes, when failed to load:
moreover these are some more helping Cluster Commands once the cluster is created successfully:
getting the cluster name created
getting the specific cluster created
Get-Cluster -Name Cluster1