[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 550
  • Last Modified:

Citrix XenApp 7.6 logon performance issues

Hello,

We have a small XenApp 7.6 environment with 2 DDCs running Windows 2012 R2 and 4 XenApp machines running 2008 R2

We are having performance issues with users logging on after deploying 2 new machines and this has now started to occur on the first 2 machines which were working fine before

Events being logged are:

Event ID 6004 The winlogon notification subscriber <TermSrv> failed a critical notification event.
Event ID 6001 The winlogon notification subscriber <Sens> failed a notification event.
Event ID 6005 The winlogon notification subscriber <Profiles> is taking long time to handle the notification event (Logoff).
Event ID 6006 The winlogon notification subscriber <Profiles> took 95 second(s) to handle the notification event (Logoff).

We've tried updating windows, is it recommended to update XenApp?

Any help would be much appreciated

Many thanks
0
neilfreeman
Asked:
neilfreeman
  • 2
  • 2
1 Solution
 
James RankinCommented:
Updating XenApp can't hurt, in that it keeps you abreast of fixes and updates.

However that logon performance could be caused by a number of things.

Do you have antivirus exclusions properly configured for XenApp? Do you have logon scripts or large numbers of policies being deployed (either Citrix or AD policies)?

Running tools like uberAgent may help with getting data from various parts of the logon process and showing you where there are any potential problems.
0
 
neilfreemanAuthor Commented:
Good morning

Many thanks for your help and apologies for my delayed reply

We checked through your suggestions but the problem turned out to be with the Citrix roaming profiles

Our XenApp servers normally reside in their own OU to keep the profiles very small (less than 2MB)

We added the new machines using MCS but forgot to specify the correct OU. By the time we moved them into the correct OU the Citrix profiles were all bloated and this is why the issue carried over to the previous machines which were working normally before

To solve we had to place all the old machines into maintenance mode, delete the affected Citrix roaming profiles from the profile server, generate 2 new machines and place into the correct OU, then allow people to log back on

Last question regarding updating Citrix, do we apply the updates to the DDCs first and then the XenApp servers?

Thanks again and kind regards
0
 
James RankinCommented:
It's not a hard and fast rule regarding updates, but I'd generally start with the DDCs or brokers first as there is less chance of user impact that way if there is an issue. Obviously if you have a test environment that mirrors live that would be ideal for testing, normal change processes should apply at all times.
0
 
neilfreemanAuthor Commented:
Many thanks for all your help
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now