Ok, thank you for your replies, I will try thursday and will return the result 🙂

^^Tom got’s it lol yeah yea I know this is an old post but I’m running CentOS 6.6 and all is good in the hood?! 😉

i have a suggestion that will make it so that you don’t need an isolated network for testing. what i do is redirect the boot.php requests for my test clients to my test server in the default.ipxe of my production fog server file, like so:
[CODE]#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

:bootme

redirected to dev server for test environments

##test-3020 optiplex 3020
iseq ${serial} F8HLK02 && chain http://<dev-server-ip-address>/fog/service/ipxe/boot.php##params ||
##testing VM
iseq ${net0/mac} 00:0c:29:ce:74:46 && chain http://<dev-server-ip-address>/fog/service/ipxe/boot.php##params ||

normal fog server

chain http://<normal-server-ip-address>/fog/service/ipxe/boot.php##params
[/CODE]

[URL=‘http://fogproject.org/wiki/index.php?search=snapins&title=Special%3ASearch’]http://fogproject.org/wiki/index.php?search=snapins&title=Special:Search[/URL]

A little wiki searching goes a long way.

[url]http://fogproject.org/wiki/index.php/Make_Snapins_Using_FOSS[/url]

Not a good day to be building a new server… ack

I also noticed the new site. It’s very nice and I’m glad the development continues. Keep up the good work

[quote=“Junkhacker, post: 41710, member: 21583”][url]http://fogproject.org/wiki/index.php/Modifying_the_Init_Image#Version_1.0.0_and_up[/url][/quote]

Thanks for the information, I’ve had a poke around and couldn’t locate the [I][SIZE=12px]fog.reg.man [/SIZE][/I]script. Are you able to point me in the right direction?

Thanks!

Edit

Found it!

[url]http://<ip[/url] of server>/fog/management/index.php?node=about&sub=mac-list

is there a approve all macs?

FYI: Wireless macs show up for hosts if the client is installed. Also to install snapins client must be installed.
FYI2: New Client will be more useful for snapins and other exciting options.

YES the trick was [SIZE=5][B][FONT=Consolas]next-server <ip of PXE Server>[/FONT][/B][/SIZE]

10:11:43 up 89 days, 17:46, 1 user, load average: 0.17, 0.27, 0.26

Hi Junkhacker,

Thanks for your help !

thanks i got it, change the FOG Service start from automatic to automatic delayed…
thats it…

no need to bloat your image with drivers

model way (just look at driver stuff):
[url]http://fogproject.org/forum/threads/utilizing-postscripts-rename-joindomain-drivers-snapins.12175/[/url]

or Hardware ID way (also has a wiki page posted):
[url]http://fogproject.org/forum/threads/automatic-hardware-detection-driver-installs-in-fog.11933/[/url]

Images are literally stored in the root directory “/images” go into your terminal and type:
[CODE]cd /
ls
cd /images
ls[/CODE]
This is the DEFAULT location for your images. It is possible that in your storage management you have changed the location but you would already know that.

Connect to your Fog server via FTP through your Windows machine and download the images. I would suggest WinSCP program. Uses a more friendly interface. [url]http://winscp.net/eng/index.php[/url]

There is no direct “reboot” task. Just when there is a task when the client is installed and the firewall is configured correctly, the client will check for a task. If a task is found it should reboot.

In about a month’s time or so this whole conversation will be moot for me as I’ll be replacing the images with updated recipes captured via PartClone.

If there is a bug and a solution I’m trying to find it not for my sake. I’ve already instructed our techs to use QuickImage and unicast in the meantime.

If the PartImage-captured PartImage-deployed image has a sector problem when multicast, then would it not also be corrupt when it is unicast?

Aggressively zero’ing the drives prior to PartImage Multicast results in the same.

Interestingly, interrupting a PartImage-multicast session will corrupt the drive similarly to the point where FOG will refuse to work with that drive until it is re-zero’d.

I haven’t run the installer yet, I wanted to be sure I could set it up the way I want it first. Should I be able to do it with the 1.2.0 installer version as well? Also do I need to drop the database before I run the installer?

I have uploaded our master image into the new server. I’m planning on just doing an .sql dump of the fog hosts table and importing into the fog hosts table on the new server. That way I bring all the old host information into the new server. I have 1 image and 1 host already, but we have that one master image for most of our machines. We have a few more images on the old fog server I need to bring over, and was just worried about transferring them. Thanks again for your suggestions!

when it’s done. at this point, i would say the release date will be “soon”
we can’t really schedule a release date, because many of us can’t really schedule time to work on fog. we work on fog in our spare time, for free.