Jump to content
Welcome to our new Citrix community!
  • 0

Provisioned Physical Desktops woth slow performance and excessive retries


Anthony Bennett

Question

Weird issue here. We are running Provisioning Services 7.15 CU4. Our reference computer that the vdisk was created from works fine. Little to no retires and performance is what we expect. Taking the same vdisk and booting another lab computer same make and model we get slow performance and excessive amounts of retries. Has anyone ever seen this? Its as if Windows 10 sees a computer that is not the reference computer and creates havoc. Windows 10 1809 is what is currently running and we have verified that the hardware specs, BIOS, etc. are identical.

Link to comment

3 answers to this question

Recommended Posts

  • 1

Is everything else about the problematic machine the same as well (OU location in AD, physical connectivity (speed/duplex settings))?  Just trying to gather what might be different.

 

Take a look at the following Citrix Support article(s), if you haven't already:

 

https://support.citrix.com/article/CTX232340 - Windows 10 PVS target devices experience poor performance

 

Quote

Solution

The issue is resolved by configuring the following Microsoft policy setting on the target device:

Computer Configuration/Administrative Templates/Network/Network Isolation/Subnet definitions are authoritative

This creates a setting in the target device registry:
 
Registry Hive: HKEY_LOCAL_MACHINE
Registry Location: Software\Policies\Microsoft\Windows\NetworkIsolation
Value Name: DSubnetsAuthoritive
Value Type:  REG_DWORD
Enabled Value: 1

 

(this references slow login performance, but also references the same registry key being the solution)

https://support.citrix.com/article/CTX232313 - Citrix Provisioning Services: Slow Login Performance with Windows 10 VDA Machines

 

Quote

Solution

First of all verify if the issue is fixed by stopping and disabling the Network Location Awareness Service on the Master Image before vDisk creation. 

If we get the issue fixed by following the above step, enable and start the Service before vDisk creation and enable the following Local Policy on the Master Image:

 

Policy Name: Subnet definitions are authoritative

Policy Location: Computer Configuration/Administrative Templates/Network/Network Isolation


Enabling this policy will create the following registry key:

Registry Hive: HKEY_LOCAL_MACHINE

Registry Path: HKLM\Software\Policies\Microsoft\Windows\NetworkIsolation

Value Name: DSubnetsAuthoritive

Value Type: REG_DWORD

Enabled Value: 1

Disabled Value: 0

  • Like 1
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...