Microsoft direct push troubleshooting

This might sound like a silly question, but this particular server runs a self signed cert. The particular mobile vendor that is being used requires that you load the self signed cert into the flash on the phone with 3 rd party software.

I loaded the cert on all the phones, but found there was a problem with the cert and we were forced to recreate it. When I attempted to reload the new cert on the phones, I would immediately get a failure message because the utility would not force an overwrite of the existing cert.

That being said, is this my problem? If so, any suggestions around it? HTTPS is not required for direct push to work, however it is smart to use as you dont' want passwords flying though the air in clear text On the lack of push, is this happening to all clients?

Have you got SP1 installed? If no SP1, what is your activesync policy defined to? I know I need to blank out the phones and reinstall the cert, just haven't had time. Exchange does not have SP1 installed on it. If changes occur within the lifespan of the HTTPS request, the Exchange server issues a response to the device that states that changes have occurred and the device should initiate synchronization with the Exchange server.

The device then issues this request to the server. When synchronization is complete, a new long-lived HTTPS request is generated to start the process again. This guarantees that email, calendar, contact, and task items are delivered quickly to the mobile device, and that it is always synchronized with the Exchange server. This request is known as a PING. The request tells the server to notify the device if any items change in the next 15 minutes in any folder that's configured to synchronize.

The mobile device then stands by. The minute time span is known as a heartbeat interval. The mobile device receives this response, resumes activity known as waking up , and issues its request again. This restarts the process. If any items change or new items are received within the minute heartbeat interval, the server sends a response that informs the mobile device that there's a new or changed item and provides the name of the folder in which the new or changed item resides.

After the mobile device receives this response, it issues a synchronization request for the folder that has the new or changed item. When synchronization is complete, the mobile device issues a new PING request and the whole process starts over.

The following steps describe how Direct Push operates when the carrier network for a mobile device has a time-out value of 13 minutes. If the server doesn't respond after 15 minutes, the mobile device wakes up and concludes that the connection to the server was timed out by the network. Cancel Submit. Linley Meslier MVP. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to Linley Meslier's post on October 1, My data service is thru T-Mobile.

In reply to coolaggie's post on October 1, And I assume that "As items arrive" is selected in Schedule in Activesync. In reply to Linley Meslier's post on October 2, My problem is that it works sometimes and it doesnt during other times