Newbie getting started
-
I am using a VMware ESXi 5.5 server. Does the UEFI/BIOS layout come from the actual vm hard drive? I was thinking it pulled that from the autoattend.xml file?
-
@bogle No it comes from the mode the VM is in. I can’t say for sure if 5.5. supports uefi VMs or not. Its like on the advanced tab of the VM setup.
VM Options->Boot Options->Firmware Options
-
Found it, its under options
-
How do you configure joining a domain and local accounts on your images? Do you join the domain after deploying your image?
-
@bogle said in Newbie getting started:
How do you configure joining a domain and local accounts on your images? Do you join the domain after deploying your image?
Yes, the only time the image is connected to the domain is after it has been deployed. I personally use the unattend.xml file to connect the computer to the domain due to some complex OU and system naming convention. The other option is to use the fog client to connect the system to AD. Either way will work.
-
@bogle Ah you are still using the C# client for vSphere. The path I gave you was for the web ui in vSphere. It gives you the same results. I have one VM for bios and one VM for UEFI.
-
@george1421 Don’t know about the C# client. I know I am using the vSphere Client 5.5.0 Build 3237766 with VMware ESXi server 5.5 Build 3568722.
-
@bogle said in Newbie getting started:
@george1421 Don’t know about the C# client. I know I am using the vSphere Client 5.5.0 Build 3237766 with VMware ESXi server 5.5 Build 3568722.
If you are using the vSphere client .exe that is the C# version. Starting in ESXi v6.x they don’t use the C# tool to admin ESXi. You have to use the HTML5 Web UI or Flash client.
-
Do you guys use sysprep in the process of creating your golden image? I am currently using it but I am beginning to think its not necessary if you prepare your image the way you want it then deploy it.
-
@bogle said in Newbie getting started:
Do you guys use sysprep in the process of creating your golden image
Yes you need it, if you want to have one image for multiple hardware platforms.
