WUAUCLT no more working on Windows 10 and Server 2016?
Please replace with USOCLIENT.EXE
When you connect to Microsoft Windows RDS (Remote Desktop Services), it can be done either as a USER or as an ADMIN.
If you don't do anthing, each administrator consume one license.
Moreover, if you are behind an RDS-broker, a user would always be load balanced to a particular server
Windows Server 2016 is the first version of Windows to ship support for container technology built in to the OS. In Server 2016, two types of containers are available: Windows Server Containers and Hyper-V Containers. Each container type supports either the Server Core or Nano Server SKU of Windows Server 2016.
It often happened in my developments to have to protect my sources, and be sure that the configuration XML file I used, was not modified by some people.
For that, the idea if to sign my configuration XML file, and later the program which has to read the file to first check XML signature.
As it regularly happens when you stop a test platform for a long time, computer accounts password expire and Active Directory controllers do not replicate anymore (well known item since Windows 2000 Active Directory).
When you try to manually replicate using dssite.msc, you get the error message "2148074274 The target principal name is incorrect".
As I searched the web how to automatically deploy NANO server and join it to Active Directory, I could only find incomplete solutions.
I saw many things with manual copy of the blob generated with djoin.exe ...
During some automatized deployments, as often, we have to deploy Microsoft Exchange 2016 automatically.
When a user opens an Active Directory session with his smartcard, it happens that some applications do not support smartcard logon, but needs classical user/password login.