Difference between revisions of "Windows Wireless Connection Errors accept key when changing wireless controllers"
From MediaArts KB
Line 2: | Line 2: | ||
[[Category:Wireless]] | [[Category:Wireless]] | ||
WLAN Profile for windows 10 that sets connection properties so it won't become disconnected when crossing controllers between buildings | WLAN Profile for windows 10 that sets connection properties so it won't become disconnected when crossing controllers between buildings | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The Wi-Fi-Columbia FacStaff.xml looks like | The Wi-Fi-Columbia FacStaff.xml looks like | ||
Line 56: | Line 39: | ||
</MSM> | </MSM> | ||
</WLANProfile> | </WLANProfile> | ||
+ | |||
+ | </pre> | ||
+ | |||
+ | A bit more digging and WLAN profiles can still be exported from netsh via command line | ||
+ | |||
+ | <pre> | ||
+ | Netsh WLAN export profile name="Columbia FacStaff" key=clear folder="WLAN" | ||
+ | </pre> | ||
+ | |||
+ | This dumps the attached xml to a folder in the root of the users profile called WLAN. This xml can be imported with the following command | ||
+ | |||
+ | <pre> | ||
+ | Netsh WLAN add profile filename="WLAN\Wi-Fi-Columbia FacStaff.xml" | ||
+ | </pre> | ||
+ | |||
+ | We could script netshell delete the existing profile first then import the exported profile | ||
+ | |||
+ | <pre> | ||
+ | |||
+ | Netsh WLAN delete profile name="Columbia FacStaff " | ||
+ | Netsh WLAN add profile filename="WLAN\Wi-Fi-Columbia FacStaff.xml" | ||
</pre> | </pre> |
Revision as of 16:37, 27 January 2017
WLAN Profile for windows 10 that sets connection properties so it won't become disconnected when crossing controllers between buildings
The Wi-Fi-Columbia FacStaff.xml looks like
<?xml version="1.0"?> <WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1"> <name>Columbia FacStaff</name> <SSIDConfig> <SSID> <hex>436F6C756D626961204661635374616666</hex> <name>Columbia FacStaff</name> </SSID> <nonBroadcast>false</nonBroadcast> </SSIDConfig> <connectionType>ESS</connectionType> <connectionMode>manual</connectionMode> <autoSwitch>false</autoSwitch> <MSM> <security> <authEncryption> <authentication>WPA2</authentication> <encryption>AES</encryption> <useOneX>true</useOneX> <FIPSMode xmlns="http://www.microsoft.com/networking/WLAN/profile/v2">false</FIPSMode> </authEncryption> <PMKCacheMode>enabled</PMKCacheMode> <PMKCacheTTL>720</PMKCacheTTL> <PMKCacheSize>128</PMKCacheSize> <preAuthMode>disabled</preAuthMode> <OneX xmlns="http://www.microsoft.com/networking/OneX/v1"> <cacheUserData>true</cacheUserData> <authMode>user</authMode> <EAPConfig><EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><EapMethod><Type xmlns="http://www.microsoft.com/provisioning/EapCommon">25</Type><VendorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorId><VendorType xmlns="http://www.microsoft.com/provisioning/EapCommon">0</VendorType><AuthorId xmlns="http://www.microsoft.com/provisioning/EapCommon">0</AuthorId></EapMethod><Config xmlns="http://www.microsoft.com/provisioning/EapHostConfig"><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>25</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV1"><ServerValidation><DisableUserPromptForServerValidation>false</DisableUserPromptForServerValidation><ServerNames></ServerNames><TrustedRootCA>5f b7 ee 06 33 e2 59 db ad 0c 4c 9a e6 d3 8f 1a 61 c7 dc 25 </TrustedRootCA></ServerValidation><FastReconnect>true</FastReconnect><InnerEapOptional>false</InnerEapOptional><Eap xmlns="http://www.microsoft.com/provisioning/BaseEapConnectionPropertiesV1"><Type>26</Type><EapType xmlns="http://www.microsoft.com/provisioning/MsChapV2ConnectionPropertiesV1"><UseWinLogonCredentials>false</UseWinLogonCredentials></EapType></Eap><EnableQuarantineChecks>false</EnableQuarantineChecks><RequireCryptoBinding>false</RequireCryptoBinding><PeapExtensions><PerformServerValidation xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">true</PerformServerValidation><AcceptServerName xmlns="http://www.microsoft.com/provisioning/MsPeapConnectionPropertiesV2">false</AcceptServerName></PeapExtensions></EapType></Eap></Config></EapHostConfig></EAPConfig> </OneX> </security> </MSM> </WLANProfile>
A bit more digging and WLAN profiles can still be exported from netsh via command line
Netsh WLAN export profile name="Columbia FacStaff" key=clear folder="WLAN"
This dumps the attached xml to a folder in the root of the users profile called WLAN. This xml can be imported with the following command
Netsh WLAN add profile filename="WLAN\Wi-Fi-Columbia FacStaff.xml"
We could script netshell delete the existing profile first then import the exported profile
Netsh WLAN delete profile name="Columbia FacStaff " Netsh WLAN add profile filename="WLAN\Wi-Fi-Columbia FacStaff.xml"