Posts made by Jaymes Driver

Do you have a Windows imaging server in your network? Does it dole out pxeboot information? I ran into this issue with IP helpers from other buildings within my corporation.

I know you feel like NOTHING in your network has changed but fog doesn’t just magically stop being able to provide the boot file, unless it was never able to be provided in the first place.

I think there is something in the network that is either preventing the full cast of the boot file (that was the case in my environment) or you did not set up the correct information at the DHCP server, you can correct the information at the DHCP, or you can use a proxy dhcp service to serve ip addresses during the pxe boot stage (I HIGHLY recommend this method as it has worked in the past for myself and many others, AND you don’t have to mess up your network to do it!)

Just because the Web side of FOG works doesn’t mean that the FTP sections are behaving as expected. It could also be a misspelling in the boot file name, please note it should be pxelinux.0 (that is a ZERO not an O), or it could be a wrong password. Did you set up passwords for MYSQL when the prompt presented itself?

So please report back what your findings are so was can help further.

If you don’t want to try the proxy dhcp: You can start by isolating the FOG network on a hub or router (something needs to dole dhcp during pxe boot or you won’t get anywhere) and see if you can get a piece of hardware to boot to the FOG pxe menu.

If the device fails, try another make and model (if available).

Running wireshark in your network can help to pin point the issue where the pxeboot file is being dropped as well.

Thank for letting us know where the issue was! I haven’t worked with Azure, so I am sorry I couldn’t be of assistance.

Thanks Tom! I’m really digging the iPXE direction!

[quote=“Valden, post: 22881, member: 21858”]Do you think, that is possible to download the usb image directly into the ram with tftp ?[/quote]

It may be possible to load with tftp, but you have to make sure that enough ram is available for the image though…

FOG isn’t designed to handle ISO image files.

I’m not really a phone call kind of person… I would be more than happy to provide any walkthroughs I have conjured up they are aimed at Fog Newbies.

Hey if it’s working leave it alone. I was going to have you isolate the network to rule out problems with your network communication or things blocking traffic.

Yes it is possible to use a NAS store.

You have to register every machine you want to use with FOG to the FOG server.

There are scripts around that will allow you to do things without registering them, but really, the best method is the register them so you can keep track of what image is installed on the host.

[quote=“Tom Elliott, post: 23043, member: 7271”]

I ask all these questions because if you have only one DHCP server and your systems work fine throughout, you may want to look into the ip-helper commands.

Where I work, we have a similar type of setup, and from our “Master” switching location, we just ran ip-helper for all of the subnets to point at our DHCP Server. Then just set the DHCP Server scopes to point Options 66/67 to the FOG Server/File (respectively).[/quote]

I use these, it’s pretty awesome

I also set up some nodes on the sites, but that is a different story.

you should ALWAYS use sysprep (some will argue) but it really helps generalize you install for the real user.

[FONT=Verdana][COLOR=#333333]Before trying to open the FOG management webpage [/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Install PHPMYADMIN (this makes database management easy)[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Open //localhost/phpmyadmin [/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Create a new user and give them ALL permissions for ALL HOSTS (basically they should be the same as ROOT[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Check the user is there and the permissions are set correctly. [/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Go into the PERMISSIONS tab and remove the password for ROOT under localhost & 127.0.0.1[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Open the FOG webmanagement page[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Set up the users in FOG[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Go back to PHPMyAdmin and make sure FOG has been added as a database. You will need to log on as the ‘new user’ above[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Reset the root password to something secure (as per pre install???)[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Open the FOG database[/COLOR][/FONT]
[FONT=Verdana][COLOR=#333333]Go to Permissions and BLANK the root password for localhost & 127.0.0.1[/COLOR][/FONT]

Then I recommend checking the BIOS to make sure all settings are correct, use legacy settings, UEFI is currently not supported and others have had trouble with the advanced format drives, but some have been able to image them, please take a look here on the forums for further trouble shooting.

An option you may consider is trying Tom’s kernel set up as it has helped others get some unruley hardware cooperating, but I believe the problem you are experiencing is from the 4K advanced drives. If the folder is only a few KB, it did NOT save properly and should NOT be used as an image.

If you can use FOG to image other machines that you use to be able to image, the problem is not at the server it’s at the new hardware.

[quote=“Marco Dinis, post: 23036, member: 22226”]Hi
Is there a fogprep for Windows8?[/quote]

FogPrep is not longer required.

strange, it must be using the /var/www folder (Sorry I see at the top you are using Wheezy, it will reside in the /var/www folder sorry for the confusion )

please check the /var/www for a fog folder

Well that’s good that the page is displayed, it seems that apache is working.

That is because FOG 0.32 is sorely outdated and was meant to run on the older versions of linux. Since then newer and updated packages are being used in the later distributions. Tom is working on FOG 0.33b and I’m sure when all is said and done he will iron out the issues with htmldocs and clamav by updating the repositories and versions it uses/installs.

In the mean time please use the work arounds found on the forum to install and configure the services.

Tom started working on FOG here recently he wasn’t always the maintainer so he doesn’t have access to edit the old FOG 0.32 files and NOR should he.

look in /var/logs/apache2 for log files

when you navigate to localhost, does it display anything? it should display a web page that says “IT WORKS!” letting you know that apache is running correctly.

if it doesn’t display at first, try localhost/index.html. Fog adds a index.php file to the /srv/www folder that is suppose to redirect to the FOG management page, so we can attach the file name to the end and it should display the correct file.

okay so it seems to be failing when it wants to move the files over to the /images folder, you can do so manually by making a folder in the /images folder equal to what you set in the Image Store as the image name. BUT FIRST lets check the size of the files in the /images/dev/MAC folder and tell me how large the files are.

to SOLVE the issue… Make sure your server fog user password is set and that that password is what’s set in Storage Management Password and in FOG Settings->FOG_TFTP_FTP_PASSWORD

What kind of a machine are you imaging (make and model)

Is this a new fog server or was it working in the past and recently stopped working?

Was this model a new purchase this year?

Can you try another test client (different model and type hopefully to rule out hardware issues)?

No problem, hopefully you learned some things in your adventure so it’s not a loss

try removing your .mntcheck files and recreating them

/images/.mntcheck
/images/dev/.mntcheck

edit your /etc/expotrs to look like this
[code]
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)
[/code]

ALSO, if you are using the FOG server to store your images (Not a NAS or another server, or save space or something HAS TO BE STORED IN THE /images folder on the Ubuntu box) then try isolating the network with a basic router. Set up a network between the host and the server only and try to image.

Add a script to the END of the setupcomplete.cmd file that runs another script to remove the fill/folder.

Just keep chaining scripts until you accomplish the goal you desire lol

Ubuntu is a derivative of Debian, that means the main core files are the same.

Linux normally comes in Five flavors:
Debian (widely used includes Ubuntu, Linux Mint, and a few others)
RPM (wideley used mainly noted as Fedora Core or RedHat, SUSE just to name a few)
Gentoo (Supposed to be updated frequently and suppose to be highly optimized for use, If you are familiar with ChromiumOS it is Gentoo based)
Slackware (Slax Based, not cutting edge but stable and highly customizable)
Arch Linux (High points: elegance, minimalism, and simplicity)

These are the linux BASE operating systems. With each base comes many different distributions.

Lets take Debian for example, has ~ 50 different distributions, ubuntu being one of them.

EVERY distribution based off Debain use the SAME core files, and NORMALLY the same package handler.

Every flavor of LINUX has the OPTION of running a GUI… but is not required to. there are many different “desktop types” that linux uses.

Ubuntu breaks the use of the desktop environment down into further distributions such as:
Ubuntu (use to be Gnome until 12.00 they switched to Unity which many users coming from Windows find easy to use.)
Kubuntu (Flashy eye candy and uses KDE environment)
Xubuntu ( is intended for use on less-powerful computers, uses XFCE)
Lubuntu (lighter, less resource hungry and more energy-efficient, uses LXDE)
Edubuntu ( eductation based I think it uses gnome)
Mythbuntu (based off of MythTV mainly for media centers)
and the list goes on

As you can see for each Derivative there are Distributions.

You are using Ubuntu, a distribution of Debian, any Debian base files are ALREADY installed on your system.

That being said… Every version of linux has a login page that greets the users for ease of log in, be it a text only log in or a graphical log in. The splash page, also called the greeter, is able to be customized, but in doing so none of the core OS files change, only the LOOK of the log in page, and it can’t actually tell which OS you have installed, it just passes the information to the OS.

With the LTS versions of the Linux OS there is no desktop environment included, you have to install your own, including the graphical login page.

It sounds to me that during the installation or set up of some files (if you were using a guide it probably told you to run commands and that is probably how the graphical interface got installed) that a graphical interface was installed.

I can’t tell you why or how it got installed, as Tom expressed, this Forum is based on helping users with FOG, and the issue you are describing is NOT something that FOG has done. I have installed FOG many times on Ubuntu LTS (the one without a graphical interface) and it has NEVER installed the desktop environment or the graphical log in on its own, only if I issue commands specific to adding an environment or login.

NOTE When you install a graphical log in page you can install one specific to Ubuntu, or any other flavor of linux, it is probable that when the command was typed it had an appendage that told it to install the “debian” back ground on the graphical log in, this can be changed when logged in.

I hope this helps any confusion, if you would like some assistance in understanding how the error occurred or where the graphical interface came from, you really need to visit the Ubuntu forums, I am an Ubuntu nut, but I don’t know everything sadly

If you would like to revert back to a text only login environment you will need to visit a page such as this:

[url]http://ubuntuforums.org/showthread.php?t=1293350[/url]