Some of the IT people overlook this SID attribute of a machine forgetting the importance of unique SID/GUID requirements.
1. Try creating a clone of VM in Hyper-V or VMware Workstation and have them in Workgroup and see if you can enable communication between two clones
2. Try join the same clone VMs into Lab based domain and see how it goes
3. With domain user accounts added in the VM’s Lusrmgr.msc, post AD join and logging into VM with one of AD account and then demoting VM from domain, and then try to do a sysprep with domain accounts still there in local user accounts, and see if you can run sysprep successfully
Please do this Labwork and comment your results…
Just a sneak peak at the SID error…
It’s been long time, visiting again this blog for another Worth post. This time I have been to blog intentionally to post about Setting up the user-defined name to the Virtual Machine, which will be worth using; helpful in navigating through the open tabs of VM’s or for the sake of easy viewing purposes.
The below Video unveils the setting up of VM Name:
The network has been changed from NAT to Bridged for the sake of internal VM’s communication.
If the internet access or need to communicate with the Host operating system by the VM; Guest operating system, the NAT (Network Address Translation) should be left unchanged or to be configured for intended operation.
The removal of Floppy from the configuration window has been made intentionally to show, how the removal can be used as well. The removal of FLOPPY is recommended for some Computers, one which affects the boot process if the boot process is configured accordingly and had the FLOPPY in the Drive
The CDROM drive has been seen here with the “using C:\program files\ xxxxx” however if u want to use the original physical drive, you should choose “USE PHYSICAL DRIVE”, It sets the HOST O.S (your original desktop or laptop’s O.S) CDROM drive to used. If you want to use the physical drive in the VMware as if yuo use the drive physically.
The rest queries could be answered here; however related posts and further advanced settings and configurations could be expected in the future blog posts.