Re: Remote Desktop fouls MRP access to its database

Was the MRP application installed on the server *after*
installation of Terminal Services?
And was the Terminal Server in "install mode" during installation
of the MRP application?

If yes to both questions, you could download FileMon and RegMon
from http://www.sysinternals.com/. Run them as administrator (when
no user is connected) on the console of the server, start a TS
session as a normal user and try to run the application.

FileMon and RegMon will show you all "access denied" and "path not
found" errors that occur, so that you can give your users the
necessary permissions on a file-to file or Registry subkey basis.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"SAR" <sarogers@xxxxxxxxxxxxxxxx> wrote on 30 mar 2006 in
microsoft.public.windows.terminal_services:

I am using DBA Manufacturing, an MRP system, on Win2003 Server.
All works well when I run the MRP system from the local console,
but when I run it from within a Remote Desktop session (same
login), I get a different result - what appears to be a
permissions error that prevents the MRP application from
connecting to its Firebird database server. So, logging in as
exactly the same Administrator level user from RD produces a
different application behavior than logging in on the console.

I have gleened from newsgroups that there are some rights
differences between the same user logging in locally vs through
remote desktop login, but I haven't been able to find any
detailed info yet on how to correct this. As a shot in the
dark, I added Remote Desktop Users to both the MRP directory and
the database file, with full control. Didn't make any
difference. I am not a security expert...

Any ideas what might be different between these two (I thought)
identical sessions? The MRP vendor says many of its customers
are using RD to access this program successfully.

Thanks...

Stephen, LRS Solutions
.

Relevant Pages

  • RE: Terminal Server and Outlook
    ... Normally you install the resource kit tools on a workstation, where you can create transforms or profile settings. ... Run setup /a from the office setup disk to copy the setup files from the CD to an Administrative Installation Point ... Install on the Terminal Server with the MST ...
    (microsoft.public.windows.terminal_services)
  • Re: Users can Install on Terminal Servers
    ... Microsoft MVP - Terminal Server ... I've also noticed that switching compatibility mode after the ... initial installation doesn't produce exactly the same results as ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Networked Office
    ... the idea of a Terminal Server is generally a really good idea. ... / question as to why do you would want to turn them into thin clients. ... you can indeed make an Administrative Installation of Office 2003 ...
    (microsoft.public.windows.server.general)
  • Re: Networked Office
    ... the idea of a Terminal Server is generally a really good idea. ... / question as to why do you would want to turn them into thin clients. ... you can indeed make an Administrative Installation of Office 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Networked Office
    ... the idea of a Terminal Server is generally a really good idea. ... / question as to why do you would want to turn them into thin clients. ... you can indeed make an Administrative Installation of Office 2003 ...
    (microsoft.public.office.setup)