Exam Ref 70-740 Installation, Storage And Compute With Windows Server 2016 Downloads Torrent

0 views

Skip to first unread message

Kody Baril

unread,

Aug 20, 2024, 12:26:02 PM8/20/24

to antravezel

More than 16 hours of video instruction, quizzes, and exercises to help you prepare for Exam 70-740: Installation, Storage, and Compute with Windows Server 2016, one of three exams required to achieve the MCSA Windows Server 2016 certification.

This engaging, self-paced video course includes demonstrations and configurations of various features of Windows Server 2016. Even if you're not planning to take the 70-740 exam, this video training will help you get up-to-speed on the new and updated features in Windows Server 2016.

Exam Ref 70-740 Installation, Storage and Compute with Windows Server 2016 downloads torrent

Download https://psfmi.com/2A3uQR

The course is designed to emulate the process by which users can build their own lab environment, using a single Windows server to create complex configurations, such as failover clusters, shared storage, and nested Hyper-V hosts. The only hardware required is a single computer with at least 12 gigabytes of memory. The only software needed is the evaluation version of Windows Server 2016.

Trainer and author Craig Zacker has been working with Windows Servers for more than 20 years. Throughout each lesson, he describes key concepts and puts them into action with demonstrations and real-world scenarios. Follow along by creating your own practice environment using virtual machines in Hyper-V.

Craig Zacker is a writer, editor, and educator who has written or contributed to dozens of books on operating systems, networking, and PC hardware, as well as several college texts and online training courses. Craig is the author of Exam Ref 70-740: Installation, Storage, and Compute with Windows Server 2016 published by Microsoft Press (January 2017).

Pearson publishes expert-led video tutorials covering a wide selection of technology topics designed to teach you the skills you need to succeed. These professional and personal technology videos feature world-leading author instructors published by your trusted technology brands: Addison-Wesley, Cisco Press, Pearson IT Certification, Prentice Hall, Sams, and Que Topics include: IT Certification, Network Security, Cisco Technology, Programming, Web Development, Mobile Development, and more. Learn more about Pearson Video training at

In this first chapter, we will cover the installation of Windows Server and Nano Server, and migration to Windows Server 2016 from previous versions. We will start by determining the important installation requirements of Windows Server 2016, including which versions and Windows Server editions to install and what hardware is essential for a solid and reliable infrastructure. One important part is installing and configuring a special version of Windows Server without a GUI, Windows Server Core. We will see how to configure the installation of Windows Server 2016 using various options and tools.

Essential to Windows Server administration is the ability to perform server management remotely and use automation tools to reduce management errors and save time. We will then move on to the installation and configuration of Nano Server and the tools we need to build Nano Server images and configure Nano Server workloads. Finally, we will learn how to perform upgrades from previous versions and how to activate Window Server installations.

You will need a version of Windows Server 2016. This can be a retail version, a volume-licensed version, or an evaluation version with which you can experiment. I suggest you set up your own lab, preferably in a sandboxed environment. You can set up your lab either in Hyper-V or in Microsoft Azure. Additionally, Hyper-V is available on Windows 10, or you can use any other virtualization platform to build your own lab: VMware, Amazon Web Services, VirtualBox, and so on. Be aware that Microsoft Azure does not support some Windows Server roles and features, including the following:

Sometimes, when you click on Windows Server 2016 under the Products menu, only a list of Windows Server 2012 products is displayed. This might be a temporary glitch. To display the Windows Server 2016 version, click on the plus sign next to any Windows Server 2012 version and expand the entry. After an automatic refresh, the list will show the Windows Server 2016 versions that are available for evaluation and download. There are three options available: Azure, ISO, and Virtual Lab. Choose whichever suits you best.

Windows Server 2016 is available in many different variants, but before choosing the appropriate version for your specific workloads and needs, you must be sure that your current or future hardware will be able to support it.

The following system requirements are minimum hardware requirements that are common to all Windows Server 2016 installation options and editions. The actual minimum hardware requirements are estimated and may vary depending on the planned roles and features. Obviously, for production environments and optimum server performance, you should plan to install Windows Server 2016 on hardware that exceeds these requirements.

The optional requirements are exactly that, options, and are not necessarily needed to install Windows Server 2016 because the server administration should be performed almost exclusively remotely. Specific features may require additional hardware, such as BitLocker Drive Encryption, which requires a TPM chip. If you plan to use BitLocker, then hardware-based TPM chip must adhere to version 2.0 of the TPM specification. Additionally, it needs to support the SHA-256 encryption and the EK certificate.

The features that are exclusive to the Datacenter Edition include shielded virtual machines, Software-Defined Networking (SDN), networking stacks, Storage Spaces Direct, and Storage Replica. The Standard Edition includes rights to two Operating System Environments (OSEs, or virtual machines) or Hyper-V Containers, whereas the Datacenter Edition includes unlimited OSEs and Hyper-V Containers. OSE is a Microsoft term that represents a Windows instance running either as a physical or a virtual installation. The Standard Edition therefore grants you the right to run a physical server OSE instance in addition to a virtual instance.

If a physical OSE is used exclusively to host and manage virtual OSEs, you can use two virtual OSEs in addition to the physical OSE. At first, the Standard Edition OSE limit might not look very attractive, but the price is an important factor to consider as well; currently, Datacenter Edition price is approximately six to seven times higher than Standard Edition. Unless you will run more than twelve to fourteen virtual machines, having a single Datacenter license might not be a good decision because you could spend less money buying Standard Edition licenses instead. Of course, licensing and money are not the only variables here. Should you decide to buy Standard licenses, you have to consider expense of buying the same amount of additional server hardware.

If you choose the Datacenter version, a high-end server with hardware characteristics powerful enough to run fourteen virtual machines might be more expensive than buying seven low- or mid-end servers suitable to host Standard versions of Windows Server. With in increased number of servers, the administrative burden increases as well.

The Datacenter and Standard Editions require every user or device that accesses a server to have a Client Access License (CAL). The following table gives you a comparison of the features of Windows Server 2016 editions:

There are several different ways of installing Windows Server 2016, each of which are suitable for different scenarios. In this section, we will explain a clean installation, while upgrades and migrations will be described later.

The term clean installation describes how to install Windows Server 2016 either on new hardware or a virtual machine, or on old hardware or a virtual machine without retaining the old operating system.

Whether you install Windows Server 2016 on a physical server or as a virtual machine, the process is the same. The only difference is in how you supply the installation files. To install an operating system on a virtual machine in Hyper-V, you would provide a Windows Server 2016 ISO file. This can be used to burn a DVD or to make a bootable USB drive.

There are four choices available. There are two Windows Server 2016 versions, Datacenter and Standard, each of which is presented in two different configurations: with a GUI (Desktop Experience) or without it (Server Core). Unless you have a specific reason to install GUI elements, you should always choose to install the Server Core version.

In earlier Windows Server releases (in Windows Server 2012 and Windows Server 2012 R2 for example), you could choose either Desktop Experience or Server Core version and remove or install a GUI easily after installation. Windows Server 2016 releases do not support installing or uninstalling a GUI anymore. If you change your mind about which version you want to choose, you should do a clean installation:

Each of the selected roles and features might have their own configuration page. After performing eventual configuration tasks and entering required information, the Confirm installation selections button appears.

If the server requires a restart after installation, select this option, but ensure that the users are aware of possible interruptions in operations. The Export configuration settings button saves the steps performed by Add Roles and Features Wizard in an XML template file, which can be used later to perform identical installations using PowerShell.

If the Windows Server 2016 source files are incomplete or missing, the Specify an alternate source path option will tell the wizard the location of the Install.wim file that contains the required source files:

After clicking Install, you can close the wizard window without disturbing the installation. You can track its progress by clicking on the Notifications flag at the top of the Server Manager window: