Note: It is
recommended that you read the Release Notes document before installing
target-device software. Before installing the product software on a Master
Target Device, turn off any BIOS-based-virus protection features. To include
anti-virus software on the vDisk image, be sure to turn the anti-virus software
back on prior to running the Imaging Wizard.
Services target device software must be installed on a Master Target Device
prior to building a vDisk image. Install and configure Microsoft NIC teaming
driver, introduced in Windows Server 2012, or OEM NIC teaming software prior to
installing Target Device software.
Services target device software components include:
- Provisioning Services Virtual
Disk, which is the virtual media used to store the disk components of the
operating system and applications.
- Provisioning Services Network
Stack, which is a proprietary filter driver that is loaded over the NIC
driver, allowing communications between the target devices and the Provisioning
- Provisioning Services SCSI
Miniport Virtual Adapter, which is the driver that allows the vDisk to be
mounted to the operating system on the target device.
- Provisioning Services
Imaging Wizard, use to create the vDisk file and image the Master Target
- Virtual Disk Status Tray
Utility, to provide general vDisk status and statistical information. This
utility includes a help system.
- Target Device Optimizer
Utility, used to change target device setting to improve performance.
Services target device software is available for 32-bit and 64-bit Windows
installing Provisioning Services target device software on NT6.x systems within
a multi-NIC environment, all available NICs can be used. Therefore bindcfg.exe
is no longer required and no longer installed with target device software
(Windows Vista, Windows 2008, Windows 7, Windows 2008 R2, Windows 8, and
Windows Server 2012). However, if Provisioning Services detects NT5.x systems
(Windows XP or Windows 2003), bindcfg.exe continues to install with the target
device product software and appears during the target device installation
process. With NT5.x Windows XP or Windows 2003 systems, if the inactive NIC
fails to bind to Provisioning Services, start bindcfg.exe from the Provisioning
Services installation directory (default is: C:\Program