Re: SHaring a MS access frontend amongst all TS users
- From: "TP" <tperson.knowspamn@xxxxxxxxxxxxxxx>
- Date: Wed, 1 Aug 2007 16:48:02 -0400
That is a good point I didn't consider. It could be failing and thus not running the copy. In my experience I have not had that fail so unless there is something strange going on my first guess would be it is working. If the script was unable to get the common paths there would likely be other problems manifesting with applications because that is something lots of programs do.
Jason, can you test this by moving the code to the end of the file, after :Done?
I am concerned that usrlogon is not running at all like if the server is in remote administration mode. That is why I was asking him about the licensing mode.
Jason, can you test that usrlogon is actually running by placing a pause at the top of the usrlogon.cmd file? If it is running this will cause it to stop during logon so that you can click on the command window and press a key to continue.
Thanks.
-TP
Vera Noest [MVP] wrote:
Maybe usrlogon.cmd never gets to the :Cont1 label, because.
SetPaths.Cmd fails?
Call "%SystemRoot%\Application Compatibility Scripts\SetPaths.Cmd"
If "%_SETPATHS%" == "FAIL" Goto Done
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
- References:
- Re: SHaring a MS access frontend amongst all TS users
- From: TP
- Re: SHaring a MS access frontend amongst all TS users
- From: TP
- Re: SHaring a MS access frontend amongst all TS users
- From: Vera Noest [MVP]
- Re: SHaring a MS access frontend amongst all TS users
- Prev by Date: Re: SHaring a MS access frontend amongst all TS users
- Next by Date: Re: Group Policies for different users in TS
- Previous by thread: Re: SHaring a MS access frontend amongst all TS users
- Next by thread: Re: SHaring a MS access frontend amongst all TS users
- Index(es):
Relevant Pages
|