Posts made by Jaymes Driver

Yeah that works too lol

I didn’t have access to my WDS server, and I am the only one adopting FOG in my corporation, the rest wants to spend all their time dicking with that WDS server, FOG is easier for me to use. So long story short, I wasn’t allowed to just disable the service

You must reboot your network and switches before the new “next-server” will take affect.

alternatively, you can install the DNSMasq (ProxyDHCP) to circumvent this. In the event that your FOG server is unavailable, it will continue to boot WDS, it’s a nice fail safe.

I had to use the service to make my pxelinux.0 reach my clients, but it will work for “temporarily” taking control of the DHCP service and boot to FOG.

You can also use a gPXE disc, you can supply your server and filename and it will boot your fog server instead of WDS.

Look here [url]http://fogproject.org/wiki/index.php/Setting_up_ProxyDHCP[/url]

I agree with Falko, It was to my understanding that before the tweaks were made so that Win 7 and Win 8 could be uploaded you had to use FogPrep before uploading the image.

Now that we sysprep and the FOG server knows how to handle the partitions, I have not used FOGPrep.

To be honest I never used it on my XP images either

Disk Fail = the Issue.

That is because it is an advanced format drive. I recommend taking a look at the .33 revision of FOG, the advanced format drives are reported to work with the 0.33 build. [url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/[/url]

[quote]Advanced Format is a generic term pertaining to any sector format used to store data on the magnetic disks in hard disk drives that exceeds 512 to 520 bytes per sector. Advanced Format is also considered a milestone technology in the history of hard-drive storage, where data has been generally processed in 512-byte segments since at least the introduction of consumer-grade hard-disk drives in the early 1980s, and in similar or smaller chunks in the professional field since the hard disk’s invention in 1956. Changing the sector format convention to larger data sectors, such as the 4096-byte structure used in the first generation of Advanced Format technologies, uses the storage surface area more efficiently for large files but less efficiently for smaller files, while enabling the integration of stronger error correction algorithms to maintain data integrity at higher storage densities.

Generation-one Advanced Format, 4K sector technology, utilizes the storage surface media more efficiently by combining data that would have been stored in eight 512-byte sectors into one single sector that is 4096-bytes in length. Key design elements of the traditional 512-byte sector architecture are maintained, specifically, the identification and synchronization marks at the beginning and the error correction coding (ECC) area at the end of the sector. Between the sector header and ECC areas, eight 512 byte sectors are combined, eliminating the need for redundant header areas between each individual chunk of 512-byte data. The Long Data Sector Committee selected the 4K block length for the first generation AF standard for several reasons, including its correspondence to the paging size used by processors and some operating systems as well as its correlation to the size of standard transactions in relational database systems.

Many host computer hardware and software components assume the hard drive is configured around 512-byte sector boundaries. This includes a broad range of items including chipsets, operating systems, database engines, hard drive partitioning and imaging tools, backup and file system utilities as well as a small fraction of other software applications. In order to maintain compatibility with legacy computing components, many hard disk drive suppliers support Advanced Format technologies on the recording media coupled with 512-byte conversion firmware. Hard drives configured with 4096-byte physical sectors with 512-byte firmware are referred to as Advanced Format 512e, or 512 emulation drives.

[/quote] <- [url]http://en.wikipedia.org/wiki/Advanced_Format[/url]

Did you run a compatability check to see if there would be errors with the hardware?

It will tell you what the issue is.

From the fog PXE boot menu, you will see:

Boot from hard disk
Run memtest86
Quick host registration and Inventroy
Perform full host registration and Inventory
Quick Image
Client system information
Debug Mode

A. Choose Client System Information

B. Your computer will load another menu and it will look like this:

1.) Reboot
2.) IP Information
3.) Partition Information
4.) Check FOG compatability
5.) Ping a Host
6.) Display MAC Address
7.) Show DMI Information

C. Type 4 and press Enter

If it is a hardware driver, a custom kernel can be compiled to include the information.

If it is an advanced format drive, I believe there are users who have over come the situation.

I hadn’t even thought about that, It’s a great idea Tom!

Damn not only do we get updates almost daily, we can see you obviously spend a lot of time working on this, and we appreciate it!

Keep up the good Work Tom, time to update my VM as well

We re-installed the server from the ground up using Ubuntu 12.10 as a base.

Then we started at it again.

He actually figured out the last bits on his own before I got back to my station (damn) but I’m glad he solved it

Did you first create an image in the Web GUI before trying to upload the image?

Create a Virtual machine and export the Virtual machine to a large external hard drive, or usb drive, i think there are some as large as 128gb now, this should suffice for fog demonstration.

I use Virtual Box because it is fast to set up, doesn’t require a dedicated server, and it runs along side my current OS installation. I would recommend using Virtual Box.

I would stay away from VMWare unless the places you are going to be showing FOG off at have a VMWare server. The reason I say this is because VMWare uses particular hardware when setting up your VDI and it is a pain to convert to other medium to import to say Virtual Box or another Virtual set up. You can change the hardware before you install anything to it, I am not very versed in VMWare though, and I think Virtual Box has made it pretty easy to understand for dummies (this is a reference to myself not you )

Hope this helps, good luck!

Since this is a blank server with no data on it yet have you entertained the idea of re-naming the installation directory and re-installing the server again?

I blew my server away and re-configured it about 5 times before I found the method that worked with my hardware.

I’m with Tom on this one, sounds like Apache server isn’t configured for the bond0 interface.

Are the HP-Z210 the only machines you have tried to boot? Do you have other machines?

I had some Tangent computers that flat out REFUSED to boot via pxe menu from FOG but always displayed my WDS server.
I had to contact Tangent for a BIOS update that allowed me to properly connect to my fog server.

Do you have other units you can test with? It looks like your file is okay. At least it looks like mine does, the ip addresses are different of course, but the contents are the same.

I’d be interested to see if the pxe menu fails on any other make/model.

Just as an FYI the fog client is NOT required to boot the fog PXE menu.

The FOG client is an add on for your image and will allow FOG to register the freshly imaged machine with your AD network, and a few other nifty things.

Some of the options that the client allows you control of are as follows:

Auto Log Out - The Auto Log Out service module will log a user out of a workstation after x minutes of inactivity.
Client Updater - Client updater will keeps your FOG client up to date. (a.k.a. updates configurations when you change it on the GUI.)
Directory Cleaner - The Directory Cleaner module will clean out all files and directories within a parent directory during log off. This module can be useful if you have an application that uses cache that you don’t want to persist between users.
Display Manager - The Display Manager service module will reset a computers display to a fixed setting such as 1024 x 768 on user log in.
Green FOG - Green FOG is a service module that will shutdown / restart the client computers at a set time.
Hostname Changer - The hostname changer is a service module that rename the client’s hostname after imaging. This service also handles Microsoft Active Directory integration.
Host Registration - Host registration is a service module that will register unknown fog clients with the fog server.
Printer Manager - Printer Manager is a service module that will install, remove, and set the default printer on clients.
Snapin Client - The Snapin Service module is used to install snapin files to the client computers.
Task Reboot - The task reboot service will periodically query the fog service to determine is a the client has a task associated with it. If it does and no user is logged in, the host will restart.
User Cleanup - The User Cleanup module will clean out “stale” user account left over from services such as dynamic local user.
User Tracker - The user tracker module will watch for local login/logoff and log them to the fog database.

I usually leave all of these options enabled on the client side and then disable those that I don’t need on the GUI.

When you log into your fog management site, the fifth icon from the end is the Fog Configuration page, this is where you can enable, disable, or change the settings your Fog client will use.

and of course, Welcome to FOG!!!

From the fog PXE boot menu, you will see:

Boot from hard disk
Run memtest86
Quick host registration and Inventroy
Perform full host registration and Inventory
Quick Image
Client system information
Debug Mode

A. Choose Client System Information

B. Your computer will load another menu and it will look like this:

1.) Reboot
2.) IP Information
3.) Partition Information
4.) Check FOG compatability
5.) Ping a Host
6.) Display MAC Address
7.) Show DMI Information

C. Type 4 and press Enter

Download a live cd offline, it’s like 30 or so MB, really small. You can supply it your server and pxe file information.

I was able to still get my pxe menu to display with the gPXE live disc, but for some reason the pxe file was getting blocked when fog sent it out. I used the information gathered when the pxe file failed and compared it to the dumps when I ran it with the gPXE disc (granted that the gPXE option works for you).

Just follow the instructions that Chad gave you.

Good luck

NBP is a Network Boot strap Program.

Your pxelinux.0 is a NBP file.

Can you try to load the menu with a gPXE disc?

In my particular case, only part of the pxelinux.0 file was being received, I had to set up the DNSMasq in order to properly load my pxe menu.

[quote=“chad-bisd, post: 15982, member: 18”]Please post the details unless they are embarrassing, of course.[/quote]

^ LOL!!!

I don’t care if they are embarrassing or not, if you have the will to come ask for help, the LEAST you can do when you solve it is:
1.) let the community know that you have solved the issue. and
2.) post the steps it took to resolve so others can use it for troubleshooting notes/reference when trying to help others!

Sounds like you have been having some FUN. Thanks for documenting the process so the rest of us may be able to use the information on future troubleshooting.

wow upload at 4.31 GiBs O.O I WANT IT

Sounds awesome, keep us posted I want to know what speeds you hit!