Bumping this thread… Running into the multiple domain thing again at work…

Just read through Tom’s reply… seems sorta confusing but I’ll give it a shot but I don’t think it will work.

Two or more domains in one environment also means two or more users / passwords for domain joining in an environment…

@Jean-Jacques-Morda Group Description … notes…

I would agree.

Any task, be it on a registered or un-registered machine, should show up in the web console as an active task and show in the task list.

@Tom-Elliott said:

All other pages still redirect to edit page. This is because there’s more likely a need to edit the element after creating it. However, I do agree that creating users should not need this level of action, as you have the exact same choices in edit or add.

Hopefully you don’t mind.

The Username field is pre-populated with the last entered username, this is to be expected as if you make a mistake somewhere, rather than have to start ALL over, it puts the original value back. This still holds true even on successful create.

I just read this and it’s not very clear.

I added what you suggested. The User page now goes to “add”, rather than editing the user you just created.

Yes, that was this option help me to find out how to deactivate it… but, my request was to avoid deactivate for all, just for computers that are bugging with that. All of mine this case but i certainly will have the case that some will works and others not. A by group WOL activation should be really cool.

don’t get me wrong. we know how to script installs / use GPO.
just some items are just not worth the work at the moment.

You lost me at “pass the write flags around…” I don’t currently have the knowledge to even know how to start with this. Would you be willing to provide a solution for this even though you’re not a fan of the idea? This feature would give me and other service shops a huge increase in speed and flexibility when backing up random client’s computers as they arrive for service. With Fog already as powerful as it is, this is the only request I constantly get from technicians and other shops we’ve introduced to Fog.

Figured it out.

goto ${username} || goto MENU :fogUser menu item --gap -- ---------------- Welcome fogUser ---------------- item return return to previous menu item kav Kaspersky Antivirus choose --default return target && goto ${target} :fogTech item --gap -- ---------------- Welcome fogTech ---------------- item return return to previous menu item Clonezilla Clonezilla ISO item UBCD Ultimate Boot CD item Hirens Hiren's Boot CD item kav Kaspersky Antivirus choose --default return target && goto ${target} :MENU menu item --gap -- ---------------- iPXE boot menu ---------------- item return return to previous menu choose --default return target && goto ${target}

Then just define the functions below the menu. fogTech and fogUser being different users that the menu accounts for and MENU being the default menu.

This was made apparent after looking at the advanced.php code presented here https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options

Access to this menu can be granted without granting that user rights to the website by clicking the “Mobile/Quick Image Access Only?” toggle when creating the user.

No idea if this is the best way, but it seems to be working. I’ll let y’all know when it finishes compressing.

for f in *.img; do mv "$f" "${f%.img}-bak.img"; done for f in *bak.img; do pigz -d -c $f | pigz -9 > "${f%-bak.img}.img"; done

Here’s my 2 cents:

Option 1.) Make a plugin. Please don’t even attempt to edit FOG gui without using a plugin. The plugin API is much simpler to use.
Option 2.) Make a bash script. It could copy the image directory and the appropriate SQL data.

@Wayne-Workman said:

the WiKi SVN article somewhat promotes upgrading to the developmental revisions…
I really think that the other upgrading methods should be ditched, IMHO. But others here feel otherwise.

I very much agree. There have been so many major fixes, changes and improvements, that anything less than SVN (3410 in my case) is hamstrung by comparison.

Sad truth is, although Tom is fuc**** awesome at what he does, he is largely a one-man-army and he has a full time job and wife and so on. He’s the driving force behind FOG.

Indeed 👏 👏 👏

The IP field may not be visible, directly, but it is not gone. When you search for a host, it automatically searches for the ip field, at least in SVN.

Or something more elaborate than a green dot…

Funny you should request this. I actually implemented this exact thing at my old work place. You could update the host location from the ipxe boot menu, and see their locations when editing the host.

[quote=“Joseph Hales, post: 47440, member: 18131”]Maybe adding a hash check to the troubleshooting script? Were we going to include the updated troubleshooting script in the utils folder for SVN.[/quote]

Now that’s a winner. Let ya know if your FOG files are busted or not.

How about…

Apply the snapin to everyone,

Then, in your script, just specify computer names… if the computers name matches such-n-such, install the font.

Added.

No idea if this is currently possible or not, I’ve not gotten the opportunity to mess with the location plugin yet…

But this is a good idea.