Abstract
This chapter delves into operational settings, and some more detailed configuration settings. It discusses the components of the Provisioning Services Console looking into server and site settings. It focuses on using the Boot Device Manager to create a boot file as an alternative to using PXE boot. Thereafter, it emphasizes adding a physical write cache disk for enhanced performance. The Provisioning Services Boot Device Manager is used in situations where PXE (Preboot Execution Environment) and Dynamic Host Configuration Protocol (DHCP) are not available to be used. This can be particularly useful in a proof of concept environment where DHCP is not available to be used in the datacenter. The use of DHCP is often restricted on networks. Care should also be taken with PXE that there are no clashes with other PXE services running. Microsoft SMS and Altiris Deployment Server are two examples of other programs that use PXE. The .ISO files can be used to provide the network location of the provisioning server, as well as to assign an IP address to the virtual desktop. The Provisioning Services BOOTPTAB Editor can be used to manually edit the PXE boot file, however, it is not the recommended method of editing the boot file. The recommended mechanism to edit the boot file is to rerun the Provisioning Services Configuration Wizard, which will automatically make the changes to the file.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
