@ckasdf said in USB Boot UEFI client into FOG menu (easy way):
and found that it actually was recognized by UEFI and FOG,
The key is for the uefi bios to have a driver for the network adapter. FOG will most likely support the hardware because of linux. Actually uefi is also a high level OS akin to linux with drivers and such. But to make the OS fit nicely in NVFLASH memory the hardware manufacturer doesn’t support every flavor of network adapter. So you have to be particular on which network adapter is pxe bootable. But great job locating something that works well
@ckasdf said in Issue joining domain & activating Windows after deployment:
sysprep /generalize /oobe /shutdown /unattend:c:\unattend.xml.
I would only place the unattend.xml in the c:\windows\panther directory. That is the first place winsetup looks when it starts, If you define one, as in your case c:\unattend.xml and it finds one in panther first, it will use the panther one over the defined one.
I mentioned this in my reply to Sebastian a few minutes ago, but it seems something I did fixed the primary issue: SetupComplete is now running without needing to log in. However, it ALSO runs at every login, instead of quitting, so there’s still something strange afoot
The execution of setupcomplete.cmd is managed by WinSetup/OOBE. That is the only process that will execute that script. If windows login is executing that script then you have something amiss there.
I’m pretty sure it’s volume media that I’m using, but as asked to Sebastian, do you know a way to check the ISO to confirm that it’s VLK media?
By looking at the cdrom, I don’t think there is a way. I can tell you that oem media will not accept vlk keys and vlk media won’t accept oem keys. Does your boss know if he downloaded the dvd image from the MS VLK site? If you have VLK keys (MAK or KMS) you must have access to the media 2 because they are in the same area on the VLK site.
is a scrubbed copy of the unattend.xml file
Ah, that is why setupcomplete.cmd is running at each login, because you put that in your unattend.xml file. Yeah it doesn’t belong there.
Only WinSetup/OOBE media will call the setupcomplete.cmd.
Just for reference here is a scrubbed version of my unattend.xml file. This is the same one I used for win7 and win10: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7
Sorry for the long delay.
You guys are doing beautifully, I appreciate the work you do!
I just pushed a change to the scripts so that the output of the command checking the disk is not suppressed.
Can you provide the github link to the script(s) that were changed so I can check it out? I also need to figure out how to properly update FOG as new releases come, but haven’t had time till this week to sit down and read. I think I spotted some documentation out there on the subject though, so I’ll try to check that out today.
Would be also great to have that in the reports section of the web UI but I fear we don’t have the time to implement that right now.
Totally understand. That suggestion was more to toss on the list of future idea implementations as time allows. BTW, what language(s) is/are used for this? I’ve been interested in learning some software development. Maybe with time I could contribute back to the project. :)