Target Device RAM - Selecting the target device RAM as the write cache location sets aside a portion of the RAM on the target device for the write cache.
Benefits: 
- It is the fastest type of write cache.
Considerations:
- The RAM is diverted from workload use.
- The cost is greater than using storage.
- The amount of RAM required for the write cache is difficult to determine yet critical to the stability of the environment.
- The target device fails when the allocated write-cache space reaches capacity

Target Device Local Storage - Create the cache file on the local Provisioning Services host in order to help determine future cache drive size requirements. This should be done in the Proof of Concept and Pilot phases of a rollout.
Selecting local storage as the write-cache location dedicates a portion of the target device local storage for the write cache. The local storage can be either a physical or virtual disk drive.
Benefits:
- Does not require additional resources if local disks are unused and installed already on physical target devices
- Provides fast response times because reading to and writing from the write cache is performed locally
- Requires you to determine the size of the write cache, which is critical to prevent server failure
- Provides ample space for the write cache, minimizing risk of underestimating disk requirements
Considerations:
- Live migration is not possible on virtual target devices because the storage is not shared across virtual infrastructure servers

Target Device Shared Storage - Selecting target device shared storage as the write-cache location places the write cache on a shared storage device attached to the target device. This write-cache type is usually only valid in environments that use virtual target devices, such as Citrix XenServer. The storage is assigned to each virtual machine from a shared storage repository. Using a shared storage solution for vDisk storage with Provisioning Services requires that a shared file system be placed in front of the SAN or other shared storage to coordinate multiple server access to the NTFS formatted LUN.
Benefits:
- Response times are faster
- Storage costs are significantly cheaper than RAM
- Live migration is possible because the target device cache storage is accessible from multiple virtual machines
Considerations:
- Speed is slower than target device RAM or local disk cache
- Setup and configuration of a shared storage solution is required if one is not already in place

Provisioning Services Local Storage - Selecting Provisioning Services local storage as the write-cache location stores the write cache on the physical disks on the Provisioning Services host
Benefits:
- Simplest option to set up
- Additional resources or configuration within the environment not required
- Inexpensive disk space
Considerations:
- Performance is the slowest due to write-cache requests traversing the network between the target device and Provisioning Services host.
- Provisioning Services host scalability is reduced because Stream service must also service the write-cache requests.
- Provisioning Services high availability is not possible because the write-cache storage is not accessible by other Provisioning Services hosts.
- Provisioning Services host fails if the local storage space is exceeded.

Provisioning Services Shared Storage - Selecting Provisioning Services shared storage as the write-cache location places the write cache on a shared storage solution that is connected to the Provisioning Services host
Benefits:
- Provisioning Services high availability is possible because all Provisioning Services hosts attached to shared storage can access the write cache
- Shared storage devices typically hold a large amount of data, which mitigates storage size concerns
Considerations:
- Performance is reduced because write-cache requests must traverse the network between the target device, Provisioning Services host, and the shared storage
- Provisioning Services host scalability is reduced because Stream service must also service the write-cache requests
- Setup and configuration of a shared storage solution is required if one is not already in place