@lazybeard In this case, you could extract the contents of the iso into a http path on the fog server (i.e. /var/www/html/iso/diskwipe

And then reference the files via http

linux http://<fog_server_ip>/iso/diskwipe/vmlinuz.x86_64 root=/dev/ram0 rw init=/init video=efifb loglevel=3 initrd http://<fog_server_ip>/iso/diskwipe/wipe-x86_64.lz http://<fog_server_ip>/iso/diskwipe/firmware.lz /bcwipe

Understand this is just a guess and it will need to be translated into what iPXE needs to boot the file (you can see that from the url I provided before).

thanks, it works

Hello,

Thanks for your help, i’'ve managed to get FOG working now on the 1.3.4 version.

@Tom-Elliott Hi Tom. I had the same problem when I wanted to deploy my last image (Dell OptiPlex 330/Windows 7 created with the last version of FOG: 1.3.4)
It works fine now thanks to the 1 value in the d1.fixed_size_partitions. Thank you 🙂

@kibade I don’t know if the donate option still works as it was compiled from long ago, but I did see the issue about the clearScreen. I’ve pushed a fix for the clearScreen issue.

I’m not planning to work on anything for the clamav tasking as the intention is to have it mount the clamav portion from an NFS (of which you would need to configure first. This way sigs would not have to be downloaded everytime from the internet.)

Please try :

wget -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init.xz wget -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init_32.xz

As I stated, I don’t know if it will still work, but the reboot and error message should be gone. (This is specific to the donate task.)

@Tom-Elliott 0_1485899730465_Firefox snapin.PNG

how long does the client takes to communicate with fog server?

@dbakerwardog
Just checking, the “FOG_AD_DEFAULT_USER” you have set, have you double checked it has permission to add and remove computers from the domain?
I would try moving that computer to a workgroup using the above user and see what happens.

Ok, I found the issue. The Geo IP filter on the firewall was preventing accessing the remi repository, which was keeping me from updating php. Disabled the Geo IP filter and ran a fresh install and everything is working like a charm.

Thanks again guys for the help!

@saablord no problem

yes, solved.

I moved this to “FOG Problems” rather than a “bug” report as there’s nothing I can do to fix this.

As @Wayne-Workman suggested, use the wiki link to help clean up the problems you were seeing.

@rstockham23 I meant reboot once the entire domain process is complete, and then check how long the service takes to startup. (This can be done by monitoring the fog.log by using get-content -wait C:\fog.log from powershell). If there’s an authentication issue again, please post the entire fog.log after you test the reboot.

If the readiness of the client would be sent to the server as unicast (TCP) … * sigh *

@lawrence1997 On this model, have you run through the FOG compatibility tests from the iPXE menu?

@digi One last comment is if you can find the newsid utility on the internet. Then just deploy that with a FOG snapin. That will change the workstations SSID still.

I just checked my current copy of Ghost and that software no longer contains the sid update utility either.

@Tom-Elliott Another example:

You have a lab of 30 computers. 8 of them are Dell, 22 are Lenovo. You have an image that works on the dells, and an image that works on the Lenovos, but not an image for both yet.

You’d make three groups. ONe for the dells, one for the lenovos, and one for all 30 of them.

Use the dell group to apply the Dell image to all the dells. Use the Lenovo group to apply the Lenovo image to all the Lenovos. Use the bigger classroom group to apply Active Directory settings, Snapin Settings, Printer Settings, and whatever else.

Another example:
You have a building with 500 computers. 250 of them are Dell Optiplex 7010 models. The rest are other models. For this, you could have two or more groups. One group for all Optiplex 7010 models, and one group called “Blah-blah-Building” for every computer in the building. You’d use the building group to deploy updates for things like Chrome, and you’d use the model-specific group to do mass re-imaging when that time comes.

@jjacobs Thanks for the help!!!

This morning, I checked a new time, reboot the machine, and I got the same error in the log.

Remark, when I change the status of the “Reboot host on hostname changes and AD changes even if users are logged in?” check box, the Host Product Key is blanked.

@Quazz said in GIT Update not working?:

@Joe-Schmitt It was in permissive for OP and did not work, though 😕

If it was really in permissive mode and still not working, then it’s not an issue with SELinux. That older article on CentOS 7 is incorrect.

@george1421 I just changed search scope to subtree and below and magically I was able to login with domain user ID (no domain name is needed). I can’t thank you enough for your support. Thank you!!!