• Hotfix: Large URI request in Web Application Proxy on Windows Server 2012 R2

    In one of the last posts we discussed the option to put a Web Application Proxy in the DMZ as a reverse proxy for NDES. You could request a hotfix via Microsoft Support in order to get this to work. The good news is that you no longer have to contact support, it’s available in the in the December Windows Update:

    Large URI request in Web Application Proxy fails in Windows Server 2012 R2
    http://support.microsoft.com/kb/3011135

    Just install the latest Windows Update on your Windows Server 2012 R2 and you should be good to go:

    December 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
    http://support.microsoft.com/kb/3013769

  • Force a refresh of Microsoft Intune policies on iOS

    When testing new policies or deploying applications it’s useful to force a policy refresh. In iOS you can force this when using the latest Company Portal.


    Follow these easy steps:

    1. Open the Company Portal
    2. Select your device in use
    3. Hit the Sync button

    Checkin

  • 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.

  • 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.