Posts made by JBurgin

To the best of my knowledge, no building of the FOGclient is required. The Fogclient is precompiled and available for you to install by going to your fog servers web management page: [url]http://<fog_server_ip>/fog/client[/url]

hope this helps.

Gotcha, will try all this out once I get some data gathered Thanks a bunch.

I’m using 0.32. I forget they offered a template file on the fog server, so I checked that out. They listed “Operating System ID” and “Image ID” as the options, so now I’m wondering if I need to use the ID number instead of the literal name of the image or OS.

To clarify, you are saying if I have a column of data that I don’t want to include, to LEAVE a blank column between the other two pieces of data. Example: If I don’t want to include IP address data, then I would have an empty column between Hostname and Description?

Hey all,

it looks like the CSV file format information on the Wiki hasn’t been updated in awhile, so I have a question I hope someone can answer.

We’re working of compiling lists of computers using an inventory program, and then intent on importing a CSV of that info into FOG so all hosts will be registered.

I’ve read the tip here: [url]http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Tips[/url] (#3), but I have a feeling it hasn’t been updated in awhile, especially since Windows 7 was released.

[B]My question is this: What’s the options to use for OS so I can make sure it gets applied properly?[/B] The tip says “XP/Vista” as the choices but what about Windows 7? Should I expressly use whatever the OS option is listed as in the FOG management page? (such was Windows 2000/XP, Windows Vista, etc etc) or should I use the OS ID #?

Also, if I don’t want to provide information that the CSV file say it needs (such as IP address, description, etc) should I leave a column for those open and just have no information typed there?

If anybody has used this feature successfully and can provide some information, I would appreciate it.

I would like to think that you can setup a DHCP server on the server (assuming you are using ubuntu here) without it directly affecting FOG too much. Here’s some basic instructions for installing a DHCP server on it’s own. There may be some modifications you have to change in TFTP, but I can’t guarantee that.

[url]http://www.ubuntugeek.com/how-to-install-and-configure-dhcp-server-in-ubuntu-server.html[/url]

Outside of that, I would point you to this: [url]http://www.fogproject.org/wiki/index.php?title=Backing_up_FOG[/url]
[url]http://www.fogproject.org/wiki/index.php?title=Restoring_FOG_from_Backup[/url]

That page will show you at the very least what areas of FOG you can backup and then restore, so that if you do blow out FOG and reinstall, you could easily get your database and images back.

[quote=“John Johnson, post: 2800, member: 30”]I have several images created and saved. This summer I want to update the images with the latest windows updates, etc. Can I just upload the updated image to fog and overwrite the existing one or will they have to be uploaded as a new image and the older one deleted?[/quote]

As long as the host you upload the image from has the same image ID as the image you want to “update”, it will be overwritten on the upload.

[quote=“Robin Commander, post: 3278, member: 64”]I’ve had a look at this today - in my case it seems to be caused by the hard disk being brand new and having no partition table.
[/quote]

I remember this being an issue in older verisons of FOG (around .26) but I thought they had resolved that. Interesting. Regardless, good information to know it’s still around.

If you would like me to, I think I still have a undi universal boot CD ISO for ghost that I could send. I think its all scripted, but you could extract the auto execs and edit them as necessary.

Understood.

I’m assuming the 2nd error happens on the client youre using to test PXE booting, which might make sense. I would probably venture a guess that the Client being virutalized is the reason for that error. You’re essentially switching to a DOS/Floppy based environment and the virtual machine may be getting confused. That’s only my guess though and not very educated either as I never really worked in a dual virutalized environment (our FOG servers are bare metal and I would occasionally use a virtual machine to test PXE menu stuff).

I would recommend trying to boot to your fog server from a bare metal client and seeing how it reacts if you have the luxury.

Just curious, from the menu options, are you trying to make a UNDI symantec ghost client to boot in fog?

[quote=“brett lutkehus, post: 3207, member: 1029”]not a bios issue… is there a way to delete these from the fog database and then rebuild the database?[/quote]

You can individually delete the computer hosts by going to the web server -> host management -> list all hosts, find the hostname you gave it and click on it. Then go to delete host. Then go through the whole process of registration again.

[quote=“Rob Wood, post: 3208, member: 1025”]I should explain I’m testing this in a virtual environment. my virtual client booted but I go the following screen followed by the following error. I’m not sure if this would be different on a physical machine or not. Do you think it is just because it is a virtual machine?
[/quote]

Let me make sure I’m clear on this, is your FOG server virtualized? Or is the client you’re using to test the PXE booting virtualized?

Change the “iso” after append to “floppy”, that might fix it.

by dashboard, do you mean webpage? just wanted to verify.

Is your FOG server also acting as a DHCP server? or do you have another server handing out IP addresses?

[quote=“Rob Wood, post: 3191, member: 1025”]
Since posting this someone informed me that dos can only use files that are 680kb or smaller, hence why it is complaining about it being too large.[/quote]

Well, maybe. How big is the VFD? It maybe a memory issue. Memdisk dumps the whole image to RAM so if you don’t have enough RAM, the system will fail out.

Could you possibly share your pxelinux.0 entry for this boot option? We may need to change some appends.

Make sure the static address is the same as the DHCP address you originally set it up with. Chances are the IP addresses are different and therefore PXE isn’t broadcasting on the proper IP.

What kernel are you using to boot the vfd files? memdisk?

[quote=“sid, post: 2583, member: 558”]I made up a password and typed it in as Master Password and the Capone showed up, but nothing happens when I select the capone in Pxe menu.
I assocciated the System Product Name to the Capone, but it won’t do anything in PXE menu.
any Idea?
Thanks[/quote]

Sid,

I think I have an idea what’s going on, as I just enabled CAPONE on a FOG installation yesterday and had some issues as well.

I did the same as you, adding the boot menu text into PXE Boot Menu page on the webserver, but for some reason, the page isn’t separating the text properly. IF you have physical access to the fog server, I would suggest doing this:

[I]At the fog server, open a terminal (this may vary depending on your flavor of Linux, I’ll assume you know how to get this far. [/I]

At the Terminal:

[CODE]sudo nano /tftpboot/pxelinux.cfg/default[/CODE]

Use the arrow keys to browse to the line of text that starts with [B]“LABEL Capone”[/B]

If I am correct, then the line starting with “LABEL Capone” also has the words “kernel” and several other parts of text next to it. We need to separate these lines.

There should be 3 main lines. One Beginning with “LABEL CAPONE”, one with “KERNEL”, and then a final one with “APPEND”. I’ve included my Capone listing so you can see what I mean.

[CODE]LABEL capone
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=<dns> mode=capone ftp=<fog_ip> storage=<fog_ip>:/images/ web=<fog_ip>:/fog/ shutdown=on loglevel=4[/CODE]

the append line must not be separated at any point, from “Append” to “loglevel=4” is one solid line, but the key is separating the LABEL line and kernel line.

After you make edits in the file above, hit CTRL+X and then y to confirm you want to save the file.

Hopefully this helps!

I think, during the upload process, the boot sector is removed as a preparation step, so this would make sense why you have a blinking cursor. If you have access to a Windows 7 DVD, you can boot to it and attempt to repair your computer. The startup repair wizard should be able to fix this.

If not, you can try going to the command prompt on the DVD and running “bootsect /NT60 /force /mbr” that should rebuild the Boot Sector for it. This will allow you to boot back into the PC (you’d have to resysprep it)

To answer your question about the “Resizing Partition” freezing, Joshua’s advice above may be correct, I have yet to have success with uploading a Windows 7 image as a Single Partition. You may also want to consider updating your “Boot Kernel” for Fog by going to “Other Information -> Kernel Updates -> and selecting a new kernel to download and install”

Hope this helps.

This is probably way out in left field, but I figured I’d ask.

I’m working on ways to streamline our image deployment across all our fog servers (16 servers in 16 different subnets). I’ve written a script on our original fog server (where all our images get created/uploaded) that deploys the image to each of the other servers via SCP.

My question is, is there a way to also “script” the adding of the image definition under image management through some command line magic? So, then when the image gets moved, it auto adds itself to the image management section?

Any help/discussion is appreciated.

We let go of version 9.X when Ubuntu stopped providing updates. 10.04 is actually very good and runs everything smoothly.