Product Documentation

Fixed issues

Sep 21, 2016

Compared to: Provisioning Services 7.9 

Provisioning Services 7.11 contains all fixes that were included in Provisioning Services 7, 7.1, 7.67.7, 7.8, and 7.9, plus the following, new fixes:

Console Issues

  • The XenDesktop Setup wizard does not use the template boot properties when creating targets. To enable the fix, create the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ProvisioningServices
    Name: UseTemplateBootOrder
    Type: REG_DWORD
    Data: 1

    [#LC5237]

  • Attempts to create virtual machines through the XenDesktop setup wizard might fail in a non-English Microsoft System Center Virtual Machine Manager (SCVMM) environment.

    [#LC5451]

  • Problem connecting to a PVS 7.8 Farm console. This issue only occurs for customers with large AD setups where the user logging on to PVS belongs to a subdomain of the domain containing the group that provides Farm Administrator rights. 

    [#LC5432]

Server Issues

  • The number of target devices on the Provisioning Services Console might show less than the actual value after the database connection is lost and recovered.

    [#LC4275]

  • The Citrix PXE service might ignore the entries in the BOOTPTAB file.

    [#LC4600]

  • The Provisioning Server logs might show incorrect IP addresses for target devices.

    [#LC5323]

  • The following database access error might appear in the event viewer of the Provisioning Server:

    "DBAccess error: <Couldn't add record -- same fields as an existing record><-31749>."

    The issue occurs when multiple Provisioning Servers call a specific stored procedure simultaneously, causing conflicts between the calls to the stored procedure. As a result, an attempt to insert a record with the same key value twice might occur.

    [#LC5364]

  • Attempts to create virtual machines through the XenDesktop setup wizard might fail in a non-English Microsoft System Center Virtual Machine Manager (SCVMM) environment.

    [#LC5451]

  • Attempts to restart provisioned targets might fail intermittently because of a database timeout error. The following error message might appear:

    "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

    [#LC5511]

Target Device Issues

  • The target device software does not recognize the AppDisk drive and uses the AppDisk drive for write cache, which can cause conflicts.

    [#LC5409]