Thanks for that!!! I’ll try it out!

unless you are just tied to fedora for some reason, install ubuntu 10.04 Server LTS and you can follow the instructions in the wiki article. I do not use Fedora currently, and I have no idea how to customize dnsmasq to do what it needs to do without the Ubuntu LTSP stuff.

[quote=“chad-bisd, post: 4419, member: 18”]Go to the sourceforge page for fog and go through the downloads. There should be kernels listed there. Start testing out the most recent kernel and move your way backwards through them. Without access to their configs, I can’t tell which supports what hardware other than trial and error.[/quote]
Thanks. I’ll give that a try.

Fog polls the computer for DMI information, including the Asset Tag info from the BIOS during registration, but after the host has been named. You probably just need to update the fog scripts inside the init.gz (/tftpboot/fog/images/init.gz) to update the database with the asset tag as the host name at the end of registration and before the machine is imaged.

This sounds like a possible plug-in/add-on idea.

[LEFT][SIZE=12px][COLOR=#2a2a2a][FONT=Segoe UI]If you are not doing a one size fits all image and only want to put the image on the same model/hardware then this might help. It helped me with a similar issue.[/FONT][/COLOR][/SIZE][/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
[LEFT][SIZE=12px][COLOR=#2a2a2a][FONT=Segoe UI]Configure your answer file to persist the drivers by specifying the PersistAllDeviceInstalls setting in the Microsoft-Windows-PnPSysprep.[/FONT][/COLOR][/SIZE][/LEFT]
[LEFT][SIZE=12px][COLOR=#2a2a2a][FONT=Segoe UI]<settings pass=“generalize”> [/FONT][/COLOR][/SIZE][/LEFT]
[LEFT][COLOR=#2a2a2a][SIZE=12px][FONT=Segoe UI] <component name=“Microsoft-Windows-PnpSysprep”> [/FONT][/SIZE][/COLOR][/LEFT]
[LEFT][COLOR=#2a2a2a][SIZE=12px][FONT=Segoe UI] <PersistAllDeviceInstalls>[B][FONT=inherit]true[/FONT][/B]</PersistAllDeviceInstalls> [/FONT][/SIZE][/COLOR][/LEFT]
[LEFT][COLOR=#2a2a2a][SIZE=12px][FONT=Segoe UI] </component>[/FONT][/SIZE][/COLOR][/LEFT]
[LEFT][SIZE=12px][COLOR=#2a2a2a][FONT=Segoe UI]Another way would be to configure the registry key:[/FONT][/COLOR][/SIZE][/LEFT]
[LEFT][SIZE=12px][COLOR=#2a2a2a][FONT=Segoe UI]HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Settings\sppnp set [B][FONT=inherit]PersistAllDeviceInstalls[/FONT][/B] to [B][FONT=inherit]1[/FONT][/B].[/FONT][/COLOR][/SIZE][/LEFT]

Tom and Kansuke,

This is also maddening me! Is it possible for Dell or HP to send a client(me) a list of MACs on a shipment? We have ordered up to 80 machines at a time, and it really sucks to have to manually add them.

In current projects we have had to tie a Dell Service Tag to a laptop for warranty reasons:

Boot host
Quick inventory
List all hosts (in FOG)
xx:xx:xx:xx:xx --> gatesbill
Record MAC and Service tag Name in spreadsheet
Shutdown
Do this 9 more times
Start Multicast imaging
Box em up

Do 7x more times

Does this sound right, or am I out of it?

It would be awesome to even use the asset tag as a host name like Kansuke said. I don’t know how to program, let alone tackle linux. But I’m willing to learn!

Thanks!

F8 is a Windows boot up option, nothing to do with Fog. You do it right after the fog boot menu goes away and right before you see the windows logo. It brings you to the Windows menu to boot into safe mode/etc.

It may be a problem with the firmware on those cards. I have about 30 rebranded Compal JHL91 laptops and 270 Acer Iconia Tab w500p tablets. These two models of devices do not PXE boot properly by setting DHCP with the server and filename options. They would give me a tftp: file not found.

I installed WireShark (and WinPCap included) on a machine and setup my switch to let me monitor the port the problematic machines were plugged into. I found that when these machines booted to PXE, they would get the IP of the fog server and the name of the bootfile (pxelinux.0) but would fail when making the TFTP read request.

If you have access to the switch config, download a copy of WireShark (free on Linux and Windows) and investigate what’s going on during the PXE boot and TFTP initial transfer.

[B]Tip: [/B]Start your packet capture as the problematic computer boots and stop it right after you get the error. Then use filter: “not arp and not http and not snmp” in WireShark and look for UDP messages related to DHCP. The first should be a DHCPDiscover, then a DHCPRequest, followed by a DHCPAck.

If you look at the lines for DHCP, pay attention to the Bootp section in the data window.

Let’s see exactly where the failure is before we offer solutions.

Thanks, the one one tab I never goto

This happened to me when I tried to use any location other than %systemroot%\system32\sysprep\ as the location of the unattend.xml file and I don’t use the full path when calling sysprep from the comman line. usually my sysprep call looks like
[CODE]C:\Windows>%systemroot%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:%systemroot%\system32\sysprep\unattend.xml[/CODE]

You have a few options, listed in order of complexity and setup requirements:
[LIST=1]
[]Disable DHCP on your DLINK ADSL modem and use Fog as your DHCP server. The config is really easy if you just need it to give out adresses to a small network.
[]Disable DHCP on your DLINK ADSL modem and use a spare computer running Ubuntu as a dedicated DHCP server.
[*]Leave DHCP running on your DLINK ADSL modem and configure your Fog server to use LTSP/ProxyDHCP so it answers PXE boot requests with next server and file name options, but doesn’t handle giving out IP addresses.
[/LIST]

If you choose the single disk resizable, you get 1 file under /images/
If you choose the other image types, you get a folder name, and several files created undernearth representing the disks and partitions.

You should compare the /images/ directory structures on both servers, including permissions and ownership of files. Also, make sure the rsync is complete before you try to use the image files.

On 10.04 LTS [B]Server[/B], you should not have to make that change. Create a new thread with the particulars of your issue including Fog version, OS Version, and as much information about the error as you can. We’ll be glad to help you.

while i’m thinking about it, is there a way to find your config during the initial setup of FOG? It sure would be trying to track down all the IP’s used for setting it up if you can just pull up your initial config.

Nevermind after searching the syslinux iso, I found the vesamenu.c32 file under syslinux-4.05\com32\menu for anyone wondering.

thanks i have your email

Hi Terry,

Take a look here : [url]http://www.fogproject.org/wiki/index.php/Modifying_the_Init_Image[/url]

Once you have access to all of the scripts it’s pretty easy to add the linux command (for the life of me I can’t remember what it was as I’m a confirmed Linux noob to my eternal shame !) so that at the end of the process it’ll sit there and wait for a keypress.

HTH
Cheers
Robin

I’m really sorry that I did not get a chance to reply to this earlier, but thank you so much for taking the time to help me out with this! I had been wrapped up in other projects until today, but I will definitely work on this and let you know if I make any progress! Again, thank you! 🙂

[quote=“joshua, post: 3872, member: 146”]Hunter, when you goto the server IP /fog/client in your web browser, you should already have a download for Sysprep.
for me when I goto 192.168.1.63/fog/client I see this:
[ATTACH=full]120[/ATTACH]

However, if you want to add more to it, I guess you could just modify the index.php file to include whatever you wish.
You can find that file here in Ubuntu 10 (and probly the same for all Debain based installs).
/var/www/fog/client/index.php

Hope this helps[/quote]

Thanks for the direction, it works, added a DL for the Win7 unattend file.