I can confirm Dell E6410’s work with v1.0.1. They work with the new updated kpxe files in [url]https://mastacontrola.com/ipxe/latest-DEFAULT-TEST/undionly.kpxe[/url].

I have no issues with this right now.

[quote=“number_one, post: 28807, member: 24434”]As a new FOG user, are there any quick tips to make sure there aren’t any catastrophes related to users booting PXE with a FOG server in an existing production network ?

I’ll be using an existing DHCP server that redirects PXE requests to the FOG server and I want to be dead certain that a random user isn’t going to be able to accidentally image their computer when booting up. There is is much info out there and so many complex configurations related to PXE so I thought I’d just ask for any quick pointers.

And if I missed a post or WIKI page that covers this I apologize.[/quote]

In 0.32 and earlier the PXE boot system was a little more “dangerous” in that it had all options by default. What I mean by this is it had:

Boot to Hard disk
Run Memtest86+
Quick host registration and Inventory
Perform Full host registration and inventory
Quick Image
Client System information
Debug Mode

The user could, if the host wasn’t registered, perform full host registration and inventory, join their system to FOG and have it perform an image of their system without knowing any information. They could also boot the system into debug mode, and completely wipe their systems or erase passwords if they knew what they were doing. So, yes, there were ways to have regular users hurt their systems. This was not typical though as it does require some knowledge of computers and linux. But there was always the possibility. Unless of course you added pass codes to each of the menu’s.

With 1.0.0, we started actually limiting options. If a host is registered, it only presents:

Boot to Hard Disk
Run Memtest86+
Quick Image
Quick Deletion
Client System information.

The Quick Image and Quick deletion options require the FOG username and Password natively to be successfully entered to run. So the user could run a memtest operation or boot into the Client system information, but the only real harm with these would be loss in production, no damage to the system.

If the host is not registered, it only presents:

Boot to Hard Disk
Run Memtest86+
Quick registration and inventory
Full registration and Inventory Client System information
Client System information.

With quick registration the user “could” register their system to fog, and if you’ve enabled the QUICKREG_AUTOPOP stuff their systems could be imaged for them, based on the circumstances, but that’s about the only threat. Full Registration could occur, but if you set it up to image there, it will prompt for username and password of the FOG System to allow imaging.

You’ll notice options are removed and display for the variants of the host. You’ll also notice the debug option is not available in the default menu system. So while Quick registration, if setup on the FOG Server with an IMG id, the system COULD be imaged, this is really the only time this could happen.

That all being said, where I work we have around 2500 systems that are imaged with fog. We have never had a person “play” with the menu options in 0.32 with or without the passwording of the menu options. They typically just boot the system and wait until it’s booted into Windows. 0.32 you can simple password encode the menus. You could also Hide the menu structure if you’re that worried.

1.x.x you can Keysequence the menus, meaning they’re not available to the user in the first place, until a preset key sequence is pressed AND a valid fog username and password are entered. You can also have a No Menu option which simply checks if there’s tasks for the host, if not, just boot to the hard disk. So there are many ways you can prevent and/or stop this “issue” altogether if needed.

Hope this explains it.

[quote=“Junkhacker, post: 28517, member: 21583”]there was a line in the install script telling you that you would need to edit the config.php file if you had a password
you had to hit enter to proceed past that message[/quote]

here is the line:

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]We are about to install MySQL Server on[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]this server, if MySQL isn’t installed already[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]you will be prompted for a root password. If[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]you don’t leave it blank you will need to change[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]it in the config.php file located at:[/SIZE][/FONT][/COLOR]

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]/var/www/fog/commons/config.php[/SIZE][/FONT][/COLOR]

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]Press enter to acknowledge this message.[/SIZE][/FONT][/COLOR]

It talks about if MySQL isn’t install. It was already installed. Therefore It did NOT apply to me. Maybe you should read the line before criticizing me. Or you should write the line in the script so that it says change the config.php file even is you already have MySQL installed.

Also a line in the script says:
[COLOR=#000000][FONT=Arial][SIZE=15px] Please see our wiki for more information at [url]http://www.fogproject.org/wiki[/url][/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px][/SIZE][/FONT][/COLOR]
That is why I suggested it should be in the wiki, not the script.

[COLOR=#000000][FONT=Arial][SIZE=15px][/SIZE][/FONT][/COLOR]

Hi Tom,
finally it seems solved. But I have had to make another action to make snap-ins work. You know that there is a change in snap-in file selection; i chose it from a select list an then click on “update” to make it efective, and then you see the file in the “sap file max size” box. But after migration to 1.0.1, in that box there is the whole path of file and that makes snap-in file download fails. It is necessary to click the “update” button i all of your snap-ins to make it work fine.

I think that is so much important to advise users who are going to migrate. So my advise for them regarding to snap-ins will be:
[LIST]
[]double-check that your snap-in task tables are empty, specially if you see after migration snap-in tasks in fog console which should not be there
[]apply update on all of your snap-ins
[/LIST]
Thank you very much for your hep Tom.
I hope not to bother you more (at least in short ;))

Frank
UPC-Terrassa8Barcelona)

It seems that a “Dell PowrConnet” has Spanning Tree Proticol (STP) enabled by default.
~[url]http://en.community.dell.com/support-forums/network-switches/f/866/p/17031843/17154977.aspx[/url]

If you disable this feature on this switch it may allow PXE to route through.

To quote Tom another thread…
[QUOTE]2) Check all networking switches that can be managed have portfast enabled (cisco) and/or *STP Spanning Tree Protocol) are disabled on the switch. The and/or meaning with Cisco, portfast should be all that’s needed, but turn off Spanning Tree Protocol if you can just to ensure this is NOT a factor in blocking the DHCP from iPXE.
~[url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/#post-27260[/url][/QUOTE]

It is:
[code]
svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_latest
cd /opt/fog_latest/bin
./installfog.sh
[/code]

will it work if you try an Image Type of RAW?

Thanks a lot Tom, that solved the issues. Great!.
Excuse me if it was so obvious to ask it here.
Now it’s time to test this brand new fog version.

Best regards.

Frank
UPC - Barcelona

delete the files in /management/reports
that should make most of them work

[QUOTE]Go to FOG Configuration Page->FOG Settings->Proxy Settings enable bogus proxy ip information. It should auto fail and make loading the pages much quicker.[/QUOTE]

FOG_PROXY_IP > was empty i put my server ip adress but i solve this and other problem appear:
At Home page > Dashboard at Disk Information is an error (Failed to connect to … ) can i do smth to apear disk info again?

But some questions: Only me and two ppl more have this problem? I was searching on the forum and only two threads about this problem and no solution.
You can’t make something when you install fog 1.X.X to work good like 0.32 with the same or better configuration?
Because that delay it’s verry frustrating.

[quote=“Jaymes Driver, post: 27721, member: 3582”]I don’t think this is currently possible, you can submit a feature request and we can see if we can work something out. However, in the past forum members have been successful at coming up with their own fix or add in that we have later incorporated. So please don’t be afraid to try![/quote]

Unfortunately with work at present i will not have the time to contribute. I will however make a feature request. Thank you for your assistance.

That should work, but definitely read the wiki article on how to upgrade.

If you’re wanting a newer OS that still runs smoothly and lacks bloat then I’ll toss in another shout out to using Debian 7.5 . But yes, with any system its best to get major OS work out of the way before trying to set up software that you want to be stable. Dependencies change, folder locations change, kernels change… it can be a mess for software to go through OS upgrades.

Fedora and CentOS are supported.

Ubuntu has just been making some changes and that is why you see all the chatter about Ubuntu lately.

I would NOT update to 14.04. I, personally, wouldn’t upgrade form 10.04 ever, I still have servers running 10.04 and I have NO ubuntu issues at all! Fog works wonderfully on a GOOD base OS. 12.04 would not be a bad upgrade, and 13.10 would be safe too.

Personally I would back up my databases and move my fog folders and install 1.0.1 on the 10.04 machine.

If you would like to upgrade your Ubuntu I would upgrade to 13.04 or 13.10.

It would be recommended to upgrade to OS BEFORE installing FOG though.

I agree with both of them. If you plan to use fog for DHCP you should take your FOG server out of the network and run a private network for imaging. And in which case you should stop the service with a command should you wish to introduce the machine to the network once more.

the hosts that are looking for the old IP will not communicate with the server while it’s running unless you reconfigure the hosts to look for the new name or IP. assuming you set up your dhcp server correctly for the new IP of the server, network boot operations should be unaffected. you could probably make a snapin to deploy to all hosts before changing the server that updates the config files on the hosts for the new server.

[quote=“Juan Antonio, post: 27635, member: 23837”]Good night from Madrid
I’m going to change the PC of fog for a newer computer.:)
Can I move images OS from the old server to the new server?😕

How can I do?o_O[/quote]

Easiest method to Copy the old images to the new server is to:
[code]scp -r /images <NEWFOGSERVERIP>:/images[/code]

Then on the New server as root run:
[code]touch /images/{.mntcheck,dev/.mntcheck}
chmod -R 777 /images
chown -R root:root /images[/code]

Then you have to recreate the associations for the images in FOG which I leave completely up to you.

Thanks for the info, using that I found this and updated php on the Fedora 10 box that was getting the white screen.
I then ran the installer script, which finished correctly now and then I was able to update the fog DB just fine.

[url]http://www.sohailriaz.com/how-to-update-php-on-servers-centosfedorarhel/[/url]

thanks for the help Tom

I missed the Banner in my haste. The Password was being delivered from the Storage Node. I didn’t think to look there. Makes sense on a large scale operation. Thank you for the help Junkhacker. By the way your avatar looks so angry. Makes me read all your responses like your angry and grumbling or scolding people… brilliant.

Well… This is Fog 1.0.1 We haven’t had time to write new wiki articles regarding adding items to the iPXE system. But this guide will not work for you. We no longer serve from the /tftpboot/pxelinux.cfg/default file, so these settings will not work for you.

We also upgraded the system from pxe to ipxe, thus the commands listed on this wiki will not work for you.

Instead, please take a look here -> [url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403[/url]

This will assist you in creating a custom menu on the new ipxe system.

As far as changing your graphics, I will assume you mean the back ground image? If that is the case, everything is served from your /var/www/fog/service/ipxe you will want to edit the background.png image there.

please note if you are on ubuntu 14+ you need to look in /var/www/html/fog/service/ipxe