CMG – Post to http://.COM/CCM_Proxy_MutualAuth//ccm_system/request failed with 0x87d00231.

Following up on a similar post I did here about requiring Azure AD User Discovery and Active Directory user discovery so Windows 10 machines can communicate over the CMG using Hybrid Azure Active Directory  – https://nhogarth.net/2018/10/26/sccm-1806-cmg-hybrid-azure-ad-failed-to-get-ccm-access-token/

You may run into an issue where a specific Windows 10 client cannot communicate with the CMG. In ccmmessaging.log you will see “Post to http://<CMG&gt;.COM/CCM_Proxy_MutualAuth/<ID>/ccm_system/request failed with 0x87d00231.”

You can run through the CMG Connection Analyzer to confirm that everything is working fine.

cmg01

Then you realise it is something on the Windows 10 device end.

If you run “dsregcmd /status” and see that AzureAdJoined is set to No, then you know that the device is not Hybrid Azure AD joined, thus it cannot communicate with the SCCM CMG.

cmg02

This particular machine was put in an OU that was not synced to Azure AD using Azure AD Connect. After moving it in the correct OU and doing another Azure AD Connect Sync (Start-ADSyncSyncCycle -PolicyType Delta) the device can then communicate over the CMG fine.

cmg03

Advertisements

Conditional access – Require app protection policy

Microsoft recently added “Require app protection policy (Preview)” to conditional access. App Protection Policies in Intune are a great way to secure the apps on either a managed device or an unmanaged device.

Suggested Reading – https://docs.microsoft.com/en-us/intune/app-protection-policy

This blogpost will show creating an example Conditional Access policy leveraging the “Require an app protection policy (Preview)” control, targeting Exchange Online, and the user experience for a device that does not have any App Protection Policies assigned.

In devicemanagement.microsoft.com go to Conditional Access, and create the new policy.

01

Give the policy a name, and in my policy I am testing out this policy, so I have only targeted one user.

02

I will be testing this policy only for Exchange Online.

03

I will only be using iOS and Android for this policy.

04

I have configured the conditions for all apps.

05

I have selected the control to require app protection policy.

06

The policy has now been created and enabled.

07

Below is the user experience when trying to add an email account targeted by the CA policy to the native mail app on an iOS device. You can see that it is blocked (similar to what happens if you require an approved client app in the CA policy)

08

Now If I try and setup the account in Outlook, I get the error saying that no application protection policies have been assigned.

09

 

 

 

 

 

 

Intune – BitLocker Encryption report (Preview)

In the Whats new Page for Intune (https://docs.microsoft.com/en-us/intune/whats-new), you can see that Microsoft recently added some BitLocker encryption reports in Preview.

For more information: https://docs.microsoft.com/en-us/intune/encryption-monitor

To access the Bitlocker reports, go to the Intune portal (portal.azure.com or devicemanagement.microsoft.com) and go to Device Configuration > Encyrption report (preview)

An example of the Bitlocker report is below:

BitLocker01

You can also use the Filter button to filter the encryption readiness by Ready/Not ready and Encryption status by Encrypted/Not encrypted

BitLocker02

The example below shows the devices that are not encrypted:

BitLocker03

Hybrid Azure AD Tip – The device object by the given id (ID of machine) is not found.

Recently when working with a customer I was troubleshooting why their devices were showing up as Azure AD Registered in the Azure portal in Azure Active Directory when they should be Hybrid Azure AD joined. These were Windows 10 1809 devices.

When running “dsregcmd /status” on one of the machines, it would show as AzureAdJoined : NO. When it is Hybrid Azure AD joined, it should still say Yes.

If you run the command as admin, you will see there is Diagnostic Data section. On my devices, it said:

Client ErrorCode : 0x801c03f2
Server ErrorCode : DirectoryError
Server Message : The device object by the given id (guid) is not found.

This is because the device(s) has not been synced to Azure AD by Azure AD Connect. Make sure that the OU’s that the computer objects are in are set to sync to Azure AD. In my customer’s configuration, they had additional filtering where the users and computer objects needed to be in a Security Group to be synced to Azure AD.

Once the Azure AD Connect sync had completed successfully, and the device registration task had run again on the client, the machine now shows as Hybrid Azure AD joined in the Azure portal.

 

Intune – iOS – Profile installation Failed

When enrolling an iOS device in Intune, it may fail at the Installing Management Profile with the error “Intune – iOS – Profile installation Failed A connection to the server could not be established.”

01

If you happen to see this error, login to the Intune portal and go to Device Enrollment > Enrollment restrictions > and look through your existing restrictions to see if there are any settings blocking personal enrollments.

02

The example below shows that there is an enrollment restriction blocking personally owned iOS devices.

03

For the iOS to be enrolled, it needs to be a corporate owned iOS device. From https://docs.microsoft.com/en-us/intune/corporate-identifiers-add

At the time of enrollment, Intune automatically assigns corporate-owned status to devices that are:

  • Enrolled with a device enrollment manager account (all platforms)
  • Enrolled with the Apple Device Enrollment Program, Apple School Manager, or Apple Configurator (iOS only)
  • Identified as corporate-owned before enrollment with an international mobile equipment identifier (IMEI) numbers (all platforms with IMEI numbers) or serial number (iOS and Android)
  • Joined to Azure Active Directory as a Windows 10 Enterprise device
  • Set as corporate in the device’s properties list

Tip – Using Azure AD Monitoring to track Conditional Access failures

If you ever wanted to have an overview of the devices in your environment that have have been blocked from accessing cloud resources due to Conditional Access, then you can use the Monitoring Sign-Ins feature in Azure AD. Using this really simple feature, you can view the user name, the application that the user used, the operating system, and the actual conditional access policy that blocked the user from accessing the cloud resource.

This post will show how you can use Azure AD Monitoring to find devices that failed to meet the needs of the Conditional Access. In my example I have a simple Conditional Access policy for iOS devices that require the device to be compliant to access Exchange Online. I will test accessing Exchange Online using the Outlook mobile app on an iOS device that is not enrolled in Intune.

In Azure Active Directory in either https://devicemanagement.microsoft.com/ or https://portal.azure.com, go to Azure Active Directory and you will see a section called Monitoring. Under Monitoring, you will see Sign-ins.

If you click on Sign-ins, you can then use the drop downs and buttons to view specific information. For example, if you click on Columns you can choose to hide or show certain columns to get the information that you need.

Columns

 

In the example below I have clicked the drop-down under Conditional Access and selected Failure so I can see the devices that have been blocked due to not meeting the Conditional Access policies. In the screenshot below you can see there is an iOS device that used the Outlook Mobile app with a Conditional Access failure.

CAPolicy

 

If you select this, you can then view more information about the device including Username, Application, Client App, and you can also view the Conditional Access policy name that it failed on by clicking on the Conditional Access tab.

In the example below you can see that I have a Conditional Access policy called “Exchange Online iOS Managed Only Devices” with the Grant control of “require compliant device” and that my device failed against this Conditional Access policy.

CADetails

Conditional access – third party apps

This post will show how you can add a third party app to Azure AD that supports SAML, and then create a conditional access policy so that only compliant devices can access the third party cloud resource.

In my example I have signed up for a GoToMeeting trial. I will add GoToMeeting app to Azure AD and configure the single sign-on options to use SAML, and then on the GoToMeeting side I will configure Azure AD to be the Identity Provider. Once this is set up, I will create a Conditional Access policy that will require devices to be compliant in order for them to access GoToMeeting. When logging in with a work account to GoToMeeting, GoToMeeting will then redirect me to sign in through Azure AD, and then the conditional access policy will kick in.

Always test conditional access with test users, and plan thoroughly for any changes in a Production environment. The information below is for testing purposes.

Recommended reading:

Single Sign-On SAML protocol
https://docs.microsoft.com/en-us/azure/active-directory/develop/single-sign-on-saml-protocol

Single sign-on to applications in Azure Active Directory
https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/what-is-single-sign-on

Tutorial: Azure Active Directory integration with GoToMeeting
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/citrix-gotomeeting-tutorial

What is conditional access in Azure Active Directory?
https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/overview

Tutorial: Configure GoToMeeting for automatic user provisioning
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/citrixgotomeeting-provisioning-tutorial

In Azure Active Directory, go to Enterprise applications then click on New application.

01

Search for the application. Note that it says it supports SAML based sign-on for the Single Sign-On Mode. Click on Add.

02

Once the application has been added, I will give access to my test users by clicking on Users and groups, and then Add user.

011

Now I will configure SAML for the single sign-on mode. Click on Single-Sign-On on the left hand side, then select SAML.

04

In the Identifier (Entity ID) I have put in https://authentication.logmeininc.com/saml/sp and Reply URL (Assertion Consumer Service URL) https://authentication.logmeininc.com/saml/acs and Relay State
https://global.gotomeeting.com

05.jpg

Now I am going to download the Federation Metadata XML and upload it to the GoToMeeting site.

06

When logging in with my admin account in https://organization.logmeininc.com/ on the Identity provider section, I have selected to Upload SAML metadata file. This will contain all the Azure AD information and then configure Azure AD as the identity provider.

07

Now with a user I will login to https://www.gotomeeting.com/meeting/sign-in and select My Company ID so it can redirect me to my identity provider (Azure AD)

08

As expected, it has redirected me to Azure AD. I can confirm that the the SAML single sign-on mode has been configured successfully.

09

Next I will add the conditional access policy.

10

For the Cloud apps, you can see that GoToMeeting now appears because we added it earlier. I will select this as the Cloud app.

11

I will configure it to apply to all device platforms.

12

I have configured it to apply to Browser, and mobile apps etc.

13

In this test example, I have configured it to require only Intune enrolled compliant devices to access GoToMeeting.

14

Now lets login to https://www.gotomeeting.com/meeting/sign-in with the My Company ID

08

It will redirect us to Azure AD as we configured Azure AD as the identity provider earlier (and the domain used in my UPN was also added and confirmed in GoToMeeting)

15

Now because my device is not enrolled into Intune, I am blocked from accessing the GoToMeeting cloud resource as expected.

16

I have installed the GoToMeeting app on an Android phone, and it is the same expected user experience.

IMG_1295

On an Intune enrolled compliant device I can login fine as expected (or you can launch the app from myapps.microsoft.com

17