@ckasdf I can share my DELL experiences, the 2-in-1 do NOT have Ethernet port and a generic Amazon dongle did NOT work. However the 2-in-1 has “recommended DELL made Ethernet dongle” which was detected by the UEFI and network boot was possible. So I would look for (Microsoft Surface tablets, Lenovo Carbon X1 laptops, etc) recommended dongle (which will be expensive, I paid $50 for the DELL one) and I bet one would exist which then will be recognized by the device UEFI. In summary: generic dongle IMHO doesn’t work for these non-Ethernet integrated devices.

Same here; except my computer names start with lab-xxxxx

<ComputerName>lab-*</ComputerName>

Works like a charm!

@ckasdf @george1421 guys I must also share with you that getting the expensive dongle wasn’t the end of the line for me In a mixed environment (as was my case) meaning one has legacy PXE laptops and the newer iPXE machines the tftp server needs to know which image file name to serve back the the client based on a bare metal architecture ID, and that must occur at the DHCP level, which of course only Windows 2016 supports lol

So doing the USB stick automatically solves that problem since the human knows which is which (architecture wise that is) and would pick the correct stick to boot from

@Psycholiquid I did see it in your script but I have NEVER put it in \panther just the \sysprep as you posted your command so maybe your habit saved you from facing my “challenges” lol

Hi guys,

I’m posting here as a long time FOG user and although this isn’t FOG specific thing I am using the collective expertise accumulated around FOG user base to seek Windows advice.

We’ve observed this anomaly with ANY sysprepped windows 10 image where sysprep was used with an answer file. I am deliberate in making that clear because the issue doesn’t manifest itself if one uses the stand alone sysprep method where you have to answer by hand the interview questions after a re-seal/generalize without an answer file.

So back to the issue; once the image has been reselaed then any future user will get stuck with moving blue dots upon any kind of start menu search. The only fix is to copy c:\users\Administrator\AppData\Local\Packages\windows.immersivecontrolpanel_cw5n1h2txyewy to the profile of the user in question. Of course that must be done for every user that would use that machine - you can see how crazy that is.

Domain join or workgroup – no difference. It happens with local users so this isn’t the GPO thing some are talking about as a potential culprit.

Has anyone encountered this and if so what’s the remedy? Thank you all!

@imagingmaster21 Thanks - I don’t get any files replaced or indicated as an anomaly when using sfc. This isn’t an anomaly caused by some corruption, it is replicated 100% of the time using a clean install and going into audit mode straight on the first boot.

I am astonished how nobody is actually using sysprep from a clean ISO boot and ctrl-shift-f3 since those who claim to be “using” sysprep do not confirm this issue yet this is a FOG forum. If one is using FOG then sysprep and audit mode is a must? I may be missing something of course.

The MDT method does not manifest this issue, sure but then that requires changing to a whole another animal. There’s a reason why I love fog!

@obeh said in Fog imaging problem:

latitude 7400

7400 does not have integrated Ethernet, I’ve had my share of crap with these. You MUST use the $50 bucks DELL sold USB-C to Ethernet dongle, not some cheap USB-to-Ethernet or else all kinds of weird unexplained stuff happens.

Are you using the DELL USB-C dongle?

Has there been any development on the ability to boot into one’s custom WinPE ISO on a UEFI system?

Thank you
Boyan

@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

@Derek-Newbold You’re correct, the ps1 is called from C:\Windows\Setup\Scripts\SetupComplete.cmd but since it is a power shell script it can not be pasted into the bat file, so I use powershell.exe -executionpolicy bypass -file “C:\Windows\Setup\Scripts\expandhdd.ps1”

As for partition numbers, this was a trial and error process, the disk only has 2 partitions, windows reserved and the OS so that is how it came about.

I do agree that if your OOBE bombs out due to disk space issues then my suggestion won’t work, the HDD expansion happens downstream

@obeh said in Fog imaging problem:

latitude 7400

7400 does not have integrated Ethernet, I’ve had my share of crap with these. You MUST use the $50 bucks DELL sold USB-C to Ethernet dongle, not some cheap USB-to-Ethernet or else all kinds of weird unexplained stuff happens.

Are you using the DELL USB-C dongle?

@Derek-Newbold I’ve had HDD expansion issues using FOG’s native feature for years and even though it maybe fixed by now here’s what I’ve used.

I have a “last boot” script as part of the sysprep and there the HDD happens. Simple power shell script to expand it to maximum physical size possible:

$size = (Get-PartitionSupportedSize -DiskNumber 0 -PartitionNumber 2)
Resize-Partition -DiskNumber 0 -PartitionNumber 2 -Size $size.SizeMax

@mpatel as others have mentioned here - speed is the key; we’re in an identical situation, all sites connect to HQ via VPN but then all sites have Gig Internet so imaging machines at the remote sites has never been an issue, you just talk the end user over the phone to his F12 and that’s that (FOG job must be submitted ahead of time of course).

@ckasdf @george1421 guys I must also share with you that getting the expensive dongle wasn’t the end of the line for me In a mixed environment (as was my case) meaning one has legacy PXE laptops and the newer iPXE machines the tftp server needs to know which image file name to serve back the the client based on a bare metal architecture ID, and that must occur at the DHCP level, which of course only Windows 2016 supports lol

So doing the USB stick automatically solves that problem since the human knows which is which (architecture wise that is) and would pick the correct stick to boot from

@ckasdf I can share my DELL experiences, the 2-in-1 do NOT have Ethernet port and a generic Amazon dongle did NOT work. However the 2-in-1 has “recommended DELL made Ethernet dongle” which was detected by the UEFI and network boot was possible. So I would look for (Microsoft Surface tablets, Lenovo Carbon X1 laptops, etc) recommended dongle (which will be expensive, I paid $50 for the DELL one) and I bet one would exist which then will be recognized by the device UEFI. In summary: generic dongle IMHO doesn’t work for these non-Ethernet integrated devices.

I agree with @Sebastian-Roth - a new install runs, in fact just recently I asked the same exact question just to be sure before I undertake a move since I’ve seen some prior issues but the discussion put that to rest, Ubuntu 18.04.1 LTS installs just fine: