OMS Automation: How to handle OMS Alert result data in a runbook

Currently we are doing Demos upon demos, POC upon POC of OMS. Everybody seems keen to get into to it! One of the function of OMS Log Search is Alerts. These alerts can be setup to trigger a runbook in Automation when the alerts trigger. Here is a simple template to use for getting the content of the data sent from OMS: param($webhookdata) # Get Webhook Data $RequestBody = ConvertFrom-JSON $WebhookData.RequestBody # Searching Webhook Data for Value Results $SearchResults = $RequestBody.SearchResults $SearchResultsValue = $SearchResults.value Foreach ($item in $SearchResultsValue) { $UserName = $item.TargetUserName #Field name } Thats it !  

By |2016-06-29T16:18:35+01:00juni 29th, 2016|Azure|1 Kommentar

Error enrolling devices into Intune & Configuration Manager 1602

Enrolling devices into Intune and & ConfigMgr is normally straight forward until you run into issues. Below is an example where I received an enrollment error (picture 1), clicking Continue leads me to picture 2. As you can see in picture two the Enrollment Update turns from Warning to Checkmark, but only for about 5 seconds then it goes back to a warning.     Troubleshooting mobile devices is slightly different than traditional desktop troubleshooting. The troubleshooting options depends on the device (Android, iOS or Windows). In this example my device was an Android. You can email the log files [...]