Lanwench, Vamsi,
comments in-line......
--
Cary W. Shultz
Roanoke, VA 24014
Microsoft Active Directory MVP
http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
"Lanwench [MVP - Exchange]"
OK - as said, a user cannot grant himself more permissions than he already
has.
Correct! Think about the consequences were this not the case. Network
Security would be a complete farce. Users would be able to make themselves
members of the local Administrators group and God knows whatelse.
This logon script would actually need to be a start up script.
And, there is a much better way to do this. Look into the Restricted Groups
GPO. Here are two MSKB Articles that will get you going:
http://support.microsoft.com/?id=320065
http://support.microsoft.com/?id=810076
You might want to look into the Restricted Software GPO to help out with
this. Granted, in a WIN2000 environment there is an easy way around this
for the end-user ( simply rename the .exe or whatever ) but with WIN2003
this is not possible as a hash is used...renaming the .exe or whatever does
not make a hill of beans of difference.
You also might want to take a workstation and try to install the software on
it. Assuming that this fails then you might want to take a look at regmon
and filemon from
http://www.sysinternals.com to figure out where the failure
is occuring.
You need to run it under computer, not user, I think.
I will spare you the stories that I could tell you about users deleting all
of their fonts because they needed special fonts and did not want to have to
remember which ones were special or about the users who deleted a ton of
things to make room for their music files or......
I never never never encourage this and do just about everything to prevent
this. Domain user account objects should be in the USERS or at most POWER
USERS local groups....no more.