Q: IPCU 3.4 and Network Settings

When I saw the addition of proxy to the wi-fi setup components of IPCU I thought it was great...I haven't tried it yet, but will do so and  report back...hope it really does work; this will simplify deployments quite a bit if it does. 

CCS I had the same experience you did using a ATT iPhone 4 upgraded to iOS 5...I'm going to talk to our wireless team and see what they can figure out..I'll be back if I find anything out.  I was able to browse out internal network OK with cellular data turned off, wi-fi on, but it seemed to choke on the proxy server to get out to the internet.  I tried it auto and manual, with and without entering the proxy credentials...without the credentials, I wasn't prompted by Safari for the proxy credentials from the browser page either...

We are having the same problem. The proxy settings in the profile look like they have deployed (they are visible and correct in the settings on the iPad), but the iPad doesn't actually try to use the proxy. If you then go into the settings on the iPad and manually delete and re-enter one character in the server name, it all works. It's as though there's an internal flag that's not being set by the profile, but when you edit the string in the iPad settings, it is fixed and it all works from there.

We are having sort of the same issue. But we don't get any proxy settings on the device at all, though they are specified in the .mobileconfig file.

having investigated the file further, I've found out that there er 2 further options, which is disabled (set to 0). I don't know exactly what thees options does (http and https), but expect that they might have something to do with the issue in question.

<key>Proxies</key>

     <dict>

          <key>HTTPEnable</key>

          <integer>0</integer>

          <key>HTTPSEnabled</key>

          <integer>0</integer>

          <key>ProxyAutoConfigEnabled</key>

          <integer>1</integer>

          <key>ProxyAutoConfigUrlString</key>

          <string>http://proxy.aalborg.dk/proxy.pac</string>

          <key>ProxyAutoDeicoveryEnabled</key>

          <integer>0</integer>

     </dict>

For my case, we do not enter the proxy info in iPhone Confug Utility, we only use that to enforce password policy.

Manually entering the proxy config in iOS 5 iPad works. However, many apps (e.g. activating iMessage, Adding additional email account for Gmail etc) do no work because I discovered that even with correct proxy config configured, I do not see any hits in my proxy server when trying the above mentioned. In other words, they are totally ignoring the proxy config and tried to connect direct instead.

Apple should really work on this to ensure iOS 5 works semalessly with proxy in a coporate network environment.

These seem to come from IPCU for Windows. In IPCU on Mac there is no "Proxies" key.

Just to confirm - the exact same experience through MDM profile (using MobileIron).  The Wi-Fi profile is successfully received by the iPad/iPhone and appears to have picked up the pac file url - but the connection never works until the url has been manually edited (as above, removing and readding a character is enough - so the end result is that the url string is unchanged).  However, this is then overwritten by the MDM delivered profile within a few hours, so it must be continually changed.

It seems at present that the feature (setting pac file url for Wi-Fi through configuration profile) quite simply does not work.  Worse than this, we cannot even go back to the previous situation of the URL being manually configured during deployment without rolling back our MDM version since there is no option in the profile for "unconfigured" - proxy is either set to manual, auto or off (and this then keeps overwriting any manual setting). Ideally this should be resolved by Apple ASAP - can anyone from Apple confirm whether this is being investigated/corrected in the next minor revision of iOS?

We attempted a manual proxy setting (which is less desirable as there is no means of configuring zones/ip addresses that should bypass the proxy), but this also does not work.

We've run into this exact same problem when network profiles are delivered via iPCU 3.4 or Mobile Iron. I submitted this bug/glitch/easter egg to Apple 2 weeks ago via the iOS for IT program. It's a MAJOR setback, seeing as I cannot automatically configure devices on our internal networks to use the proxy, which renders them useless.

FYI - It looks like this has been addressed in iOS 5.1 Beta 3. Can someone else confirm?

I have installed iOS 5.1 and installed th latest iPhone Configuration Utility 3.5 for Windows and still having the issue where I cannot add the proxy.

I was looking forward to the update as many developers said it would fix this issue but has not.

Some users are reporting that the Mac version is working. Anyone can confirm this? Is anyone got it working on their Windows PC?

Just installed iPCU 3.5 for OSX. Loaded our wireless profile with proxy included. It installed on my 5.1 iPad, connected and instantly began prompting for my proxy credentials. I will ask my colleague to test with his iPCU 3.5 on Windows.

I exported that same profile from OSX 3.5, imported to Windows 3.5. Then installed the profile to my iPad running iOS 5.1 and was able to connect using the embedded proxy settings with no questions asked.

If you created the profile with Windows IPU 3.5, would it work as it may be something that the Mac version may add additional settings in the codin where does the Windows may be missing.

I have recently retried IPCU 3.5 for Windows and it seems the proxy is now applying - will keep monitoring it when apply on devices as other sites