By default all Windows Virtual Desktop session hosts are joined with your domain. And in most cases you will apply policy configurations to them via Group Policy Objects (GPO). If you also using Microsoft Endpoint Manager – Microsoft Intune for managing Windows 10 devices, it might also be worth considering to manage your WVD session hosts VMs with it as well.
Samsung Knox Mobile Enrollment (KME) is a Zero Touch provisioning solution. You can fully automate the enrollment of new, or factory reset devices into an MDM solution like Microsoft Intune. The end user only have to turn on their company-owned Android device and connect to a Wi-Fi or cellular network. This will start the enrollment which the end user cannot cancel or work around.
The Microsoft Store for Business is a powerful service to distribute and manage modern Windows 10 applications from the Windows 10 Store (both free and paid applications). You can connect the Microsoft Store for Business with Microsoft Intune to sync the applications for easy deployment via Microsoft Intune. After the application is synced to Intune you only have to assign the application to a user of group. It is very easy to setup. However, there is not an easy “delete” button to remove applications that are no longer needed or added accidentally. In this blog I will show you step-by-step how to remove Microsoft Store for Business applications in Microsoft Intune.
In July, 2018, I wrote this blog about how to setup Windows Autopilot and add existing devices the quickest way. After publishing this blog the Get-WindowsAutoPilotInfo script has been updated several times by the author Michael Niehaus. New functionalities have been added to the scripts. Therefore Windows 10 devices can be added to Windows Autopilot even faster then described in my old blog. Let’s see how you can add Windows 10 devices even faster to Windows Autopilot.
I get the following question regularly; “can we configure our Apple iPads as Shared device. Where you as a user, can login and logoff without seeing each other’s data?”. Most of the time it’s about medical personal that works in shifts and don’t have a personal device. But you can also think of maintenance and field agents or flight crew members for example. In this case you want to let the employees use their applications across a pool of shared devices. They should be able to pick any random device from that pool, login and do their work.
After companies apply Mobile Application Management (MAM) / App Protection Policies to their employees’ mobile devices, and forced them to use the Managed Outlook app instead of the native mail application, one of the most frequently asked questions are “how can I see who’s calling me?” and “where are my contacts? I don’t see them in my native contacts app”. This has everything to do with the fact that contacts are now in a “isolated/secured app container” and not accessible by other non-managed / secured applications.
In the last few weeks I have had contact with a few companies that use Microsoft Endpoint Manager / Microsoft Intune for managing their mobile devices. In most cases they do this for a longer time and they also use Mobile Application Management (App protection policies) for securing the company data, for example, on BYOD (Bring Your Own Devices / Private owned devices). And this is a good thing if you want to isolate company data in a secure container, but in some cases they did not know about the existence of the new Microsoft Office (Hub) application. Without securing this application, end users may have access to company data via an unsecured way.
With the October 14, 2019 Microsoft Intune update, management of Microsoft Intune has become a little easier. And with “little easier” I mean that it is now possible to assign multiple resources like applications and policies at once. With Policy Sets you can assign applications, application protection policies (MAM), configuration-, compliance- and type restriction policies, AutoPilot profiles and enrollment status page with one single assignment. The resources itself don’t have to be assigned separately to users or devices.
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
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.