I restarted my fog server and made sure that the fog server node also had a copy of the snapins on the server. After that, I added the snapin and gave it about an hour before I moved on to checking the snapin list.

Thanks for all the help but i finally decided to reinstall everything from scratch.

Thank you Sebastian for this explanation.
I actually use the short name but by default, I would have preferred to use the long name.
But the whole is currently configured as well, so I will stay on this configuration while waiting to update the posts with a new image at the end of the school year.

@Fog_Newb said:

Either use groups as suggested by George or add it to the global settings: FOG Configuration -> FOG Settings -> General Settings -> KERNEL ARGS (not sure if this would cause trouble for other hosts as we don’t know all the other hardware you have)

This ended up being the case. Apparently there was a bug in the version of ipxe.efi and cloning the version in the github repo below resolved the issue. I was so caught up in other things I forgot to actually try this until I was reading over this thread again today.

Thank you for your help!

@george1421 said in UEFI Boot:

@londonfog Hmm, ok that isn’t it then. I thought it was possible that something happened with the 1.5.8 update and ipxe.efi was damaged some how.

In each of the boot loaders (undionly.kpxe and ipxe.efi) there is a script that calls default.ipxe on the FOG server… But thinking about it now, its getting past that point because it calls default.ipxe which chains to bootp.php. That http call is failing for some reason. So default.ipxe has already been loaded by ipxe.efi.

I don’t have an answer why only uefi has this issue. I can say that 1.5.5 is kind of old, but I don’t remember your issue being an issue in 1.5.5. I guess you could try ipxe.efi from 1.5.8 to see if that changes anything. Here is the link to the github site where you can download ipxe.efi https://github.com/FOGProject/fogproject/tree/master/packages/tftp

There is 2 ways to image target computers. The first method you already know, but registering the target computer, then select image at the end of the process or schedule a deployment in the web ui. You uses this method if you want FOG to manage the target computer after imaging. In this method the FOG Client is used to name and connect the computer to AD.

There is another method that MSP (system rebuilders) use need to load an OS on the computer, but the computer will not be managed by FOG after imaging. Typically once a system rebuilder loads a computer that computer is put up for sale and is never seen again by the FOG server. You access this method via the Deploy Image iPXE menu.

There is another process that is in between these two methods. Where you use the Deploy Image menu to image the machine, but the system name is caculated in a post install script and the unattend.xml file in windows is used to connect the computer to AD. In this case the fog client isn’t used or needed. If the FOG Client is installed in the image it will contact the FOG server after OSD is done in windows and will be added in a pending state in the web ui. From there you will need to accept the system in the UI and then you can manage the system.

So there are a couple of ways to image a machine, none are totally hands off and some take some setup to complete.

@Sebastian-Roth Understood. Sorry. I will make a new thread.

OK, I’ll try it soon
Thank you @Sebastian-Roth

This has been solved, the problem was our Cisco switch, somehow it was blocking the download

just to let you know that the issue was solve this week buy updating the latest version of fog
seem that you finaly found the problem

thank’s

@Sebastian-Roth Хорошо, спасибо!

@AlexPDX said in Location Plugin Not Working as it should ...:

So…i had to instal phpmy admin and find that there wos a problem in the data base …

What exactly was the issue? How did you fix it?

@Sebastian-Roth thank you very much for your help !
You put me on the way !
Everything is fine now, after I ask the people who are managing the proxy to “open the tap” !! (and sorry for my English !)

@Sebastian-Roth Thanks so much for the detailed explanation. It worked like a charm!

@Sebastian-Roth Interesting. I’ll keep that in mind. Thanks.

@hancocza said:

maybe you have a better way of doing this?

In your case you better just comment or remove those five lines from the PHP code. The fog-client code is made to check if “url” ($location in the PHP code) is empty and defaults to the values specified in settings.json on the client.

Not sure if there should be a change to use the hostname instead of IP if specified in the .fogsettings file

Using DNS name is adding another layer of complexity and I wouldn’t want to add that as default for every FOG user. You can run FOG without setting up proper DNS and I see this as a good default to not add another hurdle for most of our users. If you want to switch to DNS/hostname you wre welcome to do so.

If there are issues in the code that we need to fix preventing you from using the hostname instead of IP, let us know. Best to open an issue on github and point out where things are going wrong.

@Mark-Shelton As seen in the picture the version of partclone is 0.2.89 which is the version we used in FOG 1.5.7. Sadly it’s not able to deploy images that were created with the newer version of partclone (0.3.13) which is now used in FOG 1.5.8.

Partclone 0.3.13 can deploy older images created by version 0.2.89 but not the other way round. Please upgrade your Raspberry Pi FOG install to FOG 1.5.8 (manually fixing the udpcast compile issue) or FOG development version (dev-branch has the udpcast compile fixed already).

@dmathews If you are going to start over, once the linux server is built. Create the /images directory by hand and then create the mappping of /dev/sdb1 to /images THEN install FOG. It will create everything correctly then and no changes will need to be made to FOG because the disk was added at the OS layer.

@AlexPDX Please open a new topic as your request has nothing to do with the initial post as far as I can see. Just copy and paste your text from this.

@Mark-Shelton Great, thanks for the feedback. I just added a fix to the code.