FOG 0.33b is not a direct drop in upgrade from 0.32.
It is recommended to do a full re-install when using FOG 0.33b as so much has changed that it doesn’t transpose well.
My recommendation is to put another hard drive in your machine and begin there, or if you are virtual, set up another server. Then migrate your images over.
I’m not sure I understand what it is you are asking. I am able to image perfectly fine using ipxe and virtual machines.
I run Oracle VirtualBox machines and as long as I set up the network card as a bridged mode I can communicate with my pxe server.
I have in the past used ESXi to build virtual images and upload them, and with the previous kernel 3.8.8 and FOG 0.32, I had to add the ability to talk to SCSI drives because of the way ESXi handles the virtual disks. I was unable to solve the issue with EXTREMELY slow upload speeds while using ESXi though, this is why I moved to VirtualBox and recommend using it to set up your virtual images. Speeds aren’t blazing fast but it still only takes ~ 25-30 min to upload a 20+ gb image. If I were to use ESXi to upload the image, it takes upwards for 7 hours -.-
Hope this helps.
[quote=“pmonstad, post: 24126, member: 17422”]Read somewhere in the forum about replacing ftp/NFS with http. Is this something which is going to be realized in an upcoming release?[/quote]
Please don’t hijack threads, yes http transfer is slated for 0.33b and its being implemented with iPXE
[quote=“Tom Elliott, post: 24058, member: 7271”]There shouldn’t be any change.
Just the pointing from pxelinux.0 to undionly.kpxe[/quote]
you know… I thought that too, but it just yells that it can’t find the boot file 
either way… YOUR stuff [B]works[/B], let me play with the dnsmasq stuff to get it working.
GOLDEN!!! now I have to figure out how to get DNSMasq working with the iPXE stuff!
My fresh ubuntu install of 0.33b has errors On revision 1302.
First, on the FOG Configuration page, Under TFTP Server settings the FOG_TFTP_PXE_KERNEL_DIR is pointed to the wrong folder.
it is pointing to /var/www/fog//fog/service/ipxe
it needs the extra “/fog” removed.
After doing so and pointing my ipxe stuff to the 32 bit version it still complains about not being able to find the correct file.
Should I be entering anything into the FOG_TFTP_PXE_CONFIG_DIR ? because it is currently pointed at “FOG_TFTP_PXE_CONFIG_DIR” which isn’t actually a directory
Please don’t post multiple topics on the same issue!
As Albatros stated in the other thread, I would try one of Tom’s Kernels, they tend to work for most computer models.
I don’t use Snap ins or Power Shell, I am of no use to you.
At this point I would scour the BIOS and check settings, if you can pxe boot other clients and not this particular model, the problem most likely lies in the hardware, or the BIOS settings.
If adjusting the BIOS settings does not have an affect or if you have already exhausted all methods to enable the LAN Option Rom, Pxe boot options, Next server options, etc then I would contact Lenovo and see if there is a BIOS Flash that you can acquire to make the units PXE boot.
Have you ever imaged any of your machines with FOG?
Do you have another model of computer that will pxe boot?
Did you set up Options 66/67 like Tom suggested? It is part of the installation script that tells you to add values to your DHCP server. If you can not modify your DHCP server we have a work around.
And in FOG we use Partclone and Partimage. The problem is we are using previously created services to complete the required task here. FOG is open source, it uses all open source pieces to complete the puzzle. These are free.
Ghost is a privately created and operated, it uses it’s own services specifically designed for Ghost, not a piece designed for something else but achieves the same goal. That is why ghost costs. They also have a development team… I know your heart is in the right place, but as long as you keep comparing FOG to another imaging solution that is maintained by a full team of devs, FOG is always going to seem to be lacking.
My corporation uses FOG because it is free and it is versatile.
Personally I tend to enjoy the fact of being able to over come my obstacles with my own knowledge of linux. I realize that not everyone has this experience, but if you continue to compare apples and oranges eventually your fruit will rot if you don’t eat it 
[quote=“Oma Voss, post: 23921, member: 22725”]Hi Tom,
thank you for your support.
It did not work. I get the browser in big black letters back:
[code]
It works!
This is the default web page for this server.
The web server software is running but no content has been addet, yet.
[/code]
From the wiki I’ve taken, how to completely uninstall FOG and have done that. But despite reinstalling FOG again and again the same error, I can not get to the GUI.
Can you still give advice, except perhaps completely new set up the Ubuntu system to me please?
Best regards and thanks again.[/quote]
In order to get to the web GUI you need to add /fog/management to the end of your URL.
so if the IP address of your FOG server is 192.168.115.5 you would use
[url]http://192.168.115.5/fog/management[/url]
The problem is that the service installed to server the HTTP portions of fog is Apache2. apache sets up a stock page for use to let you know the service is working, that is the page you are seeing stating that “IT WORKS!!!” meaning your Apache is working.
You can set up a simple redirect page in the future to point your address to the /fog/managment folder.
[quote=“BigMan99211, post: 23884, member: 21932”]Whew!.. I just figured out how to save my butt here! I’m going to virtualize my 500GB drive onto one of my virtual hosts, then shrink the C:\ partition volume down to around 30-40GB, then shrink the virtual drive size down to match! Then, all I have to do is pull an image back to FOG. 
[/quote]
This is why I wanted you to run the compatibility check, it will tell you exactly where the issue is. It seems to think you are putting a larger image on the drive than what there is space.
This is probably the best idea… I have , in the past, used a Gparted live cd and fix your partition to be smaller that your SMALLEST hard drive in your corporation… When I create images I ALWAYS start with a small drive, ~ 30 gb. You CAN NOT find a drive for less than 80 GB unless you REALLY try. This give you the ability to put your image on a larger drive. Just add the portion to your unattend file that expands the partition to the end of the disc.
The size of the drive you image on is imporant, the ammount of spaced used by the image or on the fog server for storage is USELESS to calculate the size of an image or a disk.
I think you’re right Tom, I’m not sure what my revision is on this server right off the top of my head but I know it’s atleast a month old running 0.33b and I have the option but this is before the switch to iPXE and all that.
At the bottom of the installation script it gave you a link on how to get to your web GUI, as well as a user name and password.
I don’t know why you are complaining about documentation because during installation you specify the IP address the machine uses so you are aware of the IP address to enter into the web browser. Shortly after it explains the default user name and password are as follows.
[url]http://<ipaddressofserver>/fog/management[/url]
Username: fog
Password: password
To navigate to the web GUI use the ip address you assigned FOG during installation. I chose 10.6.22.3 so in order for me to see my fog GUI I use
[url]http://10.6.22.3/fog/managment[/url]
hope this helps.
[FONT=Tahoma]To [/FONT]Run a compatibility test.
[FONT=Tahoma]From the fog PXE boot menu, you will see:[/FONT]
[FONT=Tahoma]Boot from hard disk[/FONT]
[FONT=Tahoma]Run memtest86[/FONT]
[FONT=Tahoma]Quick host registration and Inventroy[/FONT]
[FONT=Tahoma]Perform full host registration and Inventory[/FONT]
[FONT=Tahoma]Quick Image[/FONT]
[FONT=Tahoma]Client system information[/FONT]
[FONT=Tahoma]Debug Mode[/FONT]
[FONT=Tahoma]A. Choose Client System Information[/FONT]
[FONT=Tahoma]B. Your computer will load another menu and it will look like this:[/FONT]
[FONT=Tahoma]1.) Reboot[/FONT]
[FONT=Tahoma]2.) IP Information[/FONT]
[FONT=Tahoma]3.) Partition Information[/FONT]
[FONT=Tahoma]4.) Check FOG compatability[/FONT]
[FONT=Tahoma]5.) Ping a Host[/FONT]
[FONT=Tahoma]6.) Display MAC Address[/FONT]
[FONT=Tahoma]7.) Show DMI Information[/FONT]
[FONT=Tahoma]C. Type 4 and press Enter[/FONT]
try wiping the partitions and putting a basic NTFS partition on the drive and try to image it again.
if you run the fog compatibility checker what does it say about the drive?
Please explain what you mean by “the client gets updated”? I don’t exactly know what you mean. FOG doesn’t dole out “updates”, it doles out images you assign to the Hosts. Are you referring to FOG trying to image the machines after the task is complete?