Error unable to right to win.ini in while using a GPO

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Application that whenever you open it tells the users that it "Error
Adding Entry to Win.ini:0". I have tried Giving the user's group full access
to the win.ini and it did not help. Also I saw another question/solution on
EE to setup on the Computer GPO under Windows Settings->Security->File
System. I tried adding the win.ini file here but I'm still getting the
error. I then added the Winnt directory and still no luck. The path I put
for the win.ini file under the gpo was \\testserver\c$\winnt\win.ini. Is
this correct or does anyone have any other suggestions?
 
Sounds like all of your users are writing to the same shared
win.ini file. The error message you see has probably nothing to do
with permissions, but that the file is opened for writing by the
first user, and therefore all subsequent users can only read the
file.

Can you test if this is the case (first user has no problems?)

Did you install the application while the Terminal Server was in
install mode? All users should have their own \windows folder in
their home folder, and get a personal copy of any ini files which
the program needs. But if your application is using a hardcoded
path to win.ini, it won't work.

Recommended reading:

186498 - Terminal Server Application Integration Information
http://support.microsoft.com/?kbid=186498

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*
 
I reinstalled using the install mode and then turned it back into Execute
mode. I see that it is using the user's win.ini but I still get the error.
The user does have permissions to that file. The program works fine if I
login with Admin and no GPO, but if I use the test user account that is
locked down I get the error.
 
In that case, download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator (when no
user is connected), 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.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*
 
Any other Suggestions?



Vera Noest said:
In that case, download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator (when no
user is connected), 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.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*
Click to expand...
 
Why? Have you resolved all "access denied" and "path not found"
warnings from FileMon and RegMon?

_________________________________________________________
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 ___
 
Back
Top