I spent a few days and tried all this. And it still does not work. Our old imaging solution was Ghost. I pulled a image off of that and made some modifications to it for FOG and pulled it with these recommended settings and it didn’t work. But if you image with Ghost it works perfect for Bitlocker via GP. I compared the volume/partition settings and everything is exactly the same.
Any ideas? @Wayne-Workman
@wayne-workman
That make sense. I just captured it with the settings in the screenshot. I will see how it goes. If its no good I’ll change it to 9 or 11.
@wayne-workman
Would that cause it to get stuck on 'resizing file system?
I have BitLocker turned off on the machine I am pulling the image from. I have it go through group policy after imaging. Are these settings right below:
What are the best practices for building a image with FOG for Windows 7, what settings do you select. I seem some people say you select Sing Re-sizable or Multiple not re-sizable. The machines using the image will be using BitLocker Encryption.
@ale-com Did you try disabling the Security Chip? Also is there a virtualization option in the BIOS settings? You can try to enable that also and it may work. Do you have the argument set in your FOG Config to allow USB NIC?
I originally had my DHCP file working for UEFI Machines, but would not work for Legacy machines. I changed this to recommended ones on the Wiki Example 2 and now neither UEFI or Legacy will work. When I boot any machine it will get stuck trying to start IPv4. Here is my DHCP file:
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name "xxxxxx";
#option domain-name-servers x.x.x.x;
default-lease-time 600;
max-lease-time 7200;
# Use this to enble / disable dynamic dns updates globally.
#ddns-update-style none;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server x.x.x.x;
authoritative;
# A slightly different configuration for an internal subnet.
subnet x.x.x.x netmask x.x.x.x {
option subnet-mask x.x.x.x;
range dynamic-bootp x.x.x.x x.x.x.x;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers x.x.x.x;
option routers x.x.x.x;
class "UEFI-32-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
filename "i386-efi/ipxe.efi";
}
class "UEFI-32-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
filename "i386-efi/ipxe.efi";
}
class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
filename "snponly.efi";
}
class "UEFI-64-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
filename "ipxe.efi";
}
class "UEFI-64-3" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
filename "ipxe.efi";
}
class "Legacy" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
filename "undionly.kkpxe";
}
}
Any ideas?
@Sebastian-Roth
@Wayne-Workman
I had to change it to the snponly.efi file for this to work. Seems to work fine with machines that support uefi bios.
So I know I have to change the #option 67 option bootfile-name to the ones we are trying, but in my dhcp file screenshot I attached do I also have to change it in the class’s file names as well. I am guessing yes, but I want to check with you.
@sebastian-roth
@Wayne-Workman
So I see that you suggest changing the pxe binary to one of these:
snp.efi, snponly.efi, intel.efi, realtek.efi
Which one should I use for mine, I have all of these available to use. I guess I would just change it in my dhcpd file and run the FOG Installer again?
I have multiple machines that are requiring the usb-ethernet adapter (have this issue) and ones that have an ethernet port (currently no issue).
@imagingmaster21
@Sebastian-Roth
Also I am using uefi BIOS settings on this. I am able to register other machines fine.
@wayne-workman
@Sebastian-Roth
Also what do you mean by the ignore list?
@wayne-workman
I tried doing it with just the USB-Ethernet Adapter and tried pushing a capture task out to it and it gets stuck at ‘int.xz…ok’. I then tried it with both of the MAC address in host registration and still the same result. If I cancel the tasks I am still able to get to the FOG Menu.
@wayne-workman
So should I give it the WiFi MAC or the MAC of the USB to Ethernet adapter?
@wayne-workman
Ok I see that, but my machine is not even registering as a host. Should I manually create it per its MAC address and give it those settings and try it?
Ok I see that, but my machine is not even registering as a host. Should I manually create it per its MAC address and give it those settings and try it?
I have a Lenovo 13e machine. It does not have a Ethernet port built in. So I am using a USB Adapter. I am trying to register the machine and when I do it freezes up on a black screen. I am not sure what the issue is. Is there some sort of BIOS Setting for this. It is able to reach the FOG menu fine though.
Any ideas?
@george1421
I set mine up on a private network segment. But I tried it out after changing that code and it is working!
@george1421
Ok so lets say the username and password for it are the default fog and password. Is this right for fog.deployimage parameters:
login
params
param mac0 ${net0/mac}
param arch ${arch}
set username fog
set password password
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme