No option to enter a WiFi password when creating a WiFi profile with wpa or wep security
Pushing out an iOS WiFi profile that contains wpa or wep security is useless without a password. When I attempt to create a WiFi profile and select wpa (any type) or wep I does not give me the option to enter a password. We have WiFi password that is shared among multiple sites and we do not want to distribute it to employees so they can't use it to connect personal devices.
Every other MDM I have used has the option to enter a password.
Is this expected or is this a bug??
This may be a make or break bug for our deployment.
from the week of Nov 6:
Wi-Fi connections support pre-shared keys on iOS
Customers can configure Wi-Fi profiles to use pre-shared keys (PSK) for WPA/WPA2 Personal connections on iOS devices. These profiles are pushed to user’s device when the device is enrolled into Intune.
When the profile has been pushed to the device, the next step depends on the profile configuration. If set to connect automatically, it does so when the network is next needed. When the profile is connects manually, the user must activate the connection manually.
Robert Russell commented
You marked this as completed but a WPA2 Personal PSK is different than allowing us to enter a username and password for a WPA2 Enterprise connection. Most corporations will be using WPA2 Enterprise over Personal with a PSK.
ETA on this item? This is complicating deployment strategies.
Any updated on this feature? We have this ability in our existing MDM and are actively planning Intune deployment.
Is there an update on this? We are going to lose a large deal with a client using XenMobile as it can include a PassPhrase when setting up a wireless profile. I can see this being a very large competitive issue moving forward if we don't have a compete.
James Read commented
Will this be available in the Config Manager console?
Bob Becker commented
Cathy Moya - Is there an ETA or general Idea when this feature to fully configure a Wi-Fi profile will be available complete with a SSID AND the password for it? Also Is it not available yet due to a security concern/issue with entering Network SSID Passwords in the Azure portal? will those passwords and configurations be secure? - 8-8-17 3:26pm CST.
Craig Jones commented
This is stopping us from implementing intune for a global company and we will have to stick with our current mobile iron solution and carry on paying for the product. Shame as we really wanted to go down the intune route.
Is this still on the 'Planned' train after 2 years?
Would like to get the ability to distribute PSK WiFi passwords to all devices.
Sooo.....another year.....and its only PLANNED?????
How many conference calls did you folks have to have before someone actually fixed this?
2 years to get a simple feature implemented.
Seriously guys.....if I were a dev and it took me 2 years to get a simple feature in my product I would have been fired at least a year ago. This is pretty pathetic at this point.
Anthony Mather commented
create a custom profile and following this blog - http://www.concurrency.com/blog/w/intune-android-ios-psk-xml-mobile-config-generator
Again.....I opened this over a year ago. June 17th, 2015.
Figure out how to store passwords in a multi-tenant system. It shouldn't be that hard.
Another instance of every other MDM being able to do this but Intune can't.
When people start using words like "bonkers" to describe the way things are done you know you are doing something wrong.
Let me make this loud and clear:
HAVING THE OPTION TO PUSH A WPA OR WEP PROFILE IS USELESS WITHOUT A PASSWORD.
I CAN SEE THE NETWORK. I DONT NEED A PROFILE TO TELL ME WHAT THE NETWORK NAME IS. I NEED A PROFILE TO GIVE ME THE PASSWORD FOR THAT NETWORK.
There seems to be a disparity on what people who use Intune think are important ideas and what the developers and product managers think are important. It's like there users and the Intune development team are speaking two different languages.
Haven't even released a tool to make a custom XML profile. Still the only option is to use a Mac.
ITS BEEN OVER A YEAR. FIX THIS. IT SHOULD BE LOW HANGING FRUIT.
Dan Chemistruck commented
This is a recent Microsoft post:
stewart lawrie commented
Why on earth would you have a policy to allow configuring a Wifi profile but not allow you to enter/mange the password? Bonkers....
Have just been through creating a custom profile for IOS and Android. Is a bit cryptic, but this command was very helpful, to essentially output the configuration required for Intune.
1. Connected to the network with Windows
2. Run netsh wlan export profile name="<SSID>" folder=c:\temp
3. The file created from that command, can essentially be copied into the config, as referenced here.. http://www.theenterprisemobilityguy.com/2014/09/creating-a-wi-fi-profile-with-wpa-psk-and-wpa2-psk-to-windows-phone-8-1-via-windows-intune-and-configuration-manager-2012-r2/
OMA-URI path - ./Vendor/MSFT/WiFi/Profile/<SSID>/Settings
...beware special characters in your passphrase, these may need to be converted.
Sean DeLessio commented
Is there any update when this can be released? I'm running into the same issue and it seems kind of pointless to push a Wifi profile when the user still has to enter the password
@MSFT. What went wrong? Earlier this year you could add the password to a Wifi Profile for iOS but now it's gone... I'm due to start enrolling devices soon. We've decided to go ahead and push out Wifi profiles, but the password settings have gone. This is a going to be a massive pain. Can you please reinstate and perhaps apply some common sense. WiFi profiles without the ability to enter in a password are pointless.
Apple doesn't block this. I am running other MDM products that allow fully configuring WiFi
when pushing a wireless profile, include the ability to save the password in the profile. We don't want to publish wireless passwords for some ssids, if we can push these to mobile devices users do not need to know the password, can't give it out or lose it.
I was told that Apple does not allow the ability to create a wifi profiles with the username and password in it or with the client certificate in it. I am not sure if they just don't let Microsoft do it or what, but this is fully supported with Meraki.