• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 8422 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Quest Logon Script User and Citrix XenAPP

MBreitenbach
over 6 years ago

Hello together,


we have setup an application Server for XENAPP with Office etc.
The users see these applications, can open them, etc.


But -> they cannot save or open documents etc. cause the company drives are not shown.

And this is why i am asking here:   the Logon script is a slogic script (Quest Desktop Authority)

Drives are not mapped like "net use" in the script, it is configured via Quest Desktop Authority.

So i created an testuser with "normal" net use logon script - this is working.

Does anyone know how can i add the network drives via logonscript or any alternate possibilities ?

I use Client Configuration -> Profiles -> Drive Mappings

One more point:

Network drives are not identical for every user, depending on department

  • 0 over 6 years ago

    Drives are mapped the same way when either using Desktop Authority (DA) or when using a script that is running the NET USE command. So if one works the other should as well. There are many factors that could cause DA not to map a network drive. With issues like this it’s best to open a support case and have Tech Support review the diagnostic log files. You can open a support ticket HERE.

  • 0 over 6 years ago
    Heya, if you haven't opened a ticket with tech support yet. You can quickly check a couple of things. In the "%TEMP%\Desktop Authority" folder is a nice log of exactly what was done during login for each user. Named "SLTrace.htm" it is rebuilt after each login. There is a section for drive mappings and you should be able to tell from it if it is trying to map the drives and failing or not even trying (which usually is a validation logic issue). In our case the drive section looks like:
    08:06:16 Processing Drive Mapping elements [7/27]
    08:06:16 Troubleshooting
    08:06:16 Pre-existing drives: C2,D2,E2,F3,H5
    08:06:16 Existing mapped network drives for this user will be preserved
    08:06:16 Mapping drive: J: to \\staff\Common\Common.DO [AllUsers 3/27 - 4ea0625f-66d3-423f-9f96-d29c4eb3cc71]
    08:06:16 Mapping drive: I: to \\staff\Common\Common.LHS [AllUsers 10/27 - 4ea0625f-66d3-423f-9f96-d29c4eb3cc71]
    08:06:16 Mapping drive: J: to \\student\LHSstu.Collaboration [AllUsers 11/27 - 4ea0625f-66d3-423f-9f96-d29c4eb3cc71]
    08:06:16 Mapping drive: G: to \\WINAPPS\WINAPPS\WinApps.LHS [AllUsers 18/27 - 4ea0625f-66d3-423f-9f96-d29c4eb3cc71]

    hope that helps!
  • 0 over 6 years ago
    one more thing! you said "Network drives are not identical for every user, depending on department"

    that is exactly why you want to go DA for drive mapping rather than scripts. We currently have 27 different drive mappings depending on dept, function and location. All are based on AD group mappings so all I have to do is add a user to the "These people get mapped the Secretaries drive" group and the next time they log in, they have the new drive letter.