- Launch the Console
- Farm Properties
- Server Properties
- vDisk Stores
- Device Collections
- Prevent “No vDisk Found” PXE Message
Launch the Console
- Launch the Provisioning Services Console.
- Right-click the top-left node, and click Connect to Farm.
- Enter localhost, and click Connect.
- Right-click the farm name, and click Properties.
- On the Groups tab, add the Citrix Admins group.
- On the Security tab, add the Citrix Administrators group to grant it full permission to the entire Provisioning Services farm. You can also assign permissions in various nodes in the Provisioning Services console.
- On the Options tab, check the boxes next to Enable Auditing, and Enable offline database support.
- In Provisioning Services 7.9 and newer, notice the new Send anonymous statistics and usage information checkbox, which enables Customer Experience Improvement Program (CEIP).
- See http://www.carlstalhood.com/delivery-controller-7-15-ltsr-and-licensing/#ceip for additional places where CEIP is enabled.
- In the Problem Report tab, you can enter MyCitrix credentials.
- Click OK to close Farm Properties.
- Click OK when prompted that a restart of the service is required.
Q: What is the optimum number of ports for the Stream Service?
A: The best Stream Process performance is attained when the threads per port is not greater than the number of cores available on the Provisioning Server. For best performance, use the following formula:
# of ports x # of threads/port = max clients
- Expand the site and click Servers. For each Provisioning Server, right-click it, and click Configure Bootstrap.
- Click Read Servers from Database. This should cause both servers to appear in the list.
- From Carl Fallis at PVS HA at Citrix Discussions: when stopping the stream service through the console the PVS server will send a message to the targets to reconnect to another server before the stream service shuts down. The target then uses the list of login servers (Bootstrap servers) and reconnects to another server, this is almost instantaneous failover and can’t really be detect . In the case of the PVS server failing the target detects it and reconnects, slightly different mechanism and the target may hang for a short time. Check out the following article for more information https://www.citrix.com/blogs/2014/10/16/provisioning-services-failover-myth-busted for the PVS server failure case. 💡
- On the Options tab, check the box next to Verbose mode.
- Right-click the server, and click Properties.
- On the General tab, check the box next to Log events to the server’s Windows Event Log.
- Click Advanced.
- Increase the threads per port. The number of threads per port should match the number of vCPUs assigned to the server.
- On the same tab are concurrent I/O limits. Note that these throttle connections to local (drive letter) or remote (UNC path) storage. Setting them to 0 turns off the throttling. Only testing will determine the optimal number. See http://blogs.citrix.com/2011/02/23/optimizing-pvs/ for more details.
- Click OK to close Advanced Server Properties.
- On the Network tab, change the Last port to 6968.
- Note: port 6969 is used by the Provisioning Services two-stage boot component.
- According to Citrix Blog Post Updated Guidance on PVS Ports and Threads, you can set the First port to 7000 to avoid port 6969 and get more ports. 💡
- Click OK when done.
- Click Yes if prompted to restart the stream service.
- If you get an error message about the stream service then you’ll need to restart it manually.
- From Carl Fallis at PVS HA at Citrix Discussions: when stopping the stream service through the console the PVS server will send a message to the targets to reconnect to another server before the stream service shuts down. The target then uses the list of login servers and reconnects to another server, this is almost instantaneous failover and can’t really be detect . In the case of the PVS server failing the target detects it and reconnects, slightly different mechanism and the target may hang for a short time. Check out the following article for more information https://www.citrix.com/blogs/2014/10/16/provisioning-services-failover-myth-busted for the PVS server failure case. 💡
- Repeat for the other servers. You can copy the Server Properties from the first server, and paste them to additional servers.
Create vDisk Stores
To create additional vDisk stores (one per vDisk / Delivery Group), do the following:
- On the PvS servers, using Explorer, go to the local disk containing the vDisk folders and create a new folder. The folder name usually matches the vDisk name. Do this on both PvS servers.
- In the Provisioning Server Console, right-click Stores, and click Create Store.
- Enter the name for the vDisk store, and select an existing site.
- Switch to the Servers tab. Check the boxes next to the Provisioning Servers.
- On the Paths tab, enter the path for the Delivery Group’s vDisk files. Click Validate.
- Click Close and then click OK.
- Click Yes when asked for the location of write caches.
Create Device Collections
- Expand the site, right-click Device Collections, and click Create Device Collection.
- Name the collection in some fashion related to the name of the Delivery Group, and click OK.
If you are migrating from one PvS farm to another, see Kyle Wise How To Migrate PVS Target Devices.
Prevent “No vDisk Found” PXE Message
If PXE is enabled on your PvS servers, and if you PXE boot a machine that is not added as a device in the PvS console, then the machine will pause booting with a “No vDisk Found” message at the BIOS boot screen. Do the following to prevent this.
- Enable the Auto-Add feature in the farm Properties on the Options tab.
- Create a small dummy vDisk (e.g. 100 MB).
- Create a dummy Device Collection.
- Create a dummy device.
- Set it to boot from Hard Disk
- Assign the dummy vDisk and click OK.
- Set the dummy device as the Template.
- Right-click the site, and click Properties.
- On the Options tab, point the Auto-Add feature to Dummy collection, and click OK.