@Wayne-Workman So far so good. I think this might have done it. Two birds with one stone.

Thanks Wayne. I’ll write on here if it ends up breaking again. 🙂

@THEMCV In that case, I’d like you to reduce max clients to 1 just for troubleshooting, and also increase the snapin timeout for the fog client. Set it to something much larger, something that you know the snapin will get done within. But it would seem the default is unlimited already… Can you upload a client log from an affected system?

EDIT - this is the timeout field:
0_1482959351373_2016-12-28_15-08-19.png

@george1421 This close to release, I’d rather change absolutely nothing at this point.

@THEMCV said in Imaging a computer in UEFI mode doesn't add it in the boot order in the BIOS:

but when the computer reboots it doesn’t know how to get to Windows.

That sounds like an exit type problem to me.

At my old job, we had Optiplex 7040s, they imaged fine. If memory serves, set the UEFI and BIOS exit types to grub. Do this on the host’s general page via the web interface. If you have a bunch of them, this can also be done via groups.

It could also be that you took the image from a BIOS type machine, and are deploying to UEFI type machines. In this case, you need to make sure the reference machine is setup exactly like the target machines are firmware settings wise.

If you’re using the default script, I believe it looks for /dev/sda, which nvme drives aren’t.

You’ll need to alter the script to a more universal version, I believe there’s a thread where some people were working on that a bit.

Any news on this. Would love to buy a shirt or 10

Cool, thanks. 🙂

@Wayne-Workman My point isn’t about people’s “mentalities” just rather the direct facts.

People who are working to create a postdownloadscript that would like logging to be included in some form should be thinking of these things. They’re ultimately in full control of the process, which would also include logging/reporting if that’s what they so need.

While you’re correct that snapins and snapinpacks have the “logging” built in, that’s not to say a postdownload script cannot. The idea of postdownload scripts is to give the person creating it FULL control. What you do with it is completely up to YOU. How you approach logging is up to you. What that script will do is up to, you guessed it, YOU.

Just because it’s not something others may be thinking about does not mean it’s a failure in the “system” itself.

@Tom-Elliott Awesome, thanks!

@george1421 Yeah, our names have one letter in front of the SN. Easy to get them mixed up.

Maybe it’s best to call it a day on it and just accept that I’ve got a good imaging solution limited by third party software.

Next job I’ll get it perfect. 🙂

@Sebastian-Roth
yes, i want to say that i correct it in the post

@Tom-Elliott Great! 🙂 Thank you!

@Tom-Elliott I am an idiot, I totally misread 3000M.

I have no clue where I got 3MB.

Sorry Tom. Thank you. 🙂

This makes things a lot easier.

I made some more, I think, significant approaches to URL testing tonight that should help limit CPU intensity.

21 had some better methods as well, but it was far from perfect. I doubt it’s perfect now too, but it certainly seems a lot better from what I could see.

I agree with you that it works wonderfully well with postdownloadscripts,
Thanks to the scripts provided by the forum community. Thanks to them.

But we must look for a bit before we find the existence of this functionality.

Many people will turn to OPSI because it is better indicated in the documentation and it is native in the application.

http://www.opsi.org/en

I always love Fog because it’s very light.

Thanks to the Fog team

@Wayne-Workman I will give that a shot. Thank you!