The graphic below provides a high-level view of a basic Provisioning Services infrastructure and shows how Provisioning Services components might appear within that implementation.
The rest of the article provides a brief introduction to Provisioning Services components.
Network services include a DHCP service, Preboot Execution Environment (PXE) service, and a TFTP service. These service options can be used during the boot process to retrieve IP addresses, and locate then download the boot program from the Provisioning Server to the target device. Alternative boot options are also available.
A farm contains one or more stores. A store is a logical name for a physical or virtual vDisk storage location. The store name is the common name used by all Provisioning Servers within the farm.
The physical vDisk for Windows 10 resides on a Provisioning Server local to a site. The logical name that is given to this physical location is the store.
Store name (logical name): bostonwin10
Physical path to the vDisk is: C:\vDisks\
The physical vDisk for Windows 10 resides on a network share (FinanceVdisks) at the farm level.
Store name (logical name): financevdisks
Physical path to the vDisk for all Provisioning Servers in the farm is: \\financeserver\financevdisks\
Sites are represented in the Console as follows:
A Provisioning Server is any server that has Stream Services installed. Stream Services is used to stream software from vDisks to target devices. In some implementations, vDisks reside directly on the Provisioning Server. In larger implementations, Provisioning Servers may get the vDisk from a shared-storage location on the network.
Provisioning Servers also exchange configuration information with the Provisioning Services database. Provisioning Server configuration options are available to ensure high availability and load balancing of target device connections.
vDisk pools are the collection of all vDisks available to a site. There is only one vDisk pool per site.
vDisk Update Management
The vDisk Update Management feature is used to configure the automation of vDisk updates using virtual machines. Automated vDisk updates can occur on a scheduled basis, or can be invoked directly from the Console. This feature supports updates detected and delivered from Electronic Software Delivery (ESD) servers, Windows updates, or other pushed updates.
Device collections are logical groups of target devices. A target device is a device, such as a desktop computer or a server, that boots and gets software from a vDisk on the network. A device collection could represent a physical location, a subnet range, or a logical grouping of target devices. Creating device collections simplifies device management by enabling you to perform actions at the collection level rather than at the target-device level.
vDisks exist as disk image files on a Provisioning Server or on a shared storage device. A vDisk consists of a .vhdx base image file, any associated properties files (.pvp), and if applicable, a chain of referenced VHD differencing disks (.avhdx).
vDisks are assigned to target devices. Target devices boot from and stream software from an assigned vDisk image.
vDisk images are configured to be in Private Image mode (for use by a single device, read/write) or Standard Image mode (for use by multiple devices, read-only with various caching options).
Any updates to a vDisk base image can be captured in a versioned differencing disk, leaving the original base disk image unchanged. The following illustrates the basic relationship between a base disk and versions that reference that base disk.
Each time a vDisk is to be updated, a new version of the VHDX differencing disk can be created and the file name is numerically incremented, as shown in the following table:
Booting a vDisk
The method used to locate and boot from a vDisk on a server share is illustrated in the following graphic:
Views allow you to quickly manage a group of target devices. Views are typically created according to business needs. For example, a view can represent a physical location, such as a building, or a user type. A target device can be a member of any number of views, although it can be a member of only one device collection.
Views are represented in the Console as follows: