L
Leo Vasiliou
Hello:
I just want to make you aware of an unfortunate side-effect with the rsop
snap-in. It probably won't be that big of a deal for most of the admins,
but for those of us it affects, it will be.
When you run rsop.msc, the parameters of any startup/shutdown scripts
supplied by the gpo are passed to the rsop. In my case, in one of my
scripts, I was passing an administrator password in the parameters field (as
recommended by the Windows & .NET periodical, 'Security Administrator' insta
doc 27330).
For example, my startup script contained the following:
net user administrator %1 (where %1 is the local admin password I was
passing to the parameter input on the script)
Yes, the security is set appropriately and the account I am logged on with
has only user permissions in the domain.
-leo
I just want to make you aware of an unfortunate side-effect with the rsop
snap-in. It probably won't be that big of a deal for most of the admins,
but for those of us it affects, it will be.
When you run rsop.msc, the parameters of any startup/shutdown scripts
supplied by the gpo are passed to the rsop. In my case, in one of my
scripts, I was passing an administrator password in the parameters field (as
recommended by the Windows & .NET periodical, 'Security Administrator' insta
doc 27330).
For example, my startup script contained the following:
net user administrator %1 (where %1 is the local admin password I was
passing to the parameter input on the script)
Yes, the security is set appropriately and the account I am logged on with
has only user permissions in the domain.
-leo