When planning for storage tiering, you should assess the workload characteristics of your storage environment so that you can store your data most cost-effectively depending on how you use it.

In Windows Server 2016, the server automatically optimizes your storage performance by transparently moving the data that's accessed more frequently to your faster solid state drives (the SSD tier) and moving less active data to your less expensive, but higher capacity, hard disk drives (the HDD tier).

Cold, or cool, data is files that you access infrequently, and have a longer lifespan. In contrast, the most common workload characteristics also includes a smaller portion of the data that is typically hot. Hot data, commonly referred to as working set, is files that you are working on currently; this part of the data set is highly active and changes over time.

Don't allocate all available SSD capacity for your storage spaces immediately. Keep some SSD capacity in the storage pool in reserve, so you can increase the size of an SSD tier when a workload demands it.

Don't pin files to storage tiers until you see how well Storage Tiers Optimization can optimize storage performance. When a tenant or workload requires a particular level of performance, you can pin files to a storage tier to ensure that all I/O activity is performed on that tier.

Do consider pinning the parent VHDX file to the SSD tier if you're providing pooled desktops through VDI. If you have deployed a Virtual Desktop Infrastructure (VDI) to provide pooled desktops for users, you should consider pinning the master image that's used to clone users' desktops to the SSD tier.

Event 103: The capacity consumption of the storage pool %1 has exceeded the threshold limit set on the pool. Return Code: %2.

Event 104: The capacity consumption of the storage pool %1 is now below the threshold limit set on the pool. Return Code: %2.

Event 102: Majority of the physical drives of storage pool %1 failed a configuration update, which caused the pool to go into a failed state. Return Code: %2.

Event 200: Windows was unable to read the drive header for a physical drive.

Event 100: Physical drive %1 failed to read the configuration or returned corrupt data for storage pool %2. As a result, the in- memory configuration might not be the most recent copy of the configuration. Return Code: %3.

Event 201: The metadata on a physical drive has become corrupt.

Event 202: The metadata on a physical drive has become corrupt.

Event 203: An I/O failure has occurred on a physical drive.

Event 300: Physical drive %1 failed to read the configuration or returned corrupt data for storage space %2. As a result, the in- memory configuration might not be the most recent copy of the configuration. Return Code: %3.

Event 301: All pool drives failed to read the configuration or returned corrupt data for storage space %1. As a result, the storage space will not attach. Return Code: %2.

Event 302: Majority of the pool drives hosting space meta-data for storage space %1 failed a space meta-data update, which caused the storage pool to go in failed state. Return Code: %2.