• New blog, New content. Links to old posts.

    My role has previously primarily focused on Microsoft Intune, nowadays it’s more towards our whole Enterprise Mobility Suite. This includes Azure AD premium, Microsoft Intune and Azure Rights Management Service. Due to the change of focus (and name change of Microsoft Intune) I decided to create a new blog.
    My previous blogs and content can be found here:

    Tune in to Windows Intune:

    Technical tips related to, mostly, Intune:

    Home is where I lay my head


    Technical stuff from my times as a Senior Premier Field Engineer:

  • Certificate Revocation using Microsoft Intune

    There are several ways to initiate a revocation of a certificate on a mobile device, in this post we will discuss the options and their behavior per platform. It’s important to note that we can only revoke certificates which are delivered via SCEP.

    There are two types of removal:

    1. Due to device wipe/retire or unenrollment.
    2. Due to user leaving the targeted collection/group, deployment being deleted or profile/policy is being deleted.

    From a server side perspective, the certificate will always be revoked on the CA.
    From a client side perspective, the certificate will be removed from the device. This applies to all platforms we currently support: Windows, Windows Phone, Android and iOS with one exception (see below).

    The only scenario is we are currently investigating is removal type 2 in combination with Windows Phone, in certain conditions the certificate is not removed from the device.

  • NDES - Error 12186 in ndesplugin.log

    Are you trying to configure certificate deployment for mobile devices and run into the error 12186 in ndesplugin.log? This post might help you reach a solution.

    The exact error shown in ndesplugin.log is:

    Failed to send http request /CMCertificateRegistration/Certificate/VerifyRequest. Error 12186

    This error occurs if the account under which NDES application pool runs may not have read permission to the client certificate's private key while doing https connection to the Certificate Registration Point (CRP).

    In order to assign this permission connect to the NDES server and perform the next steps:

    1. Get the Unique Container Name of the NDES client certificate:
      certutil -VerifyStore My
      The container will be listed as something similar to this:
      Key Container = fc9b3ab746d7b0739ae8c6c0468e0eb5_6de86d88-a02c-4b33-91b0-43d27ebe455b

    2. Check the location of the certificate by matching the unique container name acquired at step 1 with the filenames, on Windows Server 2012 R2 check this location:
      %ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys
      (these certs will be hidden, use ATTRIB or adjust Explorer to show hidden files.)

    3. Run the icacls.exe command line tool to grant R (Read) permission for the NDES user account (DOMAIN\User).  Make sure you adjust the filename starting with fc9b3……
      iCacls.exe %ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys\fc9b3ab746d7b0739ae8c6c0468e0eb5_6de86d88-a02c-4b33-91b0-43d27ebe455b /grant DOMAIN\User:R

    image

    Restart the NDES server and you should not get the same error. Please consider leaving a reply in case this post helped you.

  • Configure certificate based authentication to Wi-Fi with ConfigMgr and Intune

    Once you have certificate deployment working, you can use it for several purposes. One example would be to use certificate based authentication against Exchange (on-prem), VPN or WiFi Profiles. Certificate based authentication against WiFi profiles is a common ask, in this post I'll explain how to configure this in ConfigMgr 2012 R2.

    1. Create a new WiFi profile.
      image

    2. Enter SSID details.
      image

    3. Select your Security Type, Encryption and “Smart Card or other certificate” and select “Configure”.
      image

    4. Configure as follows: “Use a certificate on this computer”, deselect “Verify the server’s identity…..”  and hit “Advanced”.
      image

    5. Pressing the “Advanced” button will bring you to the “Configure Certificate Selection” dialog.
      Make sure you select your issuing CA and add the “Client Authentication” SKU at the AnyPurpose section. 
      image 

    6. Hit OK until you return to “Add Wi-Fi Profile Security Configuration” wizard (shown at step 3).
      Select the appropriate Root Certificate.
      Select the appropriate Client Certificate.
      image image

    7. After selecting “Next” make sure you enable “Specify Authentication Mode” and select “User Authentication”.
      image

    8. If a proxy is required, details can be provided in the next dialog.
      image

    9. Select the platforms and deploy this profile to a user group.
      image

    After deploying the profile, wait a few minutes and enroll a new user or enforce a policy refresh on Windows Phone 8.1. You phone should connect to the WiFi automatically using the SCEP Certificate.

    If this post helped you, consider leaving a reply.

  • How to assign EMS licenses using the Azure Portal

    In this post I will show you how to assign EMS licenses using the Azure Portal.
    Open a browser, to prevent cookie issues I recommend to use InPrivate mode.

    image

     

    Navigate to http://manage.windowsazure.com/ and sign-in using your administrator account for your tenant (e.g. admin@mycompanyname.onmicrosoft.com)

    image

    After successful logon, on the left side navigate to Active Directory. Select the desired directory.

    image

    After selecting the directory, navigate to the License section.
    Select the EMS licenses that are bound to this tenant. In case your licenses don’t show up you will have to call support to have your licenses assigned.

    image

    From this point you can either assign licenses to individual users or a group.

    image

    After selecting a group or individual you can assign licenses by pressing the “assign” button at the bottom of the screen.

    image

    In case this post helped you, please consider leaving a reply.