Recent content by Armadillo7237

Glad you figured it out. Those two lines are the only parts that differ for me as well.

Interesting, you're adding key=clear when you're running netsh wlan export, correct? The XML files should not be the same. On the several machines I've tested on, the XML exported with key=clear shows me the plaintext version of my SSID password in the XML file, whereas the standard export shows...

OK, I figured out what the problem *actually* was. When I came into work today, I noticed the machines were hanging on "Connecting" after a fresh install with my NTLite image, just like they were when I first asked my questions. I got so wrapped up in a small portion of the problem, I forgot...

Just tried %WINDIR% again with Machine execution. I made sure to adjust the commands accordingly, and I made sure the .xml profile was added in Machine execution as well. Still not working. Hard-coding the path is the only way I've gotten it to work.

Unattended user account + no improper /S flag is the configuration I'm using right now, which is working (though it's in the User execution). The only difference between that and what I have now is my usage of the absolute path instead of the %WINDIR%. I will try again with %WINDIR% as a sanity...

As you suggested, I was manually creating a user during the Windows install wizard. I'm assuming that's what you mean by out-of-the-box experience in this case. Before, I was creating a user automatically via NTLite.

I changed the file location since that screenshot.

Well, I got it to work. Not really sure why %WINDIR% wasn't working, but manually pointing the netsh command to C:\Windows\Setup\FilesU\Wi-Fi-SC.xml worked. I have been encountering a lot of very frustrating bugs in NTLite so far, from the commands I've entered re-ordering themselves upon...

I see. Removed that and tried again; no difference. I will try out the RunOnce method. Anyway, I realized that sometimes when I compress and reopen my session into an ISO, the order of the commands gets messed up occasionally. Is there a better way to apply my changes to an ISO that doesn't...

Tried removing the quotes entirely, and no difference - still doesn't work. In fact, now I don't have any log output, meaning netsh isn't running at all. If I can't get Post-Install to do what I need, I may look into RunOnce.

Here is the output of ipconfig /all in the OOBE after skipping the network join wizard via the option in Post-Setup: Mod note: Redacted MAC addresses for privacy.

In case it's helpful, here is my Wi-Fi-SC.xml (even though the password is encrypted as alphanumeric gibberish, I've redacted it)

I tried that already, still doesn't work unfortunately. I realized I messed up the order before I took that screenshot, but I did fix it on my end. Originally, I had everything in the "Machine" section up top, but I couldn't get some commands to work, such as powercfg. I have just tried again...

OK. Rebased the installer on the same Windows ISO to fix the BSOD problem. I disabled the automatic user creation. The first thing I'm prompted with is the network menu to sign into a wifi network. I'm not a huge Windows guy, so not sure exactly what to look for in the output of ipconfig /all...

The wifi drivers I'm using for these machines are built-in to Windows. I have some other machines I will need to load drivers for, but I haven't done that yet. My user account I was creating had no abnormal characters besides an underscore. I was skipping "Network configuration" in OOBE, but...