centralcity
asked on
How to run DOS app in Remote Desktop using Terminal Services
I'm trying to run a DOS app in a Remote Desktop using Terminal Services on Windows 2003 Server. The problem is that the app writes an .ini file to the root of the C: drive. It appears that a user is not allowed to change that file unless the user is a member of the Administrators group. Unless I include the user in the Administrators group, I cannot successfully run the app.
I certainly don't want to give all remote users Administrators access. How can I get around this problem?
I certainly don't want to give all remote users Administrators access. How can I get around this problem?
You don't have to give the permissions to all remote users. Why wouldn't you just give the permissions to the account you're using to log in with?
Sorry, I see what you mean. What is the program in question? It it a supported app?
Either add the user to the Poweer Users Group, or loosen the permissions on the target directory. A normal user does not have write privileges on a W2K3 machine
ASKER
The program in question is called Swiftlink. It is used primarily by the home appliance sales and service stores.
I tried this. Made the accounts members of the Power User Group. Started with giving "write" permission to the C drive (did this by going to Windows Explorer, right-click on drive and go to security tab. Should I do it some other way?)
When that didn't work, I gave the accounts full permission and it still didn't work.
I tried this. Made the accounts members of the Power User Group. Started with giving "write" permission to the C drive (did this by going to Windows Explorer, right-click on drive and go to security tab. Should I do it some other way?)
When that didn't work, I gave the accounts full permission and it still didn't work.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will talk to the vendor tomorrow about it. Even giving full access did not work. Only when I made the users members of the Administrator group did it work.
ASKER
Dumb me! I gave permission on the c: drive, but did not give permission on the folder on the d: drive which has the app!
Now that I've done that, it works fine. Thanks for pointing me in the right direction.
Now that I've done that, it works fine. Thanks for pointing me in the right direction.