How to update the provisioning profile on the Work Hub.
Article ID: 178620
Updated On:
Products
Mobility Suite
Issue/Introduction
Resolution
How is the provisioning profile updated for the Work Hub on Mobility Suite 5.2?
1. Go to the Mobility Manager > Settings > Device Configuration > iOS Client.
2. Make note of the the Bundle Identifier (example: net.smmglobal.appcenter.installer).
3. Go to developer.apple.com > Member Center > iOS > Certificates > App ID's.
4. Search by App ID's to find a match for the Bundle Identifier listed for the iOS Client (example: net.smmglobal.appcenter.installer).
5. Make note of the name given to the Bundle Identifier.
6. Click the 'All' button under 'Provisioning Profiles' and click the "+" button in the top right corner.
7. Choose In House > Select the associated App ID > Press 'Continue' > Select the iOS Distribution certificate that has been uploaded to the Mobility Suite tenant > Click 'Continue' > Create a name for the Profile > Click 'Generate'.
8. The new .mobileprovision file can be downloaded and uploaded to the 'iOS Client' screen on the Mobility Suite.
9. Click the 'Upload Distribution Profile...' button and upload the .mobileprovision file.
10. Press the 'Build iOS Work Hub' button in the bottom left hand corner of the screen and wait approximately 3 minutes for the Work Hub to be built.
What is expected to be seen on iOS devices that are already enrolled with the old Work Hub?
11. Users will see a push notification on their Work Hub saying that an application can be updated.
12. The user will login to the Work Hub and be taken to the Updates screen where the newly updated Work Hub can be downloaded.
13. The update will be downloaded and the user can re-authenticate once completed.
14. Once the application is finished installing, there will still appear to be a push notification on the Work Hub's icon.
15. Once the authentication completes, the user will be taken back to the Updates screen and show that there is still an update for the Work Hub. However, it will disappear from that screen within 5 seconds since the update has already been installed.
*Note* - If the APNS (Apple Push Notification Service) certificate used to allow push messages to be sent to the Work Hub's provisioning profile in its App ID created on developer.apple.com is expired, then the badge notification will not occur. It is best practice to create an App ID with two push certificates so that when an older one expires there is another one that is still valid to send badge notifications. Ensure that the provisioning profile is updated before both of those two push certificates expire for badge notifications to appear.
The following query can be run on the database to view the users that have installed the latest version of the Work Hub (Note the modification necessary prior to running.):
SELECT ad.NAME as DEVICE_NAME,ad.ACID as MOBILITY_MANAGER_ID,ad.PLATFORM,ad.DATE_UPDATED as LAST_CONNECTED,aav.VERSION_STRING,aav.VERSION_CODE,aav.DATE_UPDATED as CLIENT_BUILT,aa.DATE_UPDATED as CLIENT_BUILD_TIME_ON_SERVER,au.USERNAME,au.FIRST_NAME,au.LAST_NAME,au.EMAIL
FROM APPSTORE_APP aa
JOIN APPSTORE_APPVERSION aav
on aa.ID = aav.APP_ID
JOIN APPSTORE_APPINFO aai
on aav.VERSION_CODE = aai.VERSION_CODE
JOIN APPSTORE_DEVICE ad
on aai.DEVICE_ID = ad.ID
JOIN AUTH_USER au
on aai.USER_ID = au.ID
WHERE aav.DATE_UPDATED >= TO_DATE('07-MAY-15','dd/mon/yy') --Change the '>=' value to '<' to see the inverse of this query.
AND aa.PACKBUND = 'net.smmglobal.appcenter.installer';
The example date and package bundle entered above should be changed to correspond with the environment that it is being run on. The 'PACKBUND' value should be the same as the 'Bundle Identifier' collected in step 2. The 'DATE_UPDATED' value should be the same as the date value listed in the Mobility Manager for when the Work Hub was last built which can be collected from the same location as the 'Bundle Identifier'.
The 'WHERE' clause can be modified to include the VERSION_CODE instead of the DATE_UPDATED which can be collected from the Work Hub's authentication screen. For example, the Work Hub version could be [5.0] (19.17) which is located below the Copyright information section. '19.17' would be the VERSION_CODE and the new 'WHERE' clause would look like the following:
WHERE aav.VERSION_CODE = '19.17'
*Note* - There is also a report available in the Mobility Manager called 'Out of Date ADA' which shows the users and devices that have an old Work Hub version installed.
1. Go to the Mobility Manager > Settings > Device Configuration > iOS Client.
2. Make note of the the Bundle Identifier (example: net.smmglobal.appcenter.installer).
3. Go to developer.apple.com > Member Center > iOS > Certificates > App ID's.
4. Search by App ID's to find a match for the Bundle Identifier listed for the iOS Client (example: net.smmglobal.appcenter.installer).
5. Make note of the name given to the Bundle Identifier.
6. Click the 'All' button under 'Provisioning Profiles' and click the "+" button in the top right corner.
7. Choose In House > Select the associated App ID > Press 'Continue' > Select the iOS Distribution certificate that has been uploaded to the Mobility Suite tenant > Click 'Continue' > Create a name for the Profile > Click 'Generate'.
8. The new .mobileprovision file can be downloaded and uploaded to the 'iOS Client' screen on the Mobility Suite.
9. Click the 'Upload Distribution Profile...' button and upload the .mobileprovision file.
10. Press the 'Build iOS Work Hub' button in the bottom left hand corner of the screen and wait approximately 3 minutes for the Work Hub to be built.
What is expected to be seen on iOS devices that are already enrolled with the old Work Hub?
11. Users will see a push notification on their Work Hub saying that an application can be updated.
12. The user will login to the Work Hub and be taken to the Updates screen where the newly updated Work Hub can be downloaded.
13. The update will be downloaded and the user can re-authenticate once completed.
14. Once the application is finished installing, there will still appear to be a push notification on the Work Hub's icon.
15. Once the authentication completes, the user will be taken back to the Updates screen and show that there is still an update for the Work Hub. However, it will disappear from that screen within 5 seconds since the update has already been installed.
*Note* - If the APNS (Apple Push Notification Service) certificate used to allow push messages to be sent to the Work Hub's provisioning profile in its App ID created on developer.apple.com is expired, then the badge notification will not occur. It is best practice to create an App ID with two push certificates so that when an older one expires there is another one that is still valid to send badge notifications. Ensure that the provisioning profile is updated before both of those two push certificates expire for badge notifications to appear.
The following query can be run on the database to view the users that have installed the latest version of the Work Hub (Note the modification necessary prior to running.):
SELECT ad.NAME as DEVICE_NAME,ad.ACID as MOBILITY_MANAGER_ID,ad.PLATFORM,ad.DATE_UPDATED as LAST_CONNECTED,aav.VERSION_STRING,aav.VERSION_CODE,aav.DATE_UPDATED as CLIENT_BUILT,aa.DATE_UPDATED as CLIENT_BUILD_TIME_ON_SERVER,au.USERNAME,au.FIRST_NAME,au.LAST_NAME,au.EMAIL
FROM APPSTORE_APP aa
JOIN APPSTORE_APPVERSION aav
on aa.ID = aav.APP_ID
JOIN APPSTORE_APPINFO aai
on aav.VERSION_CODE = aai.VERSION_CODE
JOIN APPSTORE_DEVICE ad
on aai.DEVICE_ID = ad.ID
JOIN AUTH_USER au
on aai.USER_ID = au.ID
WHERE aav.DATE_UPDATED >= TO_DATE('07-MAY-15','dd/mon/yy') --Change the '>=' value to '<' to see the inverse of this query.
AND aa.PACKBUND = 'net.smmglobal.appcenter.installer';
The example date and package bundle entered above should be changed to correspond with the environment that it is being run on. The 'PACKBUND' value should be the same as the 'Bundle Identifier' collected in step 2. The 'DATE_UPDATED' value should be the same as the date value listed in the Mobility Manager for when the Work Hub was last built which can be collected from the same location as the 'Bundle Identifier'.
The 'WHERE' clause can be modified to include the VERSION_CODE instead of the DATE_UPDATED which can be collected from the Work Hub's authentication screen. For example, the Work Hub version could be [5.0] (19.17) which is located below the Copyright information section. '19.17' would be the VERSION_CODE and the new 'WHERE' clause would look like the following:
WHERE aav.VERSION_CODE = '19.17'
*Note* - There is also a report available in the Mobility Manager called 'Out of Date ADA' which shows the users and devices that have an old Work Hub version installed.
Attachments
Feedback
Yes
No
Powered by
