Hi, This MS Forum Quoting " How to script Group policy change" may help you out: ---quote---

Hi

Some of those settings you should be able to set with the Win2k (or Win2k3) resource kit tool ntrights.exe:

ntrights.exe +r SeServiceLogonRight -u SomeUserNameHere

How to Set Logon User Rights with the Ntrights.exe Utility

How to: Determine NTRIGHTS Names and Meanings

Ntrights.exe is in the free Win2k3 resource kit (it very well might work on Win2k as well):

Windows Server 2003 Resource Kit Tools "

(The kit will install on WinXP or later, but you can copy Ntrights.exe to a Win2k computer and try it out if necessary)

--

torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx
---/quote---

Alternative link for Win32 resource kits downloads.

So according to this MS post by executing ntrights + relevant parameters through perl you should be able to unblock the situation.

Alternatively you can run a diff of a registry dump before and after applying the security change on a test machine. Then reapplying through Perl Registry handling this setting on the target machine.

Alternatively you can also ask the network administrator to create an OU (W2K* active directory Organizational Unit) containing all your target machines and to define a group policy applying this security policy. Which may be in the long run the best idea since Domain Group Policies override Local Security Policies thus suddenly breaking your local settings and scripts.

Hope this helps you out.

With kind regards.

ddn123456