Improve company productivity with a Business Account.Sign Up

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

Citrix Xenapp 4 Network Drive issue

Have a strange issue occurring with our Citrix environment.  When a user launches an application a sysvol script executes that maps several drives for the user.  The script first deletes any instances of the drive letters and then remaps them.  We have 5 citrix servers in the farm.  Over the last few weeks each one of the servers has experienced the following issue.  

The Z: drive will fail to map, all other drives will map correctly.  A server reboot or making the user a domain admin will resolve the issue.  There are no conflicting physical drives on the host server.  Help is appreciated, this one has us stumped.
0
nathanspowell
Asked:
nathanspowell
  • 4
  • 3
1 Solution
 
Matt VCommented:
Any event log errors when the drive fails to map?
0
 
nathanspowellAuthor Commented:
Nothing appears in the logs other than printer creation and logon events.  No errors or warnings related to the login or script.  As I mentioned the script actually executes and maps all drives except Z:.
0
 
Matt VCommented:
Havfe to ask, did you check the logs on the server where the Z: drive resides?  Look in the security log in particular.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
nathanspowellAuthor Commented:
Nothing in the security log of the host server other than a logon event for the user.  Updating the issue though, it actually appears that the script isn't running at all now.  The other drives were remaining from a previous logon session.  If the user is made a domain admin the script will execute.
0
 
Matt VCommented:
Double check the permissions on the script, make sure the user can read it.  They should be able to launch it with \\domain.local\netlogon\scriptname.cmd after they are logged in.
I just saw this last week where a server admin rebooted the DC and the problem went away.
0
 
nathanspowellAuthor Commented:
There was a rogue root entry in the DNS zone.
0
 
nathanspowellAuthor Commented:
No one else suggested this.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

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