I dunno… just kicking around ideas…
I've used FOG at a past job pretty intensely. During that time I contributed a lot to the FOG forums and it's documentation, a handful of pull requests, and contributed to the fog-community-scripts repo. I built automated tests for FOG's installer which run daily against many operating systems, link is in my signature. My fog time has slowed down a lot in the last couple years, but I still try to help as I can. I've got a lot of knowledge about FogProject in general and I can help you gear up or contribute if you would like.
I dunno… just kicking around ideas…
[quote=“Theodor, post: 42811, member: 28660”]Got it working with Tom’s 32 bit .config file using Linux 3.15.6 kernel, linux-firmware.git and added USB Mass Storage and SCSI Block Storage drivers, all that did the trick. Thank you all.[/quote]
I find myself entering the host names via the “Full Registration” option on the boot menu.
Originally, I wanted to register everything in the entire building here… that proved to be way too much work.
Now, I find that simply registering them as I need to image is much more simple. And, I enter in the desired host name right there, can start an imaging task right from there… it’s pretty sweet.
[quote=“PaganLinuxGeek, post: 42774, member: 2226”]Already considered that. It’s not an option on this device. :-/ I have a raspberry PI running on the home lan that could handle dhcp as it’s always on.[/quote]
Install FOG with DHCP anyways, then disconnect from that modem/router thing. Use a cross over cable to connect directly to the target machine.
Just kicking around ideas…
Turn DHCP off for that device you have, and install FOG with DHCP turned on… see what happens…
[quote=“hesslr, post: 42721, member: 17210”]We had been running on build 2048(?) without problems for quite a while. Last week we decided to get the latest SVN and had some issues. We took the opportunity to install proxmox and virtualize FOG. We Created a Debian container and got the latest SVN installed on the fresh machine, but we still had some issues (could not create new hosts/image definitions).
I have since gone back to 1.2.0 on yet another fresh proxmox container. It all seemed well until after a successful image, the computer did not change hostname or join domain.
[code] 2/24/2015 3:17 PM FOG::HostnameChanger Attempting to connect to fog server…
2/24/2015 3:17 PM FOG::HostnameChanger Module is active…
2/24/2015 3:17 PM FOG::HostnameChanger AD mode requested, confirming settings.
2/24/2015 3:17 PM FOG::HostnameChanger Length of the data to decrypt is invalid.
2/24/2015 3:17 PM FOG::HostnameChanger at System.Security.Cryptography.RijndaelManagedTransform.TransformFinalBlock(Byte inputBuffer, Int32 inputOffset, Int32 inputCount)
at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)
at FOG.FOGCrypt.decrypt(Byte cipherData, Byte Key, Byte IV)
at FOG.FOGCrypt.decryptHex(String hex)
I have not had any luck searching for this issue, and I have gone over the FOGcrypt password and other AD settings many times. I’m really hitting a wall on this one; any help would be greatly appreciated.
I wish I could go back to an earlier SVN but I don’t think that is a possibility; am I correct about this?[/quote]
Just an idea but, does the target machine you’re working with have the client installed from the version of FOG you’re using? Not sure but, changes to the old client [U]might[/U] have happened between different releases/revisions
[quote=“Clifford Raymond, post: 42764, member: 28730”]I have a latitude 3540 that is running on Win 7 and the server is running on Ubunto. We are running FOG .32 and every time I try to upload an image it freezes. We have restarted the server a few times with thinking that either an image was “stuck” or something else was processing and causing the issue. We read through many threads and thought it could be a kernel issue but no one has stated how to fix it on Ubunto only on Windows.[/quote]
There may be a solution to your problem (I wouldn’t know it, that’d be up to a more experienced FOG user), but have you considered upgrading to the latest release or a solid development version?
[quote=“ChrisJ, post: 42766, member: 28617”]I’ve got a new FOG1.2.0 install on Ubuntu 14.10. I’m running a quick register from the PXE menu to allow me to get all the hosts on before we start moving PCs round and reimaging them. Most seem to go into the host list OK (some are very old) but none have their host names filled in, just a MAC address (less the colons).
Being new to Fog I’m not sure where to start with this one.
It would be good to get name resolution working properly but in the meantime is it going to break anything if I update the host names directly in the DB using SQL and a hostname/mac address list I’ve got from spiceworks?[/quote]
This might just be me but, I manually enter my host names via the [U]WEB GUI[/U]. I thought that’s how it’s supposed to be done?
What version of Linux?
Simple stuff first; Make sure the /data/images/dev directory exists.
[quote=“PaganLinuxGeek, post: 42706, member: 2226”]I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?[/quote]
Simple question but, in your install log, you answered no for using FOG as a dhcp server. Have you covered DHCP options 66 & 67, made sure they are correct?