@dylan123 FYI, we use the 1663 adapters as well. The way I do this in my environment is I manually added a registration for each of my surface nics (I have two of them). So, when I go to image a Surface, I search for one of my mac addresses for my adapters, change the pertinent information (name, image, etc). Then, I set a deploy task to that client. From there, I can go through the steps of swapping keyboards/usb adapter (@george1421 I know I could use a powered USB hub, but I just don’t).

You could also set up a capture the same way, just choose Capture instead of deploy from the Basic tasks section.

Below are the steps that I wrote up for my environment that does work with imaging Surfaces:

1. Search FOG hosts for the Surface MAC address for the Ethernet adapter you are using.
2. Rename the host to the desired name and save changes.
3. Hold down the Volume UP button, press the power button, then release the power button. When you see the Surface logo appear center screen, release the Volume UP button.
4. In BIOS : Select Security. Under Secure Boot, change configuration, select None, click OK. Under Trusted Platform Module, change Enable TPM-Change to Off. Select Boot Config. Verify that all items are selected. Select Exit. Click Restart while holding down the Volume DOWN.
5. When the red bar shows up, release the Volume DOWN button. The device should PXE boot and go to the FOG menu.
6. Select Deploy Image.
7. Select the Surface Pro 4 image.
8. When prompted to unplug your USB NIC, unplug the NIC and plug in a USB Keyboard. Press Enter.
9. Immediately unplug the USB Keyboard and plug back in the USB NIC. YOU WILL ONLY HAVE 5 SECONDS TO ACCOMPLISH
10. Allow the device to image.
11. When the device finishes imaging, do not try to join a wireless network, just hit NEXT. Move the device to the correct OU. Run gpupdate on the device.

YRMV, but this works for us.

@theBiggestRick Internet Explorer is still available in Windows 10. Not necessary to install another browser.

If you click in the “Cortana” search at the bottom left of the task bar, you can just type in Internet Eplorer (Easy Way).

Or, browse to the actual location of Internet Explorer, “C:\Program Files\Internet Explorer\iexplore.exe”

I have run into this same exact issue but on a much smaller scale. I had the bios settings set right with the right boot order and everything.

What I ended up doing was change the BIOS settings anyway to remove PXE boot as an option, boot the computer up once, reboot, enter BIOS and change settings back. After that, it worked like a champ.

On your large scale issue though, it almost seems like a port issue on the switch, or perhaps an DHCP scope option not pointing to the right boot file/boot server.

Also, within the Lenovo BIOS, you may want to see if Secure Boot is enabled. If so, you want to disable it.

In my environment, I use both Surface Pro 3s and Surface Pro 4s.

I use snponly.efi and can image my Surfaces.

I don’t want to assume anything, but have you added the kernel argument for the Surface? Try and add “has_usb_nic=1” (minus the quotes).

I am able to image Surface Pro 3s and 4s, using the Microsoft Surface Ethernet adapter. Now, if only FOS could understand to look for USB nics without forcing it to search for them, that would be great.

I should also mention that since the Surface has only 1 USB port, you will need to have a USB keyboard handy. After you are able to boot to the Ethernet Adapter, it will tell you to unplug the usb nic, plug it back in, and press Enter.

Once you pull it out, plug in your USB Keyboard and hit Enter (once in FOS, the Surface keyboard will not be usable). After hitting Enter, unplug the keyboard and plug the USB adapter back in. You will have roughly 5 seconds to complete these tasks (no joke).

Hope this helps.

@danilopinotti I have noticed that if this is an existing host in fog already, if the Active Directory settings were already applied, both of the passwords will not be in the host. You have to de-select active directory/update/recheck active directory. Then, both password fields will be populated.

Using the FQDN seems to be working. We were able to join a computer to the domain from a different subnet.

Thanks Wayne for your help! Not sure why FOG client is not using our DNS entries, but it worked.

@george1421 I will work on getting something together and post it once complete.

In the meantime, I use Windows DHCP service (not FOG’s DHCP). I simply set my 66 and 67 scope options to my fog server and to snponly.efi ( I still have to manually change this setting as my DHCP server is 2008).

I use the actual Microsoft Surface USB Ethernet adapter. I used to have to add has_usb_nic=1, but that was not needed after a particular RC (I can’t remember which one).

Also as part of the imaging, I do have an issue with using the Type Cover. I can use it in the FOG menu, but when it wants me to disconnect the NIC, plug it back in, and hit Enter, it will not recognize any input from the Type Cover. I simple plug in a USB keyboard, hit enter, then plug my Ethernet adapter back in.

Thanks @Quazz! I did reset using recovery mode and can now log in.

I’m going to do another SVN update to try to resolve the No Disk Passed error. What should the new version be after the upgrade?

@benswan Yes. However, you have to make sure that it is not only stopped, but disabled. If it is not disabled, the service will start back up automatically and then hostnamechanger will do its job.

Not sure if this is your issue, but I know that before you capture your image, you should stop the FOG Service and also set it to Disabled for the startup. Then, use a script that is called after the imaging to start the service again. I use a setupcomplete.cmd myself.

@Scott-Boucher 2 logins is for other processes that we run. You should be able to change that number without issue.

0_1540914509994_unattend.txt

Do you have a mix of 32-bit and 64-bit machines? I’m seeing both references all throughout your unattend file.

I’m in agreement with you that this must be a sysprep issue. This is a very detailed sysprep file. It appears to be doing a lot of different things.

Tell me, what all are you trying to do with the sysprep file? Mine is pretty simple and we image without an issue.

@george1421 I just verified, that line is indeed in my fog.conf file. If you look through the code that is posted on that particular thread, the change has already been made in the code that is posted. But, I did open the file on my server just to verify. Like i said, it is correct.

@george1421 I am. Even though they are way lower. Originally, loads were above 50, now load averages are < 10.

I am on Ubuntu 16.04.4

@george1421 I did the 1.5.0 update before working on the php-fpm stuff, so I should be good there.

After looking in the info.php, I am still seeing the Apache 2.0 handler. I have restarted services and server again just to try to force it, but still no go on getting FPM/FastCGI to show up.

All of the following information is the way our server has always been configured. No changes have been made and it has worked just fine in the past. This is a virtual box, running on Hyper-V with 2 CPUs assigned. The disk is a raid configuration disk, and this FOG server utilizes 1 of the NICs.

@joe-schmitt I have followed the directions provided by @george1421 via link https://forums.fogproject.org/topic/10717/can-php-fpm-make-fog-web-gui-fast/4, as well as updating to 1.5.0 stable.

php-fpm is enabled and I have changed checkin time to 15 minutes. My webui is still slow moving from page to page, as well as imaging still not working.