Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Microsoft have posted about resuming the rollout and how they test and validate updates over on the Windows blog. There’s also a good post on the Windows IT Pro blog regarding the volume license availability of the new update.

Update v1.2 Download for Windows, Mac and Linux This is a minor update to all versions of 3D Maze Remix. The changes can be seen below. V 1.2 Change Log Added walk forward/backward control to the left and right mouse buttons, for one handed play. Slight redesign to the controls screen. Some control labels have been fixed for consistency. Slight title screen redesign. If you have any questions or comments, please leave them below.

Update 2019-06-16 I recently learned that Office 365 licensing can be managed via Azure Active Directory’s group based licensing feature and I have since switched to using this and have retired this script. I’ll leave this post and the script itself available here, on the Microsoft TechNet Gallery and GitHub, but I’ll not be developing the script any further. For more information on Azure Active Directory group-based licensing please check out Microsoft’s documentation here and here to start with.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Hi all, Given I’ve posted my usual guides on how to deploy Windows 10 1809 with MDT, I thought it important to also post that Microsoft has chosen to delay the rollout of Windows 10 1809 and Windows Server 2019 for the time being due to some users reporting that files are missing after an upgrade.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. Continuing from a previous post: Building A Windows 10 1809 (October 2018 Update) Reference Image with MDT, this post will walk through creating a Deployment Share to deploy the Windows 10 reference image. It is assumed that you have a Server or PC with Microsoft Deployment Toolkit and it’s dependencies installed and have been through the post previously mentioned.

Update 2018-11-13: Microsoft has resumed the rollout of Windows 10 1809, Windows Server 2019 and Windows Server, version 1809. The ISO’s are now available to download from the Volume Licensing Service Center once again. This post will walk through installing and configuring Microsoft Deployment Toolkit to build a reference image of Windows 10 1809 (October 2018 Update) using a Hyper-V Virtual Machine. It is assumed that you have a Server or PC ready to install MDT onto and create an file share for MDT to build the image with.

I’ve been revisiting my MDT process as I wanted to try and use Windows Update to get drivers during deployment - by itself this is not a problem, I can just remove the WSUSServer=http://wsus:8530 configuration from the CustomSettings.ini. However as the device is added to the domain, Group Policy will configure the device to use the local WSUS for updates, this is desired as I still want to use WSUS for future updates, but I want to use Windows Update during deployment.

Windows Server Update Services, along with a growing list of other traditional Microsoft server products, seems to be in ‘maintenance mode’ at best. It’s been on my mind as to whether they’re going to release a cloud based version in Azure (unless they already have something like that and I’ve missed it) or if they’re going the route that I think they are: just update from the internet and don’t worry about it, which seems to be the answer when looking at Windows Autopilot.

Download it from the Microsoft TechNet Gallery the PowerShell Gallery and GitHub. Today I’ve released an update to my Hyper-V Backup Utility. In version 4.3 I’ve added the ability to specify the Hyper-V Virtual Machines you wish to backup using a TXT file. I’ve also improved some of the commenting and cleaned up some of the code. Whether you are running Hyper-V on a Windows 10 desktop or a Windows Server 2016 cluster, this utility can be used to backup your virtual machines.

PowerShell based network attached device monitor Please consider donating to support my work: You can support me with a one-time payment using PayPal Network Device Status Monitor can also be downloaded from: The PowerShell Gallery Please report any problems via the ‘issues’ tab on GitHub. -Mike Features and Requirements The utility can output the network device name and IP address as specified in the CSV file.