@mashina Can you get select * from history; out of your database?

I’m having a sneaking suspicion the issue is likely part of a rewrite to substaintially make save our save to database functions, that has some repercussions on other things because so much had required things that shouldn’t have bene required.

Similarly, can you provide the exact version?

“Latest working-1.6” is a shifting target. like i’m pretty sure you were not on the latest since I made pushes today so pretty sure the error you are getting is not related to today.

I think this is an issue envolving this kind of nic hardware (Intel I226-V). I opened an issue (18125) where I have some appliances for pfsense, they have got four NICs with this kind of hardware, and we are not getting successfull to deploy an image because it’s not processing authentication, even typíng correct user and password.

Yes, you are right!
I can confirm that it is still functional.
Install clean Windows 11 + drivers + all the updates -> configure windows as you like it -> sysprep -> shutdown -> Image -> Deploy.

Although, I have searched the answer for the main question, to sysprep or not, for years!
What I mean, is that if you sysprep, some of the Windows settings and configuration will be wiped out during the sysprep, so you cannot configure image 100% ready and need some manual steps after the cloned pc (deployed) boots up.
Of course those manual configurations can be automated (by a script or some other way), but still, it would be nice that image can be setup without sysprepping if it is not needed anymore in Win10/11.

I have tested hundreds of PC-s in domain environment without sysprepping - they work flawlessly, no issues with Domain, WSUS or other things, but I am little bit worried, that if some issues arise, e.g some weird errors then I must reinstall all the deployed pc-s with sysprepped images…

Can somebody confirm?

Yes, I understand, that without sysprep, all the PC-s deployed from the same image will be using same SID, but is it bad somehow?
Can someone confirm that for Intune it is also OK?
Domain doesn’t care, WSUS either, but what else might break?

@Tom-Elliott @Tom-Elliott it’s not authentication issue. We don’t have problem when deploying images to other hosts, like PCs and minipcs with just one NiC. But over these Appliances with 4 Nics we got stuck in the authenticon screen even putting correct username and password. Look, we are trying to disable 3 nics in Bios but we can’t . We excluded them to Boot Order and left just the first, but even so, the error persists.1000110829.jpg - I found the issue 16746 about this problem, but it’s happening to us!