DOS Application requires Domain Admin Rights (HELP)

[efector]

I have created a Win2K AD Domain(the network was previously a peer to peer windows w/Linux Samba server). I have an application, which is DOS, and sits on our file server. Each user, has a shortcut to the batch file, which resides in the shared directory on the file server.

I have set the share & NTFS permissions to FULL for Domain users & have set domain users, to be local admins on their machines.

Even with the above steps, the application will ONLY run, if a user has Domain Admin rights. I even went through and reset the permissions at the file level, but nothing seems to work.



Anyone have any ideas?

 

[58sniper]

DOS isn't AD aware, so you're missing some permissions somewhere. I'd grab something like diskmon and see what's going on when you access it as a domain admin, and then set them accordingly for the users.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Titleist]

Regmon and Filemon will also help you narrow down the appropriate permissions.

 

[itsp1965]

As Pat indicated, DOS programs are neither AD aware nor do they require permissions beyond execute to work.. What exactly is this program doing..

 

[victorv]

hi,

segment the promlem !

In this moment, you are using:

+ a domain user
+ a computer in domain (I belive the pc is in the AD)
+ a share (which require authentication)
+....

Begin (just for test) with:

+ Use the same client (PC in AD)
- use a PC local user (admin or not)
- copy the application on the on the PC on a folder
- use the command SUBST to create a local X: on this folder

If the program continues to fail,(invoke StClause), check
OS requirements. If goes, use a admin use with local disk, ... and so on.

ciao
vittorio

 

[w33mhz]

What do you mean by "run" does the batch start to execute, or do you get an error right off? You should probably post your code of the batch file, maybe the batch file is trying to do something that the use doesn't have access to do. You have to remember that when you execute the batch file it is running under the user's credentials.