Register-ScheduledTask -TaskName "Pin Dedup Metadata CSV1" -TaskPath "\Microsoft\Windows\Storage Tiers Management" -Action $PinTaskAction -User "SYSTEM" -RunLevel Highest -Trigger $PinTaskTrigger -Settings $PinTaskSettingsSet Best practice: Ensure that Data Deduplication metadata files in the chunk store are pinned to the slower tier. Follow this with the Storage Spaces Tier optimization job to move the Data Deduplication chunk store to the slower tier, freeing space in the faster tier for recalled user data. Virtual machine configuration To simulate customer scenarios, Windows 7 SP1 (with the latest updates) was used as the guest operating system. For compatibility with the VDI solution in Windows Server 2012 R2, the tenant virtual machine was configured as a generation 1 virtual machine. The virtual machine template was set with two virtual processors, and it was configured to use dynamic memory with a minimum of 1 GB RAM allocated for startup and maximum limits set to 1.5 GB. All the tenant virtual machines were deployed by using Microsoft System Center Virtual Machine Manager 2012 R2 (SCVMM). The virtual machine template was set to use two virtual hard disks. The guest operating system was configured to create a page file on an additional disk that is dedicated for this purpose. The page file data was separated from the base operating system data for the following reasons: To allow better management of transient page file data for operations such as backup and replication. To allow deployment of frequently accessed page file data to fast SSD storage. To allow exclusion of frequently accessed page file data from Data Deduplication, which avoids expensive processing of easily invalidated data. Each virtual machine was set up with typical information worker applications such as Microsoft Office, Internet Explorer, Adobe Reader, and FreeMind for test purposes, before finalizing the VHD templates. The operating system VHD template was compacted by using the Windows PowerShell cmdlet to reduce its overall size and reduce file copy overhead during deployment. SCVMM was made aware of the storage and compute resources, and the file shares that were exposed by the Scale-Out File Server were configured with the appropriate classification. This allowed SCVMM to efficiently deploy a large number of virtual machines and distribute the virtual hard disks across the file shares according their classification. For more information, see
Register-ScheduledTask -TaskName "Pin Dedup Metadata CSV1" -TaskPath "\Microsoft\Windows\Storage Tiers Management" -Action $PinTaskAction -User "SYSTEM" -RunLevel Highest -Trigger $PinTaskTrigger -Settings $PinTaskSettingsSet Best practice: Ensure that Data Deduplication metadata files in the chunk store are pinned to the slower tier. Follow this with the Storage Spaces Tier optimization job to move the Data Deduplication chunk store to the slower tier, freeing space in the faster tier for recalled user data. Virtual machine configuration To simulate customer scenarios, Windows 7 SP1 (with the latest updates) was used as the guest operating system. For compatibility with the VDI solution in Windows Server 2012 R2, the tenant virtual machine was configured as a generation 1 virtual machine. The virtual machine template was set with two virtual processors, and it was configured to use dynamic memory with a minimum of 1 GB RAM allocated for startup and maximum limits set to 1.5 GB. All the tenant virtual machines were deployed by using Microsoft System Center Virtual Machine Manager 2012 R2 (SCVMM). The virtual machine template was set to use two virtual hard disks. The guest operating system was configured to create a page file on an additional disk that is dedicated for this purpose. The page file data was separated from the base operating system data for the following reasons: To allow better management of transient page file data for operations such as backup and replication. To allow deployment of frequently accessed page file data to fast SSD storage. To allow exclusion of frequently accessed page file data from Data Deduplication, which avoids expensive processing of easily invalidated data. Each virtual machine was set up with typical information worker applications such as Microsoft Office, Internet Explorer, Adobe Reader, and FreeMind for test purposes, before finalizing the VHD templates. The operating system VHD template was compacted by using the Windows PowerShell cmdlet to reduce its overall size and reduce file copy overhead during deployment. SCVMM was made aware of the storage and compute resources, and the file shares that were exposed by the Scale-Out File Server were configured with the appropriate classification. This allowed SCVMM to efficiently deploy a large number of virtual machines and distribute the virtual hard disks across the file shares according their classification. For more information, see
WindowsServer2012R2DeduplicatedVDIDeployment.docx