Sensors are script based command to allow administrator to retrieve not out of box attributes from Windows10, Android or MacOS.
In this blog, I am going to show you how to use sensor to automate Windows10 application installation.
If you have never had a chance to implemented a sensor before, there are a lot of examples from the github: https://github.com/vmware-samples/euc-samples/tree/master/UEM-Samples/Sensors/Windows
Here is the sensor used in this tutorial. This is a sensor to retrieve country from the GPS reported by Windows 10.
To make sure GPS is turned on, create a restriction to force location on a Windows10 laptop.
Now we can start sensor deployment. Create a sensor by uploading the sensor sample from above.
Assign the sensor and make sure your device can have the location reported back.
You can find sensor value from device details page on UEM console.
We wanted to use the tag for assignment. The next thing we have to do is to create a new assignment group based on the sensor.
I wanted to get Zoom installed to a tagged Windows10 and this is what I did for Zoom app assignment. You can get Zoom app from the UEM enterprise app repository.
Make sure the device is not tagged and the Zoom is not assigned to your testing device.
Now, move to Intelligence. Create a new custom workflow under automation.
The workflow is triggered when sensor value is Hong Kong. There are two actions to be defined. One is to add a tag and other one is to send a email to the device owner.
This is the first action to tag a device. The device ID is a substitute value which is a dynamic value. The tag is a constant which we can search UEM to retrieve it.
The second action is to send a email to notify the user who is the owner that an application Zoom is going to be installed.
Now you should have a workflow similar to this one.
Expand the first action. There is a testing tool to to validate the workflow. We can populate the device ID and the tag ID with actual device ID value and tag ID value.
If you are not sure about your device ID and tag ID, you can get them from UEM console. You will see the ID by place your mouse over the device and tag.
Press the test button and it is expected to get response code 200 OK
Your device should be tagged and assigned with the Zoom app.
Open the second action and perform a similar test with real values.
This time you will get response code 202.
You will get a notification email.
The setup is now complete. Make sure you keep the substitute values but not the real values in your actions.
In this demo video, an WSO intelligence automation was tested out. It got a Windows10 device tagged “HongKong”. An assignment group was setup based on this tag. Zoom app was assigned to this group. The final result is that Zoom was installed to a tagged device automatically.
After a successful test, you can have the automation enabled and set to automatic. Otherwise, you can choose either manual or schedule.
Comments