Posts made by ArchFan

[quote=“d4rk3, post: 37526, member: 23583”]Specific MAC’s, sorry…tedious I know, but you only have to enter them once and then update the policy as needed.[/quote]

I’ve found the policies section you’re referring to and I’m going to try to test the second method I suggested this week. I would think one could create a new policy called something like ‘EFI iPXE booting’, set the ‘Condition’ to ‘MAC Address’, ‘Operator’ to ‘Equals’, and create a ‘value’ for each MAC OUI assigned to Apple, using the ‘append wildcard’ option for each option and ‘OR’, not ‘AND’, then specifying the correct option 66 and 67. We’ll see how it goes

[quote=“d4rk3, post: 37496, member: 23583”]On our Server 2012 R2 DHCP Server I set up a policy for EFI boot files for matching MAC addresses of our UEFI-only PXE boot stations. It works great :)[/quote]

Are you using the specific MAC addresses of each individual Apple host in your organization in said policy, or just the prefix of the MAC address (OUI) where the manufacturer is Apple? The first method sounds tedious, which is why I ask. If you can apply the policy to those with an OUI matching Apple’s using regex that would be awesome. Here: [url]http://standards.ieee.org/develop/regauth/oui/public.html[/url] when searching for Apple lists the OUIs that belong to Apple. Can you tell me where to find this option in 2012 R2?

[quote=“Tom Elliott, post: 37318, member: 7271”]You all are aware, you can also use the svn *pxe files to attempt to do what you’re trying to do? All it would require is some user class redirections in the dhcp server to tell the systems what file to download. Specifically, you’ll want to use the snp.efi or ipxe.efi files.[/quote]

Tom, I haven’t yet been able to find a way to do what you’re suggesting with Microsoft DHCP, although I’ve seen directions and examples when using FOG for DHCP, thus-far it’s a no-go if you’re using Windows Server for DHCP. Even then, I don’t see a way around the physical boot media unless you re-bless the Mac using the legacy boot flag. I was able to boot from the *.efi files when using the boot CD without re-blessing, but not without. I believe that’s why someone else created a netboot image for iPXE - so that they could netboot from Mac Server which then pointed to the FOG server. Just my experience

[quote=“Raff, post: 37317, member: 298”]If you have your dhcp setup correctly with the address of your fog server, all you had to do was burn [URL=‘http://boot.ipxe.org/ipxe.iso’][U][COLOR=#0066cc]http://boot.ipxe.org/ipxe.iso[/COLOR][/U][/URL][/quote]

While this worked for some of our Macs, we had others that wouldn’t boot from their pre-built iso - at least the version they had on the website at the time, which was fixed by the method I explained. I assume the rom-o-matic site is more up-to-date, but I don’t know

I didn’t have luck with usb booting iPXE media, but I didn’t spend much time on it. I’ve successfully used the ROM-o-matic site to build an iPXE ISO which I burned to CD and booted from. I haven’t found a Mac it doesn’t work on yet and I’ve tried quite a few ranging in age from 2006 to 2010.

Here’s how I did it and the method that works for me - I’m not saying it’s 100% correct or the only way to do it. There was talk on another forum about creating a netboot image containing iPXE somehow, but I haven’t looked into it.
[LIST=1]
[]Go to [url]https://rom-o-matic.eu/[/url]
[]Choose the ‘Advanced’ option
[]Choose the desired output format - I chose ISO, but you may want to try the .usb - I’ve never tried it
[]I left the NIC options set to default ‘all-drivers’ for compatibility - don’t know if it’s necessary or not
[]Under the configuration options, choose the options listed here: [url]http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe[/url] - you want to check all options from the rom-o-matic page except for those on the Building_undionly.kpxe page with the “//” preceding them
[]In the ‘Embedded script’ box, paste the custom iPXE script shown on the Building_undionly.kpxe page, remembering to edit the IP to reflect that of your FOG server.
[]Leave the rest of the options as-is, and click ‘Proceed’
[]It will then generate the iPXE media in the requested format and download it to your local machine.
[]Burn or copy the generated file to its intended media as you would via any image - likely ‘dd’ or similar
[]Insert the media into the Mac you wish to image and boot from it using the ‘Option’ key or ‘C’ key
[/LIST]

Have you ever had FOG running in this configuration, or is this a first attempt?

Thiago, have you looked into Puppet? The options are endless. [url]http://puppetlabs.com/[/url]

Thanks for all your hard work Tom. I’ll see what I can figure out. [URL=‘http://ipxe.org/howto/msdhcp’]Here[/URL] is a how-to for an older version of Microsoft DHCP server that looks like it describes how to do the same think as your isc-dhcp link - I haven’t tried it myself. DHCP option 93 can do architecture detection too, so that may be useful: [url]http://technet.microsoft.com/en-us/library/cc725614(v=ws.10).aspx[/url]

How often do you plan on imaging them? We have a lab of Latitude 3847’s that will only boot with undionly.kpxe.INTEL, not undionly.kpxe, but we have other devices that won’t boot using undionly.kpxe.INTEL. What I did to get the 3847’s imaged for the year was to move the undionly.kpxe file to undionly.kpxe.0 as a backup, then create a symbolic link from the desired boot file (undionly.kpxe.INTEL) to undionly.kpxe, like below:
mv /tftpboot/undionly.kpxe{,.0}
ln -s /tftpboot/undionly.kpxe.INTEL undionly.kpxe

This way all I had to do was ssh into the FOG server, but avoided altering the DHCP options. Then to reverse it, I just ran:
rm /tftpboot/undionly.kpxe
mv /tftpboot/undionly.kpxe.0 /tftpboot/undionly.kpxe

If nothing else, it’s a quick way to test if the change in files breaks booting for other devices

If your legacy devices have the UEFI option though, and both those and the tablets will boot from either the ipxe.efi or snponly.efi file, that’s preferable, IMO

Eric, I don’t believe there’s currently a way to boot both unless you disable UEFI on those machines and use the same undionly.kpxe or whatever *.*pxe file as you’re using for the legacy devices. Given the context here: [url]http://fogproject.org/forum/threads/uefi-pxe-booting.10149/[/url] I believe it’s something Tom is working on. Once snponly.efi is fully Apple compatible, we’ll be wanting the same feature, as our other devices are all legacy, but the Apples won’t PXE boot without extra steps

I had a few ideas for additions/modifications to FOG. I suggested a few in another thread, but their correct place is here, plus I have an additional few.

With regards to the Full Registration option, if possible:
[LIST]
[]Where it asks the yes/no questions, like joining the domain, it accepts input of other characters other than y/n. Is there any way to have FOG only accept y/n and if anything else is entered, prompt again, this time entering y/n? It would avoid having to shut down and restart the registration if you accidentally enter the wrong key
[]By default, the answer to the full registration questions is ‘no’ - is there any way to add an option in the web interface to change the defaults? For example, every machine we image gets joined to the domain - I know that can be done with groups, but it would be nice to be able to just hit enter when doing the registration
[/LIST]
[LIST]
[]Provide an option in the web interface to disable the host pinging that happens by default when using the ‘host management’ menu. Just in an attempt to speed up loading of the host listing
[]Add a dedicated host hardware inventory tab. From what I’ve seen, the only way to view the hardware configuration is on a per-host basis from the ‘host management’ menu. It would be nice to be able to sort and filter all hosts based on hardware configuration.
[/LIST]

Tom,
I had a few ideas for Full Registration option, if possible:

[LIST]
[]Where it asks the yes/no questions, like joining the domain, it accepts input of other characters other than y/n. Is there any way to have FOG only accept y/n and if anything else is entered, prompt again, this time entering y/n? It would avoid having to shut down and restart the registration if you accidentally enter the wrong key
[]By default, the answer to the full registration questions is ‘no’ - is there any way to add an option in the web interface to change the defaults? For example, every machine we image gets joined to the domain - I know that can be done with groups, but it would be nice to be able to just hit enter when doing the registration
[/LIST]

[quote=“x23piracy, post: 33663, member: 3982”]Hi,

install subversion and get the trunk the right way…
[url]http://fogproject.org/forum/threads/ad-integration-on-new-fog-1-1-2.11128/#post-33016[/url]

When a SVN checkout is finished it displays the SVN Version:
[IMG]http://i.imgur.com/WWduiVV.png[/IMG]

Regards X23[/quote]

IIRC, I believe doing a ‘cd’ to the trunk directory and then typing ‘svn info’ will also show the revision.

Hopefully I’m not reposting a known issue, but I ran into this yesterday on FOG 1.0.1 (Ubuntu 13.04)

[SIZE=3][FONT=verdana][COLOR=#222222]The name format we use to register hosts (via Full Registration) is beyond the character number limit in some cases. FOG attempts to truncate the name when beyond the permitted length. When this happens, it gives a message something to the effect of ‘unable to append co.txt’ - I can get the exact message next time I’m at work if it helps. I assume the truncating is what’s failing, as the registration then halts completely and doesn’t register keypresses, etc. To do anything, you have to shut the machine down, boot to FOG again, but then registration succeeds the second time around - using the original too-long name. I know the ‘smart’ solution is probably to change to a shorter naming scheme, but I was hoping there would be something else that could be done[/COLOR][/FONT][/SIZE]

[quote=“Tom Elliott, post: 26556, member: 7271”]I’ve already tried testing it all. While I could add all of the needed elements to the download scripts, I haven’t been able to figure out a good method to force MAC’s to actually Network Boot and allow image Uploads through FOG. So for right now it’s on hold. If you know how to get all of that working, please share and I’ll be more than happy to try getting it all working.[/quote]

I was able to upload and download NTFS Windows 7 images to/from a Mac before using one of the methods below, but not natively. Unfortunately those are the only ways I’ve figured out as I don’t understand the cause of the issue or possess any coding skills. I don’t understand why booting from an iPXE iso from their website works, yet FOG uses iPXE and they won’t boot from that. Are you still chainloading from PXE to iPXE? That’s the only thing I can figure, but I know you had reasons for doing it the way you did.

1. get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
   2)get a Mac install disc compatible with the machine, boot from it, and re-bless the disk using the command “bless --mount /Volumes/Macintosh\ /HD/ --setBoot --legacy --verbose”. The legacy argument seems to force the machine to use some type of legacy BIOS emulation. Reboot, then the machine will boot from FOG as many times as you’d like - I don’t know whether this will persist once the machine is reimaged or not.

Tom, do you think you could get HFS/HFS+ working? I think the info you need is all here - if you need more, just let me know

[url]http://www.fogproject.org/forum/threads/latest-fog-0-33b.6476/page-65#post-24721[/url]

I did it at one point, but not with any of the revisions within the past month. Verify that the FogMulticastManager service is running - mine would do the same thing with the partclone screen until Tom helped me out with that step. If it’s not running, do a ‘sudo service FogMulticastManager start’ - that should start the service

[quote=“Tom Elliott, post: 23426, member: 7271”]As I don’t have any Mac’s in my possession, it will likely be a little while, unless you can give what the output of the command: [code]blkid -po udev <partitionnumber>[/code] for each of the partitions on the system (especially a freshly installed system) it’ll probably be a little bit.

While I have made sure to have the partclone.hfsp binary available, and also included the hfs file system support in the kernel, I don’t know what to check for to get the MPS/MPA imaging types to use the proper binary.[/quote]

Tom, I’m not sure whether this is exactly what you were looking for or not, but if not, let me know. Apparently Mac OS doesn’t have the blkid command, so I booted from a linux live cd to get the info. The machine was a MacBook 1,1, freshly imaged with 10.6.8 using DeployStudio.

elementary@elementary:~$ sudo blkid -po udev /dev/sda
ID_PART_TABLE_TYPE=gpt

elementary@elementary:~$ sudo blkid -po udev /dev/sda1
ID_FS_LABEL=EFI
ID_FS_LABEL_ENC=EFI
ID_FS_UUID=70D6-1701
ID_FS_UUID_ENC=70D6-1701
ID_FS_VERSION=FAT32
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_NAME=EFI\x20System\x20Partition
ID_PART_ENTRY_UUID=62f42160-c44f-48e3-94ab-ba3acef0e71f
ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=40
ID_PART_ENTRY_SIZE=409600
ID_PART_ENTRY_DISK=8:0

elementary@elementary:~$ sudo blkid -po udev /dev/sda3
ID_FS_UUID=7e9cb753-bf5c-343c-8dad-cd086af5164b
ID_FS_UUID_ENC=7e9cb753-bf5c-343c-8dad-cd086af5164b
ID_FS_LABEL=Macintosh_HD
ID_FS_LABEL_ENC=Macintosh\x20HD
ID_FS_TYPE=hfsplus
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_NAME=DS_DEV_DISK_X
ID_PART_ENTRY_UUID=a954672e-850a-4493-b852-ff139b5e6002
ID_PART_ENTRY_TYPE=48465300-0000-11aa-aa11-00306543ecac
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=409640
ID_PART_ENTRY_SIZE=116538416
ID_PART_ENTRY_DISK=8:0

The bigger issue, unless I misunderstand you, is that you’re talking about making the filesystems work so that machines can be imaged using Mac OS and its HFS filesystems. What I intended to post initially was that Macs won’t boot at all from any version of FOG, 0.33b included (at least without doing the steps listed below). I assume it has something to do with EFI and PXE. I’ve found 2 ways to boot from FOG as-is

1. get the iPXE image from their site, burn to CD or copy to flash drive, then boot from the newly created iPXE media. Then FOG is found and booted from without further interaction. The con is that to boot from FOG again, you have to use the CD/Flash drive each time.
   2)get a Mac install disc compatible with the machine, boot from it, and re-bless the disk using the command “bless --mount /Volumes/Macintosh\ /HD/ --setBoot --legacy --verbose”. The legacy argument seems to force the machine to use some type of legacy BIOS emulation. Reboot, then the machine will boot from FOG as many times as you’d like - I don’t know whether this will persist once the machine is reimaged or not.

[quote=“Tom Elliott, post: 23631, member: 7271”]I don’t know any more

I’ve since changed it to one required file.

/var/www/{fog,html/fog}/commons/config.php

The other config.php just tells the FOG<SERVICENAME> files to point to the main config.php file.[/quote]

Thanks Tom, didn’t realize it had changed - I was referring to the 2 mentioned [URL=‘http://www.fogproject.org/wiki/index.php/Template:Updating_config_files_for_non-empty_MySQL_root_password’]here[/URL]. I’ll try the fix for the other issue. Thanks

[quote=“BigMan99211, post: 23619, member: 21932”]What has changed since version 1256, that would stop “Full Host Registration…” from running? It worked fine 2 days ago, now it’s just bypassing and trying to boot to the hard drive…[/quote]

I have the same issue, except that any time I choose anything from the iPXE menu, it boots to HDD regardless. I thought it was just me, so I was going to try a fresh install. I didn’t customize any of the configs, etc other than adding the MYSQL passwords to the 2 required files