Posts made by jbsclm

You are stuck with it.
Although all the images are created with partclone, different image types create a different mix of files and folders.
Hope this helps.

Bluenix here you are.
The iso I’ve included will try and get a dhcp address, if that fails, it will ask for the address details.
It then asks for the IP address of your fog server, and chains on to it.
I’ve included details of how to build your own.

[url=“/_imported_xf_attachments/0/592_ipxe_ask33.zip?:”]ipxe_ask33.zip[/url]

Help buttons not appearing on fog configuration settings page.
Fixed in the attached, to go in fog/lib/pages

[url=“/_imported_xf_attachments/0/591_FOGConfigurationPage.class.zip?:”]FOGConfigurationPage.class.zip[/url]

N.B. Fog 0.33 is currently beta,this will allow you to test 0.33 alongside your existing 0.32 installation.

It assumes an existing working 0.32 installation, and also a working 0.33 install.

On your 0.32 installation.

Via the “other information” -> “PXE Boot Menu screen” -> “Advance Configurations” Add the following to your custom text, where xxx.xxx.xxx.xxx is the IP address of your new 0.33 server.

LABEL FOG 0.33 Beta
kernel ipxe.krn dhcp && chain [url]http://xxx.xxx.xxx.xxx/fog/service/ipxe/boot.php?mac=${net0/mac}[/url]
MENU LABEL DEV menu

Don’t forget to suppy a Master password before saving pressing “Save PXE Menu”

copy the ipxe.krn file from /tftpboot on the 0.33 server to the same location on the 0.32 server.

On the 0.33 server.

[B]Disable[/B] the dhcp service on the 0.33 server, you will need to consult the O/S documentation for details on how to do that.

Hi Bluenix. I’ve done at 0.32 what I think you mean, ie a boot cd/usb, which then connects to the fog server, over the WAN.
I don’t think it would work over a proxy though, I don’t think IPXE is that goog.
It should be easier for 0.33.
Let me know if this is what you mean, and which release you want and I’ll try and put one together for you.

Attached zip contains the changes needed to add shutdown or reboot after capone deploy.
You just need to drop the files in as the base files haven’t changed since the changes were done.

[url=“/_imported_xf_attachments/0/566_capone.zip?:”]capone.zip[/url]

also task deploy of xp single partition seems broken, says checking disc, a couple of lines later it reboots, without ever having run partclone.

One for Tom to look at methinks.

If I revert pxelinux.0 back to pxelinux.0.old it works.

I wonder what the difference is?

Confused
trying 1263, but getting int 18 boot fail as per the attached.[ATTACH=full]565[/ATTACH]

Oddly the ip address is missing from the http line.
I thought this would come from
/tftpboot/pxelinux.cfg/default
but that has the IP address in, and if I modify it the changes don’t appear, implying it is coming from somwhere else.
my fog ip is 192.168.3.11.
Any thoughts

[url=“/_imported_xf_attachments/0/565_boottest Clone.png?:”]boottest Clone.png[/url]

Just done a one off speed test deploying on r1257 against 1249.
an 8gb W7 single partition image, went from 3 mins 43 to 3 mins exactly.
On a sample of one, the NFS tweaks look to be worthwhile.

as further info, I’m also getting the same 2 error messages when trying to just about anything to a newly created (empty) group, on r1249.
PHP Warning: Invalid argument supplied for foreach() in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 239, referer: [url]http://localhost/fog/management/index.php?node=group&sub=delete&groupid=1[/url]
PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/GroupManagementPage.class.php on line 252, referer: [url]http://localhost/fog/management/index.php?node=group&sub=delete&groupid=1[/url]

Rgds

Checking out capone after Tom incorporated my changes for ipxe, it looks like the following was missed.

1. Getting unable to mount images due to missing argument for capone, amended version of /fog/service/ipxe/boot.php attached.
   I’ve also attached an updated version of management/plugins/capone/run.php, it removes the pxe configuration stuff at the end, as it is no longer needed.
   ArchFan, as you say, the PC is not being associated with the image, check your DMI Field and DMI Result setting.

[url=“/_imported_xf_attachments/0/554_run.zip?:”]run.zip[/url]

Well spotted.

Attached are the changes to add capone into the ipxe menu.
There is no longer a requirement to copy and paste entries for the pxe menu.
3 files.
management/plugins/capone/run.php
fog/commons/basic.inc.php
fog/service/ipxe/boot.php

[url=“/_imported_xf_attachments/0/550_ipxe_capone.zip?:”]ipxe_capone.zip[/url]

For info I have added a background image to my ipxe boot cd.
I built an ipxe at
[url]http://rom-o-matic.eu/[/url]
with the following options.
CONSOLE_VESAFB
CONSOLE_CMD
IMAGE_PNG
in my ipxe boot file I added the console line.
so it now looks like
#!ipxe
console --picture ${boot-url}bg.png
:start
menu iPXE boot menu

item tftp FOG via tftp
item http-live FOG via http( live menu)

choose target && goto ${target}

I’ve tried adding the console line to the fog code, but it looks like your ipxe.krn wasn’t built with the CONSOLE_CMD option.

Hope this makes sense.

[url=“/_imported_xf_attachments/0/543_boottest Clone.png?:”]boottest Clone.png[/url]

For info, the vbscript function we use to check for presence of a particular device id is below.
This allows us to install the associated software as well rather than just the inf files.
the command line utility Devcon is available from Microsoft at the following link.
[url]http://support.microsoft.com/kb/311272[/url]

Function device_present(device)
Dim cmd,oShell,ScriptPath,rexec,strtext
ScriptPath = Left(WScript.ScriptFullName, Len(WScript.ScriptFullName) - Len(Wscript.ScriptName))
cmd=Scriptpath & “drivers\devcon find " & device & “*”
'msgbox cmd
Set oShell = CreateObject(“WScript.Shell”)
set rexec= oShell.exec(cmd)
strtext=”"
strtext=Ucase(rexec.stdout.readall())
if(InStr(1,strtext,“NO MATCHING DEVICES FOUND”,1) >0 )Then
device_present=false
else
device_present=true
End If
'wscript.echo strtext
End function

Excellent work Tom, thanks.
A minor issue the ipxe menu could do with a longer timeout, or preferably none at all.
A gotcha to avoid. if you are running virtual box and your client hangs downloading bzImage or init.gz, you need to change the network card type to intel. The entry I found suggested that vmware had the problem as well.
I seem to be getting Unmountable boot device on deploy of xp single partition, is the ipxe init.gz the latest version.
Keep up the good work.

We do something similar, ie a vanilla w7 image, at the end of the install, we have a VBscript which installs the “known” items, based on the model, after which we check if certain device ids, eg, PCI\VEN_xx&DEV_xxxx, are present, and then run the installer silently with no restart, after which it reboots.
This catches for example desktops with special video cards, or laptops where the same model can have different wireless or 3g card, which also needs its own management utility. For example you need the full ati catalyst suite to get the best from the card, rather than just the bare driver from windows.

Interestingly enough, I have just, ( this week ), created an IPXE based boot cd/usb, for 0.32, capone only not tasks, and also DELL diags.
What is very noticable is the speed difference downloading bzImage and init.gz, ipxe uses http which is much faster.
The pxe boot config is tiny, it just chains the menu via http.
My wish list for the future would be very much as yours.

1. move from pxlelinux/tftp to ipxe/http for the initial boot and bZimage and init.gz download.
2. pass the mac address, manufacturer, model and asset to the service code, and lookup the image association.
3. Add authentication for the http requests.
4. use http to initiate the move after uploads.
5. If the image download could be moved to http from nfs as well, this would mean that we could go totally http, which would make getting fog to work across a firewall much easier. I’ll set up a test to see how the speed compares.

As a say a wish list, of which IPXE is just the enabler, some of these would have to be long term.