Posts made by alh

HELP: I cannot mark answer as solving the problem!

That did the trick. Thanks a lot for the speedy reply.

Server

• FOG Version: 1.4.4
• OS: Debian 9 Stretch

Client

• Service Version: N/A
• OS: N/A

Description

Since upgrading to 1.4.4 we experience the following error if we boot into FOG-iPXE and choose the option Deploy Image. After asking for username and password the iPXE environment quits with error 2e022001 and the following error message:

params: command not found
Could not boot: Exec format error (http://ipxe.org/2e022001)

Deploying via a Basic Task works fine.

Any ideas?

@Tom-Elliott we already had FOG_TASK_FORCE_REBOOT set but to no effect. I will try disabling it completely.
Btw. I cannot mark answers of others as correct…

We solved by doing the following:

On the FOG-Server install Winbind:

sudo apt-get install -y winbind libnss-winbind

Edit the Samba config:

# /etc/samba/smb.conf

[global]
    ...
    workgroup = <domain/workgroup>
    ...
    wins server = <ipofyourwinsserver>
    ...

Edit the nsswitch config:

# /etc/nsswitch.conf

hosts: files dns wins

Reboot your server.

On the Windows 7 clients we had to add the following firewall rule:

netsh advfirewall firewall add rule name="FOG Service" dir=in action=allow remoteip=<ipofyourFOGserver> protocol=tcp localport=445

That worked for us.

Server

• FOG Version: 1.4.0
• OS: Debian Jessie

Client

• Service Version: 0.11.12
• OS: Windows 7

Description

We would like to add imaging tasks to a group of clients and then take a walk through the building and reboot into FOG to trigger them.

However, the moment we deploy an imaging tasks our users are prompted to reboot their machines and we can also observe that our Windows-VMs are forcefully rebooted.

Is there a possibility to “schedule” imaging tasks but to execute them manually? A kind of silent queue?

So if I change the settings of a group, this change is applied to all members of the group overwriting the settings received through “earlier” group memberships?

In FOG it is possible to add a host to different groups. How are conflicts handled and resolved (e. g. conflicting AD information)?

Maybe also this link helps in setting up MS DHCP correctly:

ipxe.org/howto/msdhcp

Actually when looking at the source of ipxescript it doesn’t prompt conflicting information but when the option next-server (for whatever reason) is not set:

:nextservercheck
isset ${proxydhcp/next-server} && set next-server ${proxydhcp/next-server} ||
isset ${next-server} && goto netboot || goto setserv

:setserv
echo -n Please enter tftp server: && read next-server && goto netboot || goto setserv

To me it is not clear why at this stage (after we booted from the undionly.kpxe and therefore already found our desired boot server) one does not simply hard-code the IP of the FOG server here during installation?

https://svn.code.sf.net/p/freeghost/code/trunk/src/ipxe/src/ipxescript

Nope, not for me:

Copied that. Maybe just me being used to have an indication if an option/password is set. So for me there is no way to know if the user is Mobile/QIA only from the Web-GUI, is there?

Server: Ubuntu 16.04 LTS
FOG: 1.3.5

When adding a user to FOG the password and type are not shown in the GUI. They are however stored in the database.

We had a similar effect when using PXE chaining. I believe the issue occurs when undionly.kpxe hands over to the “normal” FOG boot image. So the DHCP server initially hands out the correct boot image and the client is instructed by “undionly.kpxe” to boot “http://IPofFOGserver/fog/service/ipxe/boot.php?mac=${net0/mac}”. But then DHCP sends again “undionly.kpxe” as boot image and you have your conflict.

We solved it by compiling undionly.kpxe ourselves which is really easy. After downloading the source create a file, e. g. fog.ipxe with the following content:

#!ipxe

dhcp
chain http://IPofFOGserver/fog/service/ipxe/boot.php?mac=${net0/mac}

Then you need to compile the file like this: make bin/undionly.kpxe EMBED=fog.ipxe.

That makes sure that the DHCP parameters regarding boot image are ignored. Works perfectly for us and we got rid of entering the IP manually.

@Wayne-Workman I send you the mail address.

Regarding our little issue I added to firewall rules to our Win7 clients:

• Allow incoming ICMPv4
• Allow incoming for FOGService

I can ping the clients by hostname from the FOG server but they still show up as Connection timed out. in the host list.
And isn’t port 445 already used by a lot of system services like Netlogon, File and Printer Sharing, Remote Service Management, etc.?

OK, so the status icon is a mere ping to the host -> copied that.

By port 445 being allowed on the Windows clients you mean outgoing connection. That means I do not need to allow any incoming connections anymore, right?

Wiki: We, the German Literature Archive (http://www.dla-marbach.de), would be willing to help in updating the wiki. We are introducing FOG now and document everything for ourselves anyway. However, I could not find a register button on the wiki page.

Server

• FOG Version: 1.3.5
• OS: Ubuntu 16.04 LTS

Client

• Service Version: 0.11.11
• OS: Windows 7

Description

After installation all hosts were marked with a red exclamation mark with the error message: “no such device or address”. We tried to solve this by adding WINS-resolution and hostnames are now resolved properly on the server “getent hosts hostname”.

However, we now in FOG see a new error message “connection timed out”. We tried to adjust the Windows firewall following this guide: https://wiki.fogproject.org/wiki/index.php/Client_Setup#Firewall_Exceptions but it seems to be outdated since “C:\Program Files\FOG\FOGServiceConfig.exe” does not exist anymore. For which of the following EXEs do I need to add a firewall exception or is there another cause for this issue?

• FOGService.exe
• FOGTray.exe
• FOGUpdateHelper.exe
• FOGUpdateWaiter.exe
• FOGUserService.exe

Thanks for your help!

Update: our (hardware) XP-clients seem to work just fine, even without the FOG Client Service.