About me

  LinkedIn | 

I’m a Dutch Cloud Infrastructure DevOps Architect with over 15 years of experience in the Microsoft Cloud business.Currently employed at internedservices, one of the leading hosted cloud providers in The Netherlands. Internedservices is a subsidiary of KPN, one of the biggest telecom providers of the country.

The last couple of years my interest, passion and focus shifted to multitenancy, deployment and automation in the hosted and public cloud.  I will try to cover interesting subjects relating to deployment and development in these clouds which aren’t covered yet in other blogs.  Expect topics about Azure, Azure Stack, SDDC, Software-Defined Storage, Networking, PaaS, aPaaS, SDWAN, Express Route, Hybrid Cloud, MicroServices,Containers and so on.


Skip to comment form

  1. Shawn


    First, thank you for this article:

    I experienced the issue with ShrewSoft VPN and uninstalling/installing the filter manually solves my issue. However, the fix does not survive reboots with the latest build of Windows 10 (10130). Do you experience the same issue?


    1. Ruud Borst

      Great, then you have to install the fixes from Citrix, scroll down the post and read the ‘Still Problems?’ section.

  2. Rhodesie


    Great site here, just stumbled across it.

    I just read your article about setting up user provisioning in Azure without DirSync and AADConnect.


    We have multiple domains connecting to multiple instances of Office 365 very similar to how you have set it up using the ImmutableID to the base64 encoded string of the domain user’s ObjectID value via FIM etc., and everything has been working sweet with ADFS and SSO.

    The issue I have faced recently is one of our customers wants to set up Exchange Online and remote migrations aren’t picking up any users UNLESS they have been provisioned via AADConnect. Checking the difference between a user we provision and one done via AADConnect via Azure AD Powershell and the only thing I can see is the LastDirSyncDate value is set for the AADConnect user whereas our ones aren’t.

    I was just wondering if you had ever encountered this issue before and/or whether or not you have heard of a way to manually adjust the LastDirSyncDate attribute against a user account in Office 365?

    Anyways cheers mate,


    1. Ruud Borst

      Hi Rhodesie, I didn’t stumbled upon your problem because we don’t do migrations of mailboxes. It seems that AADconnect sets the LastDirSyncDate via the custom API’s it uses to sync all data to AzureAD. The attribute can’t be modified with PowerShell or AzureADGraph, it’s read-only, see here https://msdn.microsoft.com/en-us/library/azure/ad/graph/api/entity-and-complex-type-reference#UserEntity

      The only way to set it is via the same API’s AADconnect is using, you have to find out and maybe trace the calls and see if you can do the same.
      Maybe someone at the Technet forums knows how to resolve your Exchange migration problem without modifying the attribute? I hope your problem will be resolved and my apologies for the late anwser, your comment got clouded with all the comment spam.



  3. Claus

    Thanks to Ruud, the author of this article !!

    According to “Shawn” I must say, that with win10 build 1607 and all patches up to 01.Sept.2016 the posted fix (reinstalling Shrewsoft-Service) everything workes fine – even shutting down the machine and used it the next day, Shrewsoft VPN connected properly to the remote host and established security associations.
    Status: 09.09.2016


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">