Terminal Services - MSAccess Vs. Printers.

[moolie]

I am running terminal services 2000 with office 2000. Each user needs to access an application that runs in Access 2000. Here's the rub:

Users sometimes print to the work location - IE. user accessing the server from Company X prints a document and it comes out on Company Y's printer.

Each user is a member of Domain admins. Here's why:

If the users are domain users only they cannot run the Access application. They get an error message saying access is in use by 'Admin' and they cannot proceed. If they are all members of Domain Admins the application works properly and everyone is happy.

BUT ... all users can see and print to other users printers. not good. I need to lock down users to only see and print to their own printers without effecting the Access application - HELP.

 

[VinceF]

I would suggest using something like the filemon and regmon utilities.

Filemon can be run from a seperate session. Log in from someplace as a non-admin user. Start filemon from your admin session and then run access and the application you need to run, let it fail. Go back to filemon and review the output. There will probably be a place where access is denied to a file or folder. Assign the permissions to that location and re-run the application as a non-admin user.

Using this process you will be able to find where the issue is and resolve it, and you will not have to have all the users with administrative access, that just isn't the right thing to do.

 

[moolie]

No good.

User permissions for the session have been dropped to Domain Users. This takes care of the printing issue but does not let the application that runs in Access to load. The message comes up as "Could not use 'Admin'; file already in use."

I need to overcome this as this is a multi-user application.

 

[moolie]

I basically need the user to have full access to access.exe as Office2000 while only having domain users access to the session.

 

[moolie]

Found the answer on TEK-TIPS!!!!!

user Larsson posted way back in 2002 in the Access forum the following solution:

"I have solved it.
I had to give the users modify rights on the following catalogs:
c:\program files\common files\system
and
c:\program files\common files\Microsoft shared\webb server extension

Larsson"

I added the DOMAIN USERS to the permission granting full permission to the above folders and you guessed it--- Everything works!!!!!!!