FOG Client 0.11.12 Released
-
-
Always hiding snapin details is a good choice. In reality people need to look no further than the fog web interface ’ snapin command area for issues with the commands. having details in the logs only really helped fog devs, mods, and testers to more quickly help people because snapin details were built into the logs.
From now on, when we help folks with snapin issues, we need the log and a screen shot of the snapin configuration too - this isn’t much to ask, because before the same details were in the logs.
-
“Renaming a Windows computer and then joining a domain is now 2 times faster
Renaming a Windows computer inside a domain is now 3 times faster”What black magic is this?
Like open source community computing? Why not do it for a good cause?
Use your computer/server for humanitarian projects when it is idle!
https://join.worldcommunitygrid.org?recruiterId=1026912 -
@fry_p The blackest magic.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
-
@x23piracy @fry_p Basically I finally had the time to rework how domain joining / renaming happened to only require 1 reboot to apply all the changes.
-
@joe-schmitt Our new HP machines are working as they should (renaming and joining the domain), but older machines on which we have installed the same new W10 (sysprep) image are not renaming and not joining the domain. What can we do about this? BIOS of the machines have been updated. Machines are f.ex. Dell Optiplex 3010.
-
@josken71 does your windows system have the network drivers for the dell machines? The client doesn’t sound like it’s the problem here as the client is working on the same exact image for the hp machines.
-
@josken71 I think I am having a similar issue, on specific Dell computers (Optiplex 380s for example). Newer Dell computers do not have the issue. After imaging is complete, post sysprep re-enables the FOG Client and reboots the computer; on the troublesome computers the FOG Client never full re-enables. If you log in as local admin and check under services the FOG Client is set to automatic, but not started. If we manually start the service, the computer reboots after a few minutes, joins the domain, and renames the computer as expected.
This is not a problem on newer Dell computers or VMs.
-
@jeffrey-boulais we have seen occurances of this in the past where we had race conditions while starting the service, could you please try to set the service from auto to delayed-auto? will this work? Which version of windows are you using?
How do you deal with the fog client? You need to disable the service before you create the image and you have to enable it again while deploying (setupcomplete.cmd).
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep -
@x23piracy I believe this may have solved our issue; we are still testing. This was for a Windows 10 LTSB image.
-
@jeffrey-boulais there is a LTSB of 2015 and 2016, 2015 is 1511 and 2016 1607 afai remember 1511 still had the autostart problem.
-
@x23piracy That image is on 1607.
