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?
Best posts made by alh
-
RE: Group Management: Handling Conflicts
Latest posts made by alh
-
RE: FOG-iPXE: Deploy Image fails with error 2e022001
HELP: I cannot mark answer as solving the problem!
-
RE: FOG-iPXE: Deploy Image fails with error 2e022001
That did the trick. Thanks a lot for the speedy reply.
-
FOG-iPXE: Deploy Image fails with error 2e022001
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 error2e022001
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?
-
RE: Deploy imaging tasks but only run them manually?
@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… -
RE: Host list: connection timed out
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.
-
Deploy imaging tasks but only run them manually?
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?
-
RE: Group Management: Handling Conflicts
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?
-
Group Management: Handling Conflicts
In FOG it is possible to add a host to different groups. How are conflicts handled and resolved (e. g. conflicting AD information)?
-
RE: Updated Fog server now have to manually enter tftp server address
Maybe also this link helps in setting up MS DHCP correctly:
-
RE: Updated Fog server now have to manually enter tftp server address
Actually when looking at the source of
ipxescript
it doesn’t prompt conflicting information but when the optionnext-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