For more information, see Windows Phone 8.1 mobile device management.
Note The following restrictions pertain to push notifications and WNS:
- The WP8.1 device provides a channel Universal Resource Identifier (URI) to the MDM server.
- The channel URI is valid for only 30 days. The device automatically renews the channel URI after 15 days and triggers a management session on successful renewal of the channel URI.
- MDM Push may fail to automatically renew the WNS Push channel, causing it to expire.
Problem statementIf the channel URI is not renewed by the WP8.1 device within 30 days, a server-based approach is required. For example, a device that has been powered-off for more than 30 days cannot re-establish communication.
This article provides a workaround to let you re-establish communication between an MDM server and the device.
Key scenarios in MDM push notification
MDM server enables push notificationWhen an MDM server enables push notification, it sends a new PFN to the DMClient CSP that's running on the device through an OMA-DM session. The PFN is used to register for push notifications with the WNS client. Along with registering with the WNS client, the DMClient CSP also requests a channel URI. The WNS client communicates with the WNS server to get a channel URI. The WNS client returns the Channel URI to the DMClient CSP, which then stores the URI in a data store on the device.
MDM server push command for policy syncWhen an MDM server prepares to run a push command, it sends an HTTP post to the channel URI associated with the WNS server. The WNS server resolves the target device for the notification and communicates with the appropriate WNS client. The WNS client then signals a WNF event whose name was provided during PFN registration and which triggers a task on the device to handle the notification. The notification handler proceeds to start a new OMA-DM session.
Essentially , the push is like a shoulder tap from the WNS client to the MDM server to wake up and perform synchronization.
Note There is no payload data involved in a push; it's just a wakeup call.
MDM server refresh PFNWhen a MDM server replaces the PFN to be used for push, the current PFN is unregistered, and then scenario 1 is performed again.
Therefore, this will also renew the channel URI, which is based on the new PFN. Because this process s initiated by the MDM server, this could be a workaround for a case in which the channel URI has already expired and the device cannot perform auto-channel URI renewal for some reason.
Client channel URI renewalThe channel URI expires after 30 days. To ensure continuity, the WP8.1 device has a scheduled task (the URI Renewal task) that renews the channel URI 15 days before the expiration date. After the channel URI has been renewed, the task reschedules itself to the next 15-day mark.
The scheduled task ends after the 30-day expiration date, which means that the channel URI has not been renewed.
WorkaroundWhen the channel URI has expired, it can't be renewed by the WP8.1 device. A server-based approach is required, and the recommended solution is to use a PFN refresh to initiate a renewal. To do this, follow these steps:
- Create a new PFN for the client, and enable push again from the MDM server. This is what happens in scenarios 1 and 3. The sample SyncML is provided below.
Note The SyncML may vary, depending on your MDM solution.
- To successfully renew the channel URI, the WP8.1 device requires Internet connectivity so that it can receive the new policy and communicate with the WNS server. Microsoft strongly recommends that you use the manual sync button in the workspace to download the policy.
- After the channel URI is renewed on the WP8.1 device, the push channel will be active again.
Article ID: 3170699 - Last Review: Jun 23, 2016 - Revision: 1