Resolve this please.

@loosus456 What OS is your FOG server running?
You will also need to be able to configure your network switch to support LACP (802.3ad) LAG.

No we do not have any requirement. we just want computers to work as normal with our modified image.

Thank you for quick response. Please mark this as answered.

@virtualdxs You can actually give it a try already! Would be great if you’d join in as tester to help us bring it forward.

git clone https://github.com/FOGProject/fogproject/ cd fogproject git checkout working-1.6 cd bin ./installfog.sh

@Sebastian-Roth Hello, yes I have setup 3 servers with fog running and I was successful in capturing the image and deploying it to 18 computers at the same time. I did look at FOG API, but I had questions about it like does is it run on bash or other script but later figure that it runs on bash.

@Sebastian-Roth Thanks!

@flo FWIW, one of the developers are adding your request to the LDAP plugin. Those should be in the mainstream code on the next release of FOG 1.5.6.

Fog did configure dhcp and it worked. we still modified it according our need. please resolve this.

@george1421

My MySQL knowledge is pretty shallow. For this situation I’ve got enough data, but I’ll read up and maybe change things then.

@mpatel For CentOS use the following:

dodhcp='Y' bldhcp='1' dhcpd='dhcpd' packages='bc curl dhcp ...'

Then re-run the installer and see it do the work.

@jsch Do you use the FOG DHCP server. I suppose you don’t. Please try changing the PXE filename from ipxe.efi to undionly.kpxe and see if that works for you.

@mpatel Disabled SELinux and Firewall???

it did finish. but took long time. Thank you guys. please resolve this.

@FeatherlessBiped This has been an ongoing topic. See my post here: https://forums.fogproject.org/post/117517

FOG was initially build to be bound to one interface and this is still the case in various places in the code and logic (PXE boot, multicast, unicast, capture). So it’s a heavy task to do all the changes and the FOG dev team currently does not seem to have the resources to do so. Don’t get me wrong. This can definitely be done and we will surely encourage and help people who want to implement multi-homing for FOG!

@george1421 No unfortunately I dont have an available to me to test.

@cary1102 For that to work you need to push the router/gateway information to the clients in the 10.10.222.0 subnet. Add the following line so your config looks like this:

subnet 10.10.222.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 10.10.222.XXX; ...

Put in the gateway IP address instead of XXX. I suppose you have a router/gateway that is making communication between the two different subnets possible?!?

You need to know that there might be other obstacles still in front of you. The clients use a couple different protocols like HTTP (easy), FTP and NFS to communicate with your FOG server and so the gateway needs to forward all those for the clients to be able to work properly.

@andre_x said in Clone PC and change product key:

Isn’t there a way to pass a field (for example “Other Tag #1”) to a script passed to the host?

There is probably a way. I know during image deployment with a post install script you can have access to this variable.

How about the drivers? How can he find them for a new hardware?

I have examples of how to create a post install script to copy over device specific drivers. I have to admit the examples are only for Dell systems, but you could adapt to other hardwares as long as you have the inf (not exe) based drivers packages. https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I use this method to seed (set) some unattend.xml settings to avoid having to use the FOG client to rename and activate the target computers. The word avoid is a bit strong, I have some unique OU naming conventions that are not supported by FOG, so I need to set then via scripting.

@ethan7888 said in error creating epoll fd: Function not implemented:

You confirm that the snapin, we can not put deployment programs of more than 3MB?

This is a setting in php.ini that limits the upload size of files. If you increase this value then you can upload larger packages. I have to tell you if the package is too large (like autocad), its better to install autocad on a hidden network share and then configure a snapin to call that network installation point instead of copying all of those files to the PC then installing the software.

Thanks @george1421 , the reason I wasn’t using sysprep oobe generalize was because it was causing my system to lock up at “Please Wait”. I found that un-joining and re-joining it to the domain “generalizes” the system enough so that everything works for us.

Anyway - I re-built the image and integrated the FOG Client (agent) into it. Now it appears the domain joining is working. Bad news is I’ll need to do another round of manual deployment, but that is the last time - after that I will have a full hands off deployment system.

Thanks for your help so far!

Your post is a bit unclear. Are you having an issue capturing the image or deploying the image?

When you say it reboots before its ready to deploy, is there an error message? Is this reboot happening in FOS image push or in/during WinSetup/OOBE? if the error is in FOS then capture a clear screen shot of the entire screen with a mobile phone and past the results here. The context of the error is almost as important as the error message itself.