Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Having Issues With Configuring Push Notifications For OWA For Devices (On-Premise Exchange 2013)

$
0
0

Hello,
I am having issues receiving any push notification on OWA Apps for Devices. My Exchange server is running 2013 CU7.

Here is what I have done:
- I created an Office 365 Account
- Verified My Domain but did not change any DNS records other than adding the TXT record required
- Followed this guide:
http://technet.microsoft.com/en-us/library/dn511017(v=exchg.150).aspx
Everything worked except when getting to the line:
New-MsolServicePrincipalCredential -AppPrincipalId $p.AppPrincipalId -Type asymmetric -Usage Verify -Value $credValue -StartDate $cer.GetEffectiveDateString() -EndDate $cer.GetExpirationDateString()
I got the error:

New-MsolServicePrincipalCredential : Invalid value for parameter.  Parameter name: Credential.EndDate.
At line:1 char:1
+ New-MsolServicePrincipalCredential -AppPrincipalId $p.AppPrincipalId -Type asymm ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [New-MsolServicePrincipalCredential], MicrosoftOnlineException
    + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.PropertyValidationException,Microsoft.Online.
   Administration.Automation.NewServicePrincipalCredential


I then removed the last two parameters of StartDate and EndDate, and reran the script and it worked. I don't know if this is the cause of the issue.

- I then tested push notifications in PowerShell with the following:
Invoke-MonitoringProbe PushNotifications.Proxy\PushNotificationsEnterpriseConnectivityProbe -Server:$s.Fqdn | fl ResultType, Error, Exception
I got the result of Succeeded.
- I then tried seeing if I'd get any notifications on my phone when receiving new mail, and I couldn't.

Note:
When I reran the Invoke-MinitoringProbe command and just got all of the parameters, I noticed the following:

ExecutionStartTime : 1/14/2015 6:05:53 PM
ExecutionEndTime   : 1/14/2015 6:05:53 PM

That time is 5 hours past the timezone we are in. Could this be an issue?

Thank you for your time.


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>