Add an menu item thruogh web GUI
-
@klkwarrior why not do full registration?
-
We have a huge amount of machines to image on a daily basis, we are trying to make this a more efficient process.
-
@klkwarrior how is it anymore effiecient for a quick reg that you define the image? For what it’s worth quickreg natively can do what you’re looking for and for. Go-to fog settings, quick reg, and select an image id and enable it. If the image is set quick reg will happen and create a deploy task.
The values to set are:
FOG_QUICKREG_IMG_WHEN_REG and FOG_QUICKREG_IMG_ID
-
@tom-elliott Thank you for the instructions, I was able to find and change this on the server but there is two concerns I have.
- Not all the machines we are imaging are using the same image ID
- some of our machines say they are already registered, but are a completely different machines.
-
@klkwarrior then do it in batches. Take one set of like machines, quick reg and image. Change settings for second batch. So on and so forth.
Or just use the full registration option as that will allow you to set the image per machine and tell the machines to image.
Either way, creating a new menu seems like overkill and more complicated than just using what is already available.
Another option you could do is use the Capone plugin. This would not require your machines to be registered at all.
-
@klkwarrior May I suggest the following:
-
If your project of imaging lots of machines are on the same network, maybe image as a group based on the model computers? Or are the computers at various sites?
-
Not sure if latest working branch has this but I know that 1.6 does have the deploy image option from the client which just basically allows for you to choose the image to deploy rather than defining anything. That I think is what is probably going to accomplish for you and you don’t have to do anything on the web UI in the sense of adding additional functions. Just define the image, upload, and then begin imaging.
-
-
@jgallo that option has been there since 1.4 I believe.
-
@jgallo We do see the deploy image option yet it always errors out with “failed chainloading -s”. I can get the full error when I use it today.
-
-
@klkwarrior please try reuploading but wait until you see the picture load before submitting.
-
-
@klkwarrior did you start creating your own menu items?
-
@tom-elliott no, this is the current state of deploy image. I have tried looking up this error and always get sent to ipxe.org/cmd. From other co-workers of mine, they say this started to happen after we had our Fog Server updated. I was not here when this happened.
-
@tom-elliott Would getting the boot.php file help diagnose this issue? if so i can provide that.
-
@klkwarrior Even better, please open the following URLs in your browser and provide the full output you get here: http://10.0.0.5/fog/service/ipxe/boot.php and http://10.0.0.5/fog/service/ipxe/boot.php?mac=xx:xx:xx:xx:xx:xx (put in the client PC MAC address instead of xx:xx:xx:xx:xx:xx)
-
-
@klkwarrior Can’t see where this
-Sis coming from. Can you please capture the HTTP traffic when this is happening?- Get your client ready but don’t start yet. Make sure you know the IP address it receives on DHCP later on.
- install tcpdump on your FOG server (e.g.
sudo apt-get install tcpdump) - run tcpdump:
sudo tcpdump -w item_issue.pcap host x.x.x.x(put in the client’s IP address instead of x.x.x.x and leave the command running) - boot up the client till you see the error message on screen - then stop tcpdump (ctrl+c), upload the item_issue.pcap file to some server/cloud and post a link here.
