on a Side note, I have 1 other image exactly like this with the same image size as 0 “empty”
Posts made by vince.villarreal
RE: Fog image size empty, captured date valid, image used to work and now throws "error trying to restore gpt partition tables"
Fog image size empty, captured date valid, image used to work and now throws "error trying to restore gpt partition tables"
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.)
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!
Hosts not joining domain (see log attached) also it shows its joined under properties, but missing from AD
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?
RE: PC domain join gets trust relationship
@tom-elliott So recapture the image? Does this sound like it will work (listing steps below)?
- image a 5490 without join domain.
- go INTO fog and delete the host first while computer is still on.
- open cmd, do a shutdown -s -t 0 -f
- Full host registration
You think those steps above should work?
PC domain join gets trust relationship
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.
RE: Is there a way to make the hostname question REQUIRED for the Full Host Registration questions?
@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.
Is there a way to make the hostname question REQUIRED for the Full Host Registration questions?
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?
RE: FOG Persistent Groups - How to remove persistent image association?
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.
FOG Persistent Groups - How to remove persistent image association?
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?
RE: FOG Persistent Groups not allowing image register to host?
you can solve this post. rewording this in a new post.