Introducing

Recommendations

Info

Installation option LTSB servicing model Server with Desktop Experience Yes No Server Core Yes No Nano Server No Yes CBB servicing model The goal is to provide feature updates approximately two or three times per year for Nano Server. The model will be similar to the Windows client servicing model, but we expect it to have some differences. Although we share the same goal of delivering new and valuable technology to our customers rapidly, we understand that a server operating environment has unique requirements. For example, even though it will be necessary to stay current with new versions as they come out, the new versions will not auto-update a server. Instead, the administrator will perform a manual installation when he chooses. Because Nano Server will be updated on a more frequent basis, customers can be no more than two Nano Server CBB releases behind. Only two CBB releases will be serviced at any given time; therefore, when the third Nano Server release comes out you will need to move off of release 1 because it will no longer be serviced. When release 4 comes out, you will need to move off of release 2, and so on. Containers By John McCabe This section introduces a new technology to Windows Server 2016 called containers. Containers come in two types: Windows Server Containers Hyper-V Containers In this section, we explain what a container is and why is it important. What is a container? A container in its simplest form is exactly that—a container. It is an isolated environment in which you can run an application without fear of changes due to applications or configuration. Containers share key components (kernel, system drivers, and so on) that can reduce startup time and provide greater density than you can achieve with a VM. Figure 3-6 shows an abstract of a container. 97 CHAPTER 3 | Application platform
Figure 3-6: Conceptual container layout As the illustration demonstrates, a host OS can host many containers and allow them to be completely isolated while sharing key components of the OS, such as the kernel. The interesting thing about containers is the application itself. The application might have various dependencies that it requires to run. These dependencies exist only within the container itself. This means that something bad that happens to Application A and the binaries it depends on has no impact on Application B and the binaries on which it depends. For example, in most environments, if you delete the registry from Application A, the consequences are disastrous for both Application A and Application B. However, with containers, Application A and Application B are each self-contained, and the change to the registry for Application A does not affect Application B. Because all binaries and dependencies are hosted within the container, the application running in the container is completely portable. Essentially, this means that you can deploy a container to any host running the container manager software, and it will start and run without any modification. For example, a developer can begin developing his application and deploy it into a Hyper-V Container using Windows 10 Anniversary Edition. When he is ready to roll it out in production, it can be run on Windows Server 2016, including Nano Server, in a public, private, or hybrid cloud. Containers are built on layers. The first layer is the base layer. This is the OS image on which all other layers will be built. This image is stored in an image repository so that you can reference it when necessary. The next layer (and sometimes the final layer) is the application framework layer that can be shared between all of your applications. For example, if your base layer is Windows Server Core, your application framework layer could be .NET Framework and Internet Information Services (IIS). The second layer can also be stored as an image, which, when called, also describes its dependency on the base layer of Windows Server Core. Finally, the application layer is where the application itself is stored, with references to the application framework layer and, in turn, to the base layer. The base layer and the application layer can be referenced at any time by any other application container you create. Each layer is considered read-only except the top layer of the “image” you are deploying. For example, if you deploy a container that depends only on the Windows Server Core image, this Windows Server Core layer is the top layer of the container and a sandbox is put in place to store all the writes and changes made during runtime. You can then store the changes made as another image for later reuse. The same applies if you deploy the application framework layer image; this layer would have its own sandbox, and if you deploy your application to it, you can then save the sandbox as a reusable image. Basically, when you deploy a container to a host, the host determines whether it has the base layer. If not, it pulls the base layer from an image repository. Next, it repeats the process for the application 98 CHAPTER 3 | Application platform
Page 1 and 2:
Introducing Windows Server 2016 Joh
Page 3 and 4:
Visit us today at microsoftpresssto
Page 5 and 6:
Creating a cloud witness by using A
Page 7 and 8:
DSC Local Configuration Manager ...
Page 9 and 10:
Ramnish Singh Ritesh Modi Jason M.
Page 11 and 12:
C H A P T E R 1 Introduction to Mic
Page 13 and 14:
The following subsections dive deep
Page 15 and 16:
Offer greater service availability
Page 17 and 18:
Self-Service In the area of self-se
Page 19 and 20:
C H A P T E R 2 Software-defined da
Page 21 and 22:
Each nested guest VM needs to have
Page 23 and 24:
A VM collection group is a logical
Page 25 and 26:
Using the Get-VM cmdlet, you can se
Page 27 and 28:
Figure 2-5: Multitier management gr
Page 29 and 30:
Windows Server 2012 R2 took live mi
Page 31 and 32:
Figure 2-12: VM shortcut menu To do
Page 33 and 34:
You can confirm this by using Windo
Page 35 and 36:
ParentSnapshotName : MemoryStartup
Page 37 and 38:
Figure 2-19: Message indicating tha
Page 39 and 40:
Figure 2-23: VM Task Manager showin
Page 41 and 42:
Failover cluster By John Marlin and
Page 43 and 44:
Figure 2-30: Entering storage accou
Page 45 and 46:
Figure 2-34: Extending a volume in
Page 47 and 48:
[=== Microsoft-Windows-ClusterAware
Page 49 and 50:
Troubleshooting an event such as th
Page 51 and 52:
Figure 2-40: Pausing cluster node N
Page 53 and 54:
-IncludeAllSubFeature 5. Add the Wi
Page 55 and 56:
Figure 2-50: VM Configuration Versi
Page 57 and 58: As Figure 2-51 illustrates, when ap
Page 59 and 60: There is no need for schema updates
Page 61 and 62: In the Configure Storage Replica Wi
Page 63 and 64: There are many options for the New-
Page 65 and 66: Deployment Choice Storage Spaces Di
Page 67 and 68: Figure 2-60: The Storage Spaces Dir
Page 69 and 70: on node A, B, and C, and the extent
Page 71 and 72: Figure 2-63: Old mapping versus the
Page 73 and 74: Multi-instance With multi-instance
Page 75 and 76: Figure 2-66 Network virtualization
Page 77 and 78: Figure 2-68: NVGRE Network Controll
Page 79 and 80: More info In this book, we cannot p
Page 81 and 82: When you have a service that requir
Page 83 and 84: Figure 2-72: Post deployment config
Page 85 and 86: Auditing access to resources Window
Page 87 and 88: Figure 2-77: Published web applicat
Page 89 and 90: Figure 2-81: Relying party options
Page 91 and 92: Figure 2-85: The Edit Claim Rules d
Page 93 and 94: This will provide you with the toke
Page 95 and 96: Figure 2-92: Viewing details from t
Page 97 and 98: Hear about it first. Get the latest
Page 99 and 100: Figure 3-1: Diagram showing the thr
Page 101 and 102: DNS server Web server running IIS A
Page 103 and 104: Figure 3-5: Architecture of differe
Page 105 and 106: Remotely managing Nano Server Nano
Page 107: Monitoring Nano Server You can now
Page 111 and 112: Figure 3-7: Windows Server 2016 con
Page 113 and 114: Figure 3-10: Containers can write o
Page 115 and 116: Firewalls Every container host has
Page 117 and 118: C H A P T E R 4 Security and identi
Page 119 and 120: At this point, it might be self-def
Page 121 and 122: UEFI BIOS configured to prevent an
Page 123 and 124: Better protection against advanced
Page 125 and 126: When a user attempts to remote desk
Page 127 and 128: New fields in the process creation
Page 129 and 130: The core areas of interest to chang
Page 131 and 132: credentials for this account with s
Page 133 and 134: Long-term plan The long-term goals
Page 135 and 136: A REST Endpoint Windows PowerShell
Page 137 and 138: Bring Your Own Device (BYOD) equipm
Page 139 and 140: Users can add their personal Micros
Page 141 and 142: More info For further information,
Page 143 and 144: C H A P T E R 5 Systems management
Page 145 and 146: Like Linux, we have some common ter
Page 147 and 148: Name InstallationPolicy SourceLocat
Page 149 and 150: uri='https://www.powershellgallery.
Page 151 and 152: Figure 5-1: Sample code in the Wind
Page 153 and 154: The first runspace, ID 1, is always
Page 155 and 156: ConfigurationRepositoryShare This r
Page 157 and 158: IISInstall is responsible for downl
Page 159 and 160:
DSC partial configurations One of t
Page 161 and 162:
You also need to provide the pull s
Page 163 and 164:
The .mof file is generated on the p
Page 165 and 166:
this information. Figure 5-9 shows
Page 167 and 168:
Backup and recovery Security and co
Page 169 and 170:
Figure 5-15: Connecting a storage a
Page 171 and 172:
Figure 5-19 depicts the first step
Page 173 and 174:
Figure 5-23: Adding logs From here
Page 175 and 176:
Figure 5-26: Sample deployment for
Page 177 and 178:
Figure 5-28: The Windows PowerShell
Page 179 and 180:
Deployment Deployment of SMT is rel
Page 181:
Free ebooks From technical overview
show all

Introducing

Create successful ePaper yourself

Delete template?

Save as template?