@mwilcox said in Windows 10 Driver and Deployment Question:

So maybe that was the other unsigned driver which caused the hang. I can do more testing tomorrow

If there are any unsigned drivers or any reason why the driver install pops up with a question it will fail the install (probably not something you want to happen at a client’s place). There is a bcd edit command you can turn on in your golden image and then turn off in the setupcomplete file that will accept all drivers signed or not. Usually Dell only ships signed drivers. So I’m a bit surprised at the condition.

With that setup does it install drivers after the deployment while it’s booting up Windows?

Yes, but in the golden image we will typically deploy the Dell WinPE driver pack so the golden image has at least the basis drivers. If you are shipping the hardware with Win10 then most of the basic drivers are already built in.

Would there be a prompt or something somewhere in the FOG GUI that would ask for a activation key before image deploy?

If you are using the load and go approach, you are not registering the computers with FOG. Normally when you do a full registration you could enter the key there. But if you are using the load and go approach then you are not registering the machine with FOG so you have to be a bit more creative. In this case you would create in your post install script a prompt to enter the key value, then take that key and update the unattend.xml file using the fog.updateunattemd. Probably that script is where you would want to stop and ask the FOG installer for the key.

Testing is the key even if you eventually end up with a hybrid of FOG doing everything, except you turn the system on at your facility do a QC check (drivers: yes, activation: yes, etc) then ship it to the customer like you do today. The idea is to eliminate as much hands on stuff you do so you can build more systems faster.

@Sebastian-Roth
Yes class and host are now declarated in groups, not in subnets.
So now, I declare all subnets first and after all groups.
Here is my new dhcpd.conf file:

# dhcpd.conf # ddns-update-style standard; authoritative; #log-facility local7; set vendor-string = option vendor-class-identifier; log (info, option vendor-class-identifier); ############################################## # rajoute pour les telephones IP IFSIC/ISTIC # C'est pour pouvoir utiliser le prise LAN # derriere le telephone dans l'un des reseau ESIR/ISTIC ################################################## option space Tel-Sip; option Tel-Sip.cfg-server-address code 2 = text; option Tel-Sip.contact-rcs code 3 = boolean; class "telephones-ip" { # voir man dhcp-eval match if substring(hardware,1,3) = 00:08:5d; option server.min-lease-time 40; option ntp-servers 129.20.251.1; #option tftp-server-name "129.20.131.108"; option server.vendor-option-space Tel-Sip; option server.boot-unknown-clients true; option Tel-Sip.contact-rcs true; option Tel-Sip.cfg-server-address "ftp://connexio994:xa3SGXZE74@10.21.7.8"; } # sacker un peu les smartphones ... class "android" { match if substring(option host-name,0,7) = "android"; default-lease-time 900 ; max-lease-time 900 ; } class "iPhone" { match if substring(option host-name,0,6) = "iPhone"; default-lease-time 900 ; max-lease-time 900 ; } class "iPad" { match if substring(option host-name,0,4) = "iPad"; default-lease-time 900 ; max-lease-time 900 ; } class "Windows-Phone" { match if substring(option host-name,0,13) = "Windows-Phone"; default-lease-time 900 ; max-lease-time 900 ; } class "Galaxy" { match if substring(option host-name,0,6) = "Galaxy"; default-lease-time 900 ; max-lease-time 900 ; } class "HUAWEI" { match if substring(option host-name,0,6) = "HUAWEI"; default-lease-time 900 ; max-lease-time 900 ; } class "Samsung" { match if substring(option host-name,0,7) = "Samsung"; default-lease-time 900 ; max-lease-time 900 ; } class "Honor" { match if substring(option host-name,0,5) = "Honor"; default-lease-time 900 ; max-lease-time 900 ; } # # machines recevant une IP dynamique dans le vlan2 (lan-free). # include "/etc/dhcp/vip.conf"; subnet 145.55.0.0 netmask 255.255.248.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.7.254 ; option subnet-mask 255.255.248.0 ; default-lease-time 86400 ; max-lease-time 172800 ; pool { allow members of "vip"; range 145.55.7.200 145.55.7.230; } #################################################### # pool d'adresse dynamique reserve aux telephones IP # masque de 255.255.255.240 pour le firewall pool { allow members of "telephones-ip"; range 145.55.0.224 145.55.0.239; } } #subnet 145.55.8.0 netmask 255.255.255.0 { ########################################## #option domain-name-servers 145.55.15.109,145.55.15.106 ; #option domain-name "monuniversite1.fr" ; #option routers 145.55.8.254 ; #option subnet-mask 255.255.255.0 ; #default-lease-time 6000 ; #max-lease-time 12000 ; #group { #} #} subnet 145.55.10.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.10.254 ; option subnet-mask 255.255.255.0 ; default-lease-time 600 ; max-lease-time 1200 ; pool { deny members of "telephones-ip"; range 145.55.10.180 145.55.10.220; next-server 145.55.4.1; #filename "pxelinux.0"; } #################################################### # pool d'adresse dynamique reserve aux telephones IP # testsip pool { allow members of "telephones-ip"; range 145.55.10.224 145.55.10.239; #avec un masque de 255.255.255.240 pour erebus } } subnet 145.55.11.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.11.254 ; option subnet-mask 255.255.255.0 ; default-lease-time 86400 ; max-lease-time 172800 ; range 145.55.11.1 145.55.11.9 ; } subnet 145.55.12.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.12.254 ; option subnet-mask 255.255.255.0 ; default-lease-time 86400 ; max-lease-time 172800 ; # range 145.55.12.101 145.55.12.140 ; #range 145.55.12.100 145.55.12.199 ; } subnet 145.55.13.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.13.254 ; option subnet-mask 255.255.255.0 ; option ntp-servers 129.20.128.22; default-lease-time 3600 ; max-lease-time 3600 ; adaptive-lease-time-threshold 80; min-lease-time 900; range 145.55.13.1 145.55.13.247 ; } subnet 145.55.14.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.14.254 ; option subnet-mask 255.255.255.0 ; option ntp-servers 129.20.128.22; default-lease-time 3600 ; max-lease-time 3600 ; adaptive-lease-time-threshold 80; min-lease-time 900; range 145.55.14.16 145.55.14.253 ; } subnet 145.55.15.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 145.55.15.254 ; option subnet-mask 255.255.255.0 ; default-lease-time 2592000 ; max-lease-time 5184000 ; } subnet 129.20.15.0 netmask 255.255.255.0 { ########################################## option domain-name-servers 145.55.15.109,145.55.15.106 ; option domain-name "monuniversite1.fr" ; option routers 129.20.15.254 ; option subnet-mask 255.255.255.0 ; default-lease-time 2592000 ; max-lease-time 172800 ; # #################################################### # pool d'adresse dynamique reserve aux telephones IP # testsip pool { allow members of "telephones-ip"; range 129.20.15.224 129.20.15.239; #avec un masque de 255.255.255.240 pour erebus } } group { #######################################VLAN2 > FOG ######################################## next-server 145.55.4.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } host admin01 { hardware ethernet 74:e6:e2:d9:dd:cf; fixed-address admin01; option Host-name "admin01";} # host admin02 { hardware ethernet b8:85:84:ac:89:fa; fixed-address admin02; option Host-name "admin02";} # proto windows salles istic .......................................................................... host imp-b42-001 { hardware ethernet 78:e3:b5:fb:31:da; fixed-address imp-b42-001; option Host-name "imp-b42-001";} host imp-b42-002 { hardware ethernet 10:1F:74:47:1E:4E; fixed-address imp-b42-002; option Host-name "imp-b42-002";} # Gateway LORA F.Bodin le 11/12/2019 ##module niusrp host niusrp6 { hardware ethernet 00:80:2f:17:b4:e3; fixed-address niusrp6; option Host-name "niusrp6";} ### Salle machines virtuelles # host virt01m01 { hardware ethernet aa:bb:aa:bb:aa:aa; fixed-address virt01m01; option Host-name "virt01m01";} host virt01m02 { hardware ethernet aa:bb:aa:bb:aa:ab; fixed-address virt01m02; option Host-name "virt01m02";} host w10 { hardware ethernet 9c:8e:99:f5:1a:a9; fixed-address w10; option Host-name "w10";} # marque debut pour dhcp-vm vlan 2, pas touche SVP. # marque fin pour dhcp-vm vlan 2, pas touche SVP. } group { #######################################VLAN2 > COSINUS ######################################## # Groupe pointant vers le pxe du Fog de test option domain-name-servers 145.55.15.109,145.55.15.106; next-server 145.55.4.2; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } # #Machine test cosinus #host centos7-6 { hardware ethernet 52:54:00:b3:30:b5; fixed-address centos7-6; option Host-name "centos7-6";} # VM sur admin11 .................................................................................................................. #host b06-013m01 { hardware ethernet 9c:8e:99:f5:69:2a; fixed-address b06-013m01; option Host-name "b06-013m01";} } group { ###################################### VLAN2 IMPRIMANTES ######################################## host imp-2a-020 { hardware ethernet 00:11:85:FA:28:9A; fixed-address imp-2a-020; option Host-name "imp-2a-020";} # h host d262m03 { hardware ethernet 00:11:43:2C:11:8D; fixed-address d262m03; option Host-name "d262m03";} # gx280 carte acquisition host e114m01 { hardware ethernet 00:13:72:0D:55:B7; fixed-address e114m01; option Host-name "e114m01";} # F Lamarche #host imp-b05-001 { hardware ethernet 00:1f:29:1f:23:c9; fixed-address imp-b05-001; option Host-name "imp-b05-001";} } group { #######################################VLAN2 COMMUT ######################################## # # groupe : commut # host c12eb { hardware ethernet ; fixed-address c12eb; option Host-name "c12eb";} # host c12ea { hardware ethernet ; fixed-address c12ea; option Host-name "c12ea";} # host c12ee { hardware ethernet ; fixed-address c12ee; option Host-name "c12ee";} # host c2ba { hardware ethernet ; fixed-address c2ba; option Host-name "c2ba";} # ................................................................................. host c12dt { hardware ethernet ; fixed-address c12dt; option Host-name "c12dt";} # host c12du { hardware ethernet ; fixed-address c12du; option Host-name "c12du";} # } group { ####################################################VLAN10################################################ # On commente les deux lignes suivantes pour eviter le menu de Fog next-server 145.55.4.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } host arrakis { hardware ethernet 00:23:AE:6A:83:FA; fixed-address arrakis; option Host-name "arrakis";} # Gx360 Gentoo AD host admin11 { hardware ethernet 9c:8e:99:f5:68:ca; fixed-address admin11; option Host-name "admin11";} #linux test 8300 AD ...................................................................................................................... #host miage-dell6 { hardware ethernet 10:65:30:83:5c:4b; fixed-address miage-dell6; option Host-name "miage-dell6";} # # marque debut pour dhcp-vm vlan 10, pas touche SVP. host winrm10 {hardware ethernet 00:11:E2:61:00:03; fixed-address winrm10; option Host-name "winrm10";} # Ajout par dhcp-vm le 22/08/2016 (11:32:32) # marque fin pour dhcp-vm vlan 10, pas touche SVP. } group { ####################################################VLAN11################################################ # marque debut pour dhcp-vm vlan 11, pas touche SVP. host pret13 {hardware ethernet 00:11:E7:61:00:10; fixed-address pret13; option Host-name "pret13";} # Ajout par dhcp-vm le 24/5/2013 (11:21:05) ........................................................................................................... host palme02 { hardware ethernet 00:23:ae:74:66:85; fixed-address palme02; option Host-name "palme02";} # poste asso Palme d193 Maxime Lambert 12006967 } group { ##########################################VLAN12####################################### next-server 145.55.4.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } # ### Salle_i204 # host i204m01 { hardware ethernet 14:b3:1f:19:81:02; fixed-address i204m01; option Host-name "i204m01";} ......................................................................................................... host i204m10 { hardware ethernet 14:b3:1f:19:80:20; fixed-address i204m10; option Host-name "i204m10";} ### Salle_i206 # host i206m01 { hardware ethernet b8:85:84:b9:68:49; fixed-address i206m01; option Host-name "i206m01";} ........................................................................................................... host i206m10 { hardware ethernet b8:85:84:b9:5e:9f; fixed-address i206m10; option Host-name "i206m10";} # ### Salle_i207 # host i207m01 { hardware ethernet 78:ac:c0:b1:aa:f6; fixed-address i207m01; option Host-name "i207m01";} # ............................................................................................................ host i207m22 { hardware ethernet 00:11:43:14:42:11; fixed-address i207m22; option Host-name "i207m22";} # } group { host psyche { hardware ethernet 00:13:72:08:e1:93; fixed-address psyche; option Host-name "psyche";} # # host psyche { hardware ethernet 00:13:72:0D:70:D8; fixed-address psyche; option Host-name "psyche";} # host anubis { hardware ethernet 00:14:22:75:AF:18; fixed-address anubis; option Host-name "anubis";} # } group { ##############################################VLAN15################################################ # next-server 145.55.4.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } # host wifsic1 { hardware ethernet 00:42:68:44:79:18; fixed-address wifsic1; option Host-name "wifsic1";} # h.................................................................................................... host satus {hardware ethernet 78:2B:CB:6D:38:C3; fixed-address satus; option Host-name "satus";} } group { ######################################## VLAN3 Personnels ############################ # On commente les deux lignes suivantes pour eviter le menu de Fog next-server 145.55.4.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } # host ad-istic1 { hardware ethernet 00:15:5d:0f:fb:00; fixed-address ad-istic1; option Host-name "ad-istic1";} ..................................................................................................... host b06-014m01 { hardware ethernet 8c:04:ba:5d:81:cc; fixed-address b06-014m01; option Host-name "b06-014m01";} # portable Samuel Crand 2019-06 host bug { hardware ethernet 9c:8e:99:f5:9c:2e; fixed-address bug; option Host-name "bug";} # HP 8300 } group { ######################################## VLAN3 Personnels > COSINUS############################ # boot cosinus pour 129.20.15 next-server 145.55.4.2; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.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"; } #host d000m02 { hardware ethernet c8:1f:66:aa:26:b2; fixed-address d000m02; option Host-name "d000m02";} #host b42-015m01new {hardware ethernet b8:85:84:b5:ea:9c; fixed-address b42-015m01new;option Host-name "b42-015m01new";} }

@tricyphona Have you tried disabling fast boot in Win 10 and do a full chkdsk before capturing? Is the partition on the client nearly full?

@ArmyHack said in Imaging a domain controller:

Could you explain how to capture a save state system?

This is my words for using FOG to backup your target system and restore it at some future time. FOG is not really intended to be a backup system. It can do it but its not the focus of FOG. If you don’t want fog changing bits in the target system don’t install the fog client on the target computer. Also Sebastian also mentioned to me that there is a setting in FOG Configuration -> FOG Settings -> General Settings called CHANGE HOSTNAME EARLY will also rename the target system during imaging.

If you want to leave the fog client installed on your target computer (for reasons like pushing out applications post OSD), under the Client Settings menu you can configure what the FOG Client software can and can’t do.

@ConJon said in DHCP Booting Fails and enters wrong IP Address:

It does seem to be working now. Thanks!!!

just changing that default.ipxe doesn’t fix the problem. There are a few other places where there is hard coded IP addresses.

in the fog server OS in /opt/fog/.fogsettings file
In the web ui
FOG Configuration -> FOG Settings->Expand All (search for the old IP address)
FOG Storage->Storage Node-> Default

Fix it there and save then back to the FOG Server command prompt and then rerun the fog installer to fix the remaining bits. If you don’t do these steps you will have a painful fog experience.

@eliaspereira Dell uefi firmware and iPXE, not specifically FOG.

The x010 series was the first to support uefi network booting (kind of). They got it right with the x020 series.

@Sebastian-Roth Thank you for all that.

I’m playing with it and got it nearly there by unt-ticking/re-ticking the AD join options in the individual host’s entry, then all my defaults populated nicely. Now have enough to go about tweaking with fog.log as you mention.

Thanks again!

@PBT said in Token.dat missing:

Response Invalid security token

This is the actual error in your case. Please go to the FOG web UI and see if the client is already in the host’s list. You might need to approve it!

If it is in the host list, then do a “Reset Encryption Data” (button in the host’s settings).

@Reuban1219 said in Does FOG still support Windows XP Imaging?:

Other than Single Disk - Resizable option there is three other choices.
a) Multiple Partition Image - Single Disk(Not Resizable)
b)Multiple Partition Image - All Disks(Not Resizable)
c)Raw Image (Sector BY Sector,DD,Slow)
Which of these do I choose?

If you don’t need to deploy the image to a smaller size disk you wanna choose “Multiple Partition Image - Single Disk(Not Resizable)”. Check out the information in the wiki on this: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images

Btw, I have an additional question. Is it okay to capture and deploy image without doing sysprep? Or is it a must to do sysprep?

Sysprep is not needed in general. FOG doesn’t care if you sysprep or not. BUT Windows will need to be syspreped if you capture from one hardware model and deploy to another one being quite different. Good you bring up this point as I have not had that in mind. While I don’t think the hang on the blinking “_” can be caused by deploying to a different hardware as it’s very early in the boot process it’s very likely Windows will give you a blue screen later on in that case.

Update: It works. The file ending was the problem.

@Sebastian-Roth, não me atentei muito para a questão dos scripts. Mas já havia tentado executar um Snapin de script Shel e um .bat utilizando slmgr. Mas no windows o slmgr /ipk e /ato parecem ser inúteis. Vou ver novamente esses tópicos quando eu tiver mais tempo.

@victorykimutai You might share here how you’ve fixed the issues as other users might find it helpful too. Thanks in advance.

I found the smart installer for 11.19 🙂 Now it works on http. We will try to activate https on our server and activate https on the client

Thank you very much, worked like a breeze!

These issues are typically related to how the structure is on the disk and where the data is placed. Its not really a fog issue, but an issue how the reference image placed on the golden image disk. This is important especially if your golden image is constantly recycled as you apply round 2 (through N) updates and applications. The ideal method is to rebuild your golden image every time as you upgrade your golden image.

So how to fix…

Make sure your 😄 drive is the last partition on the disk. This may require you to move or delete the recovery partition. The recovery partition is a non-resizable and sometimes non-movable partition. I also question the value of a recovery partition if you have an imaging solution in place. It is much quicker to just reimage the computer than to try to recover a failed disk. If you have done many updates to your golden image (especially over time) flush out all of your temp files and defragment the hard drive. This will (should) push all of the files towards the beginning of the disk. The idea/goal here would be to move all of the disk data below the size of the disk you will be deploying to. That makes FOG’s disk compression work a bit easier. If you are developing a golden image create that golden image on the smallest disk possible. Its is easier to expand the disk than it is to shrink it. So if you developed your golden image on a 120GB SSD, that image would deploy cleanly to 120GB disks and larger, for example.

@Derek-Newbold FYI I have seen ton of people running FOG in AWS with totally public IP and that works outside of any firewall issues, of course those instances involve people who have access to the local sites DHCP so they can update the tftp option in their scopes with the public IP 🙂

In my case it’s a private IP but I do have access to the networking side of things so sites throughout the organization can boot fine from HQ FOG server.

@obeh What’s the express service code or exact model number? I may have one laying around and would be happy to try it on my end… Thanks

@marc49ca Thanks for your input on this. Though I feel like it’s not related to the OP’s question on VMware Workstation.

The guide I was following to set it up mentioned that FOG wouldn’t capture from UEFI.

This statement is no true in general (as you post it here)! What’s mentioned in that guide is:

One more thing, make sure that Legacy Boot (not UEFI) is enabled on whatever computer you want to capture or deploy. I think FOG supports UEFI already but I haven’t looked into it yet.

This is specific to VirtualBox being used in that tutorial and not caused by FOG but simply an issue within VirtualBox that doesn’t properly PXE boot UEFI VMs. I am not exactly sure if this is still true for the latest version. I don’t think so but maybe. ESXi is not like VMware Workstation is not like VirtualBox.

After building my Win10 image (tried with 1903 and 1910) and getting the same problem I found took a different approach. Build the Windows system, sysprep it. Before booting again, change the system type from UEFI to BIOS (as we’re not booting Windows it won’t matter). Then registered the host and reboot to capture the image.

This hint on using legacy BIOS mode just for capturing might be helpful in the OP’s situation as well! Good point.

It turns out that this was a problem with the Trusted Platform Module. Apparently it didn’t like the new O/S being installed on hardware it had already “signed”. Not being too schooled in how TPM works, I’m making an assumption here, but clearing the TPM after deployment fixed my bootup problem. This can be done in the BIOS, or by letting the system boot from the Hard Drive at the Fog Menu, then running tpm.msc and clearing it there.

@Base2Nathan I’m not asking to be rude but there’s hardly any information to work from.

All fog does from imaging is capture what you tell it to, and deploy where/when you tell it. It’s block level, so there’s nothing fog would be doing in regards to the programs you have installed or removed.