About me

Hello, and welcome to my website!

kembit-wrade-nov16006

My name is Rens Hollanders, I’m 33 years old and living in the Netherlands.

I’ve been working in IT for almost 11 years now, over the years I have developed my expertise in the Workplace Architecture with a strong focus on end-point deployments.

I am a accredited CompTia Certified Technical Trainer as I take pleasure in transferring knowledge about the technologies I’m passionate about.

 

Besides working I have some hobbies and interests I’m just as passionate about:
Long time visitor of music venues and festivals
Collecting and listening music on vinyl records mostly Rock oriented
Watching Formula 1 and soccer
Gaming (Battlefield Franchise, SIM Racing)
Small addiction for nice shoes and watches

Please take note that the blogs, information and comments that I write are based on my own personal experience and opinions. And in no way reflects the experience and opinions of others, like vendors, employers etc.

My employer:

 

 

28 thoughts on “About me

    1. Rens Hollanders

      Hi Alexandr,

      Thanks for your comment, could you provide me a copy of your bootstrap.ini and customsettings.ini as well? You can find them in the .\DeploymentShare\Control folder.

      Cheers! Rens

       
      Reply
  1. Christoffer Ramachandran

    Hi Rens,
    Google somehow found your website and I’ve found some helpfull stuff in the long road into MDT (learning).
    I’ve never managed to install drivers during deployment.
    What I’ve tried is to put the drivers in the out-of-box drivers thing and did the big no no and didnt put any filters or anything just put it all there… NO success… Now I have tried to put them as applications and silently install them… then it’s unable to procesd cause the NIC drivers havent been installed. To me its cind of odd cause PE find the NIC but not windows… Um!
    I’ve noticed that the drivers part has been improved since the good old days with RIS… I’ve managed to install Windows but the same issue remains, does *PIIIP*-ing drivers… sigh… 😉

    Hope you can help me out! 🙂

    Cheers!

     
    Reply
  2. Ben

    Rens, Hey.. first off apologies for posting this here but I’m unsure of the right place. I’m looking for some advice on an Office 2016 deployment task. Can I pose a question to you about this and if so what format would you prefer?
    Thanks!

     
    Reply
    1. Rens Hollanders

      Hi Ben,

      Sure my e-mail address is around here somewhere, otherwise send me a DM through twitter.

      Cheers! Rens

       
      Reply
  3. Cor

    I would like to create partitions during a deploy via Wizard of MDT but how do I do that ?

     
    Reply
    1. Rens Hollanders

      Hi Cor,

      This can best be achieved through custom scripting (vbscript) you can create a custom HTA application or use the wizard designer of MDT to create custom pages.
      Unfortunately I don’t have a turnkey solution

      Cheers! Rens

       
      Reply
  4. C

    Hi Rens – do you know if it’s possible to generate the list of task sequences that are displayed by MDT based on the system model, or based on the answers to questions during the MDT interview? For example, only some models would get to choose either Windows 7 and Windows 10 task sequences, while other models would only get a list of Windows 7 task sequences.

     
    Reply
    1. Rens Hollanders

      Hi C,

      Unfortunately this is not the way MDT works or is intended to work. You cannot decide which task sequences are presented per model. However you can initiate a certain task sequence based on a model. This can be done easily in CustomSettings.ini but when things tend to get complex (or your CS.ini is getting larger) I would advise you to incorporate the database functionality of MDT, there you can present task sequences on a make / model based selection, and also per device.

      Cheers! Rens

       
      Reply
      1. C

        Hi Rens – thanks for the answer. We don’t currently use the MDT database, but I will look into it.

        thanks!
        C

         
        Reply
  5. Lars

    Rens, kan je me helpen.
    Op kantoor hebben we een M700z alleen MDT herkent hem niet als een PC of laptop.

    Ik heb het volgende in me Rules staan:

    “[ByLaptop]
    subsection=Laptop-%IsLaptop%
    [Laptop-True]
    OSDComputerName=NB-%AssetTag%
    [Bydesktop]
    subsection=Desktop-%IsDesktop%
    [Desktop-True]
    OSDComputerName=FC-%AssetTag%
    ;Set Computer Name at Deployment
    OSDComputerName=%ComputerType%-%MACHINENAME%

    maar toch geeft hij me een MiniNT-xxxx naam.
    Kan je me helpen ?

     
    Reply
    1. Rens Hollanders

      Goedemorgen Lars,

      Schijnbaar kan het ZTIgather script niet opmaken a.d.h.v. de SystemEnclosureType class (zie https://msdn.microsoft.com/en-us/library/aa394474(v=vs.85).aspx) of het een laptop of desktop is. Wat je kan doen is een powershell prompt openen op het systeem en vervolgens intypen: gwmi win32_computersystem, dan krijg je in ieder geval een Model en Manufacturer terug. Je kan je CustomSettings.ini dan aanpassen naar Priority= Model, ByLaptop, ByDesktop, Default en dan een nieuwe sectie maken met model of manufacturer naam.

      In het geval dat de Manufacturer HP of Hewlett-Packard zou zijn, krijg je dan eenzelfde subsectie als bij [ByLaptop] of [ByDesktop] maar de naam van de sectie is dan de output waarde van de WMI query. Dus [Hewlett-Packard] in het geval van manufacturer, of bijvoorbeeld [ProBook 6560b] in het geval van model.

      Veel succes! Groeten!

       
      Reply
      1. Lars

        Ken je me iets meer op weg helpen?

        dit is wat ik krijg als ik het command van hier boven uitvoer.

        Manufacturer: LENOVO
        Model: 10EY001KMH

        Kan je laten zien hoe ik dit dan in me CS.ini kwijt kan ?

         
        Reply
        1. Rens Hollanders

          Hoi Lars,

          Voeg het volgende toe in je CS.ini

          Boven in staat nu Priority=ByLaptop, ByDesktop, Default. Voeg daar nu aan toe/tussen: Priority=Model, ByLaptop, ByDesktop, Default

          En dan voeg je een subsectie toe in je CS.ini eronder:

          [10EY001KMH]
          OSDComputerName=FC-%AssetTag%
          ;Set Computer Name at Deployment
          OSDComputerName=%ComputerType%-%MACHINENAME%

          En daarna volgen dan de secties die je al had staan:
          “[ByLaptop]
          subsection=Laptop-%IsLaptop%
          [Laptop-True]
          OSDComputerName=NB-%AssetTag%
          [Bydesktop]
          subsection=Desktop-%IsDesktop%
          [Desktop-True]
          OSDComputerName=FC-%AssetTag%
          ;Set Computer Name at Deployment
          OSDComputerName=%ComputerType%-%MACHINENAME%

          Groeten Rens

           
          Reply
          1. Lars

            Top het werkt, bedankt.
            Kan ik je nog een par vragen stellen waar ik niet helemaal mee uitkomen?
            Heb je misschien een email adres waar ik je op mag mailen of mag ik ze hier bij zetten ?

             
  6. Craig

    Hi Rens

    Sorry to bother you again. Last time I promise 🙂

    I opened the deployment share VIA the MDT workbench on my production server and could not view the apps, TS’s and OS etc. id ran a DS update hoping this would fix the issue.

    I can no longer view it via MDT workbench on either server although I can browse the share just fine and the deployment wizard still works.

    What have I done? Do you have any suggestions to fix it?

    Thanks
    Craig

     
    Reply
    1. Rens Hollanders

      Hi Craig,

      No problem, when you upgrade the MDT deploymentshare certain scripts and xml files are overwritten with newer files. In the control folder you will find an xml file called version.xml. This gets updated when you update the deployment share. You can lower the mdt version inside this xml file manually or you recreate a new deployment share with the older version of MDT and replace the version.xml of that share with the share you currently cannot open. After this try mounting the share with your old MDT version.

      Let me know.

      Cheers! Rens

       
      Reply
      1. Craig

        Hi Rens

        Thanks for responding.

        I tried restoring to a previous version but both files have the same number 6.3.8330.1000

        I also tried to restore all the files with the control folder but still no change.

        Thanks
        Craig

         
        Reply
        1. Rens Hollanders

          Craig,

          Did you manually lower the version number in the version.xml? Do you have a proper file level backup so you can go back prior the situation?

          Cheers! Rens

           
          Reply
  7. Aady.

    Hi, Admin.

    it will be really great help, if you could write a post on how to only clean C drive and install windows in MDT 2013. Suppose OS is installed already installed and user has some data in the D drive. So what can be done, so that MDT will only clean C drive and install to it, without touching data on D drive.

     
    Reply
    1. Rens Hollanders

      Hi Aady,
      Be aware that automation (like MDT) drivers on constants, things that are always the same, so you can assume things. Let’s say that if you have deviant disk configurations you need to custom script exactly what you want to achieve.
      I think you need to have a look at the MDT refresh scenario: https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10, also you can specify which drive to install the operating system on. This can be found in the “install operating” step in your task sequence. Lastly you can create a custom script which formats the designated partition (usually the 2nd partition) prior to the installation of the operating system. So there should be enough possibilities to sort this out.

      Cheers! Rens

       
      Reply
  8. Betsy Brahm

    I’m in the process of studying for the 70-695 test. While deep into troubleshooting my Win 2012 Config Manager 2012 R2/MDT/WDS server and the HyperV client OS’s……. I bumped into your Webpage and what a delight it is. Troubleshooting tips from the field, just what I need!! Thank you for taking the time and sharing your knowledge and experience. I hope knowledge-sharing brings you good karma.

    Thanks
    Betsy Brahm
    San Francisco CA

     
    Reply
    1. Rens Hollanders

      Hi Betsy,

      Great to hear. I wish you the best of luck with your exam. Kind regards,

      Rens

       
      Reply
  9. Mo

    Hi Rens,

    Thanks for ur great posts. I had a quick question, i have implemented MDT/WSUS for the build and capture at the company i am working for. One of the company policy is to completely disable 8.3 notation. In my ts i run the command cmd /c fsutil 8dot3name set 1
    after the Tattoo. With fsutil query C: i can see that 8.3 notation is disable after the Install Operating System fase but still when i do a dir /x on C:\windows or C:\Windows\system32 i still see shortfiles names.
    I have even put the command between the format disk and install operating system but unfortunatelly no change.

    Thanks in advance.

    Regards
    Mo

    PS: The same command works perfect when doing a build and capture in Sccm.
    I even commented out the 8.3 part in LTIapply.wsf script but still no change. Shortnames are still there after the Install OS step. I am using MDT 2013 version 6.3.8443.1000 to capture a Windows 7 OS.

     
    Reply
    1. Rens Hollanders Post author

      Hi Mo,

      Thank you for your question. I don’t have any experience with disabling 8.3 notation. However my question would be, is MDT or SCCM the perfect way to achieve this solution? Could it be done any other way? Like GPO for instance

      Cheers! Rens

       
      Reply

Leave a Reply

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