Posts made by need2

I am happy to say that as of at least the FOG release on 7/24/2015, FOG installs and runs fine on Debian 8 (Jessie). Even the issue of the TFTP service not starting right after rebooting the server is resolved (by whom, I can’t say, but I know it is gone).

I have tested FOG and Debian 8 installations on existing FOG installations running on Debian 7, and on a fresh Debian 8 installation. If you are upgrading a Debian 7 installation, you will need to rerun your FOG installer (from a current GIT pull) after the Debian 7-8 upgrade is complete AND you have rebooted your server. If you have ANY software that is showing as “not upgraded” in apt-get, then your upgrade is not complete.

I can vouch for the GIT method being easy. Just git the files, then run the installer. It should automatically put you on the development branch, which is the one that gets all of Tom’s current changes.

I should buy you a beer.

My two cents, I would suggest Debian or Fedora, and using Hyper-V instead of VirtualBox. Also ensure your drives on the server are fast, and/or your RAID array is properly set up for fast sequential reads. And if you have an AV on the host, make sure it is told to leave your VHD files alone.

Ubiquiti can use some interesting ports for their controller communication, but I wouldn’t think they would impede PXE. Any chance that you can access their configuration, or fire up wireshark?

Yeah I really would love to find a way to package something into FOG as well. Unfortunately a lot of current UEFI systems I’ve been working with seem to really hate on the methods that are used to load the extra PXE data onto an existing DHCP Server’s response.

I know 1.3.0 is coming around the corner, but an actual ETA, that I do not know. If you can, I would suggest making a backup of your FOG server, then updating to the latest SVN. Then test if everything works well for you. I have been using the SVN for quite a while and haven’t had any major issues, but there are always things that could go wrong during development.

I’m fairly certain there was a bug with 8/8.1 in FOG 1.2.0. It is working fine in the latest SVN, but I suggest caution if you use FOG in production, since the SVN is the development branch. Bugs happen.

Oh but of course.

Which type of imaging options did you select?

I finally have all of our licenses in order, so I should be able to push forward with creating the new DHCP as early as next week. Thank you everyone for your input.

Also ensure your 7020s are on the latest BIOS release. I have seen a number of PXE issues in Dell systems that are on early editions of their BIOS, especially in 3020, 7020, and 9020s.

Given some unforeseen circumstance, I really doubt Secure Boot will ever be supported. UEFI support technically exists, it just requires customization for each network.

I was working on UEFI boot for a while before other projects came up. The result I came up against was that you either need to have a Linux DHCP or a Windows Server 2012R2 with DHCP present on the network. You could then configure the DHCP to serve different boot file names depending on detected architecture.

If nobody else does the documentation for the Windows Server configuration before I complete my current projects, I will put it into the Wiki.

Windows 8/8.1/10 do not require UEFI/Secure Boot. They just strongly suggest it. Installed all three on systems incapable of UEFI and they worked fine.

That being said, finding new systems without their OS installed in UEFI mode is near impossible, so it is still a good thing to work out.

Make sure you have fully updated your Surface Pro 3 prior to imaging. There have been significant changes to its UEFI BIOS of the past couple of months, even specifically impacting network boot.

The network boot requirements really depend on whether you are running a Linux network environment or a Windows network environment. If you have a Windows network environment, you have to have a 2012R2 DHCP.

You should try again with svn 3400+. Changes were made to partition handling.

TRIM has to do with drive maintenance, not its out-of-os read or write time.

I would say no. Everything is really stable in the trunk right now. That being said, back up anything critical if FOG is in production for you.

From what I can tell FOG had a bug a few revisions ago that caused issues with Windows 8.1+ imaging. Would mess up/not capture the EFI partition. But that should be resolved in the trunk now.