#Modern Workplace

  It was a cold gloomy day when I set out on a mission to fix an issue involving ASR rules. Something which I may have done a dozen of times so I said to myself, why it should be any different this time. But if history has taught me anything, it is that no two issues are the same, despite how much they resemble and that for every issue there is a possible solution. You just have to stay relentless and you will eventually make it to the other side. The issue.. It all began with the ASR rules in 'block mode' starting to block macros on a set of devices. Pretty routine at this stage as the logical thing to do is either to configure necessary exclusions or put the relevant ASR rule in a non restrictive state like 'Audit' mode. The problem is that no matter what changes I made to the ASR rules, they simply didn't make any difference. Macros continued to be blocked and the events in Advanced hunting would confirm the same. When I checked the registry on the devices in que...

Recently, I worked on a requirement for configuring a Macro as part of standard build for devices being provisioned using Autopilot. As of now, there is no single complete solution available out of the box in Intune to achieve this and there are a number of steps involved in the process. At a high-level, the process involves the following: 1.       Install the Macro on a reference device. 2.       Create a self-signing certificate on the same reference device. 3.       Add the certificate against the Macro and capture the .OTM file. 4.       Export the certificate as a Base 64 code. 5.       Configure the Trust setting policy in Intune. 6.       Create a Win32 app to copy the .OTM file in the user’s profile path. 7.       Configure the CSP in Intune to deploy the certificate in Root CA & Trusted...