Jump to content

vikash

Legacy Group
  • Posts

    81
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by vikash

  1. Hi Bill,

     

    To resolve this issue, configure the following registry values on all the Controllers in the site and reboot.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
    Name: MaxTokenSize
    Type: REG_DWORD
    Data: 48000

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
    Name: MaxFieldLength
    Type: REG_DWORD
    Data: 48000

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
    Name: MaxRequestBytes
    Type: REG_DWORD
    Data: 12288000

     

    Please refer to https://support.citrix.com/article/CTX208712 for more details. Please let me know if this helps.

     

    Regards,

    Vikas Hiremath

  2. Hi Tom,

     

    Could you please upgrade to 4.11 or the latest receiver (4.12), upgrade the receivers on the thin client and XD.

    This should ideally resolve the issue, there are been some known mouse scaling issues that have been fixed in 4.11 version.

     

    Please let me know if this helps.

     

    Regards,

    Vikas Hiremath

  3. Hi @Scott Knights,

     

    Good Day :)

     

    I do recollect 7.12 environments facing similar CPU hike issues with WMI provide. Not sure if this would work but could you try and reset the WMI counter (referring to https://support.citrix.com/article/CTX223754), you could achieve that by following the below steps:

     

    1. Click Start, click Run, type Wbemtest, and then click OK.
    2. In Windows Management Instrumentation Tester, click Connect.
    3. In the Namespace box, type root\cimv2, and the click Connect.

    4. 4Click Enum Classes.

    5. In the Enter superclass name box, type Win32_Perf, click Recursive and then click OK.

    6. In Query Results, you will not see results for the counters that are not transferred to WMI.

      For example, the counter object for Remote Process Explorer is Win32_PerfFormattedData_PerfProc_Process. If this counter does not exist, you will not see the following line in Query Results - Win32_PerfFormattedData_PerfProc_Process.

    To Manually reset the WMI counters:

    1. Click Start , click Run, type cmd, and then click OK.
    2. Stop the Windows Management Instrumentation service or at the command prompt, type net stop winmgmt, and then press ENTER.
    3. At the command prompt, type winmgmt /resyncperf, and then press ENTER.
    4. At the command prompt, type wmiadap.exe /f, and then press ENTER.
    5. Start the Windows Management Instrumentation service or at the command prompt, type net start winmgmt, and then press ENTER.
    6. Type exit, and then press ENTER to close the command prompt.
    7. After resetting the WMI counters, retest WMI.

    You could also try restarting the Windows  Management Instrumentation Service and check if that works.

    * Strong recommendation is that you run the antivirus scan for the all systems, sometimes virus attacks may also indicate a WMIPRVSE high CPU utilization.

     

    Let me know if this help.

     

    Regards,

    Vikas Hiremath

    • Like 2
×
×
  • Create New...