Timezone the same in fog settings as in php.ini, ntp running.

I do not schedule the wake-up event, direct execution.

In regards to #1 when you installed 1.4.3 you will have the latest kernel. There is no need to download again. That doesn’t address your issue, but know that you have the latest kernel.

I have to ask you, did you make any changes to the linux user called fog this is not the default web ui user account, this is the linux account. That account is an internal account used by the FOG application. I’ve seen people attempt to use/change the password on that linux account and use it for system administration. Doing so will break FOG.

As for your isc-dhcp config file, we really need to see it to identify what’s wrong. There is a great example of what the config file needs to be if you review this document (example 1) : https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@Tom-Elliott Dude everyone here gets it and appreciates what you do! Thanks for everything!

We have several PXE server in the same vlan, three FOG servers and one LanDesk server. We control the access to the PXE using a little daemon in the different FOG servers that update the dnsmasq.conf file with the mac of the computers that have an active task. Is simply but effective.

Historically, this option has been empty and this change may lead to unforeseen side effects.

The “port-security” option is configured enable to avoid the loops and the possibility of using virtual machines without NAT.

@Sunks said in Install problem ubuntu 15.10:

Is it possible to import fog1.2 database to a fog 1.4.x ?

It is, fog will update the db to current. you will need to adjust some settings afterwards. Such as ip, and passwords. Details on these are at the bottom of this article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@george1421 Ok, makes sense, except can’t do a Mac VM, but like you said, that’s not as important than expanding the disk…

Thanks

Are you sysprepping? Was the reference machine previously joined to the domain?

For your images, you should keep them pure - never capture a dirty image because it only causes problems. Pure means NEVER having been on the domain before, and as lean & clean as possible meaning not using old images to make new ones - keep your old images as backups, but build from scratch (installation media) every time - always delete old partitions and remake them, and capture new images.

At my old job, I would include month and year (not day) in my image names.

@grungeman said in Laptops with no integrated NIC any decent solution?:

I found several advice but cant say I found anyone that confirmed its working or any good guide how to make it work.

Maybe I get this wrong?!? Search the forums and wiki and you’ll find a lot of people successfully PXE booting USB NICs! It just depends on the combination of laptop and USB NIC. Quite often you might be lucky and it all works out of the box. If not, get back to us and we try to help.

@FiSi said in Blank page on web interface:

Please tell me it is possible to do that with fog 1.4.3

After all of this, sorry its not possible…

Just kidding, yes Win10 is possible both in legacy (bois) mode and uefi modes. UEFI modes are a little problem but is more on the hardware side than win10. Many new win10 systems are not coming with ethernet ports built in, so this means you must use an approved usb ethernet adapter to make it work.

One last comment. It is possible to setup root with a password as long as the password in the .fogsettings file is the same exact as what you set root’s password to. If you change then you need to rerun the fog installer.

Oh, even simpler, Turn off “Task Reboot” on the hosts client/service settings. Or even better, just turn off the “force” reboot portion from FOG Configuration Page->FOG Settings->FOG Client - Task Reboot->FOG_TASK_FORCE_REBOOT

The hosts won’t magically try to reboot to perform the task in question.

@Tom-Elliott
Thanks Tom! I’ll check that out. That sounds like it could be the issue!

I’m rebuilding the FOG Server today!
Everything is set to go. I backed up all of my images locally. We migrated to a new physical server. So this is a brand new install. I’m going with Debian.

@Sebastian-Roth

Look for setupact.log and setuperr.log files under the following paths:

C:\Windows\Panther
C:\Windows\Panther\UnattendGC
C:\Windows\System32\sysprep\Panther

Additional log from this post: https://forums.fogproject.org/post/96860

But now, i know all sysprep logs … :

cbs.log
setup.etl
session.xml
setupact.log in Windows folder
setupact.log in Windows\Panther folder
setupact.log in Windows\Panther\unattendGC folder
setupapt.dev in Windows\inf
setupapt.offline in Windows\inf
setuperr in Windows\Panther …

@dooleyrd What version of FOG are you using?

Here is the end of the log file for a newly imaged machine this morning which is still working on downloading a snapin. The 10.24.25.165 IP is our main Fog server. The building where the machine resides local nose is at 10.40.25.165. The image itself deployed correctly from the local node.

----------------------------------------- ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Version: 0.11.11 6/20/2017 10:29 AM Client-Info OS: Windows 6/20/2017 10:29 AM Middleware::Authentication Waiting for authentication timeout to pass 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/ssl/srvpublic.crt 6/20/2017 10:29 AM Data::RSA FOG Server CA cert found 6/20/2017 10:29 AM Middleware::Authentication Cert OK 6/20/2017 10:29 AM Middleware::Communication POST URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&authorize&newService 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Authentication Authenticated 6/20/2017 10:29 AM Bus Registering ParseBus in channel Power 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&configure&newService&json 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/management/other/SMALL.png 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/management/index.php?sub=requestClientInfo&mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?clientver&newService&json 6/20/2017 10:29 AM Middleware::Communication URL: http://10.24.25.165/fog/service/getversion.php?newService&json 6/20/2017 10:29 AM Service Creating user agent cache 6/20/2017 10:29 AM Middleware::Response Invalid time 6/20/2017 10:29 AM Middleware::Response No Printers 6/20/2017 10:29 AM Middleware::Response Module is disabled globally on the FOG server 6/20/2017 10:29 AM Service Initializing modules ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM HostnameChanger Checking Hostname 6/20/2017 10:29 AM HostnameChanger Hostname is correct 6/20/2017 10:29 AM HostnameChanger Attempting to join domain 6/20/2017 10:29 AM HostnameChanger Host is already joined to target domain ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 6/20/2017 10:29 AM Client-Info Client Version: 0.11.11 6/20/2017 10:29 AM Client-Info Client OS: Windows 6/20/2017 10:29 AM Client-Info Server Version: 1.3.5 6/20/2017 10:29 AM Middleware::Response Success 6/20/2017 10:29 AM SnapinClient Snapin Found: 6/20/2017 10:29 AM SnapinClient ID: 86642 6/20/2017 10:29 AM SnapinClient Name: MS Office 2013 6/20/2017 10:29 AM SnapinClient Created: 2017-06-20 09:34:39 6/20/2017 10:29 AM SnapinClient Action: 6/20/2017 10:29 AM SnapinClient Pack: False 6/20/2017 10:29 AM SnapinClient Hide: False 6/20/2017 10:29 AM SnapinClient Server: 6/20/2017 10:29 AM SnapinClient TimeOut: 0 6/20/2017 10:29 AM SnapinClient RunWith: cmd.exe 6/20/2017 10:29 AM SnapinClient RunWithArgs: /c 6/20/2017 10:29 AM SnapinClient Args: 6/20/2017 10:29 AM SnapinClient File: Office2013-32.exe 6/20/2017 10:29 AM Middleware::Communication Download: http://10.24.25.165/fog/service/snapins.file.php?mac=98:90:96:BF:CB:76||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=86642

@gnevills said in Fog Client 11.12 not renaming computer/joining domain (Could not authenticate):

To upgrade we installed fog 1.4.0 on a fresh Ubuntu server and then imported the database and upgraded the schema.

If the db came from 1.3 or higher, you must also copy the certs. Info on how to do all of this correctly is here: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@Sebastian-Roth FWIW: If that text exchange can be turned into a sed command in a bash script, its possible to have FOS patch itself each time FOS boots by using a postinit script. Then there would be no need to unpack, patch, and repack the inits each time there is a FOG upgrade.

EDIT: I’m not a sed expert so there may be a cleaner way to do this than escaping every bracket, but in testing it does work to exchange the text mentioned.

sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#\[Ss\]\[Yy\]\[Ss\]\[Tt\]\[Ee\]\[Mm\]#gi" /bin/fog.upload

sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#\[Ss\]\[Yy\]\[Ss\]\[Tt\]\[Ee\]\[Mm\]#gi" /usr/share/fog/lib/funcs.sh

EDIT2: It appears the forum eats the escape characters. Here are the commands in a text file.
[0_1498038914037_sysreserv.txt.bin](Uploading 100%)

EDIT3: WTF I can’t upload a frick’n text file either?
So for manual edits to the sed command, you need to add a back slash (i.e. windows path separator) character in front of each square bracket in the sed command.

EDIT4: Use double backslash…

@Benjamin_D switching to chat for a bit faster turnaround. Look at the talk bubble on the fog forum tool bar.

@Sebastian-Roth

IMAC NOT WORKING

IMAC WORKING

Video here