New
#21
I'm 99% sure that is because your user is part of the local admin group. Try it as a standard user without saving credentials.
I think OP needs to either grant admin access to these 100 users or go and save admin credentials on all the machines. Neither is a good solution. Alternatively look into what privileges the program really needs and if it really needs to be run as admin. That would depend who wrote it.
I have just test for fun a very simple script (where is not requested admin right ):
In this case it worked.msg * "Welcome in my nightmare"
If understood well GPO is unable to perform a script if it require an admin right.... and not solution to go around!
Am I right?
This lab before was in a workgroup environment. We decided to joint them in a local independent domain to make easier the management. Before there was 1 local user not admin [ student] and 1 admin user.
Now in the domain we have created a general user [ student] only part of another group = "network operational group" but NOT admin group.
Do you think there is the possibility of some user profile corruption?
The user [ student] is not a local adminI'm 99% sure that is because your user is part of the local admin group. Try it as a standard user without saving credentials.
If we elevate a student account be part of the administrative group they will mess around everything ....
I contacted the vendor of the software. They tested and confirmed the issue.
I linked the GPO to a domain admin user (at startup) and the error appear as well....so the issue is not connected totally to the admin right.
Just the last think .... I used a prompt command with elevated right adding it in the RunAs tool program and I use the import script on it below:
.....it worked fine.RunAsTool.exe “/U=Admin” “/P=PassWord” “/I=Import.rnt”
Theoretically the problem could be solved if the script could be execute in each machine using a CMD with high elevate right....
Is it possible?