MCT Program Requirements Update – effective September 2015

MCT Program Requirements Update – effective September 2015:

Current MCT Program Renewal Requirements: (/learning page)

  • Possess a current Microsoft Certification or qualification eligible for the MCT program.
  • Meet the minimum instruction quantity of at least 1 class in the previous 365 days as validated by Metrics that Matter (MTM).
  • All Microsoft training (not just MOC) will be recognized as credit toward program renewal as long as it can be measured in Metrics that Matter (MTM)* – NEW
  • Meet the minimum instruction quality of an average instructor score of at least 7 as validated by MTM.*
  • You can check your MTM records by following these steps.
  • If you taught classes but didn’t use MTM you can add the course to MTM.

*The existing exception process will still apply for ITA, Academic, Microsoft Employee (FTEs) MCTs

Changes for MCT Program Entry/Renewal– New: The MCT Program is updating our order management system to be more efficient and to better serve your needs. In doing so, we are making the following changes:

  • MCT Renewal Window Extended to 90 Days
    • The renewal window for MCTs and MCT Alumni has been extended from 30 days to 90 days. MCTs and MCT Alumni can now start to renew their membership 90 days prior to their anniversary date. All MCTs and MCT Alumni will be receiving email renewal reminders 90, 60, 30, and 15 days prior to their anniversary date.
  • Currencies and Payment Types – effective September 2015
    • Currencies to be supported will be US Dollar (USD), British Pound (GBP), Australian Dollar (AUD), Euro (EUR),and Japanese Yen (JPY)
    • Payment methods supported will be Credit Card and PayPal


For any questions, please refer here.


Media Creation Tool for Windows 10

If you need to install or reinstall Windows 10, You can use the Media Creation Tool to create a installation media using either a USB flash drive or a DVD.

You will be able to create a media for the following Windows 10 versions

Windows 10 Home
Windows 10 Home N
Windows 10 Home Single Language
Windows 10 Pro
Windows 10 Pro N
x86 & x64

Download: Media Creation Tool x86 or Media Creation Tool x64

For Enterprise editions please visit Volume Licensing Service Center

Access Director 3.0 Released

The future of Windows is coming on July 29

To make your next Windows experience even better – We have just released the next version of Access Director.                                                                                               Using Access Director you will be able to secure your desktop, simple and easy!

– Run your desktop in a non-elevated user context
– Elevate only needed applications with a single click
– Elevate in your current user-context without affecting other unsecured applications like IE or Office

What’s in Access Director 3.0 ?

– Updates to support the next Windows experience (10)
– Support for integration modules
– Minor bug fixes

Get it from the Download Center

Direct Download Link

Installing .NET Framework 3.5 with MDT 2013 the simple way

In my case I need to automate the installation of .NET 3.5 within a MDT 2013 build and capture task sequence for Windows 8.1

In the State restore add a step to set the WindowsSource Path
The Windows Source will be located within the Operating Systems folder on your Deployment Share

  1. Add a Set Task Sequence Variable step
    1. Type Task Sequence Variable: WindowsSource
    2. Type Value for your source files: %deployroot%\Operating Systems\Windows 8.1 x64 Enterprise VL\Sources\SXS

Set Task Sequence Varable

  1. Add a Install Roles and Features step
    1. Select your Operating System within the step
    2. Mark .NEt Framework 3.5 (Includes .NET 2.0 and 3.0)

InstallRoles step MDT

Is it that simple? Yes!

NOTE: If you want to use a Run Command Line to install it, you could use something like this: DISM.exe /online /enable-feature /featurename:NetFX3 /All /Source:”%deployroot%\Operating Systems\Windows 8.1 x64 Enterprise VL\Sources\SXS” /LimitAccess

Installing UniFi controller in Debian 7 (wheezy)

Installing UniFi controller in Debian

1. Edit /etc/apt/sources.list
# Ubiquiti UniFi updates
deb debian ubiquiti

2. Add GPG keys
sudo apt-key adv –keyserver –recv C0A52C50
sudo apt-key adv –keyserver –recv 7F0CEB10

3. Run the following commands
sudo apt-get update
sudo apt-get install unifi

It should now start and be running at https://:8443/


You might have to modify the path in for java in /etc/init.d/unifi                                                I had to change this from JAVA_HOME=/usr/lib/jvm/java-6-openjdk to  JAVA_HOME=/usr/lib/jvm/java-6-openjdk-amd64

UniFi Controller default TCP ports:

unifi.shutdown.port=8081 (for management purpose)
unifi.http.port=8080 (device inform)
unifi.https.port=8443 (controller UI / API)
portal.http.port=8880 (portal redirect port for HTTP)
portal.https.port=8843 (portal redirect port for HTTPs)
unifi.db.port=27117 (local-bound port for DB server)

And UDP port 3478.

Installing mFi controller in Debian 7 (wheezy)

I’ve been running the mFi controller on a Windows server, but wanted to move it to my Debian box – The install for Windows is quite simple, click and run – but for Debian a few more steps is required, so here is what I did to get it up and running

I am running Debian 7 (7u2 – Wheezy)

1. Edit /etc/apt/sources.list
## Debian Wheezy (7.0)
deb debian ubiquiti

2. add GPG Key
sudo apt-key adv –keyserver –recv C0A52C50

3. Run the following commands
sudo apt-get update
sudo apt-get install mfi

It should now start and be running at https://<yourserver>:6443/

NOTE: If your not already running MongoDB, The installation guide can be found here Install MongoDB on Debian

EasyBoot USB 1.1 has been released

Simpel, but very helpful tool to create Windows Boot or To-Go USB sticks

Download Link

It’s that simple, EasyBoot USB with 4 easy steps and you are ready to go.

  1. Insert USB stick
  2. Choose between the following types
    1. UEFI
    2. BIOS
    3. Windows To Go
  3. Browse to your ISO file
  4. Click Start

EasyBoot USB

The tool is pretty much self-explanatory

Do not hesitate to ping me with bugs, feature requests or ideas for new tools 🙂




Automating Windows 10 Enterprise Technical Preview with MDT 2013 Update 1 Preview

To follow-up on my earlier post “Deploying Windows 10 Enterprise Technical Preview with MDT 2012 Update 1 Preview” Let’s try to do a little automation to make the deployment experience a little smoother.

We just need to do a little configuration within the Microsoft Deployment Toolkit 2013 Update 1 Preview.

The first thing that comes to mind is, when we PXE/media boot our client.
We are shown the Microsoft Deployment Toolkit Welcome Wizard. We need to click Run the Deployment Wizard to install a new Operating System.

Note that in this picture is also the option to set Default Keyboard layout for Windows PE as well as a Static IP. I’m going to assume that we always have DHCP in place and accessible for our clients.

To skip the Welcome Wizard:

  1. Right Click your Deployment Share
  2. Click Properties
  3. Click Rules
  4. Click Edit Bootstrap.ini
    1. The bootstrap.ini contains configuration needed before we connect to our Deployment Share.
    2. Keep in mind that all changes here will not be reflected until a new media has been generated.
  5. in the [Default] section right under that path to your DeployRoot add: SkipBDDWelcome=YES
  6. Close the editor
  7. Click Ok to close Deployment Share Properties
  8. Right click your Deployment Share
  9. Click Update your deployment share
  10. Click Next
  11. Click Next
  12. Click Finish
  13. The ISO and WIM image within the Boot folder of your Deployment Share has now been updated – attached ISO media to VM or update WIM file on your Windows Deployment Server. I’m going to copy the Wim to my Hyper-V Host and mount it in my test VM.
  14. Boot your client to verify the changes

Next up – User Credentials Prompt

MDT User Credentials Wizard

Specify credentials for connecting to network shares

This is where need to type in the credentials for the Deployment Share. This is the last prompt before we start processing data from the Deployment Share – so we need to edit bootstrap.ini again

  1. Right Click your Deployment Share
  2. Click Properties
  3. Click Rules
  4. Click Edit Bootstrap.ini
  5. in the [Default] section right under that path to your SkipBDDWelcome add: UserID=<someusername>
    UserDomain=<domain or servername>

    1. The UserID can we a local account on the server hosting our Deployment Share.
    2. UserDomain must reflect if the account is Domain based or local on our Deployment Share server
    3. We only need NTFS read rights (and of course read share permissions) for the Deployment Share
  6. Close the editor
  7. Click Ok to close Deployment Share Properties
  8. Right click your Deployment Share
  9. Click Update your Deployment Share
  10. Click Next
  11. Click Next
  12. Click Finish
  13. Update your ISO or PXE Media
  14. Boot your client to verify the changes

We are now taken directly to the Task Sequence wizard

MDT Task Sequence list

Select a task sequence to execute on this computer

Let suppose that we only have and need one task sequence job – lets automate this step as well

Changes will be a bit easier this time, hence we don’t need to update the ISO or PXE media each time – we are now working with CustomSettings.ini

  1. Right Click your Deployment Share
  2. Click Properties
  3. Click Rules
  4. in the [Default] section right under the last line (In my case its SkipBitLocker=Yes) add:
    1. SkipTaskSequence=Yes
    2.  TaskSequenceID=IW10ETPX64
      1. The Task Sequence ID can be found in Task Sequences tab under the Deployment Share
  5. MDT Task Sequence list

    List of Task Sequences within your Deployment Share

  6. Click Ok
  7. Boot your client to verify the changes

You should now be brought directly to the Computer Details page

Domain or workgroup information

Domain or workgroup information

I’m going to keep this window visible for the computer naming part, but it can of course be skipped. It will require two skip options:

  • SkipComputerName=Yes
  • SkipDomainMembership=Yes

You could also just prepopulate the fields in CustomSettings.ini for either Domain or Group


  • MachineObjectOU=OU=Staging,DC=CLientgeeks,DC=com


  • JoinWorkgroup=SomeWorkGroup

It will automatically use the account used to connect the network share, you can for obviously reasons use a different account

  • JoinDomain=ClientGeeks.local
  • DomainAdmin=DomainJoinAccount
  • DomainAdminPassword=Pa$$w0rd1

The great part of working with CustomSettings.ini is that there is no need to rebuild boot media – changes are effective immediately – go ahead and give it a try

When you boot your client again with the latests additions, we have arrived at Move Data and Settings:

move user data and settings

Move data and settings from a previous version of Windows

The default option for this step is: Do not move user data and settings, If we where to just skip this step, the outcome would be no data and settings backup

  • SkipUserData=YES

Some other configuration options are:

  • USMTOfflineMigration=True
  • DoNotFormatAndPartition=Yes
  • OSDStateStorePath=\\MDT01\StateStore$

Configure CustomSettings.ini and boot the client again – you could also just click next, BUT we know that testing is good, and more testing is better! 😉

Next up is the Locale and Time Zone selection

Specify locale and time preferences

Specify locale and time preferences

The valid skip options:

  • SkipLocaleSelection=Yes
  • SkipTimeZone=Yes

I’m going to configure the optional options just as default

  • KeyboardLocale=0409:00000409
  • UserLocale=0409:00000409
  • UILanguage=en-us
  • TimeZone=004
  • TimeZoneName=Pacific Standard Time

If you ready and retry – you should now only be prompted with a “Ready to begin” and a blank details section, don’t see any need for this page, so let’s just skip this as well

Ready to begin

Ready to begin

This can be skipped with the follwing option:

  • SkipSummary=Yes

Let try it out! 🙂

Hopefully you have achieved an automated installation progress now

Installation Progress

Installation Progress

The IT Organization and Running Package name can also we changed, here is an example that includes the current date and tasksequence ID using a variable – can of course just be static text.

  • #day(date) & “-” & month(date) & “-” & year(date)#
  • _SMSTSPackageName=%TaskSequenceID%
Customized Installation Progress Window

Customized Installation Progress Window

Here is a snip of my CusomSettings.ini and Bootstrap.ini – yours should look similar to this








TimeZoneName=Pacific Standard Time

SkipSummary=Yes #day(date) & “-” & month(date) & “-” & year(date)#






Have fun deploying! 🙂