Settings for sending UEM Notifications with Intelligence
If you have been using Workspace ONE Intelligence and want to send out Notifications via UEM there is a nice “pre-build” UEM Action in Intelligence. But If you use it you need to make sure that you specify the right Message Type and Application per platform.
once you click the “Send Push Notification” you see the fields that are required:
So what should you type in ? I have split this per Platform and will provide the values here incl. how it looks on the Device.
Settings for Apple macOS
For sending Notification to macOS Devices the following Settings are required:
| Message | Enter your Message, Variables are supported here |
| Application | com.airwatch.mac.agent |
| Message Type | awcm |
| Device ID | ${airwatch.device.device_id} |
Once you have them in the GUI, you can also test them :
This is how it looks on the device:
Settings for Apple iOS
For sending Notification to iOS Devices the following Settings are required:
| Message | Enter your Message, Variables are supported here |
| Application | Intelligent Hub |
| Message Type | apns |
| Device ID | ${airwatch.device.device_id} |
Once you have them in the GUI, you can also test them :
This is how it looks on the device:
Settings for Windows Desktop
For sending Notification to Windows Devices the following Settings are required:
| Message | Enter your Message, Variables are supported here |
| Application | com.airwatch.workspace.one |
| Message Type | wns |
| Device ID | ${airwatch.device.device_id} |
Once you have them in the GUI, you can also test them :
This is how it looks on the device:
Settings for Android
For sending Notification to Android Devices the following Settings are required:
| Message | Enter your Message, Variables are supported here |
| Application | AirWatch Agent |
| Message Type | Push |
| Device ID | ${airwatch.device.device_id} |
Once you have them in the GUI, you can also test them :
This is how it looks on the device:
Summery of the Settings
in total here the Application and Message Types for all 4 platforms
| Platform | Application | Message Type |
| macOS | com.airwatch.mac.agent | awcm |
| iOS | Intelligent Hub | apns |
| Windows | com.airwatch.workspace.one | wns |
| Android | AirWatch Agent | Push |
hc-amis
Hi,
Thanks for this, it works well with macOS. However, it doesn’t work in Windows 10. Is this Win 11 only feature?
hc-amis
Patrick Zoeller
It should not be different with Windows 10 vs. Windows 11. But my testings where only done with Windows 11, not with Windows 10. Do you have the Hub Installed on the Windows Devices? As it requires Hub to be installed.
Tom
I’m having this issue where WNS push notifications are stuck in “Queued” status, one of them stuck for 3 days. Other commands are going through just fine. My Windows 10 machine is not on the corporate network so the WNS servers are not being blocked. Any idea how to troubleshoot the “Queued” issue for on-prem WS1 UEM?
Queued Send Message 4/7/2022 9:56 sysadmin com.airwatch.workspace.one This is a test
Queued Send Message 4/4/2022 10:32 sysadmin com.airwatch.windowsrtagent Your device is in violation of the “Testing Purposes to generate Push notification” compliance policy. Further action will be taken if the device remains non-compliant.
Patrick Zoeller
Hello Tom ,
it should be com.airwatch.workspace.one , are you using a Compliance Policy or a Intelligence Automation ? If it is Intelligence you need to Change the Application to “com.airwatch.workspace.one”and it should work.