Some time ago I wrote a blog about “How to setup Windows AutoPilot and add existing devices the quickest way”. At that time, White Glove did not exist yet. And it’s great to know how to setup Windows AutoPilot and add existing devices the fastest way, but how to get endusers to work on a new device the fastest way?
With the release of iOS 13 there were a few major changes, not only did the iPad’s got their own iPadOS, also with the Mobile Device Management (MDM) enrollment modes there are major changes. The Device Enrollment Program (DEP) is renamed to “Automated Device Enrollment” and all devices enrolled with “Automated Device Enrollment” are now automatically set in supervised mode. There is also a new MDM enrollment mode introduced with the release of iOS 13, the User Enrollment mode.
Previously, during a device unenrollment, all applications were removed that where pushed/installed via Microsoft Intune by default. This is not always handy, for example take the Microsoft Office applications. You can add multiple accounts within these applications and if you are using Microsoft Outlook for your work mail and also for your private mail. You want Microsoft Outlook to stay on your mobile device after an unenrollment.
In VLOG#2 I will show you step-by-step how to deploy Win32 applications with Microsoft Intune. This VLOG is based on my earlier blog post. Prerequisites There are some requirements for publishing Win32 applications to a client. Be aware that you must meet the following criteria; – Windows 10 – build 1607 or higher (Education, Pro and Enterprise) – The Windows 10 client must be joined to Azure AD or Hybrid domain joined – The Windows 10 must be under MDM management with Microsoft Intune – The application (including all sources files) may not exceed 8 GB in size
One of the most frequently asked questions from customers is whether it is possible to publish Win32 applications with Microsoft Intune. The answer is Yes. It is possible to deploy Windows 10 Store Apps, MSI files and even .EXE files. Although .EXE files cannot be published directly. You need to “wrap” the .EXE file (and other required source files if applicable) to an .INTUNEWIN file. In this blog I will show you step-by-step how to do this. In the following example I will publish the FileZilla FTP client with Microsoft Intune.
In the last two months I wrote some blogs regarding different type of Android Enterprise modes. It’s now time for the last mode; Android Enterprise – Corporate-owned, fully managed user devices. And as the name of this mode indicates, this mode is for user based scenario’s. The enrollment process is more or less the same as with the dedicated device mode. The enrollment process also start with scanning a QR code. However, a user needs to enter his or her credentials during enrollment and all applications and profiles needs to be published user based (see also step 6: testing the results).
In previous blogs I talked about how to configure Android Enterprise – Corporate-owned – dedicated device mode, and as an addition, how to configure Kiosk Single app mode for Android devices. In this blog I want to show you the Multi-app Kiosk mode for Android devices and how the end user experience looks like. There are some steps different than in Single app mode, I will show you this step-by-step in this blog. In this blog I will cover the following steps; Publish the Managed Home Screen app Create a Multi-App Kiosk profile Test the results
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.