Client vs Server - Paiet/Windows-Server-Wiki Wiki

Original URL: https://github.com/Paiet/Windows-Server-Wiki/wiki/Client-vs-Server

Software Assurance

https://docs.microsoft.com/en-us/windows-server/windows-server-2016
https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016/

Server with Desktop Server Core
Nano Server
--no local logon capability
--sets up significantly faster, and requires far fewer updates and restarts than Windows Server
--500MB --9 seconds to boot-- 28 vs 46 services -- 12 vs 27 open ports "Just enough OS"=Cost Savings perfect OS for Cloud Senarios for higher VM density

https://docs.microsoft.com/en-us/windows-server/get-started/getting-started-with-nano-server

Chapter 2: A Peek into Windows
Client vs. Server
See diagram
Install Lab

Hardware vs. Software
you need to know both however we see a big shift towards software skills.

Four core hardware components
System Requirements & Improvements

https://docs.microsoft.com/en-us/windows-server/get-started/system-requirements<br>

-CPU
--eXecute Disable/AMD Never or No eXecute is Intel version VT around 2006
-- Load AH from Flags and SAHF stands for Store AH into Flags
https://www.howtogeek.com/73318/how-to-check-if-your-cpu-supports-second-level-address-translation-slat/ -Memory
Startup RAM

Demonstrate

When a VM starts up, it needs a little bit more RAM than it needs while idling. Thus, the amount of startup RAM is often a little bit more than the amount of minimum RAM configured for a VM. For example, if you have a VM that needs 512MB of RAM while idling, it may need 768MB of RAM during startup.
Minimum RAM The minimum amount of RAM needed is the amount used when a server is sitting idle and performing a minimal workload. It is a good practice to set the minimum RAM to the minimum supported RAM for the operating system (or more).

** Maximum RAM** The maximum amount of RAM is the most that you want a server to consume, no matter how much it requires at a given time. If a server requires 32GB of RAM and you set the maximum amount of RAM to 16GB, then the server will be limited to 16GB of RAM. In such a case, the computer will rely on the pagefile and performance will be impacted negatively. On the other hand, the server won't be able to consume an unlimited amount of RAM and impact other VMs running on the same Hyper-V server.
Memory buffer. Hyper-V will reserve the specified amount of RAM to use as a buffer. By default, 20% is reserved. Hyper-V can rely on the buffer while it seeks to claim RAM back from other VMs during a low memory event.
Memory weight. Each VM is configured with a memory weight based on a sliding scale. On the far left of the scale, the memory weight can be set to low. On the far right of the scale, the memory weight can be set to high. VMs that are set with a low memory weight have lower priority to the hypervisor's memory than VMs with a higher weight. If a VM with a high memory weight requires additional RAM, that RAM can be pulled from VMs with a lower weight. Your least critical servers should be weighted with a lower priority while your most critical servers should be weighted with a high priority. Storage

-Storage
Historically we would think of storage as spindle drives, but today storage means so much more we are talking SSDs, SANs and NASs and even cloud based storage integration.

A computer that runs Windows Storage Server is referred to as a storage appliance, Purchased via hardware OEM who licence it for preinstallation on ready to go NAS devices.

Disk Drives aka disk shelf
Controllers-sometimes called headers or fillers manage backend storage & management from the clients
Refer to BOOK

Network interface card(NIC)
The makeup of the softwarecomponents
Fundamental networking concepts for server administrators
Physical servers vs. virtual servers
Workgroup vs. domain
How security fits with Windows Server
Windows Server in the cloud

Software Operating System
Windows Kernal
System Processes
Services
Applications
Firmware
Drivers

Fundamental networking concepts for server administrators
Subnetting
DHCP
DNS
Routing and Switching
Load Balancing
Above & beyond

http://standards.iso.org/ittf/PubliclyAvailableStandards/s020269_ISO_IEC_7498-1_1994(E).zip

Physical servers vs virtual servers
See Diagram

Workgroup vs Domain
See Diagram

How Security fits with Windows Server
Group Policy Microsoft Security Compliance Manager
http://gpsearch.azurewebsites.net/
https://technet.microsoft.com/en-us/library/cc677002.aspx
Firewalls
Proxy Servers
DMZs
VLANS
IPS/IDS

Windows Server in the Cloud
You need to have connectivity to the cloud
There may be higher latency and less bandwidth to your cloud-based servers than your on-premises servers
You don't control some aspects of the computing infrastructure

Download and show Licensing Model

Software Assurance

https://docs.microsoft.com/en-us/windows-server/windows-server-2016
https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016/

Server with Desktop Server Core
Nano Server
--no local logon capability
--sets up significantly faster, and requires far fewer updates and restarts than Windows Server
--500MB --9 seconds to boot-- 28 vs 46 services -- 12 vs 27 open ports "Just enough OS"=Cost Savings perfect OS for Cloud Senarios for higher VM density

https://docs.microsoft.com/en-us/windows-server/get-started/getting-started-with-nano-server

Chapter 2: A Peek into Windows
Client vs. Server
See diagram
Install Lab

Hardware vs. Software
you need to know both however we see a big shift towards software skills.

Four core hardware components
System Requirements & Improvements

https://docs.microsoft.com/en-us/windows-server/get-started/system-requirements<br>

-CPU
--eXecute Disable/AMD Never or No eXecute is Intel version VT around 2006
-- Load AH from Flags and SAHF stands for Store AH into Flags
https://www.howtogeek.com/73318/how-to-check-if-your-cpu-supports-second-level-address-translation-slat/ -Memory
Startup RAM

Demonstrate

When a VM starts up, it needs a little bit more RAM than it needs while idling. Thus, the amount of startup RAM is often a little bit more than the amount of minimum RAM configured for a VM. For example, if you have a VM that needs 512MB of RAM while idling, it may need 768MB of RAM during startup.
Minimum RAM The minimum amount of RAM needed is the amount used when a server is sitting idle and performing a minimal workload. It is a good practice to set the minimum RAM to the minimum supported RAM for the operating system (or more).

** Maximum RAM** The maximum amount of RAM is the most that you want a server to consume, no matter how much it requires at a given time. If a server requires 32GB of RAM and you set the maximum amount of RAM to 16GB, then the server will be limited to 16GB of RAM. In such a case, the computer will rely on the pagefile and performance will be impacted negatively. On the other hand, the server won't be able to consume an unlimited amount of RAM and impact other VMs running on the same Hyper-V server.
Memory buffer. Hyper-V will reserve the specified amount of RAM to use as a buffer. By default, 20% is reserved. Hyper-V can rely on the buffer while it seeks to claim RAM back from other VMs during a low memory event.
Memory weight. Each VM is configured with a memory weight based on a sliding scale. On the far left of the scale, the memory weight can be set to low. On the far right of the scale, the memory weight can be set to high. VMs that are set with a low memory weight have lower priority to the hypervisor's memory than VMs with a higher weight. If a VM with a high memory weight requires additional RAM, that RAM can be pulled from VMs with a lower weight. Your least critical servers should be weighted with a lower priority while your most critical servers should be weighted with a high priority. Storage

-Storage
Historically we would think of storage as spindle drives, but today storage means so much more we are talking SSDs, SANs and NASs and even cloud based storage integration.

A computer that runs Windows Storage Server is referred to as a storage appliance, Purchased via hardware OEM who licence it for preinstallation on ready to go NAS devices.

Disk Drives aka disk shelf
Controllers-sometimes called headers or fillers manage backend storage & management from the clients
Refer to BOOK

Network interface card(NIC)
The makeup of the softwarecomponents
Fundamental networking concepts for server administrators
Physical servers vs. virtual servers
Workgroup vs. domain
How security fits with Windows Server
Windows Server in the cloud

Software Operating System
Windows Kernal
System Processes
Services
Applications
Firmware
Drivers

Fundamental networking concepts for server administrators
Subnetting
DHCP
DNS
Routing and Switching
Load Balancing
Above & beyond

http://standards.iso.org/ittf/PubliclyAvailableStandards/s020269_ISO_IEC_7498-1_1994(E).zip

Physical servers vs virtual servers
See Diagram

Workgroup vs Domain
See Diagram

How Security fits with Windows Server
Group Policy Microsoft Security Compliance Manager
http://gpsearch.azurewebsites.net/
https://technet.microsoft.com/en-us/library/cc677002.aspx
Firewalls
Proxy Servers
DMZs
VLANS
IPS/IDS

Windows Server in the Cloud
You need to have connectivity to the cloud
There may be higher latency and less bandwidth to your cloud-based servers than your on-premises servers
You don't control some aspects of the computing infrastructure