I confirm that now everything works correctly. The error message was on one of the 2 partitions on the hard drive was too full. I will refine the settings and make you a return on the minimum size of available space to deploy.
I confirm that I capture and deploy on the same machine and therefore even hard drive. So no space problem available.
We can pass the inviter in resolve
As soon as I have the information on minimum available space I will add them in this topic
@Warget The FOG Client only works with Registered machines. You CAN install the client on non-registered machines and they will register their information to the FOG server in a pending mode. Once the machine is approved, you can then perform whatever actions were/are needed.
@Wayne-Workman I may have miss-configured or did something incorrectly then; the very first time I tried RAW with this dual-boot system, it did not work.
Currently, the ‘Current Setup’ I stated in the last comment does in-fact work - in my scenario.
I have successfully managed to image two machines, although it takes upwards of eight hours; however, a day to image a machine beats five days of needing to rebuild the system every time something happens to it.
Side notes though:
You need the MacOS disk, or access to the Macintosh partition to enable the bless so you can image it (as per the FOG Wiki)
After you image it, the PXE menu shows back up; return to the main menu, refresh to populate the Macintosh Partition into the menu. Boot into the Macintosh Partition and put in the Windows CD, then run BootCamp. Do not erase the partition, just run the Windows Installer.
Doing this ‘unlocks’ the Windows partition, so you don’t actually have to go into the Windows Installation Disc - just let it boot past that and into Windows.
Configure Windows like you normally would. FOG does not change the hostname on this side of the partition, so make sure you change that when and if you are putting the computer on the domain.
Beyond that, it works. Ain’t perfect, but it is about 210% better than what I was doing before - even with the additional side stuff you have to do before and after the image hits.
@Nicolas-Bricet I’m not sure if you are still following this thread but all known os x binding issues have been resolved and tested as of v0.11.4. (We finally got testing environment in place for us to test this).
I will be marking this thread as solved, if you still have issues let me know and I’ll re-open it.
@melvinpaz Ok, this is a Mac client you are having problems with. Please tell us exactly which Mac you have (serial number!). The modifications you made are correct as far as I see.
I am wondering why it is saying "Could not open net1". Are there two network cards in this client. Possibly wireless? Although I am pretty sure iPXE does not provide any wireless drivers. We need more information on the hardware (exact Mac model / serial number) to be able to help you.
LOL, Apple and its proprietary way of doing things. Simple explanation, netboot is not pxe boot. OS X is very picky about netboot. The efi iPxe file first must be named boot.efi as well as match the architecture of the machine that is booting (for you thats 64 bit) secondly not all ethernet or wifi adapters will be visible to iPxe after handoff. DHCP must point to that file as well as the boot file also.
I have lots of experience with imaging Macs with FOG. We do about 1500 or more a year.
Basically you have a few options but I will line out what we do. When I create an image, on the “master” machine I create the smallest partition possible. In that partition I add the folders:
After that I add the 64 or 32 bit ipxe file naming it boot.efi. Again for you thats a 64 bit file
Now on reboot, hold down option and select that partition. If it is able to find your nics and boot to FOG then you are in good shape!!. If it works copy the partition you just created to a usb disk. Now use that to boot your machines. Realize that you can simply select the usb disk in the boot manager and once iPxe loads up pull it out, and use it on another machine (if you are doing multiple machines). Because of limitations in iPxe do not expect a pretty FOG Menu. No background picture and such.
If your nics are not visible to the efi iPXE then you will need to use the undionly.kpxe file. That is a lot more tricky!! But if needed I will explain to you!