This might help:
Posts made by Wayne Workman
-
RE: Conditional boot menu (aka different boot menu for Windows and Mac)
[quote=“Uncle Frank, post: 42799, member: 28116”]Booting and imaging our Macminis is working great with FOG 1.2.0 but it’s still a bit of a hassle as we have both Windows and Mac OS X clients in our labs and I have to customize the boot menu by hand everytime I want to switch between those.
I started to add some code to ‘/var/www/fog/lib/fog/BootMenu.class.php’ to check $_REQUEST[‘mac’]. Depending on the MAC address a different boot menu is being send to the client…As far as I can see even in current SVN this cannot be configured eventhough you can add custom boot menu entries, right?
I’ll happily implement it myself but I wonder what would be the best way to do it? Would be great if someone could give me a hint on how to implement this the “proper FOG way”… thanks in advance![/quote]
Please, please elaborate on all your steps to image Macs.
I’m very interested in this, as we have a massive number of Macs in our school district.
-
RE: Unable to upload an image : Failed to mount NFS volume
IP Conflict?
I dunno… just kicking around ideas…
-
RE: Request for Help or maybe just answers
[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]
^ Hero
-
RE: Unresolved host names in fog hosts list
Here lately,
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.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
[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.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
Just kicking around ideas…
Turn DHCP off for that device you have, and install FOG with DHCP turned on… see what happens…
-
RE: HostnameChanger error: "Length of data to decrypt is invalid."
[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.FlushFinalBlock()
at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at FOG.FOGCrypt.decrypt(Byte[] cipherData, Byte[] Key, Byte[] IV)
at FOG.FOGCrypt.decryptHex(String hex)
at FOG.HostNameChanger.changeHostName()[/code]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
-
RE: Latitude 3540 Freezes During Upload
[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?
-
RE: Unresolved host names in fog hosts list
[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?
-
RE: Unable to upload an image : Failed to mount NFS volume
What version of Linux?
Simple stuff first; Make sure the /data/images/dev directory exists.
Thanks.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
[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?
[url]http://fogproject.org/wiki/index.php/FOGUserGuide#DHCP_Settings[/url]
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
[quote=“PaganLinuxGeek, post: 42688, member: 2226”]Ugh. this machine doubles as my workstation. Lots of work to re-install this beast… Where can I get svn 2922? Perhaps I can round up a older alower machine to install 21 on and then this developmental version.
If I knew what the failed actions were I could likely ammend or perform them manually. I had to do that with 0.32 on fedora 19, and 20…[/quote]
The command to get 2922 is in the Fedora 21 instructions on the Wiki.
Literally every single step is covered there.
As far as amending 1.2.0, that’s a Tom question.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
[quote=“PaganLinuxGeek, post: 42686, member: 2226”]You are recommending a format and fresh install of the OS? then install a development version of the software? I just want to make sure I understand you correctly. Before you respond please see my post just prior to this showing that nfs is active and exporting the images and dev directories[/quote]
Because everything else that was tried hasn’t worked & because you don’t have a functioning 1.2.0 FOG machine, I think that re-installing the OS and going with SVN 2922 (or 2948) is very safe and probably the best next-step.
The installation script alone in 2922 does so much small tweaking for Fedora 21, it really vastly cut down on the things that had to be done to get FOG working on Fedora 21. As you did, I tried putting 1.2.0 on Fedora 21 originally; I documented what I did. My instructions were a mile long, consisted of over a dozen web page links, several dozen commands, notes, etc. I didn’t even know exactly what commands were making it work… But I did get uni-cast working on my own. Tom got me straightened out further with multicasting, and other issues. We worked together so he could fine tune the installation script for Fedora 21.
After SVN 2920, my instructions dropped from 12(ish) pages to six simple, uncomplicated pages.
We know beyond doubt that SVN 2922 works on Fedora 21, and have instructions written specifically for this.
If you don’t want to do a re-install or use the SVN, maybe Tom will help.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
Note: Forwarding request to ‘systemctl enable nfs.service’.
Failed to execute operation: No such file or directoryOk, Fedora 21 support wasn’t formally added to FOG till SVN 2920(ish), Which isn’t part of 1.2.0
I’d highly recommend trying SVN 2920, 2922, or the latest SVN
I’d do a fresh install, (OS and the whole 9 yards) and follow along with those Fedora 21 instructions.
The commands to install a specific SVN are in the instructions.
-
RE: /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
[quote=“PaganLinuxGeek, post: 42573, member: 2226”]Still working on it, with no success.[/quote]
So, out of curiosity (and some valid reason to bump this thread), I checked the Wiki’s Working device & Problematic Device list. The pavillion g7 is not listed in either.
-
RE: Request for Help or maybe just answers
[quote=“Theodor, post: 42631, member: 28660”]Ok… figured it out. Blond moment… was in the wrong folder trying to do the make. Doh…
I finally got the kernel made and in place when I got the “This kernel requires an x86-64 CPU, but only detected an i686 CPU.”
So I am now recompiling after using the ARCH=i386 commands instead.
Thanks.[/quote]
If this works, you’re a hero in my book.
-
RE: Deploying images from USB
[quote=“Jørn Pettersen, post: 42619, member: 28650”]I see your point Wayne. And for 99% of the time we use an image server. But sometimes we need to do an quick imaging of a computer without having a server around and then we need to have a offline method to do the imaging. Have also thought about having a virtual box setup locally on a laptop with a fog server to run in these situations.[/quote]
But even then, if your production hardware is similar enough (just a few models), you could have ready-to-go hard drives in your bag/work van to install in those broke down systems.
And you could totally set up FOG on a laptop, and have it dish out DHCP and the works. You would need a cross-over cable in order to not use a switch. It’d work fine.
But, that’s an inefficient method. I’d personally just have hard drives ready to stick in, myself.
-
RE: Deploying images from USB
Could always just haul around hard drives with the right images on them already… Way faster than imaging!