Posts made by Nicolas Bricet

Thank you for your answer. The current client he works well on dernieère version of Mac OS X (El Capitan) or should also expect a future version of the client?

@Jbob Yes

I tried to restart the client by:
sudo launchctl unload -w /Library/LaunchDaemons/org.freeghost.daemon.plist
sudo launchctl load -w /Library/LaunchDaemons/org.freeghost.daemon.plist

After a few seconds it detects that the machine must incorporate the active directory but on reboot nothing was done

Should we make specific settings for Imac for integrating machines into Active Direcory?

By testing manually on my Imac I did aps worries to reach the area with the same information entered in the FOG interface (domain login + password + authorized way of “OU”)

Yes the command is allowed if users are connected.

The computer restarts well but the computer does not integrate in the Active Directory and after it reboots every three minutes because it fails to incorporate the machine.

I am sure that this domain account is working to integrate computers and I can not find LOG could explain to me where the error occurred.

Hello,

I have a concern for my Imac integrate into my Active Directory with the SVN version 7827.

My machines rename well but integration with Active Direcrory not done. The computer detects that he must do well and restarts but nothing happens.

------------------------------------------------------------------------------^M
--------------------------------Authentication--------------------------------^M
------------------------------------------------------------------------------^M
 25/05/2016 11:03 Client-Info Version: 0.10.6^M
 25/05/2016 11:03 Client-Info OS:      Mac^M
 25/05/2016 11:03 Middleware::Authentication Waiting for authentication timeout to pass^M
 25/05/2016 11:05 Middleware::Communication Download: http://@IP/fog/management/other/ssl/srvpublic.crt^M
 25/05/2016 11:05 Data::RSA FOG Server CA cert found^M
 25/05/2016 11:05 Middleware::Authentication Cert OK^M
 25/05/2016 11:05 Middleware::Communication POST URL: http://@IP/fog/management/index.php?sub=requestClientInfo&authorize&newService^M
 25/05/2016 11:05 Middleware::Response Success^M

------------------------------------------------------------------------------^M
--------------------------------HostnameChanger-------------------------------^M
------------------------------------------------------------------------------^M
 25/05/2016 11:05 Client-Info Client Version: 0.10.6^M
 25/05/2016 11:05 Client-Info Client OS:      Mac^M
 25/05/2016 11:05 Client-Info Server Version: 7827^M
 25/05/2016 11:05 Middleware::Response Success^M
 25/05/2016 11:05 HostnameChanger Checking Hostname^M
 25/05/2016 11:05 HostnameChanger Hostname is correct^M
 25/05/2016 11:05 Power Creating shutdown command in 60 seconds^M
 25/05/2016 11:05 Bus {
  "self": true,
  "channel": "Power",
  "data": "{\n  \"action\": \"request\",\n  \"period\": 60,\n  \"options\": 2,\n  \"command\": \"-r +0 \\\"Host joined to Active Directory, restart required\\\"\",\n  \"message\": \"This computer needs to perform maintenance.\"\n}"

Do you have an idea to solve this problem?

I thank you in advance.
Cordially.

Hello,

Attached file in debug mode.

Best regards.

Hello,

In fact both Subnet is two different DHCP file tests.

I actually just tested different files (ipxe.efi; snp.efi; snponly.efi: intel.efi: relatek.efi) on two different network cards (Intel, Atheros).
I always get the following problem: it hangs on “” Initializing devices … ".

For information, the computer is an HP Elite 7500.

There currently I raised on “ipxe.efi” and I’ll see if it is launched unlocks itself as Quazz proposes.

Thank you in advance for your assistance.

Hello,

Here is my problem, although currently I manage to PXE boot in UEFI on the following machines:

• Macbook
• Tablet Surface PRO 3

By cons on HP computers, trying several solutions, I block on “initializing devices” and nothing happens.
Here are the configurations I tested:

Thanks in advance.
Best regards.

We found where the problem came when we use the DHCP file it works without problems :

subnet *.*.*.0 netmask 255.255.255.0
{
    option routers               *.*.*.254;
    option broadcast-address     *.*.*.255;
    option subnet-mask           255.255.255.0;
    option domain-name           "****************";
    option domain-name-servers   *.*.*.*, *.*.*.*;
    
    next-server                  *.*.*.*;  
    filename                     "undionly.kpxe";
}

 host surface-pro
    {
        hardware ethernet            *.*.*.*.*.*;
        fixed-address                *.*.*.*;
		next-server                  *.*.*.*;
		filename                     "ipxe.efi";
    }

By cons with this configuration that does not start the PXE:

subnet *.*.*.0 netmask 255.255.255.0
{
    option routers               *.*.*.254;
    option broadcast-address     *.*.*.255;
    option subnet-mask           255.255.255.0;
    option domain-name           "****************";
    option domain-name-servers   *.*.*.*, *.*.*.*;
    
    next-server                  *.*.*.*;
    option tftp-server-name      "*.*.*.*";
    
    filename                     "undionly.kpxe";
   option bootfile-name         "undionly.kpxe";
}

 host surface-pro
    {
        hardware ethernet            *.*.*.*.*.*;
        fixed-address                *.*.*.*;
		next-server                  *.*.*.*;
		filename                     "ipxe.efi";
    }

This option raises concerns: option bootfile-name “undionly.kpxe”;

Can we rule out this option for the DHCP level not he runs because we have left this option in the configuration file? Or add a “class”?

Thank you if you can help me.

Hello,

When I start networking is what happens:
Checking Media Presence …
Media Present …
Start PXE over IPv4.
The last stage lasts a few tenths of seconds and we do not see what happens or an error message and then it executes the next step:
Start PXE over IPv6

So one wonders which could pose problems in the DHCP level and options for we see u’il well retrieves its IP address.

Thanks for your help.
Best regards.

Hello,

The first tests were a common DHCP server at our university, we had problems getting these two phases:

 DHCPDISCOVER (IP address of the customer request)
 DHCPOFFER (server response That Sends the IP address)

We therefore performed some tests on a local DHCP server on Ubuntu server (ISC-DHCP-server).

We now cover much we both phases “DHCPDISCOVER” and “DHCPOFFER” but it hangs at boot file “ipxe.efi” it does not appear we FOG menu and this happens on IPv6

Thanking you.

Hello,

We have a problem for PXE boot on the SURFACE PRO 3, for this we use a Microsoft Ethernet adapter (Model: 1663).

When that we start on the network we see in the DHCP logs the first two phases:

• DHCPDISCOVER (IP address of the client request)
• DHCPOFFER (server response that sends the IP address)

But the DHCPREQUEST phase (Customer must accept the IP address) is not established.

Is it in the DHCP file to a specific configuration for it to work?

Because under the Windows system and the DHCPREQUEST DHCPPACK phases happens correctly.

Thanking you in advance.
Best regards.

Hello

First, thank you to everyone.
PXE works on my two types of machinery by putting this in the DHCP with the ALT key or the “N” key :

subnet ... {
    authoritative;
    ...
}

class "Apple-Intel-Netboot" {
    match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
    option dhcp-parameter-request-list 1,3,17,43,60;
    if (option dhcp-message-type = 8) {
        option vendor-class-identifier "AAPLBSDPC";
        if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) {
            # BSDP List
            option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47;
        }
        elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) {
            # BSDP Select
            option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31;
            filename "ipxe.efi";
            next-server *.*.*.*;
        }
    }
}

This configuration was not enough:

class "Apple-Intel-Netboot" {
    match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
    option dhcp-parameter-request-list 1,3,17,43,60;
    if (option dhcp-message-type = 1) {
        option vendor-class-identifier "AAPLBSDPC/i386";
        option vendor-encapsulated-options 08:04:81:00:00:67;
    }
    filename "ipxe.efi";
    next-server x.x.x.x;
}

For Macbook snp.efi and / or ipxe.efi work, should you use one over the other?

Thanks for your help.
See you soon.

Nicolas.

Mod edited to properly display information rather than having random smilies show up throughout

@Tom-Elliott

Hello,

Yes I have tested ipxe.efi files snp.efi, snponly.efi, ipxe_i386.efi, snp_i386.efi, snponly_i386.efi without success.

Does not it come from a problem with the DHCP?

@Wayne-Workman

Hello,

I tested ipxe.efi and ipxe_i386.efi without success.

Best regards

Hello,

Here are the references of Apple computers :

Here is the information of the two network cards:

MacBook PRO :
Broadcom 57765-B0
57765-v1.37, 0x7287af41

IMac :
Broadcom 57765-B0
57765-v1.37, 0x7cfcc847

Hello,

We currently have the SVN version (4543) of FOG 1.2.0

The DHCP server is remote, this is the configuration of the network and the configuration of the machine causing problems

In your opinion should we proceed with DHCP side or modifications on the client machine?

Thanks for your help.

It works by simulating the PXE via a USB key, this loads the DHCP configuration with the filename and nex-server and then gets the FOG menu. This manipulation works on Macbook.

Here is the information of the two network cards:

MacBook PRO :
Broadcom 57765-B0
57765-v1.37, 0x7287af41

IMac :
Broadcom 57765-B0
57765-v1.37, 0x7cfcc847

Hello,

Currently in trying to boot PXE on the Imac and Macbook PRO.

Thanks to the method contained in IPXE image Clonezilla it works for Macbook PRO, but we have a problem with the Imac blocking the message 'initialising devices "that would be linked to the driver (BMC 57765-B0).

If you have ideas to solve this problem?

We also tried the method contained on this link:
https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

We executed this command (bless --netboot --booter tftp: // <your-tftp-server-ip> /ipxe.efi) on a client, the command goes well and we see that although we contact the file ipxe.efi the FOG server. So we are restarting the client Netboot but nothing happens (the earth rotates without launching anything)

Should we make further adjustments to the MacOS client level or the FOG server for this to work properly?

Thanks for your help.
Best regards.

Nicolas