TS network drive

From: Peter (anonymous_at_discussions.microsoft.com)
Date: 02/10/04 

Date: Tue, 10 Feb 2004 09:11:07 -0800

I would like user logging into out 2003 Terminal Server to be able to run FW1.1 winform apps from a network drive.
I have set the Local Intranet to Full trust on the TS.
The application runs correctly when run from a workstation on the network.
When running from a TS session :
Application has generated an exception that could not be handled
process id: xxxx thread id: xxx

I assume this is a permissions issue?
Could anyone help with how I can find out what permissions have been requested that are missing?

Thanks

Relevant Pages

  • Re: Permission Issue? Icons Denied in Terminal Services
    ... That error message comes definitively from IEES. ... Have you added the fileserver to the local intranet sites? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... may not have the appropriate permissions to access the item. ...
    (microsoft.public.windows.terminal_services)
  • Re: Computer componet of GP not being applied
    ... would expect that anything in the Computer Configuration portion of the GPO ... By "non-standard permissions", I mean what are the permissions on the GPO? ... If you look at the properties of the OU in which the Terminal Server resides ... > It all seems to be linked to the local user groups on the terminal server. ...
    (microsoft.public.windows.group_policy)
  • Re: Cannot Execute Batch File
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I have given full permissions for the shortcut. ... One of our application starts with a Batch file, ...
    (microsoft.public.windows.terminal_services)
  • Re: Cannot Execute Batch File
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I have given full permissions for the shortcut. ... One of our application starts with a Batch file, ...
    (microsoft.public.windows.terminal_services)
  • Re: Using Photoshop on Terminal server session
    ... Is Photoshop supported at all on a Terminal Server? ... I tried to give full permissions on all keys I could link to ... opens the registry key again, ...
    (microsoft.public.windows.terminal_services)