Product Documentation

Fixed issues

Mar 08, 2017

Compared to: Provisioning Services 7.12

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

Console Issues

  • Unable to restart/shutdown targets from the PVS console.

    [#LC6814]
  • When using a virtual machine to provision virtual machines from a template using a SCVMM cluster, the wizard fails to create the virtual machines after clicking Finish.

    [#LC5871]

  • When using clustered volume storage, the Streamed VM Setup wizard does not honor the volume selection and can create the target devices in random volumes.

    [#LC5890]

  • Attempts to close the Provisioning Services Console after running the XenDesktop Setup wizard or the Streamed VM Setup wizard can result in an exception.

    [#LC6048]

  • The XenDesktop Setup Wizard might not perform a full permission check, causing errors in permissions.

    [#LC6190]

  • After configuring the Provisioning Services Console, the label names might be missing in the target device properties.

    [#LC6864]

Server Issues

  • Server communication timeout. System experiences slow connections to the PVS farm.

    [#LC6249]
  • When using a virtual machine to provision virtual machines from a template using a SCVMM cluster, the wizard fails to create the virtual machines after clicking Finish.

    [#LC5871]

  • When using clustered volume storage, the Streamed VM Setup wizard does not honor the volume selection and can create the target devices in random volumes.

    [#LC5890]

  • When the target device's boot.iso code receives an ARP request that has been sent with a broadcast destination, the target device's boot.iso code sends an invalid ARP reply.

    [#LC6099]

  • The XenDesktop Setup Wizard might not perform a full permission check, causing errors in permissions.

    [#LC6190]

  • Attempts to configure Provisioning Server using the Provisioning Services Configuration wizard by selecting the "Join existing farm" option might fail while using the default instance of SQL server.

    [#LC6579]

Target Device Issues

  • When you configure a vDisk to use "Write Cache on RAM" and set the size RAM cache size to 4,096 MB or 4,097 MB, booting from a Hyper-V GEN-2 virtual machine can cause target devices to experience a fatal exception, displaying a blue screen.

    [#LC6707]
  • Provisioning Services target devices might experience a fatal exception, displaying a blue screen.

    [#LC6604]