Same problem with auto start application with terminal server(urgent)

  • Thread starter Thread starter Matthew Harris [MVP]
  • Start date Start date
M

Matthew Harris [MVP]

What is the shortcut located that starts up the
application at logon? How are you 'auto-starting' the
application?

-M
 
Under the user properties in AD under the environment tab
the application is called user.bat and it is located under
teh root of drive c ,and actually it is was working
normally even now it is working onloy if teh user is from
the same domain as the Termianl server one, but if the
user is from different domain simply the user get the
desktop.

the setting is correct this is not teh issue because the
same setting was working before.

so any ideas what may be teh problem
 
Have you checked the permissions on the file?
Is there anything in the EventLog?
Have you enable auditing of all security events in a GPO and on
the file itself?
 
The file access permission is for everyone, when the
client connect and do not get the desktop i checked if
they can start teh file or no simply they can start it
manualy.

and i discovered that these client when they log teh
system do not read teh file for them at all ic checked
with file monitor

using the environment tab to configure this properties di
it have a relation to group policy, if so where is the
configuration for it is saved for each client?

Regards,
 
Try setting this option on the Environment tab in the rdp-tcp
connection properties in TS Connection Configuration.
 
By this way it is working but for everyone , but not
everyone need this application other users just need the
desktop

any suggestion what may be the problem?

Regards,
 
Doe it work when you store this user.bat file on a network share
and write in the Environment tab: \\server\share\user.bat?
 
No it is the same
i have 2 doain controler, and i discovered that if the
user get teh policy from the group policy from dc1 after
checking with gpresult the application do not start but if
it get the policy from dc2 (i do this by shutting down dc1)
it work,

so what may be the problem?

Regards,
 
Have you checked the security on the policy?
Does it make a difference if the user is a normal domain user or an
administrator?
 
Back
Top