Registry settings at logon

[mike sullivan]

We manage networks in 5 schools, with about 1800 users
and 380 PCs and laptops.

I am trying to adjust the users' registry settings during
login. The users are on XP Pro workstations logging on
to an NT4 domain. The users are in a group which is a
member of the workstation Power users' group.
The users' login script runs a Kix script to make the
registry changes to the existing keys, but the script
returns an Access denied error for some of the changes.

HKCU\Software\Microsoft\Windows\CurrentVersion\Policies
HKLM\Software\Policies\Microsoft\Internet
Explorer\Restrictions

are the main problem. NT4server doesn't have enough
facilities to restrict these in group policy editor.

Does anyone have any ideas for fixing this?


Am I in the right newsgroup?


Thanks in advance,

Mike

 

[Jason]

We use NT4 System policies (ntconfig.pol)to role out
registry changes to xp clients. The problem with kix
script is that if the user doesnt have sufficient admin
rights to run regedit on the login you will get this
access denied error.

Hope this helps

 

[Guest]

Hi Jason,

I use a tool called RunAs Professional Version 3.1.3. It allows you to call jobs and apply them under a domain admins accounts profile (encrypted of course).

It's not perfec because I'm trying to iron out a small issue with registry settings right now, thats why I've found your posting. It's not the program that's at fault though. Give it a try.

 

[mike sullivan]

thanks for the reply - sorry about the delay in
acknowledging it.

I tried the policy editor on my NT4 server but the
available settings don't cover all the hacks needed.

I have discovered since, that making the settings in the
registry of a workstation administrator and then copying
that user's profile over the default user profile does
mean that any subsequent user logging on gets the correct
registry restrictions. You MUST be a workstation admin
user not a domain one though. Also DON'T turn off the
Start menu/run command until you have finished the
testing as you need to get to regedit to make
corrections!!!

Thanks again,

Mike