@Sebastian-Roth Haha no problem! Please let me know if I can do anything. No rush on my part, but without the coding know-how, testing is all I can do! I actually impressed myself by understanding some simple logic in the different php files that make up these plugins. Oh, and some of the API methods. But that’s it lmao

@mitnotromney Thanks for reporting this. This is not you doing something wrong but our installer running into an unexpected situation. Moving this topic to bug reports. Please help us fix this quickly. Run the following commands on your system and post output here: ip -4 route show ip -4 link Thanks!

I just updated, and it was much easier than I originally anticipated. :) Thanks again!

@Sebastian-Roth thx, cp this comand’s and now is works!!! <3 Solved!

@Sebastian-Roth Interesting to know that’s how the image is calculated… In my update I did mention the size has now recovered back after deploying the image to another machine. When I did not get the group multicast to work, I restarted the service on the server, so I think that reset the log file. All entries on it are from after I restarted the service. I’ll retry another multicast via groups next week (time running out on me today) and post the requisite log file after doing that. Having said that, I have run another multicast session (not via groups) and the output follows: [07-19-19 6:30:14 pm] ================================== === ==== ===== ==== === ========= == === == === === ======== ==== == ==== === === ======== ==== == ========= === ==== ==== == ========= === ======== ==== == === === === ======== ==== == ==== === === ========= == === == === === ========== ===== ==== ================================== ===== Free Opensource Ghost ====== ================================== ============ Credits ============= = https://fogproject.org/Credits = ================================== == Released under GPL Version 3 == ================================== [07-19-19 6:30:14 pm] Interface Ready with IP Address: 10.121.77.10 [07-19-19 6:30:14 pm] Interface Ready with IP Address: 127.0.0.1 [07-19-19 6:30:14 pm] Interface Ready with IP Address: 127.0.1.1 [07-19-19 6:30:14 pm] Interface Ready with IP Address: 216.162.61.10 [07-19-19 6:30:14 pm] Interface Ready with IP Address: newfog.cs.local [07-19-19 6:30:14 pm] Interface Ready with IP Address: tu-216-162-61-10.taylor.edu [07-19-19 6:30:14 pm] * Starting MulticastManager Service [07-19-19 6:30:14 pm] * Checking for new items every 10 seconds [07-19-19 6:30:14 pm] * Starting service loop [07-19-19 6:30:15 pm] * No new tasks found (...snipped...) [07-19-19 7:43:45 pm] * No new tasks found [07-19-19 7:43:55 pm] * No new tasks found [07-19-19 7:44:05 pm] | Task ID: 11 Name: 229 is new [07-19-19 7:44:05 pm] | Task ID: 11 Name: 229 image file found, file: /images/20190702_w10_1804_256 [07-19-19 7:44:05 pm] | Task ID: 11 Name: 229 11 clients found [07-19-19 7:44:05 pm] | Task ID: 11 Name: 229 sending on base port 57192 [07-19-19 7:44:05 pm] | Command: /usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 600 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p1.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p2.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p3.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p4.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p5.img; [07-19-19 7:44:05 pm] | Task ID: 11 Name: 229 has started [07-19-19 7:44:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:44:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:44:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:44:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:44:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:45:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:46:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:47:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:48:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:49:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:50:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:04 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:51:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:52:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:53:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:54:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:55:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:56:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:57:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:14 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:58:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:04 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 7:59:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:00:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:01:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:02:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:03:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:04:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:05:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:06:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:24 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:35 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:45 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:07:55 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:08:05 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:08:15 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:08:25 pm] | Task ID: 11 Name: 229 is already running with pid: 20229 [07-19-19 8:08:35 pm] | Task ID: 11 Name: 229 is no longer running [07-19-19 8:08:35 pm] | Task ID: 11 Name: 229 has been killed [07-19-19 8:08:45 pm] | Task ID: 11 Name: 229 is new [07-19-19 8:08:45 pm] | Task ID: 11 Name: 229 image file found, file: /images/20190702_w10_1804_256 [07-19-19 8:08:45 pm] | Task ID: 11 Name: 229 11 clients found [07-19-19 8:08:45 pm] | Task ID: 11 Name: 229 sending on base port 57192 [07-19-19 8:08:45 pm] | Command: /usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 600 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p1.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p2.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p3.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p4.img;/usr/local/sbin/udp-sender --interface eno1 --min-receivers 11 --max-wait 10 --portbase 57192 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/20190702_w10_1804_256/d1p5.img; [07-19-19 8:08:45 pm] | Task ID: 11 Name: 229 has started [07-19-19 8:08:55 pm] | Task ID: 11 Name: 229 has been completed [07-19-19 8:08:55 pm] | Task ID: 11 Name: 229 has been killed [07-19-19 8:08:55 pm] | Task ID: 11 Name: 229 is now completed [07-19-19 8:09:05 pm] * No new tasks found [07-19-19 8:09:15 pm] * No new tasks found (...snipped...) [07-19-19 8:44:05 pm] * No new tasks found [07-19-19 8:44:15 pm] * No new tasks found

@altitudehack Right, I upload a .bat and use the batch snap-in template

Thanks for the information. Relieves some of my worries.

@adamkesy said in FOG 1.5.4 - capture win 10 (1903) - issue: This new value in kernel ramdisk size can be impacted for previous images/hosts somehow? No, this should Not cause an trouble unless you have machines with less that 512 MB RAM which is very unlikely these days…

@cary1102 I had this situation earlier today. After changing the local user account from “Fog” to something non"Fog", the issue went away. I also changed the partition settings to Multiple Partition Image - All Disks (Not Resizable) from Single Disk - Resizable - (1).

@Joe-Gill said in brand new dell latitude 3500: Ding ding ding ding! I need to set my dhcp server settings for UEFI!!! You may want to consider: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

Thanks for the insight! I copied one of my build images to a test-copy, then made two changes. I then ran sysprep /generalize /reboot /unattend and allowed the VM to sysprep and reboot to see what happens. I didn’t capture it to run it through FOG, but I imagine the results will be mirrored once I do. I noticed that your unattend file didn’t contain a reference to SetupComplete. Therefore, I edited unattend.xml to remove the <Component> block that contained <AutoLogon> and <LogonCommands> (within which was contained the reference to SetupComplete.cmd). I moved unattend.xml to the Panther directory at your suggestion. When I ran sysprep, I tested it without defining a file, and sure enough, it picked it up with no problem. After allowing sysprep to do its job, I logged in as the local admin (since I didn’t have FOG to join the domain for me), and no command windows popped up to try running SetupComplete as the local user. SetupComplete didn’t appear in the Startup tab of Task Manager. FOGService was set to Automatic and was Running. In other words, the things that weren’t supposed to be happening no longer were, and the things that were supposed to happen WERE! :)   By the way, slightly on the topic, I know the wiki suggests restarting the computer with a command in SetupComplete after enabling the FOG Client, but Microsoft’s documentation suggests this is a bad idea: Warning You cannot reboot the system and resume running SetupComplete.cmd. You should not reboot the system by adding a command such as shutdown -r. This will put the system in a bad state. My SetupComplete file contains two lines: sc config FOGService start= auto net start FOGService It seems to still restart if needed, so maybe the shutdown line can be removed?   Thanks to @fry_p, @george1421, and @Sebastian-Roth for your contributions in helping me figure out this strange issue!

@george1421 Its working now :) I forgot my options 66 and 67 on that 192.168.5.x scope! Thanks you very much!

@DJGRP Guess we are on the right track here to find out what’s going on here. Which Linux OS do you use on the storage and which on the master node? Run the following command on your storage node and post the output here: find /etc/ -name "fog.conf" -exec grep "DocumentRoot" {} /dev/null \; (make sure you got all the braces and slashes right) File dates (Aug 28 2018) definitely show us that the storage node was not properly installed with 1.5.6.5. Which method do you use? Using git I suppose? Please take a look at the error logs and upload the full log here - you should find it in fogproject/bin/error_logs/fog_error_1.5.6.5.log.

In addition to what @Shad0wguy posted, your golden image should be developed on an isolated network, or at least one that doesn’t have internet access for just that reason. You don’t want windows updates to help you “fix” your system while you are preparing for it. If you are doing this in audit mode, for sure disable the windows update service until just before sysprepping it. I myself use MDT to build the golden image so one of the task sequences is to update the windows updates from our WSUS server and not to use direct internet updates. That way the updates are applied and completed in a known state before MDT exits. We will typically sysprep and capture with FOG right after MDT finishes. But its great you are documenting the problem here and the potential solution. Because if you have the issue there are 100 other folks that will have it in the future. So thank you for helping them out too.

True that, George. I was just surprised, as I had a few different USB-to-Ethernet adapters provided to me at work and none of those would work, and many Google searches solidified the suggestion that there were only a few USB Ethernet chipsets (chip manufacturers, chip-somethings, whatever) which were supported by PXE. The search was made more difficult in that even in the last few years (2016-present) people seem to continue to prefer Legacy booting over UEFI. If I ever decide to get the other device, I’ll let you know how it works so it can also be added to the list, if that’s something you guys are keeping up.

@george1421 thank you for this. I have hit a bit of a snag as I made some network changes on the VM without a snapshot and am experiencing connectivity issues. once I have resolved I will test and advise. 1.I have registered a host manually 2. I have scheculed a debug deploy 3. I will feedback once I have resolved my network issues with step 3-6

@Rivybeast I’ll take a look at this soon!

@imagingmaster21 Thanks for the heads up. I will mark this solved now here. If you see any new issues feel free to call out.

@sysengine1125 What is serving DHCP in your network? A Windows Server? Which version?

@george1421 The weird and suspicious part is that 1.5.5 was last known working version, 1.5.7…I’ll also note that the parrallel behavior has always performed that way, at least for quite some versions now. I could actually transfer a single new captured image to all nodes at the same time and they would all run at their perspective top speeds (I have 4 schools that only have 100Mb connection and the rest are all gigabit. This speed is definitely new though. Note I just manually transfered the file via ftp and the speed was back to normal at another node…then on this node in question and it is indeed a port going bad or the cable itself only allowing a very minimal top speed of 10-15 Mb. This can be closed, but I appreciate the new command.