I have an ultra cheap router. Fog server setup locally. Router is acting as DHCP. I just need the USB to point directly to my fog server’s IP rather than wasting anytime getting PXE boot to work.
This is a temporary thing as I am shipping someone a $20 router, fog server, a gigabit switch, and a few ethernet cables so he can image about 30 pcs at his location.
so I have followed the “easy” instructions on how to get this working. (which is a MUST for me since I have the option to type in my fog server IP)
It will not boot.
I have found throughout the forums “ipxe.iso”, downloaded it which contains BOOT.CAT, IPXE.KRN, ISOLINUX.BIN, ISOLINUX.CFG.
I am assuming I copy that to the root of my USB drive. create the EFI/BOOT/bootx64.efi file and path.
Nothing is working. I have the option to select boot from USB and it skips booting from USB.
Can you guys tell me what I am possibly doing wrong?
on a Side note, I have 1 other image exactly like this with the same image size as 0 “empty”
JFYI (there are 5 people that use the same default login, so I asked all of them if they broke something and none came forward… You know how that goes lol.)
Anyways,
I had a working image that was captured to FOG about a month ago. Something happened and the image size became 0 (empty) and the captured date was correct and there. Now if I try to image a computer it gives the error “error trying to restore gpt partition tables”
Do you guys know how to fix this? Maybe someone accidentally tried to capture over my original image?
Any help/guidance on how to troubleshoot this would be much appreciated!
So, if I image a computer using a certain image (UEFI image), the PC will show it is joined to the domain, but it is missing in AD. This is causing the computer to get trust relationship errors when users from the domain try to login.
The only thing I noticed that is weird is the time is off in the WEB GUI. When I check the logs, the only error for these machines that are not joining to the domain correctly is below:
Invalid promptTime, using default
Then at the bottom it will say HostnameChanger The machine is already joined to the domain, code = 2691
I am about to try a recapture and 100% making sure FOG does not try to rejoin domain before the capture part. I don’t know if this ^ happened.
Do you know what that error prompttime means?
@tom-elliott So recapture the image? Does this sound like it will work (listing steps below)?
You think those steps above should work?
I created a UEFI image for a dell 5490. To create the image, i had to temporarily join the system to the domain to get some install files. When I was done, I deleted the computer from SCCM and AD, an unjoined the PC from the domain. (yes 100% sure unjoined from domain)
After I did that I logged into the local account, downloaded fog service from my server, and did a CMD shutdown -s -t 0 -f.
Then captured the PC.
It seems like I was able to get a few computers to join a domain in the beginning, but now each one under “This PC” properties, it will show as if it is connected to my domain. When I look in AD, the PC is not there. Obviously if I log into the PC with a domain user, I get a trust relationship error.
I also tried adding a snapin that is a powershell script to join a PC to our domain. That also throws out a trust relationship problem.
What do you think could be the culprit? some computers did work during the beginning and now it is failing.
When I image and select NO to join domain, it will image just fine and skip the domain join process. Then from there I can join the domain, restart, and be done.
@george1421 yea I see that. I’m not a good programmer as well. If someone knows the command, please feel free to reply within this post.
I am going to try and google my way through this.
People keep leaving it blank and by default it puts the MAC address as the hostname. This is bad because a computer will image and then join the domain with the MAC Address since it becomes the PC name.
Any way to make “enter hostname” required and not allow someone to just press “enter” while leaving it blank?
Yes, so if I leave the template host image association to “Nothing/Blank”, then during my Full Host Registration process I will select an image, then add it to the group.
Since the group has No image associated, it overrides my image that I selected during the Full Host Registration and now the host does not have an image selected.
I tested this theory by adding a image1 to PC1, on group PC1.
Then registering a new computer, selecting a different image (image2) than PC1, and selecting group PC1.
In the end, the persistent group will overtake my (image2) selection I made during the registration process and assign the host (image1). Same goes for when I leave the template host image Blank, it will make any new host added to the group have no image assigned to it.
I would like to use Persistent Groups to be able to assign computers to specific OU’s when I am imaging. I do NOT want the image association to be a part of persistent group settings. How do I remove this?
If I have computername = OU1 ____ set to “ou in AD” ______set to “No image assigned to host”
This means that my Group OU1 will not have an image assigned to it. Therefore during my Full Host Registration, I will attempt to assign an image to a host, assign group OU1, and then the host image association gets overrided to “No image assigned to host” based on OU1’s persistent settings.
Anyway to ignore the image part of persistent groups?
you can solve this post. rewording this in a new post.
So I have stumbled upon an issue. I have persistent groups setup and there seems to be some type of conflict when adding a group and assigning an image to a host. The image does not get assigned when a group is added.
When doing the Full host registration, it will ask “Would you like to assign groups?”
I say yes, and assign it a group that has a persistent AD OU setting.
When I complete the answers and it asks, would you like to deploy image now? Yes, then login/password.
It says Done! No image assigned! even when I assigned an image to it in the question before…
Any ideas to fix this one or where to look?
@wayne-workman ok, so turn TPM off, capture, deploy to a computer with TPM off, then after the image turn TPM on.
Is that about the only way to do this?
So we are now pushing out computers to have TPM enabled.
Instead of capturing an image with TPM disabled, then going back into the bios after to re-enable TPM, I’d like to have it down to just keeping TPM enabled when capturing/deploying images.
Is this possible?
The last image I captured was on a computer that had TPM enabled, bitlocker turned off (30GB image), and then when I deployed it on another machine it was asking for the bitlocker recovery key.
Any help would be much appreciated.
Maybe one of you can help me. I am trying to get the information from this link
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
and since wiki is down, I can’t view the configuration steps. Maybe one of you have it and can share it?
@tom-elliott this might be a dumb question… but where are plugins in the newest version of fog?
@jgallo mine is a different problem though. Just leaving a single image on the default storage group with 1x storage node and 1x master node, it will not deploy images from the Storage Node within the same location as the storage node.
The storage groups I really don’t care about, it’s the problem with imaging from different locations is not working. I can’t image a PC from the Storage Node only the master node… which is super super slow.