1

I have this weird issue with Citrix being slow and maybe users just being a little dramatic, but I am curious as to why that happens. Let me give you a little bit of a background. Citrix is running off of Windows 2003 server, TSprofiles and file server were located on the same server, until recently. We have moved our file server over to a new server with tons of space. We have Citrix on one server, TSprofiles on another and file server on third. We are using logon scripts to map home drives, shared drive and etc. Now, up until we made the file server move, the logon process took several seconds and most users couldn't even notice logon script being executed as they logon. Now, it takes upwards of several minutes and users can see logon script being executed at a slow pace, one line at a time. The only new variable in this whole scenario is the new file server. All the servers are physically located in the same location and on the same subnet.

So, I guess my question is, if anyone can explain why a sudden sluggishness? And any tools I can use to troubleshoot the issue?

Thanks!

5
  • 3
    Just a thought - can you disable the login script and see if the login process is fast again? If so, then maybe remove everything except the first line of the login script and try, adding each line back until you find the slowness.
    – KJ-SRS
    Oct 4, 2012 at 18:16
  • @KJ-SRS Yeah, that would not be possible, as I have 200+ users with 190+ of them using Citirix and using home/shared directories. The amount of production time lost, while I am trying to figure it out, line by line or totally disabling the script, would be unacceptable collateral damage and will have me probably out of the door with a pink slip. It's a good idea, but it would have to be my absolute last resort, after I exhaust all other options.
    – George
    Oct 4, 2012 at 19:40
  • 1
    KJ's solution will work. Just make a copy of the logon script and edit your AD account to point to the new script. At first make it blank, then add stuff as you go. Honestly logon scripts are almost never needed anymore with Group Policy Preferences which works better and logs issues to Event Log. Oct 5, 2012 at 4:05
  • If you run the script manually, when already logged in (preferrably after removing it for your test user logon), is it slow then too?
    – ErikE
    Jul 5, 2015 at 13:54
  • have a look at how big the TSprofiles (presumably roaming profiles) are. the network drives don't get pulled down to the client but their profile obviously does. in your old setup with VDI and user profiles on the same box there would be no network and disk i/0 load - now there is.
    – Sum1sAdmin
    Apr 19, 2016 at 10:16

1 Answer 1

1

You need to change the config for a test user and rule out various potential causes. There is no "magic tool" that will tell you what is causing the slowness.

  1. What does the performance look like on these three servers?
  2. What does the performance look like during a user logon?
  3. Ensure all three of these servers are on 1GB NIC's and preferably on the same switch if you want to prevent any "upstream switch" bottlenecks.
  4. Test file transfers between the three boxes to ensure you're getting near 1GB throughput. I've seen everything from bad NIC's to old drivers to misconfigured switches cause a server to sit at 100MB rather then the 1GB.
  5. In general, and especially on old win2003, I find it better to leave the profiles alone and use folder redirection via GPO's. It requires much less work on login, but sometimes people do need things like users registry to be shared between servers. Just know that folder redirection should be what's used UNLESS you have a requirement for the full profile sync.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .