Modern Device Management

Recently, I setup a custom app in Intune for the purpose of rolling it out to both corporate and personal mobile devices. Something very routine, but it had it’s own share of challenges. The main challenge was getting the application protection policy (APP) to apply on the application after the roll out, but later on that. I won’t cover the process of adding a custom application in APP. There are a number of good blogs out there that cover this process in detail, so I’ll jump straight into the issue. The application in question goes by the name Workvivo and I added it’s application bundle id in the list of protected apps. Here is the snippet of the APP. After applying the APP, I started to notice that the application will not check-in. Normally MAM policies take a little while to apply, but this was something else. I started digging and it got me to the realization that maybe the application is not supported for APP after all. According to Microsoft, “A MAM ...

Recently, I was engaged in supporting a customer to help them progress with the roll out of Windows 10. Understandably, they wanted to leverage PXE to build the devices which worked perfectly fine until they decided to upgrade to CB 1910 along with ADK 1903. Post upgrade, PXE stopped working suddenly. Now, I have done countless upgrades till date, so it didn't make any sense as to why such a routine upgrade would cause PXE to break. This is where my quest starts. Now the write up from here on may appear long but bear with me as I try to capture the entire troubleshooting process. PXE can become tricky if the setup is not configured correctly. As the first step, I checked for the usual areas of the PXE configuration, starting with the SMSPXE.log on the Distribution Point hosting the PXE role. I could clearly see that the client was sending the PXE request and the PXE server was even responding with the policy and the NBP file . However, the client kept on requesting using the ...