1. Install Windows Server in Host and Compute Environments Flashcards
Server 2016 Minimum Requirements
- Processor: 1.4GHz
- Memory:
- Server Core: 512 MB RAM
- Desktop Experience: 2GB
- Disk: 32GB minimum
Server 2016 Maximum Hardware Limits
- Processor:
- 512 logical processors
- VM Processors: 240 per VM
- Virtual Machines:
- 1024 per host
- Memory:
- 24TB per host
- 12TB per VM
- Disk
- VHDX Size: 64TB
OSE
Operating System Environment (physical or virtual)
Windows Server 2016 Datacenter Features
- Storage Spaces Direct
- Storage Replica
- Shielded virtual machines
- Unlimited OSEs
Windows Server 2016 Standard
Allows two OSEs. Lacks advanced features in Datacenter edition.
Windows Server 2016 Essentials
For small businesses with up to 25 users and 50 devices.
Windows Server 2016 MultiPoint Premium Server
Enables multiple users to access a single server installation. Available only through academic licensing.
Windows Storage Server 2016 Server
Available only through OEM as part of a dedicated storage hardware solution
Windows Hyper-V Server 2016
Hypervisor-only download, no GUI, only hosts VMs
Storage Spaces Direct
Makes shared clustered storage directly available to clusters using Storage Space-type technology, enabling use of JBOD arrays for highly available storage.
Storage Replica
Storage-agnostic data replication between servers or clusters; allows you to synchronously or asynchronously replicate volumes at the block level using SMBv3
SMB
Server Message Block
Shielded virtual machines
Provides VMs with protection from compromised administrators that have access to the Hyper-V host by encrypting the VM state and its virtual disks
Network controller
Provides a central automation point for network infrastructure configuration, monitoring, and troubleshooting
WDS
Windows Deployment Services
A server-based system for deploying desktop operating systems automatically over the network. PXE is used to connect the computers to WDS.
PXE
Preboot Execution Environment
Allows computer to load OS from a server.
Windows Server Core
Server installation that does not include a GUI, can only be managed through PowerShell or from another server that does have the full Desktop Experience.
YOU CAN NO LONGER INSTALL/UNINSTALL THE GUI FEATURES POST-INSTALLATION
Reasons to use Server Core
- Reduced resource footprint
- Fewer updates
- Reduced attack surface
Get-NetAdapter
Cmdlet that gets the basic network adapter properties.
New-NetIPAddress
Cmdlet used to configure IP addresses and their properties. This includes creating an IP address, subnet mask and default gateway on the interface.
Example:
New-NetIPAddress -InterfaceIndex 6 -IPAddress 192.168.5.80 -PrefixLength 24 -DefaultGateway 192.168.5.254
Set-DnsClientServerAddress
Cmdlet used to configure an interface with a DNS server address. This allows a computer on a network to access resources and other computers based on their DNS name.
Example: Set-DNSClientServerAddress -InterfaceIndex 6 -ServerAddresses ("192.168.5.1","192.168.5.2")
Add-Computer
Cmdlet which adds the local computer to a domain or workgroup.
Example: Add-Computer -DomainName example.local -NewName "ServerB" -Credential (Get-Credential) (Joins machine to domain, renames machine, prompts for credentials)
Rename computer with netdom.exe
netdom renamecomputer SERVER2 /newname:SERVERB
Join domain with netdom.exe
netdom join COMPUTER1 /domain:EXAMPLE.local /userd:USERNAME /passwordd:*
(Joins domain and prompts for password
New-PSSession
Cmdlet which creates a remote PowerShell session to another machine
Example: New-PSSession -Computername "SERVERB"
Enter-PSSession
Open a remote PowerShell session you previously created with New-PSSession
Can you manage remote servers with MMC snap-ins?
Not in default configuration. By default, MMC uses DCOM and the communication settings for DCOM are not enabled by default.
PowerShell DSC
Desired State Configuration.
Uses script files to apply, monitor, and maintain a specific system configuration by either pulling scripts from central server or by central server pushing scripts to the client machines.
DSC Components
- Configurations: PowerShell scripts with node blocks to indicate names of servers to configure and resource blocks specifying properties to change/apply.
- Resources: Specify settings or components and the values the configuration script should assign.
- LCM: Engine running on client system that receives configurations from DSC server and applies them to the client
LCM
Local Configuration Manager
Engine running on client system that receives configurations from DSC server and applies them to the client
MOF file
Management Object Format file
Created by PowerShell DSC for each computer specified in a DSC script’s node block. These are the actual scripts distributed to DSC clients.
DSC Pull
In a pull architecture, MOF files are stored on an SMB share or IIS web server with an OData interface. LCM on the clients has configuration script that specifies the URL of the Pull Server and creates a scheduled task. LCM polls Pull Server for configurations and checks the local machine for compliance, applying changes as needed.
DSC Push
Run Start-DscConfiguration on the Push Server, specifying path of MOF files. Automatically pushes the MOFs to all clients specified in an MOF’s node configuration
Supported Server 2016 Upgrade Paths
- Server 2012 R2 to Server 2016
- Server 2008 to 2012 to 2016 (two-step)
- Standard to Standard OR Standard to Datacenter
- Datacenter to Datacenter
Unsupported Server 2016 Upgrade Paths
- Server 2008 to 2016
- 32-bit to 64-bit
- Datacenter to Standard
- Server Core to GUI or vice-versa
- One language to another
- Workstation to Server
Preparation for Server 2016 Upgrade
- Check hardware compatibility
- Remove NIC teaming
- Check disk space
- Check app compatibility
- Verify all drivers/software is signed
- Install all windows updates
- Perform full backup
Unsupported Server 2016 Migration Scenarios
- Migration from one language to another
- From Server Core 2008 to 2016 (2008 version of Server Core does not support .NET framework)
Export-SmigServerSetting
Cmdlet that exports certain Windows features and operating system settings to a migration store.
Get-SmigServerFeature
Cmdlet to see what features are running to prepare for server migration on another server operating systems.
Import-SmigServerSetting
Cmdlet which imports certain Windows features and operating system settings from a migration store and applies them to the local server
Receive-SmigServerData
Cmdlet which enables destination server to receive migrated files, folders, permissions, and share properties from a source server. The Send-SmigServerData cmdlet must be running on the source server at the same time.
Send-SmigServerData
Cmdlet which migrates files, folders, permissions, and share properties from a source server to a destination server. The Receive-SmigServerData cmdlet must be running on the destination server at the same time.
Generate Server Migration Tool Distribution Folder
Example: cd C:\Windows\system32\ServerMigrationTools SmigDeploy.exe /package /architecture amd64 /os WS12R2 /path C:\WS12R2
MAK
Multiple Activation Key
A product identification key, which is used to activate more than one computer
KMS
Key Management Service
A role service that allows you to activate systems within a network from a server where a KMS host has been installed
MAK Independent
Each computer using the MAK must perform an individual activation with Microsoft
MAK Proxy
Client machines receive a MAK from a system running the Volume Activation Management Tool (VAMT) which caches the installation IDs of the clients and sends a single activation request to Microsoft and forwards (proxies) the response to the client.
VAMT
Volume Activation Management Tool
Enables automating and centrally managing the Windows, Microsoft Office, and select other products volume and retail-activation process. VAMT can manage volume activation using MAKs or KMS.
KMS Activation Threshold
KMS requires a minimum of 25 workstation systems or 5 server systems as clients. The KMS host does not perform any activations until the count reaches the minimum requirement. To prevent the count from dropping below the minimum requirements, Microsoft recommends only using KMS on networks with at least 50 machines.
KMS Activation Validity Interval
KMS activations expire every 180 days which is their validity interval. Clients attempt to renew activations every 7 days, if unsuccessful for 180 days the product activation expires.
GVLKs
Generice Volume Licensince Keys
Provided by Microsoft to convert retail, MAK, or KMS Host license clients to KMS clients
Active Directory-based Activation
Similar to KMS but uses AD DS to store information instead of KMS host. Machines with GVLKs are activated automatically upon joining the domain and authenticating with AD.
AVMA
Automatic Virtual Machine Activation
Allows automatic activation for Hyper-V VMs on Datacenter editions.
Physical-to-virtual (P2V) Conversion Classifications
- Low risk
- Non-critical
- Higher use
- Business critical
MAP Toolkit
Microsoft Assessment and Planning Toolkit
Inventory, assessment, and reporting tool that enables you to discover and evaluate the hardware and software on servers and workstations.
DISM.exe
Deployment Image Servicing and Management
Command-line tool which enables you to modify Windows Imaging files.
DISM.exe Maintenance Tasks
- Add/remove device drivers
- Add/remove language packs
- Add/remove packaged updates
- Add/remove files and folders
- Enable/disable OS features
- Execute answer files
- Add/remove app packages
Mount image with DISM.exe
dism /mount-image /image-file:filename /index:# /name:imagename /mountdir:x:\folderpathname
Determine image name and index number with DISM.exe
dism.exe /get-imageinfo /image-file:x:\pathtowimfile
Add driver to mounted image using DISM.exe
dism.exe /image:x:\foldername /add-driver:drivername
What DISM.exe switch do you use to service the currently running OS?
Substitute the /online switch for the /image switch to modify the currently running OS image.
DISM.exe driver installation limitations
Can only manage drivers with Windows Information files (.inf), cannot install driver packaged as executable (.exe) files.
Types of update files you can install with DISM.exe
- Cabinet (CAB) files
- Windows Update Stand-Alone Installer (MSU) files
How do you install an update to a mounted image with DISM.exe?
dism.exe /image:x:\image /add-package /package-path:c:\updates\package.msu
Display installed updates on an image with DISM.exe
dism.exe /image:x:\image /get-packages
How do you commit the changes you’ve made to an image when using DISM.exe?
dism.exe /unmount-image /mountdir:x:\imagepath /commit
How do you discard the changes you’ve made to an image when using DISM.exe?
dism.exe /unmount-image /mountdir:x:\imagepath /discard
How do you determine which roles/features you can install with DISM.exe?
dism.exe /image:x:\imagepath /get-features
How do you enable/install roles/features with DISM.exe?
dism.exe /image:x:\imagepath /enable-feature /featurename:feature
How do you disable/remove roles/features with DISM.exe?
Similar to the enable feature:
dism.exe /image:x:\imagepath /disable-feature /featurename:feature
NIC Teaming
Also known as Load Balancing and Failover. Allows multiple network adapters on a system to be placed into a team.
Slmgr.vbs
Software License Manager script used with Wscript.exe or Cscript.exe to manage license activation on Windows Server 2016
Restarting the Software Licensing Service
net stop sppsvc net start sppsvc
LTSB
Long Term Servicing Branch
5 years of mainstream support + 5 years of extended support
CBB
Current Branch for Business
Used for nano server to continually provide new updates and features multiple times per year as they are released
WDS Server Requirements
- Minimum OS of Server 2003
- Member of domain
- At least one network adapter
- At least one NTFS partition
- WDS installed
Features On Demand
Allows administrators to completely remove role or features files.
MDT
Microsoft Deployment Toolkit
Provides a unified collection of tools, processes, and guidance for automating desktop and server deployments.
Windows AIK
Windows Automated Installation Kit
Helps configure and deploy OS images.
MDT Minimum Requirements
- Windows Server 2008 or Windows 7
- Windows Assessment and Deployment Kit (ADK)
Unattended Installation
Allows automatic installation of an operating system and applications by utilizing an answer file named Autounattend.xml
Sysprep.exe
System Preparation Tool
Used to prepare a computer for disk imaging, and the image can then be captured using any image capturing software.
Windows ADK
Windows Assessment and Deployment Kit
Set of utilities and documentation that allows an administrator to configure and deploy Windows OS.
Windows ICD
Windows Imaging and Configuration Designer
Primarily designed for use by IT departments for business and educational institutions who need to provision bring-your-own-device (BYOD) and business-supplied devices.
Windows Assessment Toolkit
Application compatibility toolkit allows an administrator to determine application compatibility between OS versions.
Windows Performance Toolkit
A utility that will locate computers on a network and then perform a thorough inventory of them.
WDS Image Capture Wizard
F8 at startup. Works in conjunction with Sysprep.exe to create and manage image files.
Automated Deployment Options
- Unattended installations
- MDT
- Windows ADK
- WDS
- Sysprep and Imaging
Windows SIM
Windows System Image Manager
Allows you to create answer files to use during unattended installations.
icd.exe
Imaging and Configuration Designer command-line tool
