Usually you use a usb cable to power and programAdafruit Feather HUZZAH ESP8266 via the mini usb port:
But what if you want to use external 3.3V (or 5V) power supply? To which pin should you connect it?
Sometimes we need to create users/groups/computers in Active Directory that will be used temporary (by a contractor, for testing etc.). The typical workflow is: Create > Use for a while > Delete. The deletion is manual and often these objects are being forgotten which poses some security risks.
It is little known fact that we can create the so called Dynamic objects (DOs, a.k.a. temporary objects) that get deleted from AD automatically when the associated TTL expires. Microsoft added this capability in Windows Server 2003. In fact the “Dynamic object” is an auxiliary class (OID = 126.96.36.199.4.1.14188.8.131.52). When linked to an object it adds some new attributes like the entryTTL (Entry-TTL) and ms-DS-Entry-Time-To-Die attribute.
The WinRM was configured to allow remote administration via a GPO but it wouldn’t let us connect with Enter-PSSession. The firewall rule was there passing the traffic on TCP port 5985.
Checking WinRM config showed something strange:
winrm enumerate winrm/config/listener
Address = *
Transport = HTTP
Port = 5985
Enabled = true
URLPrefix = wsman
ListeningOn = null
So WinRM was actually configured but wasn’t listening on any network interface. Why?
As of Windows 8.1 / Server 2012 R2 there is one beautiful cmdlet -Add-PrinterDriver. It dramatically simplifies driver/printer installation.
Naturally you will be tempted to install a driver from an .inf file like this:
Add-PrinterDriver -Name "HP Universal Printing PCL 6" -InfPath "C:\Install\HP\hpcu160u.inf"
But you will be blamed:
Add-PrinterDriver: One or more specified parameters for this operation has an invalid value.
So it does not work as you/we may think. Sigh… So then what it is used for?
Often developers and related OPs need to test stuff on Linux (web, cli, .NET Core etc.). The typical approach was to spin up a Virtual machine (VM), install and configure a Linux distro and play with it.
Main Cons include: you need a hyper-visor software, enough RAM, fast hard drive, to fight with basic operations like cope-paste text and files between machines etc.
Well, good news! As of the Anniversary Update Windows 10 supports the so called “Windows Subsystem for Linux” (WSL). It allows you to run natively* most of the non GUI Linux stuff**on Windows without the overhead of a virtual machine.