The super user account created by default is Administrator.
Initial settings include a computer name, setting the time zone, and configuring the network settings. Another important setting is configuring the Windows Updates.
Essentials supports: • 2 CPU sockets up to 64GB of RAM • Up to 25 user and 50 computer accounts • No Server Core installation • No Hyper-V full service support • No Server Clustering
Standard supports: • 512 CPU sockets up to 24TB of RAM • Unlimited user and computer accounts • Unlimited RRAS and RD connections • Server Core installation • Hyper-V support up to 2 guest OS sessions • Server Clustering up to 64 nodes
Desktop Experience
Product ID and Hardware ID are unique to the system that Windows is installed. Licensing is then associated with these unique numbers. Any significant change to the hardware of the server will require reactivation of the licensing for that system. This does not apply to additional components as long as the original components that were used to activate the license are still in the system.
Datacenter supports: • 512 CPU sockets up to 24TB of RAM • Unlimited user and computer accounts • Unlimited RRAS and RD connections • Server Core installation • Unlimited guest sessions with Hyper-V • Server Clustering up to 64 nodes
A Key Management Server is local to the systems requiring activation and does not need to activate Windows over the Internet. Activation is valid for 180 days. The default is 7 days for attempting a reactivation. A KMS system can utilize the same license for all systems based on the licensing agreement.
Some upgrade paths available for Windows Server 2016 include:
Server 2012 Standard to Server 2016 Standard or Datacenter
Server 2012 Datacenter to Server 2016 Datacenter
Server 2012 R2 Standard to Server 2016 Standard or Datacenter
Server 2012 R2 Datacenter to Server 2016 Datacenter
Also Server 2016 Standard to Server 2016 Datacenter
You cannot upgrade directly from Server 2000, 2003, or 2008.
PowerShell is a command line interface used to configure and manage tasks in Windows OS. You can create scripts that can perform management tasks much faster than if you were using the GUI.
The general format for commands in PowerShell are verb-noun – adverb. For example, verbs could be new, add, install, get, or set. Nouns could be any manageable object, application, etc. Adverbs are command options.
Use the TAB key to autocomplete a command.
A role is a major function or service that the server provides to client computers.
Role services are additional programs used to support a major role.
A feature is a software program that is not directly related to a server role.
Typical roles include Active Directory Domain Services – used for managing network resources and authenticating users, DNS, DHCP, File Services, Windows Deployment Services, Windows Update Services, etc.
Examples of a role service include the Print and Document service can have the Distributed Scan Server and Internet Printing role services as well.
Examples of features include Windows Backup, management tools, BitLocker Drive Encryption, and Failover Clustering.
Features on Demand is a feature in Windows Server that allows you to remove the source files of unneeded roles and features in order to conserve disk space.
A Server Core install provides a stable environment, has less system requirements, has fewer components to troubleshoot, and a reduced footprint (attack surface). Note that a Core install does not support all the roles that a GUI install would.
WinRM is used to remotely manage servers from the command line.
The graphical tool available to manage remote computers is through Microsoft Management Consoles (MMC).
A Nano Server installation has an even smaller footprint than a Core installation. A Nano Server installation has practically no user interface and is typically managed remotely. A Nano Server is useful for deploying single roles to the domain such as DNS, IIS Web services, and failover clustering. They are often called a ‘headless’ deployment.
Advantages of a Nano Server Installation include:
Fewer updates
Faster boot time
Reduced resource usage
Reduced footprint that reduces the attack surface of the server making them more secure.
A Nano Server is typically managed remotely using the Nano initial user interface, remote PowerShell commandlets, or remote MMCs.