Archived from groups: microsoft.public.windowsnt.terminalserver.setup (
More info?)
Thank you Vera for your response.
You are of course quite right to say that users should not be given
Adminoistrator rights.
I demoted the user and rechecked the file attributes and found that
whilst the read only attribute byte was not set, the security settings
did not give full control to the user, it now works perferectly.
Incidently Microsoft appear to have fixed the annoying message that
you used to get when trying to install software, it now automatically
goes into Add & Remove programs mode when you run a programs
setup.exe.
Thanks
Patrick
On Sat, 06 Nov 2004 13:50:44 -0800, "Vera Noest [MVP]"
<vera.noest@remove-this.hem.utfors.se> wrote:
>No! Never solve an application problem by giving your users
>Administrator rights. That's the fastest road to disaster.
>Remember that all of your users will be working interactively on
>your server. If you give them Administrator rights, they will be
>able to (and will!) install any software they want, reboot the
>server at will or by mistake, and make the system completely
>unreliable and unstable.
>
>A couple of notes:
>* You have to install all applications on a Terminal Server when
>the server is in "install" mode", to ensure multi-user capability.
>Failure to do so will nearly always lead to a situation where only
>the Administrator who performed the installation can run the
>application.
>* a lot of 3th party or older Microsoft applications are not 100%
>TS-compatible, which means they need tinkering after installation,
>often with the registry and file system permissions.
>* in all cases where an application runs as Administrator, but not
>under a normal user account, download FileMon and RegMon from
>http://www.sysinternals.com/. Run them as administrator 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" errors
>that occur, so that you can give your users the necessary
>permissions on a file-to file or Registry subkey basis.
>* Access databases are a pain when shared. Which version of
>Access? How did you install it? Check if the information here
>helps:
>
>301966 - ACC97: Error Message When You Try to Start Access 97 in
>Terminal Server
>http://support.microsoft.com/?kbid=301966
>
>http://www.granite.ab.ca/access/terminalserver.htm
>
> --
>Vera Noest
>MCSE, CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
>Patrick Fisher <info@psoftuk.com> wrote on 06 nov 2004 in
>microsoft.public.windowsnt.terminalserver.setup:
>
>> Hi
>> I solved it for the time being by giving the user administrative
>> rights, is the the correct way to go?
>> Patrick
>>
>> On Sat, 06 Nov 2004 16:20:48 GMT, Patrick Fisher
>> <info@psoftuk.com> wrote:
>>
>>>Hi
>>>I have installed Windows 2003 Server and Terminal Server, as I
>>>am only testing it I have not issued any licences.
>>>
>>>When I logon as Administrator to a remote session from a
>>>workstation I can run an Access Database that is on the server,
>>>no problem.
>>>
>>>When I logon as a user I get a message telling me that the
>>>Access Database is Read Only.
>>>
>>>Why is this happening and how can I make it work.
>>>
>>>Thanks
>>>Patrick
Facebook
Twitter
Instagram