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.
nathanspowellAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
nathanspowellConnect With a Mentor Author Commented:
There was a rogue root entry in the DNS zone.
0
 
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
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
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
 
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:
No one else suggested this.
0
All Courses

From novice to tech pro — start learning today.