- Preparing network switches
- Using UNC names
- Reducing network utilization
- Managing Roaming User Profiles
- Booting through a router
- Managing multiple network interface cards
- Updating NIC drivers
- Managing and accessing a LUN without using a network share
Normally, using a SAN for vDisk storage with Provisioning Services requires a shared file system to be placed in front of the SAN to coordinate multiple server access to the NTFS formatted LUN(s). However, in some cases it is possible to allow Provisioning Services to use a SAN without a shared file system. Provisioning Services can do this and still allow multiple servers access to the same LUN(s) without volume corruption.
Provisioning Services only allows read-only shared access to the SAN LUN(s). Therefore the desired boot modes for Provisioning Services target devices are important when using this feature.
Boot Mode | Write Cache Limitations | Restrictions |
---|---|---|
Private Image | Not supported | Not supported |
Standard Image with cache on server disk | Separate shared read-write write cache location is required for the store. | vDisk properties cannot be modified while the LUN is read-only. vDisks cannot be mapped on the Provisioning Server. |
Standard Image with cache in target device RAM | No limitation. | vDisk properties cannot be modified while the LUN is read-only. vDisks cannot be mapped on the Provisioning Server. |
Standard Image with cache on the target device’s hard drive | Fall back to cache on server disk does not function if the target device hard drive is not found or fails. | vDisk properties cannot be modified while the LUN is read-only. vDisks cannot be mapped on the Provisioning Server. |