And since you’re talking about Image, might you be using sysprep?
Then make sure to follow these instructions here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
Solved some problems for me.
And since you’re talking about Image, might you be using sysprep?
Then make sure to follow these instructions here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
Solved some problems for me.
Just throwing this out there, might absolutely not be related and me just missunderstanding whats actually happening here.
I had problems Imaging a computer at point when switching from a hdd machine as image-source to an ssd.
I had to change the host primary disk to the correct one - I think from sda to sda2 or something along those lines - for this to work.
Rereading again I suppose this is in another direction, but just in case.
Hi ddavis.
I had the same problem here: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/11
Rebooting the fog server solved the problem.
When saving a new PXE Menu:
Name, Description, Paramenters etc. are filled with the appropriate info
After clicking save and then checking back in the existing Menus, the description is not saved and has to be reentered. When saving again it finally sticks.
Running on 1.5.2
This is really great. Thanks for your work
I seem to have a similar problem when trying to run System Rescue Disk via PXE. Also something about not finding root or along those lines.
Will try booting on another machine to make sure that its not related to the Lenovo Laptop I am using …
Yes.
the DVD is extracted to /images/os…
The Kernel and init are in the tftpboot-path
The kernel and init load when I select the Ubuntu Entry in my FOG Menu, but after that when Ubuntu seems to take over -> error.
My fog ipxe menu item has the following parameters:
kernel tftp://${fog-ip}/os/ubuntu/Desk17.10/vmlinuz.efi
initrd tftp://${fog-ip}/os/ubuntu/Desk17.10/initrd.lz
imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/ubuntu/Desk17.10/locale=de_AT.UTF-8 keyboard-configuration/layoutcode=de quiet splash ip=dhcp rw
boot || goto MENU
It probably goes beyond the scope of support that I can offer on this forum, but yes, you can make images “per device-group” that have specific drivers.
You could even make a general image without drivers (or with only basic drivers) and inject the drivers according to the device type with post-deployment scripts that are available for FOG.
If you have specific questions I can try to help … but I’m by no means an expert
Hi George1421.
Thanks for the great tutorials.
Two questions:
Do you have an up to date tutorial for using SystemRescueCD (recent version is 5.2.2 i believe)
And more pressing:
When I follow your Ubuntu 17.10 Desktop instructions, everything works fine until I actually try to boot, when the boot process starts I get a Kernel panic:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)
Then some more lines and at the end again the same error message.
Any idea on what could be causing this?
Edit: Just noticed that I used 17.10.1, not 17.10, will try with 17.10 and report back - aaand, there is no 17.10 “non-.1” on the official ubuntu download page
Why not use Powershell?
msg * /server:IP/Computername "Text here"
Should work fine … the display box is rather basic, the user can only click “Ok”.
In this case it would send a message to all users on the computer defined by the /server: value
You can add /v to display what the user did with the box and /w to wait for user input. With /TIME:seconds you can define how long the message ist displayed.
Thanks for testing.
The reboot was all that was needed, sorry for not trying that immediately.
Will be in the office tomorrow again. Reboot is of course something I should have tried…
And sorry for my asking : what ist schema?
Solved by Tom Elliot as per this thread: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/7
Thanks for your work.
I upgraded to “working” branch (so: git checkout working) - is that correct?
If so:
Since upgrading I get the login screen of the fog web interface, but logging on only throws me back to the login screen again, I cannot access the web interface.
I deleted cookies and cache, still no game. Using Chrome. (Update: Same for Edge)
Any ideas?
@tom-elliott said in Fog 1.5.2 Host module settings don't save:
Mind runnning:
Select * from moduleStatusByHost where msHostID='0' or msModuleID='0'\G
I get: Empty set (0.00 sec)
Oh, I had a look around but somehow seemingly didnt use the right querys to find the other threads. Sorry.
It is on a host, the host was registered long before 1.5.2 and the last imaging was done before 1.5.2 as well.
Reproductability is the problem atm, no other host shows this behaviour. I was thinking about just re-imaging and hoping it would go away.
Things we did do:
But regarding what you wrote it seems its not in the communication part between fog and the fog-client right?
Sorry, not much more I can give. Will hang tight, thanks for your great work.
Hei.
Yesterday I updated our Ubuntu 16.04 Server to FOG 1.5.2 - no errors during update.
Since then, one of the computers that was imaged about a month ago keeps loosing the checked boxes in the “Service Settings” area of the hosts menu. As a consequence the log file on the client shows: The response module is disabled on the host - and the fog client doesn’t do its deeds.
Curiously, one of the checked boxes stays checked, but which one keeps changing, I wasn’t able to find a pattern yet.
The service settings are all set as required in the FOG Settings Menu, so those shouldnt overwrite anything.
Tried repairing the FOG client, it is up to date - tried uninstalling and reinstalling - no change.
For all the other computer in use, I haven’t found one so far that shows the same error - but I am afraid it might come back and bite me when I don’t expect it
Anybody has an idea what could be wrong?
That would be a good middleway I agree.
This way its easier to convey what is happening to the users.
Thanks!
Hi.
I did a search but wasnt successful, if you know of a thread discussing the same thing feel free to guide me to it or tell me to be even more thorough in my search.
The message that pops up on computers with the fog client installed when executing a snapin is always: Installing [Snapin-Name].
Usually thats just fine, but as I am also using the Snapin-System to push settings or uninstall programs during tests, is it possible to change that message to e.g. say “Uninstalling [Snapin Name]” or give it a completely custom message?
Thanks for your support!