Sorry for the late answer …

We’ve just upgraded to 1.5.9 and update Bitrate and Remit Hello Interval on «Storage Node» settings page.

The generated command was conform and everythings works great !

Thanks a lot

@Tom-Elliott Yes, this might work, but I didn’t want to spend too much time experimenting. If somebody wants to follow up on this, that’s fine, but I won’t. 🙂

@zfeng I believe there are some powershell tools for that and I have built a powershell module for the api (see links in my signature). I haven’t done anything CICD with it but I imagine that’s something that could be figured out. I mean I kind of do something like that with my images having powershell modules and scripts in git that build and capture my image, but it’s not automated with a CICD design as I like doing it a bit more manually to make sure everything runs smoothly.

I don’t have the ignore mac on client/imaging
Setting built in to those functions, but you can take a peek at the code to see whrte you are setting the primary property there is also a property for ignoring mac on client. I’m on my phone at the moment so can’t go test and get for sure answers. But it’s either a part of thr maclist array of a host or a different property. Point is you can for sure set that. If you give me a bit more detail I will gladly try to give you further examples on how to do it with the powershell module

@JYost What you see when you first click hosts is the search view. Typing in the menu bar search field you should see results below.

To change this you go to FOG Configuration -> FOG Settings -> FOG View Settings and change setting VIEW DEFAULT SCREEN from SEARCH to LIST. Don’t forget to click Update to save the change.

Hey thanks for all your help @Sebastian-Roth. This helps me look into things more.

Today I will try to setup a sandbox VM so I can look into playing around with 1.6.

Thanks again!

@AlexPDX Its best to start a new thread for this issue.

To help push things along… You don’t have any imaging issues? The ftp error might indicate that you have/will have image capture issues. Run through this script to ensure all of the passwords are in sync. https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

I copy pasted the function into my console and tested it with a snapin that was assigned to just my computer and it did in fact queue it to deploy.

This could be altered to quickly deploy to a given list of hosts or groups as well. Giving you a quick command line method for deploying snapins to hosts in a variety of ways.

If this is something that would achieve what you’re going for let me know and maybe I can add in the functions to the api module so they just exist and then you have a deployment tool via command line, which is typically quicker in my humble opinion

@Tom-Elliott said in Task management - add Snapin name column:

The snapin task page, if I remember correctly, displays the snapin name, the host it’s deploying, and the time and status of that task.

Yes the “Active Snapin Tasks” page does display the names.

@mousepl I can still imagine why you might it find helpful to have this information on the “Active Tasks” view as well. On the other hand we do have a lot of requests on the list and not many people actively working on the FOG code. So if you are keen to get this added you might need to get involved as well. Sorry to say this but it’s very far down on the list because the information is already available in the web UI just on another page.

@JJ-Fullmer It’s good you bring this point up. We get posts in the forums every now and then but it’s very hard to estimate how often this really happens in the wild as we have no numbers of rEFInd working properly.

Adding more options is a good idea either way as it doesn’t hurt us and might help people.

Personally having used grub2 to PXE boot I will get onto that and see what’s the best way to add this to FOG.

@Sebastian-Roth

Oh. Got it. That makes sense.

@Fog_Newb said in Capture Hackintosh drive image?:

So I would just put something like “/dev/sdx”?

Exactly! First disk usually ends up to be /dev/sda, second /dev/sdb and so on.

@astrugatch Yeah, probably a good idea. We’d need to do extensive testing on this. E.g. iPXE boot, fog-client, storage nodes (php curl calls) and so on.

PS: Moved to feature request.

@rogalskij said in Email to user who does the imaging:

Is there a variable we could set in the “Email Address” field, like “{USER}@emaildomain.edu” or something of that nature?

Unfortunately there is no variable at the moment. But it’s a tiny change to make this work. I just pushed a fix to the dev-branch. Whatever version you run you can either wait for FOG 1.5.8 to be release soon or add this change manually. Don’t worry about the schema update you see in this commit further up. No need to add this.

[Mod Note]: Cross linking posts since the issues are related: https://forums.fogproject.org/topic/14134/keyboard-not-recognized-when-using-kvm-switch

@george1421 @Junkhacker @Tom-Elliott I see what it does now. I actually tried that out. Basically, it copied the script from fog server and placed that into the target computer. Once the target computer powers up, it will run the script automatically. That actually helps. Thanks for your guys effort. I will close this issue then.

@Sebastian-Roth Thanks for the help! Sorry about the late response as well. I will be starting one soon, and we defiantly have a high-speed connection Internally. But we have multinational support and they have slow speeds. Even if it takes 7+ hours to re-image some of their machines, it would save a lot of time from shipping the devices.

I will do some research and document the process for Kubernetes, and possibly HELM support as well.

@george1421 i’m thinking we could have an “unregistered host” host and have it auto-register and auto-remove when the tasking was created/finished. that would also allow us to have a task to track in the gui.