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

Tom,

Thanks for your explanation. I thought the randomized TFTP password was a fogcrypt hash. I ended up doing a new install anyway. I’d done lots of learning and experimenting on the last install, so thought it was a good idea to reinstall before we rolled this out.

I can’t thank you guys enough for the work you’re doing. I’ll be making a donation, and I’m not a developer (not much of one anyway), but I’d be glad to help in any way I can.

Great group of people here 🙂

Thank you and till next question 🙂

[quote=“Sivasubramaniam.T, post: 27054, member: 22852”]Thanks a lot,

Can you please share the link for Fog 1.0.1 download.

Thanks in advance.[/quote]

[url]https://sourceforge.net/projects/freeghost/files/latest/download[/url]

[quote=“Albatros, post: 27059, member: 16710”]For booting iso files over network that are added to the menu. Take a look at this thread
[url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26419[/url][/quote]

Thanks! This is exactly what I was looking for.

I second using WAIK. It is alot easier than creating an Unattend file by hand. This tutorial helped me out quite a bit: [url]http://theitbros.com/sysprep-a-windows-7-machine-–-start-to-finish/[/url] .

As for activation, that is a tricky issue. My institution uses a KMS server. Somewhere I read that newer machines have the activation key hardwired into the computer somewhere. However that may only be for UEFI installations. If your computers do not have an activation code on the outside and they came with Windows pre-loaded then they key might be in the machine. That being the case any valid copy of Windows is supposed to work without having to enter a product key.

So if my thinking is correct you should be able to simply image the computer and Windows will pull the product key automatically from where ever it is stored. My laptop worked like that. I reinstalled Windows and it never asked me for a product key, but still worked. However I am not sure how that would affect you Unattend file. The only other solution is to create a separate Unattend file for each computer with the product key for that machine which is not an ideal solution.

Got it! Thanks Junkhacker! I am looking forward to upgrading my FOG server with 1.0.0 this summer.

Rock on, Tom! Thank you so much for your help!

Basically the software is stored on the storage node and gets copied down to the pc after image, also setup samba to the folder so its available as a software rep/share, we have a node on each site (any site that has more than 10 machines on site) so everything is “available” on the local network so no need to go down slow links etc… then the snapin is just a script n it determines what software is needed by hostname, model and location so once it determines what is needed jst installs them in order, i’ve used powershell in the past bt using autoit atm because its easier to be creative with GUI’s. Also got multiple tftps so the only “data” that is coming from “off” site is the snapin which is tiny 1.5MB n jst task n progress sent bk to server, so tiny tiny amounts 😄 so its jst as quick regardless of the remote site.

Perhaps I miscommunicated a bit. Typically an MSI is deployed through a domain rather than an EXE. This allows the domain to control what is done with the installer a bit more, including the use of an MST. The MST is a transform file that feeds the MSI commands and/or fills in options that the MSI usually contains. By default all domain managed MSI installs are silent, so in addition to not wanting to rely on the end user to know what buttons to push on an installer, an MST is necessary for anything other than a completely default install. I COULD replace the .ini files, but I would have to do this with another script, and I don’t know of a way to do this that is smart enough to run once per install, but also run again later if the install is marked as damaged or is somehow removed.

I’ve dug into the MSI a bit, and I have found a section under _Validation where I can modify a Table AppID with Column RemoteServerName. I will do some testing and report back.

Um Yes 🙂

I did reinstall php5 It Works!

[quote=“Psycholiquid71, post: 26623, member: 2717”]I keep seeing on Spiceworks about FOG being dead. It really bothers me as I see Tom doing a ton of work daily to make this comm unity a really good place. Small yes but good none the less. If anyone here uses spiceworks try to promote this a little bit more as I love this product and don’t want people to “slander it” as I have been seeing.

Slander is a strong word for it but misinformation is just what is happening. and it erks me.[/quote]

I have a spiceworks account. I have not had much time, between keeping you all updated on the forums and trying to fix and or program FOG itself, to go through to all the posts on Spiceworks in regards to FOG. I will try my best to do better, but it may be a bit while we’re ramping up for release.

Thx [SIZE=12px]Junkhacker; I’m on 0.32 in this case; after some testing I think the message “compression level…” may not be credible; if when it says NONE the imager clearly uses compression since the final *.img file is nowhere near the actual partition used up space. Could there be some truth to that?[/SIZE]

On image compression I found this super helpful post:

[SIZE=4][B][COLOR=#3b3b3b][FONT=League Gothic][SIZE=35px][URL=‘http://uberamd.com/post/22125061841/disable-gzip-image-compression-in-fog-for-faster-image’][COLOR=#0581d2]Disable GZIP Image Compression in FOG for Faster Image Creation[/COLOR][/URL][/SIZE][/FONT][/COLOR][/B][/SIZE]

[FONT=Helvetica Neue][COLOR=#333333]Recently I changed the software the imaging server at work uses from Clonezilla to FOG. There were many reasons for the change such as a better web interface, image deployment queue, etc however one of the main things I was looking forward to was storage nodes which allows for distribution of images across multiple servers to extend storage.

Deploying the FOG server was easy enough, however one of the first things I noticed was that image creation (uploading a new image to the server) was incredibly slow in comparison to image deployment. Image creation would take nearly 2 hours while image deployment would take about 25 minutes. This frustrated me to no end as we were doing this over gigabit and it wasn’t utilizing hardly any of the pipe on image creation. A quick glance at the screen told me why: FOG automatically assumes you want to GZIP the image. This means a smaller image, but a drastically increased image creation time since the system needs to compress the data it is sending.

I searched high and low through the config files for a way to disable GZIP compression, but found nothing. Eventually I figured out how to disable the compression, however doing so was not well documented at all. Enter this post which will hopefully help others solve the same problem I ran into.

Simply follow these steps (type these commands in your Linux terminal, you may need to be root or sudo to run some of these):

[FONT=Courier New]cp /tftpboot/fog/images/init.gz /tmp/init.gz
cd /tmp
gunzip init.gz
mkdir tmpMnt
mount -o loop /tmp/init /tmp/tmpMnt[/FONT]

Now using your favorite linux command line editor open the file /tmp/tmpMnt/bin/fog and find and replace all instances of -z1 with -z0. To do that with VIM do the following:

[FONT=Courier New]vim /tmp/tmpMnt/bin/fog
:%s/z1/z0/
:wq[/FONT]

Once you have replaced all -z1 with -z0 we need to recompress and replace your old init.gz file:

[FONT=Courier New]cd /tmp
umount /tmp/tmpMnt
gzip -9 init
cp /tftpboot/fog/images/init.gz /tftpboot/fog/images/init.gz.old
cp -f init.gz /tftpboot/fog/images/init.gz[/FONT]

Thats it. Now you have disabled compression upon image creation and you should notice a VERY large drop in image creation time! FOG does provide a script that assists in editing the init.gz file, HOWEVER the script requires you to have Nautilus installed (aka GNOME) and how many people really run a GUI on a server? Not many.[/COLOR][/FONT]

I just wanted to say thank you for the post. Have been all over looking for this answer, as I am new to both setting up a Ubuntu desktop as a Linux server and FOG. Really excited to start using FOG, great piece of software by the way, and give this school district an answer to cloning that doesn’t involve using deploy studio to clone a PC. Thank you again.