I was fortunate enough to attend the 2015 Microsoft Ignite conference in Chicago, along with 23,000 of my closest IT friends. For those of you who couldn’t make it, Microsoft made the sessions available online for on-demand viewing. In the meantime, I’d like to share with you the five key lessons I took away from the Ignite conference.
Today, I’d like to teach you a little bit about PowerShell eventing. It is an asynchronous event handling because we can check the event queue on our own time as subscribed events fire in the background.
In the previous post, we configured the MDT deployment share, imported installation media, and configured the task sequence with applications and additional steps. To capture the reference image, we still need to configure the CustomSettings.ini and Bootstrap.ini files.
Using Microsoft Deployment Toolkit (MDT) to automate the creation of your company images can ensure a clean capture and save time in your deployments. In this guide, we will populate MDT and create our build and capture task sequence.
At Microsoft Ignite 2015 in Chicago, Microsoft unveiled the next preview of Windows Server. In the latest version, not only is the GUI not the default, but it also isn’t installed at all without additional post-install steps. In this tutorial, I’ll show you how you can enable the GUI for those applications that still require a graphical user interface in Windows Server 2016.