Windows PowerShell 6 (IT Pro Solutions)

Available in Kindle or paperback format.

Practical and precise, this hands-on guide with ready answers is designed for IT professionals working with Microsoft products, whether for on-premises, hybrid or cloud support. Inside, you’ll find expert insights, tips, tricks and workarounds that will show you how to make the most of Windows PowerShell in the shortest amount of time possible. During the course of reading this book, you will master a number of complex topics, techniques, commands and functions.

Windows 10, version 1903 and Your Phone

If you have not yet heard, the Windows 10, version 1903 adds support to view and control certain smart phones using the mouse and keyboard of your computer. More details on this can be found on this Microsoft site

These are the system requirements to accomplish this;

  • Select Android phones* running Android 7.0 or greater (*Samsung Galaxy S8/S8+/S9/S9+).
  • Windows 10 PC with a Bluetooth radio that supports low energy peripheral role.
  • Latest 19H1 preview build (18342+ recommended).
  • Android phone must be on, within Bluetooth range of the PC, and connected to the same network as the PC.

If your PC does not have a Bluetooth radio which supports low energy peripheral role, it is as simple as purchasing one and plugging it in. Here is a Bluetooth which is compatible;

Driver Injection

When deploying Windows from a custom WinPE and the walkthrough-deploy.bat from Microsoft’s sample script (in the, you need to either;

  1. Create a model specific image, with device drivers built-in
  2. Manage driver injection, just in time, after Windows is installed on the hard drive, but while the PC is still booted in the WinPE environment

This page describes one possible solution for the 2nd of the two, where¬† you can deploy the Windows image, then dynamically lookup the device details from the firmware (the BIOS or UEFI) and load matching drivers to the device, just-in-time, at deployment time. Continue reading “Driver Injection”

Remove default PXE boot manager timeout in WDS

Windows Deployment Services automatically has the PXE boot menu set to a 30 second timeout. While this can be useful, many users decide they want to remove the timeout value. Removing the timeout value is useful if you typically image multiple computers and do not want the PC to automatically select a boot image when a reboot from the network occurs and if you cannot  be present during the 30 second opportunity. Continue reading “Remove default PXE boot manager timeout in WDS”