Following the availability of the new SCCM Current Branch build (1810), it is now possible to use the built-in SCCM task sequence to use Autopilot when deploying OS. To use it, you need to create an SCCM package which will contains the Autopilot settings and use the SCCM tasks sequence (this is not available for […]
SCCM – Use Autopilot when deploying OS Read More »
It has been quite a limitation so far for Windows 10 managed with Intune; it was impossible to get them to join an Active Directory domain using Autopilot, making these devices Azure AD Hybrid joined devices. Now (currently in preview – so there could be some glitch and may change), you can assign an Intune
Intune – You can now get Windows 10 join an Active Directory Domain (preview) Read More »
As you may already know Windows Autopilot simplifies Windows 10 device enrollment to Azure Active Directory (AAD) and providing seamless user experience. One of the problem with Windows Autopilot was if your already have Windows 10 devices registered to your Azure AD, you were not able to assign an Autopilot profile. With the latest update
Intune – You can now assign Windows Autopilot profile to already registered clients Read More »
With the latest Intune update, you can now display an enrollment status page after a Windows 10 device has been registered. The page will let your end-users know what is happening while their device is finalizing the registration process. To do so, you first need to enable the feature in Intune Connect to your Azure
Intune – Display an enrollment status page Read More »
If your company policy requires to allow only corporate devices to register to Intune, you can now block personally owned devices to join. To do so, from your Intune configuration blade reach out the Device enrolment blade and create/edit an Enrolment Restrictions policy The option to allow/block personally owned devices is available for each supported
Intune – You can allow/block personal devices to register Read More »
With the latest updates on Intune, you can now define specific users/devices when you apply a Windows Hello policy. Until then, the Windows Hello policy was a tenant level settings and as such applied to all users/devices. To define the Windows Hello policy, go to your Intune configuration blade and reach out the Device configuration\Profiles
Intune – You can now target specific users/devices when applying Windows Hello policy Read More »
With the latest updates on Intune, you can now edit the channel update after you have added your Office 365 Click to Run application on Intune as well as define (if required) which specific release needs to be installed on the client. To edit the update channel and/or define the version to be installed, go
With the latest updates on Intune, you can now update your Office 365 Click to Run deployment. Previously you had to delete the deployment and re-create a new one with the updated deployment settings if you had to add/remove Office application from your deployment. Just access your Intune configuration blade from the Azure portal and
Intune – You can now edit your Office 365 Click to Run Deployment Read More »
It seems it has not been widely and properly communicated As you may know with System Center Configuration Manager (SCCM) you were able to setup an hybrid mobile device management with Intune, meaning you were able to use Intune to register your device and use SCCM to manage them. So, since August 14th 2018, this
SCCM/Intune – Hybrid mobile device management is deprecated Read More »
With the latest version of SCCM Current Branch (1806), new options are available for the co-management capability: Mobile apps, to use Intune for mobile applications deployment while keeping your Windows client managed by SCCM Office Click-To-Run, to use your Intune for Office 365 Click to Run deployment
SCCM – New co-management options Read More »
