@tom-elliotthello,
Excuse me for the long time to do the tests, I don’t have much at the moment for this project.
Here is the photo of the debug (the error message comes up over and over again countless times).

image0000001(1).jpg

@Bristow-0 Has this ever worked before? I remember that others had issues with domain join in a Samba domain. Search the forums for that.

As well you might take a look at the fog-client log (usually in C:\fog.log) and post the relevant part here.

@d2freak82 said in Certificate Nightmare:

on install if I select HTTPS it will not install because of the certificate error.

Even when using the updated SmartInstaller mentioned below?

Where exactly do you see the certificate error? Can you post a screenshot? Possibly it’s something we can/need to fix in the fog-client setup.

@sborgne said in (503) Service unavailable:

Proxy parameters bad config is to be blamed…

Wow, something I would not have thought of right away! Good you found why it fails!

No there are no proxy configuration settings in fog-client. We use simple C# .NET WebClient calls. That seams to be using your system proxy settings. Can you set your systemwide proxy settings to not use the proxy server if connecting to your FOG server?

Thanks @tom-elliott . So, if I understand correctly, I only use the first one and it must not be encrypted, am I right?

@arowana Does your remote site have a server where you can preposition these dependencies files? Remember for windows the script or installer runs as a windows user. The fog client runs these snapins as SYSTEM which has admin rights on the local computer where the snapin is being installed. Your install script can map a drive to a windows file share and copy the files over smb to the target computer. That would be the easiest. If the files were stored at the remote site then it would not impact your metered connection rates. If you used a powershell script to install your application you can use a function similar to curl or wget to download the file from the internet using scripting. You might be able to use FTP too, but I have never tried. You don’t need to specifically download from the FOG server, but you can. If you wanted to download from the FOG server, I would setup a new user on the FOG server that has very limited rights, maybe to read only from the source directory and that is all. I would not use the FOG ftp user because that has more authority than what is needed here.

@jyost said in Roughly half of reimaged devices do not run first run scripts in autounattend.xml after imaging.:

If the renaming/domain join occurs AFTER the final restart I will need to run a powershell script to install our AntiVirus software and also add a domain user account to the Remote Desktop Users group –

You might want to consider deploying this action with a snapin. Snapins will run after all of the other imaging actions are complete.

@AlexPDX Which version of Windows do you use exactly?

We had reports about what sounds similar to what you say not long ago.
https://forums.fogproject.org/topic/15258/windows-10-and-fog-product-key-problem-20h2
https://forums.fogproject.org/topic/15256/win-10-pro-product-key-not-installed-probably

I am still not sure if this is something the fog-client is doing wrong (we just use the slmgr.vbs calls that worked for a long time) or if it’s Windows preventing it from happening.

@nfiglar Typically you would add the command to add the computer to azure ad in the setupcomplete.cmd batch file or in a first run command in the unattend.xml script. At the very least you could create a snapin to deploy a package that joins the target computer to azure AD. dsregcmd /join

@sebastian-roth Sorry for my late response, i use windows 10 build 20H2.
I have tried installing the key with slmgr.vbs manually, that’s not working so i think its a bug in windows…

i have tried finding a old windows 10 build (2004) to try if it works there, but no luck so far…

@sebastian-roth Thank you for your suggestions. My team and I were able to start from scratch with a new Win10 Pro image and we captured/deployed this new revision without issues. There must have been some sort of driver or configuration issue on the actual host image that was causing this.

Thank you for helping me double check that everything in my Fog settings were properly configured.

Merci je testerais cela un de ces jours.

@Navdeeppal While we use PXE boot a lot in FOG I don’t see what your question has to do with the FOG Project?!

@tom-elliott Thank you very much for your assistance and time!

@greg-plamondon That is one of the reasons I set this up, we have some wifi only devices, setting them to default boot to lan just doesn’t work. Also users get confused and or complain about the time it takes for the lan boot. So I set up a custom boot manager and got the best of all worlds.

I did recently accidentally (so sadly not sure how to recreate it) find that the windows boot manager does still have a gui mode. So you could theoretically create this functionality without the use of third party tools. I discovered it when I imaged a computer that had 2 drives. I imaged the nvme in a desktop that had a old spinning drive that still had a windows install on it and windows saw the old spinning drive’s install first and kept booting to that. At some point I had a windows boot menu that showed both windows options. So there is still a way to add custom boot entries to the windows boot manager. Probably a mix of enabling the timeout in bcd bootmgr settings and then adding a custom boot option. So you could theoretically make it so you see an option for straight windows boot and straight fog ipxe.efi file boot. Personally I like using grub, but just wanted to let people know it’s an option someone could try to figure out.

Hello

Did you find the solution, I have the same problem with 3 VM on proxmox :

1 debian fog server, 1 working windows 10 machine (That I have imaged) 1 test machine for deployment (I have the same problem after deployment)

Thanks for any help

@sebastian-roth
Nice one! thanks. I added the VPN MAC address!

@george1421 Scratch that. I was confused about how this works, my apologies.

The Windows 10 installation I used to create my image is using an MBR, aka Legacy boot.

Thanks again for the quick reply.