KB3002291: MDM settings are not applied to cloud-managed users in Configuration Manager 2012 R2

hotfixJust drop you a quick line a new hotfix for Configuration Manager 2012 R2 is released which improves the process of getting policies applied to mobile devices. When a user becomes a cloud-managed user (CloudUserID), a settings policy may not target the assignment for the user this due to different user(s) with same clouduserID. This behavior was introduced by CU2 and CU3.

  • This problem affects only environments that use the Intune Connector together with Configuration Manager 2012 R2.
  • This problem occurs only when Cumulative Update 2 or Cumulative Update 3 for Configuration Manager is installed.

To apply this hotfix, you must have Cumulative Update 2 or Cumulative Update 3 for System Center 2012 R2 Configuration Manager installed.

For more details and download see http://support2.microsoft.com/kb/3002291

For a complete list of all available hotfixes and update please consult the List of Public Microsoft Support Knowledge Base Articles wiki page.

Advertisements

Troubleshooting Microsoft (Windows) Intune Extensions

Most of you are problably aware of Microsoft (Windows) Intune extensions and using them briefly without any issue(s). New extensions becomes automatically available through the Microsoft Intune connector and new updates are merged or installed to introduce new features taking benefits of the Microsoft Intune cloud services platform.

So far so good…but if you’ve bad luck extensions comes partly down or becomes not available at all to your Configuration Manager instance! Unfortunately there is no way to force a trigger of the tenant discovery process and thus the installation of Microsoft Intune extensions. In normal circumstances it will take up to 24 hours after registering your Intune subscription untill the Intune extensions comes down to your Configuration Manager instance. This pitty if you would speed up the process of installing new deployments or you’re in a disaster recovery scenario. Hereby some guidelines for troubleshooting Microsoft Intune extensions, logs locations(s), Certificate Thumbprint ID, SQL query and validating the connectivity with Microsoft Intune.

Continue reading “Troubleshooting Microsoft (Windows) Intune Extensions”

Microsoft rebrands Windows Intune to Microsoft Intune

Microsoft Intune

Today Microsoft announced they are renaming their mobile device cloud service Windows Intune to Microsoft Intune. Reason in mine opinion Microsoft is sorting to great new features and capabilities like enterprise bulk enrollement, conditional access and extended data leak protection (DLP) which will be expected later this year (Q4).

This change reflects Microsoft’s ongoing strategy for Intune as a cloud-based mobile device management (MDM) and mobile application management (MAM) solution.  The “Microsoft Intune” name more accurately represents Intune’s capabilities, supporting both iOS and Android platforms, in addition to Windows. It is also in alignment with our commitment to embrace the new dynamics of the workplace, and increase employee productivity by enabling them to work wherever and whenever they want on any device, while helping IT keep corporate information secure.

Intune is included in the Enterprise Mobility Suite (EMS) which is Microsoft’s comprehensive and cost-effective solution for addressing consumerization of IT, BYOD, and SaaS challenges. The suite also includes Azure Active Directory Premium and Azure Rights Management (RMS).

Read the the full story here.

iOS 8 Support for System Center 2012 R2 Configuration Manager

Just drop you a quick line support for iOS 8 is now available for System Center 2012 R2 Configuration Manager! Support for iOS 8 on System Center 2012 R2 Configuration Manager was announced recently by the Configuration Manager Team but finally comes down to your Configuration Manager instance.

Standalone Windows Intune was already supporting iOS 8 from day 0 when iOS 8 was released on September 17, 2014.

image

Continue reading “iOS 8 Support for System Center 2012 R2 Configuration Manager”

How secure is Microsoft Intune? Keep calm and reassure your cloud security manager!

computer-security-14

Perhaps you noticed yourself but customers are asking more often how secure Microsoft clouds services are(Microsoft Azure, Office365 & Windows Intune)?  Valid questions like “What- and where my corporate data is stored? How my corporate data is protected in Microsoft datacenters? What security controls in place and what about backup, disaster recovery and data retention policies? Do I have control on what data is going synced to the cloud?” And so we can still go on…

By informing customers and providing them guidelines and best practices it is more clear what the impact of using Microsoft cloud services is for their organizations. This will eliminate possible restraints (rightly or not), increases confidence of cloud service as platform & accelerates the adaption as such.

This post might help you to get better understanding on what terms and conditions Microsoft clouds services performed and enables you to inform your cloud security officer! Continue reading “How secure is Microsoft Intune? Keep calm and reassure your cloud security manager!”

Troubleshooting: Federation for Windows Intune

During a Windows Intune proof of concept (PoC) I was facing some issues configuring federation in order to enable Signle Sign On (SSO).

Proxy Authentication

When configuring federation we couldn’t convert the the default domain to a federated domain type. By using the –Verbose –Debug parameters of convert –MsolDomainToFederated cmdlet the root cause became clear. Proxy Authentication was required and therefore we couldn’t convert the domain. One down two to go!

clip_image001_thumb[3] Continue reading “Troubleshooting: Federation for Windows Intune”

Deploy Active Directory Federation Services (AD FS) 3.0 in a pre Windows Server 2012 R2 era

As you probably know a prerequisite for implementing Active Directory Federation Services (AD FS) based on Windows Server 2012 R2 is to have at least a Windows Server 2012 R2 domain controller available in your infrastructure.

image

This in order to take benefit of using Group Managed Service Accounts (GMSA – generated and maintained by the Key Distribution Service (KDS) on at least Windows Server 2012 domain controllers). The same applies to Device Registration service (DRS) aka Workplace Join, which is responsible for activation and enrolment of controlled devices and represented by a new schema class in Active Directory Domain Services (AD DS). Continue reading “Deploy Active Directory Federation Services (AD FS) 3.0 in a pre Windows Server 2012 R2 era”