• RE: "Boot from local drive" menuitem is broken on HP ProLiant BL460c G6 (c7000 blade chasis)

    Since FOG seems to be using SANBOOT for exiting is your HP Server in BIOS (legacy) mode or UEFI. The answer is different based on the mode the server firmware is in.

    For this server, go into the host definition. Lets assume this sever is in bios mode, change the BIOS exit type to GRUB First Hard Drive. Hint: You may need to experiment with the ext types to find the right one that works with your hardware. The rEFInd exit type is for UEFI hardware.

    The other thing I can say (at least for my company) we don’t have servers pxe boot through FOG. When we go to image a physical machine we press the F10 or F12 to bring up the boot manager during the system POST. Then from the boot manager we select PXE boot into FOG. This way we are sure there is no way to accidentally reimage a server. We have a rule that a technician must be in front of the server before it is allowed to be reimaged. If you use this method the hard drive is always defined first in the boot order.

    posted in FOG Problems
  • RE: By 2020, Intel is ending support for legacy/BIOS/non-UEFI

    @loosus456 said in By 2020, Intel is ending support for legacy/BIOS/non-UEFI:

    At least in older Dell firmware (unsure about newer ones), turning on UEFI would remove the PXE-on-wake option

    Ah OK. thats a firmware option inside the firmware. Interesting…

    I know at least in bios mode Dells had an option called PXE boot on next boot cycle. If I remember correctly with Dell’s CCTK you can tell the system boot pxe on the next system boot. That is a one shot function. You could deploy this instruction using CCTK and a FOG snapin.

    posted in General
  • RE: Boot Windows or Linux with FOG?

    @mron said in Boot Windows or Linux with FOG?:

    I want to clarify your answers.

    1. It would be difficult to create a single image that would allow multiple machines to dual boot.
    2. It would be easier to create separate Linux and Windows images and select one for loading from a server.

    Creating a dual boot system requires skill. Can it be done, yes. Knowing both operating systems will help you achieve your goal. FOG can clone this environment once you have it setup. You have 3 different issues.

    1. creating your golden image that both OS that dual boot.
    2. prepairing your golden image for cloning (i.e. syspreping windows)
    3. capturing and deploying with FOG

    As for licensing, fog doesn’t manage licensing at all. Fog does have the ability to assign windows activation key to systems during imaging by using the FOG client that is installed in the target OS. You have to assign the OS key on a host by host. Any application that support unattended installation can be deployed as a FOG snapin. Either way you must comply with all host licensing rules and track them externally to FOG. License counting is an external process to FOG. Remember FOG is an image cloning tool.

    posted in General
  • RE: By 2020, Intel is ending support for legacy/BIOS/non-UEFI

    @loosus456 All newer dells since 2013 support uefi mode, most since 2016 come with uefi enabled. Typically we would reset them back to bios mode for imaging.

    Very interesting, I wasn’t aware that WOL did not work in uefi mode. I know Win10 mucks up WOL quite frequently. If the system is completely powered off (not the fast boot mode) WOL with BIOS mode works. I sure hope they get WOL and UEFI mode working.

    Again thank you for posting the info. Helpfully it helps others that use fog.

    posted in General
  • RE: FOG thinks all servers are a single host.

    @george1421 said in FOG thinks all servers are a single host.:

    What I find strange is why all of your target computers have the same mac address? How is this possible?

    Exactly what I was thinking - I really don’t think this is physically possible within this universe.

    posted in FOG Problems
  • RE: Boot Windows or Linux with FOG?

    @mron said in Boot Windows or Linux with FOG?:

    Is setting up dual boot so far out of the norm that I shouldn’t try it starting with so little experience?

    Just dual boot is pretty trivial. Dual boot being captured and deployed properly with FOG isn’t really supported - it’s never worked right in the past for people and I would not recommend trying it.

    To solve the problem of having Windows or Linux available quickly in your lab of 20 machines though, FOG can probably image those in a half hour if you had a half-decent gig switch to do it on.

    posted in General
  • RE: By 2020, Intel is ending support for legacy/BIOS/non-UEFI

    Thank you for sharing. We’ve all kind of known that UEFI is here to stay and the days of was BIOS interface numbered. But now to put a time line of 2020 on it, its starting to get real. FOG does handle UEFI as well as BIOS modes well. We still see flaky UEFI firmware (hear me Lenovo and HP fix your stuff) that needs to be resolved.
    The hardest parts of transitioning to uefi I’ve seen is:

    1. FOG doesn’t work when secure mode is enabled.
    2. You can’t just use any random network adapter for PXE booting. The network adapter HAS to be supported by the UEFI firmware to PXE boot. This is in opposition to BIOS where almost any random network adapter has a built in ROM that supports PXE booting.

    Today in my company we have 2 base images for Win10. We have one for BIOS and one for UEFI systems. All systems purchased in the last 3 years now get the UEFI image, with the BIOS only allocated to the older systems that don’t do UEFI mode very well.

    posted in General
  • RE: FOG thinks all servers are a single host.

    First I would say, make sure you upgrade to the latest RC10.

    I don’t think that is your problem, but the devs will request you do that anyway so they can help.

    What I find strange is why all of your target computers have the same mac address? How is this possible?

    1. What kind of servers are we talking about here?
    2. What OS are you running?
    3. Are these physical servers or virtual?
    4. If these are windows servers, was the master image ever connected to AD before it was captured?

    There is something going on here beyond what you posted.

    posted in FOG Problems
  • RE: WIM files and FOG

    @dhruvin-t Your plan sounds solid. As we discussed yesterday you can either have the unattend.xml file connect the computer to AD or you can have the fog client connect the target computer to AD.

    In my case I let the unattend.xml file do it. The reason is our AD is a bit complex. So all of our computers don’t go into just one OU. The OU is dynamically calculated based on the subnet where the computer is being installed to, what the image type is (office, vs lab), what type of device it is tablet, laptop, desktop, server. All of that info is calculated to produce the OU and computer name. All of this magic is done in a FOG post install script (what you haven’t done yet) and then the product of the calculations are used to update the unattend.xml script.

    Here is one on setting up for driver injection, it is Dell centric. It CAN be used for other system too.

    This one here is a bit more advanced. The interesting points are the sed script to change the host name and OU by patching the unattend.xml file during the post install script.

    Some other of my tutorials you might want to read is:
    PXE booting into the MDT ISO image(that iso that we copied from the MDT server to your VM Host can be pxe booted from FOG)

    posted in Windows Problems
  • RE: Boot Windows or Linux with FOG?

    @mron Not having much experience with either will be a problem for you.

    There was a thread last week where the user was installing Windows 10 and Ubuntu 16.04 on the same system dual booting with a UEFI bases system. And then imaging with FOG: https://forums.fogproject.org/topic/11054/dual-images-windows-10-and-ubuntu-16-with-uefi

    So it is possible, he even outlines the order he installed the OS’ to create this system.

    Is it possible to create a dual boot system, yes. Can you clone it to more computers, yes. It is complicated to setup, mostly yes. Its getting both Windows and linux to live happily on the same hardware. Once that is done, FOG can duplicate it.

    posted in General

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.