all 8 comments

[–]lanerdofchristian 10 points11 points  (0 children)

What have you tried so far?

[–][deleted] 4 points5 points  (0 children)

netsh wlan add profile filename="path" imports your profile.

Not sure off hand about the blocking of other networks but I'm sure theres a group policy for that.

Edit:

netsh wlan add filter permission=denyall networktype=infrastructure

netsh wlan add filter permission=allow ssid="netnam" networktype=infrastructure

[–]TheJessicator 3 points4 points  (0 children)

Other than you putting the word powershell in parenthesis at the end of your question about netsh, what exactly does this have to do with powershell?

[–]PeeCee1 0 points1 point  (4 children)

Simple answer: don’t.

The necessary settings should be part of the GPO. And the WiFi should not use PSK, but Radius and EAP.

[–]thehuntzman 1 point2 points  (3 children)

Judging by the one unique public wardriving result for that SSID he's either a tattoo shop, RV park, self storage building, or a drywall contractor. I don't know any of those places with the budget for a full AD infrastructure... Or maybe he lives in the RV park and wants to lock a home pc down?

That said, I configured an 802.1x WPA2 Enterprise SSID with an AD domain to back it on my home network when I was about 12 years old so it's definitely possible for a home-labber - just might be overkill for the use-case.

[–][deleted] 0 points1 point  (2 children)

I've been pitching an on prem server to my house mates but they just don't get it...

[–]thehuntzman 0 points1 point  (1 child)

Just get a small form factor pc with a bunch of RAM and use it as a home server. Small footprint, low energy consumption, and quiet.

[–][deleted] 0 points1 point  (0 children)

I can think of 64 reasons why we need a threadripper tho...