Enterprise Management Scheduled Tasks do not match documentation

When we started our journey towards 100% Intune managed, AAD joined devices one of our frustrations was that, after a device was joined to our AAD, we had to play a waiting game before we could verify that all deployment & configuration settings were actually applied to the device.

You can either wait for the MDM client to trigger it’s scheduled check-in, use the device’s GUI to force a manual sync, or trigger one from the Intune management portal.

For Windows 10 devices, the documented schedule for check-ins is as follows:

  • Windows 10 PCs enrolled as devices: Every eight hours.

If the device has just enrolled, the check-in frequency is more frequent, as follows:

  • Windows PCs enrolled as devices: Every three minutes for 30 minutes, and then every eight hours.

Continue reading

Enforcing Computername using Intune Powershell

When performing a ‘Fresh Start’ or ‘Factory Reset’ on an Intune managed device, the computername is reset to the default ‘DESKTOP-<random>’ name.

Our requirement however, was that every machine has a specific computername.

Since Intune offers the possibility of deploying Powershell scripts, I’ve written one that checks the device’s serial number and renames the computer if the serial is known.

Continue reading

Deploying the ‘Upgrade Readiness Deployment Script’ via InTune

Microsoft has released the “Upgrade Readiness Deployment Script” (URDS), including a method for deployment with SCCM.

Upgrade Readiness is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud based services for managing your on-premises and cloud environments. For more information about OMS, see Operations Management Suite overview.

Unfortunately, they do not provide instructions how to deploy the script using Azure InTune, the MDM solution we use.

Luckily, with the use of Advanced Installer (AI) and a short PowerShell script, I have been able to deploy via InTune 🙂

Continue reading