Newbie getting started
-
@bogle Take all the time you need, my FOG server is running just fine.
No worries, deal with what is important first.
-
Something doesn’t seem right. Here are some screenshots
Image can’t be 0.00
Image details in Fog
Screenshot of fog server /images/
This has to be the image that got uploaded
-
@bogle If something happens during the upload process the web site file size will not reflect what is on the disk. There is also an agent that runs once a day to resync the file size on disk with the file size reported via the web ui. Yes it is strange its not set correctly in the web ui after upload, but its not something to stop image deployment.
Edit after looking at the pictures again, I see the fog didn’t complete the process because directory with a mac name is still in dev. It didn’t get moved to /images/<image name> like it should have
Edit 2 this thread seems to be wandering about from issue to issue. We may need to create a new thread for new issues or we will really confuse someone reading this thread in the future.
-
Looks like image didn’t finish uploading.
Booted the pc backup with image i am trying to upload…
-
@bogle Then keep an eye on the screen when the blue partclone windows are done. There might be an error at the end when the client reports back to your FOG server.
-
-
@bogle Check out this topic: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password
-
Thanks, I synced the passwords, re-ran the installer, and watching it try to upload the image now.
-
Do you guys make your partitions Bios or UEFI?
-
Well the process is working now. I think I have to redo the image to use UEFI partition for it to work. I will give you guys an update soon.
-
@bogle said in Newbie getting started:
Do you guys make your partitions Bios or UEFI?
If I understand your question, yes. That is one of the reasons why I use MDT to build my reference images. I have 2 images one is BIOS and one is for UEFI based firmware. Depending on the VM I used to create the reference image MDT will build a UEFI or BIOS layout based on the VM type used to build the reference image.
-
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.
