Skip to Content
Author's profile photo Tracy Sykes

Service Pack 11 for SAP Afaria has been released

I am pleased to announce that SAP Afaria 7.0 SP11 has been released and is available for download in the SAP Support Portal.

Please check the Readme for further details. The Product Documentation will be updated shortly with the SP11 documents.

If you would like to stay tuned on the latest news around Afaria, you may want to watch this wiki page to receive update notifications.
Hint: You need to be logged on in order to have the “watch this page” option available.

Assigned Tags

      14 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Under new features I can and in the docs for the inspector I can see that we should now have the option to convert unmanaged iOS apps to managed apps.

      I can't find the feature in the admin console and it's also not described (as indicated by the release notes) in the section for App Policies.

      Anyone knows where to activate this in the UI ?

      Also, where can we set this for the custom signed Afaria client? We have old clients running an unmanaged Afaria client from the SSP and would like to convert this to our new managed custom Afaria client set up now.

      Peter

      Author's profile photo Tracy Sykes
      Tracy Sykes
      Blog Post Author

      Peter,

      It isn't something you have to enable.  My understanding is you just apply a managed application policy for said app and Afaria takes over control.

      Tracy

      Author's profile photo Former Member
      Former Member

      ok. It's just for all the other MDM products this is an option per app. I might want this for some apps and not for others so I was looking tor the option under each app.

      Even if this is per server the release notes states that more info can be found in the app policy section and i can't find anything there...

      Peter

      Author's profile photo Former Member
      Former Member

      Peter,

      See http://service.sap.com/sap/support/notes/2251981

      This is a per-app configuration.

      Thanks,

      Mandy Spivey
      SAP Product Support

      Author's profile photo Former Member
      Former Member

      What we see with other MDM products is that I can push the app as a managed app but I also have the option/choice of either converting already deployed app (by the end-user) to managed apps or leaving them as unmanaged.

      I was expecting this to be my choice and not be locked to always force the apps to be converted.

      Author's profile photo Former Member
      Former Member

      Tracy Barkley did you know how we can do the same for the Afaria Custom Client ?

      Peter

      Author's profile photo Tracy Sykes
      Tracy Sykes
      Blog Post Author

      Well when you upload a custom client into the iOS application page it builds a managed application policy under the covers, so it should work just the same.

      Tracy

      Author's profile photo Former Member
      Former Member

      it doesn't we have quite a few devices (40%) running an old unmanaged version and they are not prompted for an update.

      Peter

      Author's profile photo Former Member
      Former Member

      Are all of these devices running iOS9? This feature is only compatible with iOS9 and above.

      Additionally, just as a test, rather than using the iOS Afaria application option in the server config options (Server > Configuration > Enrollment > IOS Afaria Application), you can create a new managed enterprise application policy for your Afaria client and attempt to push that to an end user to see if the user will receive the prompt this way.

      Author's profile photo Former Member
      Former Member

      To Tracy's point, here is a KBA that walks through what she mentioned:

      http://service.sap.com/sap/support/notes/2251981

      Author's profile photo Former Member
      Former Member

      Thanks. You should modify the link to point to the public version and not the internal SAP 🙂

      Author's profile photo Former Member
      Former Member

      Although the external text of the link was pointing to the right place, the embedded hyperlink was pointing to the internal location. I've corrected this now. 🙂

      Author's profile photo Former Member
      Former Member

      Do you know why this is listed as new feature in SP11 when the KB points to SP6 ?

      Author's profile photo Former Member
      Former Member

      This feature was actually released in SP6. I've suggested a documentation enhancement to our documentation team to avoid confusion with this in the future.