On September 24, 2015 Microsoft announced support for iOS9 through he iOS9 extension for Microsoft Intune in Configuration Manager.
To enable the extension, go to your SCCM console (2012 R2 SP1 CU1). Under Administration, expand Cloud Services and click Extension for Microsoft Intune.
In the right pane, right click the iOS 9 Extension and click Enable (or from the toolbar). If you do not have CU1, this can fail.
Accept the License Terms – make sure you read all of it first 🙂
The MDM capabilities provided in Windows covers the complete lifecycle of the device.
- Enrollment capabilities to automate the MDM enrollment of the device as part of the Azure Active Directory join process.
- New controls for configuring and managing the Start menu.
- New controls over Windows updates, allowing you to control when specific Windows updates are deployed to MDM-managed devices (think “WSUS from the cloud”).
- New AppLocker and Enterprise Data Protection configuration settings.
- Integration with the Windows Store and the Business Store Portal (BSP) to enable automated app management.
- Full device wipe capabilities, even for PCs.
These capabilities are supported on all types of devices, including Windows phone devices, PCs and tablets, and Internet-of-Things (IoT) devices.
The following are quick steps to enroll the Microsoft Windows 10 Insiders Preview (as of build 10130) to Microsoft Intune in a hybrid environment with Microsoft System Center 2012 R2 SP1 Configuration Manager (SCCM).
This assume you have already configured Microsoft Intune into your SCCM environment.
- In the SCCM console, navigate to Administration -> Overview -> Cloud Services -> Microsoft Intune Subscriptions.
On the top ribbon bar, click the Configure Platforms button. Click Windows in the drop down
From the Microsoft Intune Subscription Properties, click the Enable Windows enrollment.
Log onto your Windows 10 desktop, go to Settings and choose Network and Internet
Click on Accounts and then Work access. On the Connect to work or school section, click the + Connect
Enter your work email address that are Intune enabled (an account that has synchronization between your on-premise Active Directory and Windows Azure Active Directory). After you click continue, you will be sent to the Microsoft site to authenticate.
Once done, you see the connected account on the main section.
In the SCCM console, you will now be able to see your newly enrolled device as a Mobile device. You will be able to deploy applicable compliance policies just like any other mobile devices in your organization.
As most have seen the blog announcing the Intune Mobile Application Management and Conditional Access for Outlook. At the very bottom, there is a Note about the hybrid customers (SCCM) availability that seems to be missed by few folks when they update to SP1.
Quick query to dynamically identify Android devices in Configuration Manager 2012 R2
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_DEVICE_OSINFORMATION on SMS_G_System_DEVICE_OSINFORMATION.ResourceId = SMS_R_System.ResourceId where SMS_G_System_DEVICE_OSINFORMATION.Platform like “%Android%”
Microsoft will be making the next update for Microsoft Intune between March 4, 2015 and March 7, 2015. New Intune standalone (cloud only) features that will be released as part of this service update include:
- Ability to streamline the enrollment of iOS devices purchased directly from Apple or an authorized reseller with the Device Enrollment Program (DEP)
- Ability to restrict access to SharePoint Online and OneDrive for Business based upon device enrollment and compliance policies
- Management of OneDrive apps for iOS and Android devices
- Ability to deploy .appx files to Windows Phone 8.1 devices
- Ability to restrict the number of devices a user can enroll in Intune
It’s important to note that the updates are for the stand alone Cloud only and not the integrated with SCCM. Updated to the integrated extensions are usually 3-6 months after the standalone is available.