Category: Microsoft Azure

Adding an Image to a Container, BitLocker Provisioning, BranchCache and PowerShell, Microsoft Azure

Introduction to Containers – Building an Azure Infrastructure

Windows containers are independent and isolated environments that run an operating system. These isolated environments allow you to place an application into its own container, thus not affecting any other applications or containers.

Think of containers as virtual environments that are used to run independent applications. They load much faster than virtual machines, and you can run as many containers as needed for all of the applications that you run.

One of the nice advantages of using Windows containers is that the containers can be managed the same way you manage an operating system. A container works the same way as a newly installed physical or virtual machine. So, once you know how to configure these containers, management is much easier than configuring a physical machine.

There are two different types of Windows containers:

Windows Server Containers This container allows you to isolate applications so they can run in their own space and not affect other applications. The question that you may be asking is, why not use a virtual machine? Well, the advantage of Windows Server containers is that they are already prebuilt and you don’t need all the other services that a virtual machine would need to run. So Windows containers are smaller, faster, and more efficient when isolating applications. In a Windows Server container, the kernel is shared between all the different Windows containers.

Hyper- V Containers Hyper- V containers and Windows containers work the same way. The difference between the two is that Hyper- V containers run within a virtual machine and the Windows containers don’t need to run in a Hyper- V environment. In a Hyper- V container, the container host’s kernel is not shared between the other Hyper-V  containers.

Container Terminology

As with any new technology, it is important to understand the terminology that goes along with that new technology. The first thing that you may have noticed is that a container works a lot like a virtual machine. Just like a virtual machine, the container has a running operating system within the container.

The container, which has a filesystem, can also be accessed through the network the same way you access a virtual machine. The advantage is that a container is a more efficient operating system. But to truly understand how containers work, you need to understand all of the components that allow containers to function properly:

Container Host This component can be on a physical or virtual machine, and it’s the component that is configured with the Windows container feature. So the Windows container sits on top of the container host.

Container OS Image This component provides the operating system to the container. Containers are made up of multiple images that are stacked on top of each other.

Container Image This is the component that contains all the layers of the container. So the container image contains the operating system, the application, and all the services required to make that application function properly.

Container Registry This component is the heart and brain of the container. The container images are kept within the container’s registry. The advantage of doing containers this way is that you can download other registries to automatically add other applications or services quickly.

Docker Daemon This is the component that runs the Docker application. The Docker daemon is automatically installed after you complete the installation of the Docker application.

Dockerfile This component is used to create the container images. The advantage of using the Dockerfile is that you can automate how containers are created. Dockerfiles are batches of instructions (within a text file) and commands that are called on when an image is assembled.

Docker Hub Repositories This component is a location where all of your images are stored. By having a central location for stored images, the images can be used among coworkers and customers, or for the entire IT community. There are Docker hub repositories on the Internet where you can grab and use images for your organization.

Install and Configure Server Containers

So now that we have talked about the different components of a container, it’s time to look at installing containers on your Windows Server 2022 system. When it comes to Microsoft, it doesn’t matter if we are installing containers on a GUI- based system or non- GUI- based system. We are going to install the components needed by using Windows PowerShell.

But before we can look at installing and using containers, I need to show you what is required on the Windows Server 2022 system. So, the first step in using containers is looking at what we need on our network and computers for containers to run properly.

Requirements

Now that you have decided to work with containers, you must make sure that your network meets the minimum requirements to install and work with Windows containers:

■        The Windows container feature is available on Windows Server 2022, Windows Server (Semi- Annual Channel), Windows Server 2019, Windows Server 2016, and Windows 10 Professional and Enterprise Editions (version 1607 and later).

■         The Hyper- V role must be installed before running Hyper-V  isolation.

■        Windows Server Container hosts must have Windows installed to C:. This restriction does not apply if only Hyper- V isolated containers will be deployed.

Here are the requirements if you are going to be running virtualization with containers:

■        For systems running the Hyper- V containers, the Hyper- V role must be installed on the system.

■        If you are going to run a Windows container host from a Hyper-V  virtual machine (and also hosting Hyper- V containers), you will need to enable nested virtualization. Nested virtualization also has some requirements:

■            Operating system that allows nested virtualization (Windows Server 2022).

■           Minimum of 4 GB of RAM available to the virtualized Hyper- V host.

■          The processor needs to use Intel VT- x (this is only available for Intel processors).

■          Two virtual processors for the container host VM.

Adding an Image to a Container, BitLocker Provisioning, Configure Azure VM Settings, Microsoft Azure

Review Questions – Configuring Storage

  1. What is the default TCP port for iSCSI?
    A. 3260
    B. 1433
    C. 21
    D. 3389
  2. You have a Windows Server 2022 Hyper- V host named Jupiter. You want to deploy several shielded virtual machines on Jupiter. You deploy a Host Guardian on a new server. You need to view the process of the shielded virtual machines installation. What should you run to see the progress of the shielded VM?
    A. Get- ShieldedVMProvisioningStatus cmdlet
    B. Diskpart command
    C. Set- VHD cmdlet
    D. Set- VM cmdlet
  3. You are the administrator of a mid- sized network. You have a Hyper- V host that runs Windows Server 2022. The host contains a virtual machine named Virtual1. Virtual1 has resource metering enabled. You need to use resource metering to track the amount of network traffic that Virtual1 sends to the 10.10.16.0/20 network. Which cmdlet would you run?
    A. Add- VMNetworkAdapteiAd
    B. Set- VMNetworkAdapter
    C. New- VMResourcePool
    D. Set- VMNetworkAdapterRoutingDomamMapping
  4. You are the administrator for an organization that has started using Hyper- V. You have a Hyper- V host named Server1 that runs Windows Server 2022. Server1 contains a virtual machine named Earth. You need to make sure that you can use nested virtualization on Earth. What should you run on Server1?
    A. Mount- VHD cmdlet
    B. Diskpart command
    C. Set- VMProcessor cmdlet
    D. Set- VM cmdlet
  5. You need to ensure that VM1 and VM2 can communicate with each other only. The solution must prevent VM1 and VM2 from communicating with Server1. Which cmdlet should you use?
    A. Set- NetNeighbor
    B. Remove- VMSwitchTeamMember
    C. Set- VMSwitch
    D. Enable- VMSwitchExtension
  6. You are the admin for a mid- sized company. You have a Hyper- V host named Server1 that runs Windows Server 2022. Server1 has a dynamically expanding virtual hard disk (VHD) file that is 950 GB. The VHD currently contains around 450 GB of free space. You want to reduce the amount of disk space used by the VHD. What command should you run?
    A. Mount- VHD cmdlet
    B. Diskpart command
    C. Set- VHD cmdlet
    D. Optimize- VHD cmdlet
  7. You have a Nano Server named Nano1. Which cmdlet should you use to identify whether the DNS Server role is installed on Nano1?
    A. Find- ServerPackage
    B. Get- Package
    C. Find- Package
    D. Get- WindowsOptionalFeature
  8. You are working on a Windows Server 2022 Datacenter Server system. You need to view which roles and services are installed on the machine. Which PowerShell cmdlet can you use to see this?
    A. Get- event
    B. New- event
    C. Trace- command
    D. Get- WindowsFeature
  9. What command would be used to register an iSCSI initiator manually to an iSNS server?
    A. iscsicli refreshisnsserver server_name
    B. iscsicli listisnsservers server_name
    C. iscsicli removeisnsserver server_name
    D. iscsicli addisnsserver server_name
  10. You are an administrator who has set up two Hyper- V servers named Server1 (Windows Server 2022) and Server2 (Windows Server 2012 R2). Each Hyper- V server has multiple network cards. Each network card is connected to a different TCP/IP subnet. Server1 contains a dedicated migration network. Server2 contains a virtual machine named VM1. You plan to perform a live migration of VM1 to Server1. You need to ensure that Server1 uses all of the available networks to perform the live migration of VM1. What should you run to complete this task?
    A. Mount- VHD cmdlet
    B. Diskpart command
    C. Set- VHD cmdlet
    D. Set- VMHost cmdlet
  11. Your company has decided to implement a Windows 2022 server. The company IT manager before you always used FAT32 as the system partition. Your company wants to know whether it should move to NTFS. Which of the following are some advantages of NTFS? (Choose all that apply.)
    A. Security
    B. Quotas
    C. Compression
    D. Encryption
  12. You are the administrator of your network, which consists of two Windows Server 2022 systems. One of the servers is a domain controller, and the other server is a file server for data storage. The hard drive of the file server is starting to fill up. You do not have the ability to install another hard drive, so you decide to limit the amount of space everyone gets on the hard drive. What do you need to implement to solve your problem?
    A. Disk spacing
    B. Disk quotas
    C. Disk hardening
    D. Disk limitations
  13. A system administrator is trying to determine which filesystem to use for a server that will become a Windows Server 2022 file server and domain controller. The company has the following requirements:
    ■ The filesystem must allow for file- level security from within Windows 2022 Server.
    ■ The filesystem must make efficient use of space on large partitions.
    ■ The domain controller SYSVOL must be stored on the partition.
    Which of the following filesystems meets these requirements?
    A. FAT
    B. FAT32
    C. HPFS
    D. NTFS
  14. You are an IT administrator who manages an environment that runs multiple Windows Server 2022 servers from multiple site locations across the United States. Your Windows Server 2022 machines use iSCSI storage. Other administrators report it is difficult to locate available iSCSI resources on the network. You need to make sure other administrators can easily access iSCSI resources using a centralized repository. What feature should you deploy?
    A. The iSCSI Target Storage Provider feature
    B. The Windows Standards- Based Storage Management feature
    C. The iSCSI Target Server role feature
    D. The iSNS Server service feature
  15. You are the IT manager for your company. You have been asked to give the Admin group the rights to read, change, and assign permissions to documents in the StormWind Documents folder. The following table shows the current permissions on the StormWind Documents
    shared folder:
    Group/User NTFS Shared
    Sales Read Change
    Marketing Modify Change
    R&D Deny Full Control
    Finance Read Read
    Admin Change Change
    What do you need to do to give the Admin group the rights to do their job? (Choose all that apply.)
    A. Give Sales Full Control to shared permissions.
    B. Give Full Control to NTFS security.
    C. Give Admin Full Control to shared permissions.
    D. Give Finance Modify to NTFS security.
    E. Give Admin Full Control to NTFS security.
  16. Will, the IT manager for your company, has been asked to give Moe the rights to read and change documents in the StormWind Documents folder. The following table shows the current permissions on the shared folder:
    Group/User NTFS Shared
    Sales Read Change
    Marketing Modify Change
    R&D Deny Full Control
    Finance Read Read
    Tylor Read Change
    Moe is a member of the Sales and Finance groups. When Moe accesses the StormWind Documents folder, he can read all the files, but the system won’t let him change or delete files. What does Will need to do to give Moe the minimum amount of rights to do his job?
    A. Give Sales Full Control to shared permissions.
    B. Give Moe Full Control to NTFS security.
    C. Give Finance Change to shared permissions.
    D. Give Finance Modify to NTFS security.
    E. Give Moe Modify to NTFS security.
  17. For security reasons, you have decided that you must convert the system partition on your removable drive from the FAT32 filesystem to NTFS. Which of the following steps must you take in order to convert the filesystem? (Choose two.)
    A. Run the command CONVERT /FS:NTFS from the command prompt.
    B. Rerun Windows Server 2022 Setup, and choose to convert the partition to NTFS during the reinstallation.
    C. Boot Windows Server 2022 Setup from the installation CD-R OM, and choose Rebuild File System.
    D. Reboot the computer.
  18. You are the administrator of your network, which consists of two Windows Server 2022 systems. One of the servers is a domain controller, and the other server is a file server for data storage. The hard drive of the file server is starting to fill up. You do not have the ability to install another hard drive, so you decide to shrink the data on the file server. What do you need to implement to solve your problem?
    A. Disk spacing
    B. Disk compression
    C. Disk hardening
    D. Disk limitations
  19. You are the administrator of a large organization. Four weeks ago you have built a new Windows Server 2022 Datacenter Server. You can’t remember all of the roles and features that you previously installed. You need to view which roles and features are installed on the machine. Which PowerShell cmdlet can you use to see this?
    A. Get- event
    B. New- event
    C. Trace- command
    D. Get- WindowsFeature
  20. What is the default TCP port for RDP?
    A. 3260
    B. 1433
    C. 21
    D. 3389
Adding an Image to a Container, BitLocker Provisioning, Microsoft Azure, Using the Web Application Proxy

BranchCache and PowerShell – Configuring Storage

As stated throughout this book, PowerShell is a command- line shell and scripting tool. BranchCache has many different PowerShell cmdlets that allow you to configure and maintain the BranchCache feature. Table 11.5 shows just some of the different PowerShell cmdlets for BranchCache.

TABLE 11.5 PowerShell cmdlets for BranchCache

Add- BCDataCacheExtensionIncreases the amount of cache storage space that is available on a hosted cache server by adding a new cache file 
Clear- BCCacheDeletes all data in all data and hash files 
Disable- BCDisables the BranchCache service 
Disable- BCDowngradingDisables downgrading so that client computers that are running Windows 10 do not request Windows 7/8 specific versions of content information from content servers 
Enable- BCDistributedEnables BranchCache and configures a computer to operate in distributed cache mode 
Enable- BCHostedClientConfigures BranchCache to operate in hosted cache client mode 
Enable- BCHostedServerConfigures BranchCache to operate in hosted cache server mode 
Enable- BCLocalEnables the BranchCache service in local caching mode 
Export- BCCachePackageExports a cache package 
Export- BCSecretKeyExports a secret key to a file 
Get- BCClientConfiguration Gets the current BranchCache client computer settings Get- BCContentServer        Gets the current BranchCache content server settings Configuration Get- BCDataCache     Gets the BranchCache data cache Get- BCStatus       Gets a set of objects that provide BranchCache status and configuration information Import- BCCachePackage    Imports a cache package into BranchCache Import- BCSecretKey        Imports the cryptographic key that BranchCache uses for generating segment secrets Set- BCAuthentication                                  Specifies the BranchCache computer authentication mode 
CmdletDescription
Set- BCCacheModifies the cache file configuration
Set- BCSecretKeySets the cryptographic key used in the generation of  segment secrets
Enhanced Features in Windows Server 2022 BranchCache

Microsoft continues to improve on many of the features of Windows Server, and BranchCache is no different. Microsoft has improved BranchCache in Windows Server 2022 and Windows 10/11. The following list includes some of the enhanced features:

Office sizes and the number of branch offices are not limited. Windows Server 2022 BranchCache allows any number of offices along with any number of users once you deploy hosted cache mode with multiple hosted cache servers.

There are no requirements for a Group Policy Object (GPO) for each office location, streamlining deployment. All that is required to deploy BranchCache is a single GPO that contains a small number of settings.

Client computer configuration is easy. You have the ability to configure their clients through the use of a GPO. If this is done, client configuration will automatically be configured through the GPO, and if a client can’t find a hosted cache server, the client will automatically self- configure as a hosted cache mode client.

BranchCache is deeply integrated with the Windows file server. BranchCache is automatically integrated with Windows file server technology. Because of this, the process of finding duplicate pieces in independent files is greatly improved.

Duplicate content is stored and downloaded only once. BranchCache stores only one instance of the content on a hosted cache server or content server, and because of this, you get greater disk storage savings. Since client computers at the remote offices download only one instance of any content, your network saves on additional WAN bandwidth.

Small changes to large files produce bandwidth savings. One advantage of BranchCache is the file server chunking system that helps divide files and web pages into smaller parts. Now when a file is changed, only the part of that file that has been changed gets replicated. This allows BranchCache to use lower bandwidth requirements.

Offline content creation improves performance. When BranchCache is deployed as content or file servers, the data is calculated offline before a client even has the chance to request it. Because of this, the systems get faster performance and bandwidth.

Cache encryption is enabled automatically. BranchCache stores its cached data as encrypted data. This guarantees data security without the need to encrypt the entire drive.

Summary

In this chapter, I discussed file servers and how they can be effective on your network.  I also discussed sharing folders for users to access, and then I discussed how to publish those shared folders to Active Directory.

You learned about NTFS security versus shared folder permissions and how to limit users’ hard drive space by setting up disk quotas. The chapter also covered the Encrypting File System (EFS) and how users can encrypt and compress files.

I also discussed how configuring file and storage solutions can be highly effective within your organization. You now have a better understanding of how Windows Server 2022 can provide you with extended functionality for effectively controlling corporate data.

I talked about Data Deduplication and how it can help protect your corporate data and also provide a backup solution.

This chapter took you through the use of many server tools and utilities such as DFS and encryption. Distributed File System allows you to set up a tree structure of virtual directories that lets users connect to a shared folder anywhere throughout the entire network.

You also learned about EFS and how to use Cipher to modify or configure EFS in a command window. Cipher is the best way to change encrypted directories and files.

Exam Essentials

Know storage technologies. Understand how to use the Fibre Channel, iSCSI, and NAS storage technologies. Know how to configure an iSCSI initiator and how to establish a connection to a target. Practice configuring tiered storage and using thin provisioning and trim.

Know how to configure NTFS security. One of the major advantages of using NTFS over FAT32 is access to additional security features. NTFS allows you to put security at the file and folder layers. NTFS security is in effect whether the user is remote or local to the computer with the data.

Know how to configure shared permissions. Shared permissions allow you to determine the access a user will receive when connecting to a shared folder. Shared permissions are allowed only at the folder layer and are in effect only when the user is remote to the computer with the shared data.

Understand how NTFS and shared permissions work together. NTFS and shared permissions are individually additive— you get the highest level of security and permissions within each type. NTFS is always in effect, and it is the only security available locally. Shared permissions are in effect only when connecting remotely to access the shared data. When the two types of permissions meet, the most restrictive set of permissions applies.

Exam Essentials

Know how to configure disk quotas. Disk quotas allow an organization to determine the amount of disk space that users can have on a volume of a server. You can set up disk quotas based on volumes or by users. Each volume must have its own separate set of disk quotas.

Understand data deduplication. Know that data deduplication involves finding and removing duplicate data within the company network without compromising its integrity. Understand that the goal is to store more data in less space by segmenting files into small chunks, identifying duplicate chunks, and maintaining a single copy of each chunk.

Know how to configure DFS. Distributed File System in Windows Server 2022 offers a simplified way for users to access geographically dispersed files. The DFS Namespace service allows you to set up a tree structure of virtual directories that lets users connect to shared folders throughout the entire network.

Understand EFS and Cipher. Users can encrypt their directories and files by using EFS. Understand how Cipher can help you configure or modify an EFS object while in the command prompt.

Adding an Image to a Container, BranchCache and PowerShell, Configure Azure VM Settings, Microsoft Azure

Configuring BranchCache Firewall Exceptions – Configuring Storage

  1. On a domain controller, open the Group Policy Management Console.
  2. In the Group Policy Management Console, expand the following path: Forest ➢ Domains ➢ Group Policy Objects. Make sure the domain you choose contains the BranchCache Windows 7/Windows 8 client computer accounts that you want to configure.
  3. In the Group Policy Management Console, right- click Group Policy Objects and select New. Name the policy BranchCache Client and click OK. Right- click BranchCache Client and click Edit. The Group Policy Management Editor console opens.

4. In the Group Policy Management Editor console, expand the following path: 

Computer Configuration ➢ Policies ➢ Windows Settings ➢ Security Settings ➢ Windows Firewall With Advanced Security ➢ Windows Firewall With Advanced Security – LDAP ➢ Inbound Rules.

5. Right- click Inbound Rules and then click New Rule. The New Inbound Rule Wizard opens.

6. On the Rule Type screen, click Predefined, expand the list of choices, and then click BranchCache – Content Retrieval (Uses HTTP). Click Next.

7. On the Predefined Rules screen, click Next.

8. On the Action screen, ensure that Allow The Connection is selected and then click Finish. You must select Allow The Connection for the BranchCache client to be able to receive traffic on this port.

9. To create the WS- Discovery firewall exception, right- click Inbound Rules and click New Rule. The New Inbound Rule Wizard opens.

10. On the Rule Type screen, click Predefined, expand the list of choices, and then click BranchCache – Peer Discovery (Uses WSD). Click Next.

11. On the Predefined Rules screen, click Next.

12. On the Action screen, ensure that Allow The Connection is selected and then click Finish.

13. In the Group Policy Management Editor console, right- click Outbound Rules and then click New Rule. The New Outbound Rule Wizard opens.

14. On the Rule Type screen, click Predefined, expand the list of choices, and then click BranchCache – Content Retrieval (Uses HTTP). Click Next.

15. On the Predefined Rules screen, click Next.

16. On the Action screen, make sure that Allow The Connection is selected and then click Finish.

17. Create the WS- Discovery firewall exception by right- clicking Outbound Rules and then clicking New Rule. The New Outbound Rule Wizard opens.

18. On the Rule Type screen, click Predefined, expand the list of choices, and then click BranchCache – Peer Discovery (Uses WSD). Click Next.

19. On the Predefined Rules screen, click Next.

20. On the Action screen, make sure that Allow The Connection is selected and then click Finish. Close the Group Policy Management console.

Now that you have looked at the distributed cache mode configuration, let’s take a look at the hosted mode configuration.

Hosted Mode Requirements

To set up a hosted mode BranchCache configuration, you must first set up a Windows  Server 2022 hosted cache server at the main and branch offices. You also need to be running Windows 7 or above (except for home versions) at the branch offices.

The Windows client machines download the data from the main cache server, and then the hosted cache servers at the branch offices obtain a copy of the downloaded data for other users to access.

Your network infrastructure must also allow for physical connections between the main office and the branch offices. These connections can be VPNs or some type of WAN links. After these requirements are met, your cache server must obtain a server certificate so that the client computers in the branch offices can positively identify the cache servers.

Exercise 11.17 walks you through the process of installing the BranchCache feature on a Windows Server 2022 machine. To begin this exercise, you must be logged into the Windows Server 2022 machine as an administrator.

EXERCISE 11.17

Installing BranchCache on Windows Server 2022

  1. Open Server Manager by clicking the Server Manager icon or by running server manager.exe.
  2. Select Add Roles And Features.
  3. Click Next in the Before You Begin pane (if shown).
  4. Select role- based or feature- based installation and click Next to continue.
  5. Select the Select A Server From The Server Pool option and click Next.
  6. At the Select Server Roles screen, click Next.
  7. At the Select Features screen, click the check box for BranchCache (see Figure 11.26). Then click Next.

FIGURE 11.26 BranchCache option

8. Check the Restart The Destination Server If Required option and then click Install. If a dialog box appears about restarting, click Yes. The system should restart.

9. After the system restarts, log in as the administrator.

Adding an Image to a Container, BranchCache and PowerShell, Microsoft Azure, Using the Web Application Proxy

Configure Advanced File Services – Configuring Storage

Windows Server has come a long way in terms of its file and storage capabilities. I have talked quite a bit about the new features and functionality provided in Windows Server 2022. In this section, you will take a closer look at some of the advanced configuration options available in the Network File System (NFS), BranchCache, and the File Server Resource Manager (FSRM).

Configure the NFS Data Store

The NFS role service and feature set gives IT administrators the ability to integrate a Windows Server–based environment with Unix- based operating systems. Most corporate environments today consist of a mixed operating system infrastructure to some extent. Using a Windows NFS file server, you can configure file shares for use by multiple operating systems throughout the environment.

Windows Server 2022 takes those capabilities even further by enabling you to integrate with platforms such as ESXi. ESXi is vMware’s exclusive operating system–independent hypervisor. ESXi is referred to as a bare- metal operating system because once it is installed on server virtualization hardware, guest virtual machines can be installed without requiring the use of any other underlying operating system. With Windows Server 2022, you can use an NFS share efficiently as an ESXi data store to house all of your guest virtual machines.

Let’s take a look at configuring an NFS data store in Exercise 11.15.

For this exercise, you will need the following:

■     A Windows Server 2022 server

■     A vMware ESXi 5 server

EXERCISE 11.15

Configure the NFS Data Store
  1. Open Server Manager on your Windows Server 2022 machine.
  2. Launch the Add Roles And Features Wizard from the dashboard.
  3. Install the Server for NFS role on the server. A reboot is not required.
  4. Create a new folder on your server named NFS_Datastore, right- click and select Properties, and then navigate to the NFS Sharing tab.
  5. Click the Manage NFS Sharing button to open the NFS Advanced Sharing page and then check the Share This Folder box. Notice how enabling the share also enables the share’s default settings. The share settings let you configure share authentication and user access further if the need arises. The default settings will work just fine for this exercise.
  6. Click the Permissions tab to open the NFS Share Permissions page. This is where you will configure the type of access that will be allowed by machines accessing this NFS data store. By default, the NFS share permissions are set to Read- Only and do not include root access. For this exercise, you will need to change the type of access to Read- Write and check the box to allow root access.
  7. Click OK to close the NFS Share Permissions page and then click Apply and OK on the NFS Advanced Sharing page. Your new NFS share is now built, ready to be presented as an NFS data store to a VMware ESXi host. Be sure to record the network path displayed on the NFS Sharing tab of the share’s Properties page. You will need that information to perform a proper mount on the ESXi host.
  8. Switch to your ESXi host and launch the Add Storage Wizard from the Configuration tab.
  9. On the Select Storage Type page of the wizard, select the Network File System storage type; click Next to continue to the Locate Network File System page.
  10. On this page of the wizard, you will fill in the server and folder information for the NFS share that you will be using as a vSphere data store. Using the information recorded from step 7, properly fill out the server and folder fields and then name your new data store.
  11. Click Next to continue to the Ready To Complete page of the wizard. Review the information and click Finish. Once the Create NAS data store task completes on the ESXi host, you are ready to use your Windows Server 2022 shared folder as a vSphere ESXi data store.

The previous exercise shows how versatile Windows Server 2022 shares can be. The same principles can be applied to making Windows Server shares available to other Unix- based operating systems such as ESXi. Now that you have configured an NFS data store, let’s take a look at what BranchCache has to offer.

Configure BranchCache

BranchCache is a technology that was introduced with Windows Server 2008 R2 and Windows 7. BranchCache allows an organization with slower links between offices to cache data so that downloads between offices do not have to occur each time a file is accessed.

For example, John comes into work and logs into the network. John accesses the corporate website and downloads a media file that takes four minutes to download. With BranchCache enabled, when Judy comes into work, connects to the corporate website, and tries to download the same media file, the file will be cached from the previous download and Judy will have immediate access to the file.

You can set up two types of BranchCache configurations:

Distributed Cache Mode In the distributed cache mode configuration, all Windows client machines cache the files locally on the client machines. Thus, in the previous example, after John downloaded the media file, Judy would receive the cached media file from John’s Windows 7 version or above (except for home versions).

Hosted Mode In the hosted mode configuration, the cache files are cached on a local

(within the site) Windows Server 2022 machine. So, in the previous example, after

John downloads the media file, the cached file would be placed on a Windows Server 2022 machine by default, and all other users (Judy) would download the media file from the Windows Server 2022 machine.

Distributed Cache Mode Requirements

If you decide to install BranchCache in the distributed cache mode configuration, a hosted cache server running Windows Server 2022 is not required at the branch office. To set up distributed cache mode, the client machines must be running Windows 7 or above (except for home versions).

The Windows client machines would download the data files from the content computer at the main branch office, and then these machines become the local cache servers. To set up distributed cache mode, you must install a content computer (the computer that will hold the original content) at the main office first. After the content server is installed, physical connections (WAN or VPN connections) between the sites and branch offices must be established.

Client computers running Windows 7 Enterprise or higher (from versions listed above) have BranchCache installed by default. However, you must enable and configure BranchCache and configure firewall exceptions. Complete Exercise 11.16 to configure BranchCache firewall rule exceptions.

Adding an Image to a Container, Microsoft Azure, Using the Web Application Proxy

Remote Differential Compression – Configuring Storage

One issue that can arise occurs when files are changed. There has to be some mechanism that helps files stay accurate. That’s where the Remote Differential Compression (RDC) feature comes into play. RDC is a group of APIs that programs can use to determine whether files have changed. Once RDC determines that there has been a change, RDC then helps to detect which portions of the files contain the changes. RDC has the ability to detect insertions, removals, and rearrangements of data in files. This feature becomes helpful with limited- bandwidth networks when they replicate changes.

To install the RDC feature, use Server Manager and then run the Add Features Wizard, or type the following command at an elevated command prompt: Servermanagercmd – Install Rdc

Now that I have shown you how to install DFS and how DFS works, let’s go ahead and set up DFS. In Exercise 11.14, I will show you how to configure a DFS Namespace and how to add a shared folder to DFS.

EXERCISE 11.14

Setting Up a DFS Namespace
  1. Open DFS Management (Start ➢ Administrative Tools ➢ DFS Management).
  2. Right- click Namespaces (see Figure 11.22) and choose New Namespace.

FIGURE 11.22 Adding a namespace

3. In the Server box, enter the name of the server that will host this namespace (I am using the DFS server). Click Next.

4. At the Namespace screen, enter the namespace you want (see Figure 11.23) to use and click Next.

EXERCISE 11.14 (continued)

5. On the Namespace Type screen, choose Stand- Alone or Domain Based and click Next. I am using a Stand- Alone DFS.

6. At the Review screen, click Create.

7. Click the Close button. Leave DFS open.

8. Go to Windows Explorer by pressing the Windows Key+E.

9. Create a new folder called Home and share the folder.

10. In DFS under the Actions section (right- hand side), choose New Folder (see Figure 11.24).

FIGURE 11.24 New Folder

11. When the New Folder screen appears, type the name for this folder and then click Add.

12. Add the shared Home folder and click OK.

13. After you have entered a name and put in the Home folder (see Figure 11.25), click OK.

    FIGURE 11.25 Home folder

    14. The namespace has been created and you have added a shared folder to the namespace. Add any of your other shared folders and then close DFS.

      BitLocker Provisioning, BranchCache and PowerShell, Microsoft Azure

      Using the cipher Command – Configuring Storage

      The cipher command is useful when it comes to EFS. Cipher is a command- line utility that allows you to change and/or configure EFS. When it comes to using the cipher command, you should be aware of a few things:

      ■        You can decrypt files by running Cipher.exe in the command prompt window (advanced users).

      ■         You can use Cipher to modify an EFS- encrypted file.

      ■          You can use Cipher to import EFS certificates and keys.

      ■          You can also use Cipher to back up EFS certificates and keys.

      Let’s take a look at some of the switches that you can use with cipher. Table 11.4 describes many of the cipher switches you can use. This table comes from Microsoft’s TechNet site. Microsoft continues to add and improve switches, so make sure you check Microsoft’s website to see whether there are any changes.

      TABLE 11.4 Using the cipher switches

      cipher switchDescription
      /eThis switch allows you to encrypt specified folders. With this folder encrypted, any files added to this folder will automatically be encrypted.
      /dThis switch allows you to decrypt specified folders.
      /s: dirWith this switch, the operation you are running will be performed in the specified folder and all subfolders.
      /iBy default, when an error occurs, cipher automatically halts. By using this switch, cipher will continue to operate even after errors occur.
      /fThe force switch (/f) will encrypt or decrypt all of the specified objects, even if the files have been modified by using encryption previously. Cipher, by default, does not touch files that have been encrypted or decrypted previously.
      /qThis switch shows you a report about the most critical information of the EFS object.
      /hNormally, system or hidden files are not touched by encryption. By using this switch, you can display files with hidden or system attributes.
      /kThis switch will create a new file encryption key based on the user currently running the cipher command.
      /?This shows the cipher help command.

      Configuring Distributed File System

      One problem that network administrators have is deciding how to share folders and communicating to end users how to find the shares. For example, if you share a folder called StormWind Documents on server A, how do you make sure your users will find the folder and the files within it? The users have to know the server name and the share name. This can be a huge problem if you have hundreds of shares on multiple servers. If you want to have

      multiple copies of the folder called StormWind Documents for fault tolerance and load balancing, the problem becomes even more complicated.

      Distributed File System (DFS) in Windows Server 2022 offers a simplified way for users to access geographically dispersed files. DFS allows you to set up a tree structure of virtual directories that allows users to connect to shared folders throughout the entire network.

      You have the ability to take shared folders that are located on different servers and transparently connect them to one or more DFS namespaces— virtual trees of shared folders throughout an organization. The advantage of using DFS is that if one of the folders becomes unavailable, DFS has failover capability that will allow your users to connect to the data on a different server.

      You can use the DFS tools to choose which shared folders will appear in the namespace and also to decide how the names of these shared folders will show up in the virtual tree listing.

      Advantages of DFS

      One of the advantages of DFS is that when a user views this virtual tree, the shared folders appear to be located on a single machine. These are some of the other advantages of DFS:

      Simplified Data Migration DFS gives you the ability to move data from one location to another without the user needing to know the physical location of the data. Because the users do not need to know the physical location of the shared data, you can simply move data from one location to another.

      Security Integration You do not need to configure additional security for the DFS shared folders. The shared folders use the NTFS and shared folder permissions that you have already assigned when the share was set up.

      Access- Based Enumeration (ABE) This DFS feature (disabled by default) displays only the files and folders that a user has permissions to access. If a user does not have access to a folder, Windows hides the folder from the user’s DFS view. This feature is not active if the user is viewing the files and folders locally.

      Types of DFS

      The following are types of DFS:

      DFS Replication (DFSR) You have the ability to manage replication scheduling and bandwidth throttling using the DFS management console. Replication is the process of sharing data between multiple machines. Replicated shared folders allow you to balance the load and have fault tolerance. DFS also has read- only replication folders.

      DFS Namespace The DFS Namespace service is the virtual tree listing in the DFS server. You can set up multiple namespaces on the DFS, allowing for multiple virtual trees within DFS. The DFS Namespace service was once known as Distributed File System in Windows 2000 Server and Windows Server 2003 (in case you still use Server 2003).

      In Exercise 11.13, you will install the DFS Namespace service on the file server. You need to start the installation using the Server Manager MMC.

      EXERCISE 11.13

      Installing the DFS Namespace Service
      1. Open Server Manager by clicking the Server Manager icon or running server manager.exe.
      2. Select Add Roles And Features from the dashboard.
      3. Select Next in the Before You Begin pane (if shown).
      4. Select Role-B ased or Feature-Based installation and click Next to continue.
      5. Select the Select A Server From The Server Pool option and click Next.
      6. On the Select Server Roles screen, expand File And Storage Services and select the DFS Namespace and DFS Replication options (see Figure 11.20). Then click Next. If a dialog box appears, click the Add Features button.

      FIGURE 11.20 Select Server Roles

      7. At the Select Features screen, click Next.

      8. At the Confirmation screen, click the Install button.

      9. After the installation is complete, click the Close button.

      10. Close Server Manager.

      Once you have installed DFS, it’s time to learn how to manage DFS with the DFS Management MMC. The DFS Management console (see Figure 11.21) gives you one place to do all of your DFS configurations. The DFS Management console allows you to set up DFS Replication and DFS Namespace. Another task you can do in the DFS Management console is add a folder target— a folder that you add to the DFS namespace (the virtual tree) for all your users to share.

      Database Cloning

      For the first time ever in DFS, Windows Server 2022 includes a new DFS database cloning function. This new feature allows you to accelerate replication when creating folders, servers, or recovery systems. You will now have the ability to extract the DFS database from a single DFS server and then clone that database to multiple DFS servers.

      You can use PowerShell and the Export- DfsrClone cmdlet to export the volume that contains the DFS database and configuration XML file settings. When you execute this PowerShell cmdlet, a trigger is engaged that exports the DFS service, and the system will not proceed until the service is completed. You then use the PowerShell cmdlet Import- DfsrClone to import the data to a specific volume. The service will then validate that the replication was transferred completely.

      Recovering a DFS Database

      Windows Server 2022 DFS database recovery is a feature that allows DFS to detect a corrupted database, thus allowing DFS to rebuild the database automatically and continue with normal operations of DFS replication. One advantage to this is that when DFS detects and fixes a corrupted database, it does so with no file conflicts.

      Before the introduction of this feature, if a DFS database were determined to be corrupted, DFS Replication would delete the database and start again with an initial nonauthoritative sync process. This would cause newer file versions to be overwritten by older data, causing real data loss.

      DFS in Windows Server 2022 uses local files and an update sequence number (USN) to fix a corrupted database, ensuring no loss of data.

      Optimizing DFS

      Windows Server 2022 DFS allows you to configure variable file staging sizes on individual DFS servers. This allows you to set a minimum file size for a file to stage. This increases the staging size of files, and that in turn increases the performance of the replication.

      Prior to Windows Server 2022, DFS Replication used a hard- coded 256 KB file size to determine staging requirements. If a file size were larger than 256 KB, that file would be staged before it replicated. The more file staging that you have, the longer replication takes on a DFS system.

      BitLocker Provisioning, Configure Azure VM Settings, Microsoft Azure

      BitLocker Provisioning – Configuring Storage

      In previous versions of BitLocker (Windows Vista and Windows 7), BitLocker provisioning (system and data volumes) was completed during the post installation of the BitLocker utility. BitLocker provisioning was done through either the command-l ine interface (CLI) or Control Panel. In the Windows 8+ /Windows Server 2022 version of BitLocker, you can choose to provision BitLocker before the operating system is even installed.

      You can enable BitLocker prior to the operating system deployment from the Windows Preinstallation Environment (WinPE). BitLocker is applied to the formatted volume, and  BitLocker encrypts the volume prior to running the Windows setup process.

      If you want to check the status of BitLocker on a particular volume, you can view the status of the drive either in the BitLocker Control Panel applet or in Windows Explorer.

      Used Disk Space–Only Encryption

      Windows 7 BitLocker requires that all data and free space on the drive must be encrypted.

      Because of this requirement, the encryption process can take a long time on larger volumes. In Windows 10+ BitLocker, you have the ability to encrypt either the entire volume or just the space being used. When you choose the Used Disk Space Only option, only the section of the drive that contains data will be encrypted. Because of this, encryption is completed much faster.

      Standard User PIN and Password Change

      One issue that BitLocker has had in the past is that you need to be an administrator to configure BitLocker on operating system drives. This could become an issue in a large organization because deploying TPM + PIN to a large number of computers can be challenging.

      Even with the new operating system changes, administrative privileges are still needed to configure BitLocker, but now your users have the ability to change the BitLocker PIN for the operating system or change the password on the data volumes.

      When a user gets to choose their own PIN and password, they normally choose something that has meaning to them and something that is easy to remember. That is a good and a bad thing at the same time. It’s a good thing because when your users choose their own PIN and password, they normally don’t need to write it down—t hey just know it. It’s a bad thing because if anyone knows the user well, they can have an easier time figuring out the person’s PIN and password. Even when you allow your users to choose their own PIN and password, make sure you set a GPO to require password complexity.

      Network Unlock

      One of the features of BitLocker is Network Unlock. Network Unlock allows you to easily manage desktops and servers that are configured to use BitLocker. Network Unlock allows you to configure BitLocker to automatically unlock an encrypted hard drive during a system reboot when that hard drive is connected to your trusted corporate environment. For this to function properly on a machine, there has to be a DHCP driver implementation in the system’s firmware.

      If your operating system volume is also protected by the TPM + PIN protection, you have to be sure to enter the PIN at the time of the reboot. This protection can actually make using Network Unlock more difficult to use, but they can be used in combination.

      Support for Encrypted Hard Drives for Windows

      One of the new advantages of using BitLocker is Full Volume Encryption (FVE). BitLocker provides built- in encryption for Windows data files and Windows operating system files. The advantage of this type of encryption is that encrypted hard drives that use Full Disk Encryption (FDE) get each block of the physical disk space encrypted. Because each physical block gets encrypted, it offers much better encryption. The only downside to this is that because each physical block is encrypted, it degrades the hard drive speed somewhat. So, as an administrator, you have to decide whether you want better speed or better security on your hard disk.

      In Exercise 11.12, you will enable BitLocker on the Windows Server 2022 system.

      EXERCISE 11.12

      Enabling BitLocker in Windows Server 2022

      1. Open Server Manager by clicking the Server Manager icon or running server manager.exe.
      2. Select Add Roles And Features from the dashboard.
      3. Select Next in the Before You Begin pane (if shown).
      4. Select role- based or feature- based installation and click Next to continue.
      5. Select the Select A Server From The Server Pool option and click Next.
      6. At the Select Server Roles screen, click Next.
      7. At the Select Features screen, click the BitLocker Drive Encryption check box. When the Add Roles and Features dialog box appears, click the Add Features button. Then click Next.
      8. Click the Install button in the Confirmation pane of the Add Roles And Features Wizard to begin BitLocker feature installation. The BitLocker feature requires a restart to complete. Selecting the Restart The Destination Server Automatically If Required option in the Confirmation pane will force a restart of the computer after installation is complete.
      9. If the Restart The Destination Server Automatically If Required option is not selected, the Results pane of the Add Roles And Features Wizard will display the success or failure of the BitLocker feature installation. If required, a notification of additional action necessary to complete the feature installation, such as the restart of the computer, will be displayed in the results text.

      You also can install BitLocker by using the Windows PowerShell utility. To install BitLocker, use the following PowerShell commands:

      Install- WindowsFeature BitLocker – IncludeAllSubFeature –

      IncludeManagementTools – Restart

      Using EFS Drive Encryption

      If you have been in the computer industry long enough, you may remember the days when only servers used NTFS. Years ago, most client systems used FAT or FAT32, but NTFS had some key benefits over FAT/FAT32. The main advantages were NTFS security, quotas, compression, and encryption. Encryption is available on a system because you are using a file structure (for example, NTFS) that allows encryption. Windows Server 2022 NTFS allows you to use these four advantages, including encryption.

      Encrypting File System (EFS) allows a user or administrator to secure files or folders by using encryption. Encryption employs the user’s security identification (SID) number to secure the file or folder. Encryption is the strongest protection that Windows provides to help you keep your information secure. Some key features of EFS are as follows:

      ■        Encrypting is simple; just select a check box in the file or folder’s properties to turn it on.

      ■          You have control over who can read the files.

      ■        Files are encrypted when you close them but are automatically ready to use when you open them.

      ■        If you change your mind about encrypting a file, clear the check box in the file’s properties.

      To implement encryption, open the Advanced Attributes dialog box for a folder and check the Encrypt Contents To Secure Data option.

      If files are encrypted using EFS and you have to unencrypt the files, there are two ways you can do this. You can log in using the user’s account (the account that encrypted the files) and unencrypt the files using the cipher command. Alternatively, you can become a recovery agent and manually unencrypt the files.

      BitLocker Provisioning, Microsoft Azure, Using the Web Application Proxy

      Configuring File Server Resource – Configuring Storage

      Manager

      As an administrator, when you need to control and manage the amount and type of data stored on your servers, Microsoft delivers the tools to help you do just that. The File Server Resource Manager (FSRM) is a suite of tools that allows you to place quotas on folders or volumes, filter file types, and create detailed storage reports. These tools allow you to properly plan and implement policies on data as needed.

      FSRM Features

      Many of the advantages of using FSRM come from all of the included features, which allow you to manage the data that is stored on your file servers. Some of the advantages included with FSRM are as follows:

      Configure File Management Tasks FSRM allows you to apply a policy or action to data files. Some of the actions that can be performed include the ability to encrypt files or run a custom command.

      Configure Quotas Quotas give you the ability to limit how much disk space a user can use on a file server. You can limit space to an entire volume or to specific folders.

      File Classification Infrastructure You can set file classifications and then manage the data more effectively by using these classifications. Classifying files, and then setting policies to those classifications, allows you to set policies on those classifications. These policies include restricting file access, file encryption, and file expirations.

      Configure File Screens You can set file screening on a server and limit the types of files that are being stored on that server. For example, you can set a file screen on a server so that any file ending in .bmp gets rejected.

      Configure Reports You can create reports that show you how data is classified and accessed. You also have the ability to see which users are trying to save unauthorized file extensions.

      Installing the FSRM Role Service

      Installing FSRM is easy when using either Server Manager or PowerShell. To install using

      Server Manager, you go into Add Roles And Features and choose File And Storage Services ➢ File Services ➢ File Server Resource Manager. To install FSRM using PowerShell, you use the following command:

      Install- WindowsFeature – Name FS- Resource- Manager – IncludeManagementTools

      Configuring FSRM using the Windows GUI version is straightforward, but setting up FSRM using PowerShell is a bit more challenging. Table 11.3 describes some of the PowerShell commands for FSRM.

      TABLE 11.3 PowerShell commands for FSRM

      Get- FsrmAutoQuotaGets auto- apply quotas on a server
      Get- FsrmClassificationGets the status of the running file classification
      Get- FsrmClassificationRuleGets classification rules
      Get- FsrmFileGroupGets file groups
      Get- FsrmFileScreenGets file screens
      Get- FsrmFileScreenExceptionGets file screen exceptions
      Get- FsrmQuotaGets quotas on the server
      PowerShell CmdletDescription
      Get- FsrmSettingGets the current FSRM settings
      Get- FsrmStorageReportGets storage reports
      New- FsrmAutoQuotaCreates an auto- apply quota
      New- FsrmFileGroupCreates a file group
      New- FsrmFileScreenCreates a file screen
      New- FsrmQuotaCreates an FSRM quota
      New- FsrmQuotaTemplateCreates a quota template
      Remove- FsrmClassificationRuleRemoves classification rules
      Remove- FsrmFileScreenRemoves a file screen
      Remove- FsrmQuotaRemoves an FSRM quota from the server
      Set- FsrmFileScreenChanges the configuration settings of a file screen
      Set- FsrmQuotaChanges the configuration settings for an FSRM quota

      Configure File and Disk Encryption

      Hardware and software encryption are some of the most important actions you can take as an administrator. You must make sure that if anyone steals hardware from your company or from your server rooms that the data they are stealing is secured and cannot be used. This is where BitLocker can help.

      Using BitLocker Drive Encryption

      To prevent individuals from stealing your computer and viewing personal and sensitive data found on your hard disk, some editions of Windows come with a new feature called BitLocker Drive Encryption. BitLocker encrypts the entire system drive. New files added to this drive are encrypted automatically, and files moved from this drive to another drive or computers are decrypted automatically.

      Windows Server 2022 includes BitLocker Drive Encryption, and only the operating system drive (usually C:) or internal hard drives can be encrypted with BitLocker. Files on other types of drives must be encrypted using BitLocker To Go. BitLocker To Go allows you to put BitLocker on removable media such as external hard disks or USB drives.

      BitLocker Recovery Password
      The BitLocker recovery password is important. Do not lose it, or you may not be able to unlock the drive. Even if you do not have a Trusted Platform Module (TPM), be sure to keep your recovery password in case your USB drive becomes lost or corrupted.

      BitLocker uses a Trusted Platform Module (TPM) version 1.2 or newer to store the security key. A TPM is a chip that is found in newer computers. If you do not have a computer with a TPM, you can store the key on a removable USB drive. The USB drive will be required each time you start the computer so that the system drive can be decrypted.

      If the TPM discovers a potential security risk, such as a disk error or changes made to the BIOS, hardware, system files, or startup components, the system drive will not be unlocked until you enter the 48- digit BitLocker recovery password or use a USB drive with a recovery key as a recovery agent.

      BitLocker must be set up either within the Local Group Policy editor or through the BitLocker icon in Control Panel. One advantage of using BitLocker is that you can prevent any unencrypted data from being copied onto a removable disk, thus protecting the computer.

      BitLocker requires that you have a hard disk with at least two partitions, both formatted with NTFS. One partition will be the system partition that will be encrypted. The other partition will be the active partition that is used to start the computer. This partition will remain unencrypted.

      Features of BitLocker

      As with any version of Windows, Microsoft continues to improve on the technologies used in Windows Server 2022 and Windows 10/11. The following subsections cover some of the features of BitLocker.

      BranchCache and PowerShell, Configure Azure VM Settings, Microsoft Azure

      Installing and Enabling Data Deduplication- Configuring Storage

      To install data duplication, you have two ways to choose from. You can install data duplication through Server Manager or through PowerShell. Let’s take a look at each way. To install data deduplication by using Server Manager:

      1. On the Windows Server 2022 system, open Server Manager.
      2. Click the Add Roles And Features link.
      3. At the Before You Begin screen, click Next.
      4. At the Select Installation Type screen, choose role- based or feature- based installation and then click Next.
      5. Choose the server where you want to install Data Duplication and click Next.
      6. On the Select Server Roles screen, select File and Storage Services ➢ File And iSCSI Services and then select the Data Deduplication option (shown in Figure 11.17). Click Next.
      7. Click Next at the Selected Features screen.
      8. Click the Install button once you’ve confirmed that all options are correct.
      9. Once completed, close Server Manager.

      Understanding Data Duplication

      FIGURE 11.17 Selecting Data Deduplication

      To install data deduplication by using PowerShell:

      1. Click the Start button, then click Windows PowerShell ➢ More ➢ Run As Administrator.
      2. In the Windows PowerShell console, enter the following commands (one at a time) followed by the Enter key: Import- Module ServerManager

      Add- WindowsFeature – name FS- Data- Deduplication

      Import- Module Deduplication

      After you have installed data duplication, you must then enable it on the servers. To enable data duplication in Server Manager, you would need to complete the following steps:

      1. In Server Manager, click File And Storage Services.
      2. Click Volumes. On right side, click the volume where you want to set up Data Duplication. Right- click the volume and choose Configure Data Deduplication (see Figure 11.18).

      FIGURE 11.18 Enabling Data Deduplication

      3. The New Volume Deduplication Settings Wizard will start. From the Data Deduplication pull- down, choose General Purpose File Server (shown in Figure 11.19). Enter the number of days that should elapse from the date of file creation until files are deduplicated (I used 3 days), enter the extensions of any file types that should not be duplicated (I used .exe), and then click Add to browse to any folders with files that should not be deduplicated ( I included \test share). Click OK once completed. You can also set a deduplication schedule by clicking the Set Deduplication Schedule button.

      Monitoring Data Deduplication

      Finally, after data deduplication is installed and configured, you will want to monitor the progress of the data deduplication jobs. To do this, you can run the following PowerShell commands (these commands will show you the status of the duplication process):

      Get- DedupStatus 

      Get- DedupVolume

      Configuring File Server Resource Manager

      Recent Comments

      No comments to show.
      Back To Top