SOTI Pulse Logo

Any updated documentation for getting WNS info?

Solved
TN
Topher Neal

I'm not sure, but I feel like I'm missing something here, and maybe it's just due to the inconsistency of documentation surrounding WNS (even Microsoft is still showing steps for the old Developer portal.)

I made a developer account for our generic Live account (because MS would not let me use my org account,) and added the Live account to our org's AD, and granted the permissions described in the Partner Center, to allow access.

I then worked with our internal developers to get a dummy MSIX to upload to the MS Store. I've gotten the MSIX through Submission, and have a PSID and PFN. I then logged into a global admin for the org's AD, and setup a secret for the dummy MSIX under App Registrations.

I copy/pasted the PSID, PFN, and secret into the MobiControl Global Settings fields for WNS, but every time I click Save, I get an error "Failed to update the Windows Notification Service configuration because the service failed to obtain a token."

Did I miss a step, or is there more to this that hasn't been documented yet? I'd just like to get WNS working so that we can fully utilize MobiControl on Windows 10+. Any help will be greatly appreciated!

WNS
3 years ago
Windows
ANSWERS
TN
Topher Neal
3 years ago

After a call with Aiman, I've resolved this issue!

In addition to not needing to more than reserve an app name to get the PSID and PFN, then registering the app in AzureAD and adding a client secret, the big gotcha was that when entering the PSID in the MobiControl WNS settings, the PSID needs to be entered as "ms-app://[PSID String]". After adding the "ms-app://" to the PSID, and providing the PFN and Client secret, MobiControl successfully connected and we can use WNS now!

Solution
RC
Raymond Chan Diamond Contributor
3 years ago

Have you checked if your corporate firewall is blocking any network traffic to Microsoft servers related to Windows MDM functionalities?

TN
Topher Neal
3 years ago

I have encountered this issue on both our company network and at my own home. Given that, and our MobiControl being a hosted cloud instance (that's on me for forgetting to include that in my OP) I don't think our firewall is blocking MC from getting the WNS token.

Given how out of date the MS documentation is on this, I broke down and reached out to MS for support. If they are able to help me resolve this, I'll update my post with how for anyone else after me in a similar situation.

TN
Topher Neal
3 years ago

Ok, got with Microsoft, as there is a new documentation page that lists a second set of steps after reserving the app name in Partner Center and registering the app in AzureAD. Afterwards a Notification Hub has to be setup through Azure. (Switched computers and can't find the link now.)

From Microsoft's email to my ticket: "I just want confirm with you again that you would need an Azure Subscription to deploy a Notification Hub, even if it's the free tier. There is no other possible way to set up WNS with AzureAD."

So it seems the roadblock I'm hitting was two-fold, 1. the instructions had changed and 2. it just can't be done with AzureAD alone now.

I
ICMOD@SOTI Bronze Contributor
3 years ago

Hello Topher,

Thanks for your post!

Here is some detailed SOTI official documentation regarding Configuring Windows Notification Services: https://www.soti.net/mc/help/v15.5/en/console/devices/managing/enrollment/windows/modern/wmodern_enable_wns.html

Hope this helps! Let us know if you are still having issues configuring WNS.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

TN
Topher Neal
3 years ago

I started by referring to this documentation first. It is the documentation that could use updating. For example, there's still reference to Microsoft's Developer Center (which is now Microsoft Partner Center) and several of the steps no longer match with the changes to that portal.

Similar Discussions