@george1421 Ok thanks for your reply. In the past i already did some research and found the arch 7 flags.
I will check out the uuid and come back with results. Thanks.
@george1421 Ok thanks for your reply. In the past i already did some research and found the arch 7 flags.
I will check out the uuid and come back with results. Thanks.
I have already a long time a problem with my DHCP on all clients (EEETop ASUS ASUSPRO A41GAR) .
My DHCP config is this:
class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
#filename "ipxe.efi";
filename "snponly.efi";
}
The system EEETop ASUS ASUSPRO A41GART needs to use snponly.efi and the system EEETop ASUS E1600WK needs to use ipxe.efi.
All the other system can also use ipxe.efi.
I have also tried other efi files but there is not any file which works for all the system.
When this happens my collegue ask me to change the dhcp settings and restarting the dhcp service, but when i’m a day off they have problem to image such system who needs snponly.efi
How can i solve this problem?
@kamburta said in LDAP plugin:
PHP Fatal error: Uncaught TypeError: ldap_unbind(): Argument #1 ($ldap) must be of type resource, null given in
ldap is enabled in php.
I have the same problem when installing the same version.
Did anyone resolve this issue?
@tom-elliott Many thanks!! I used now the internal ip address of the AD server … This was the whole problem.
A vaild domain name here did not work.
Normally this AD server is reachable with this fqdn YYYY.XXXX.com (it’s not the real domain). I can’t type public this domain here for security reasons.
I can now login with users from my AD into FOG.
@george1421 sorry for my delay. Weekend between…
TechnischeDienst is a OU.
My AD browser is already in advanced mode. What you mean with the FOG admin group??