A quick Friday tip about Intune Win32Apps that I find annoying. When using PSAppDeploymentToolkit togethe with Intune the filename in Intune will always be “Deploy-Application.Intunewin” as we point to that when we wrap the application as shown below. The same applies for setup.exe or install.exe as well and other unattended setups. The filename of the
By my Padawan and co-worker Sassan. This is a quick post about the possibility to manage and configure some BIOS settings on Dell computers using Intune and Win32 apps. In this example we’re going to set an BIOS/admin password, but this could of course be expanded to configure other settings that are available through the
In Configuration Manager we always had log files for everything, extremely useful when troubleshooting. In Intune we have the event log and the MDMDiagnosticsTool which is our best friends. Win32app and PowerShell Scripts deployed are installed using the Intune Management Extension and for that we do have log files where we can track/troubleshoot application deployment.
One of the biggest limitations in Microsoft Intune has been that we can only deploy single-file .MSI’s and not .EXE installers. With the release of Win32app install support (in Preview) that limitation is now gone! Not only does it support legacy setups like .exe files for instance we can also use it for advanced .MSI
