Re: command line tool for changing hkey_current_user

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



On May 3, 5:22 pm, "awrigh...@xxxxxxxxxxx" <awrigh...@xxxxxxxxxxx>
wrote:
On May 3, 2:47 pm, "Marcin" <mar...@xxxxxxxxxxxxxxxx> wrote:

As far as I recall, you can simply copy the user portion of the local GPO
(%systemroot%\system32\grouppolicy\user) preconfigured with the desired
settings to all of target systems (and enforce the update with gpupdate
/force afterwards)...

hth
Marcin

Didn't know I could do that.  Thanks!

Steve





<awrigh...@xxxxxxxxxxx> wrote in message

news:80be22c9-d77f-49cf-88f3-20a8849969d8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 2, 1:51 pm, "Florian Frommherz [MVP]"

<flor...@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Howdie!

awrigh...@xxxxxxxxxxx schrieb:

I've noticed that secedit can only force HKEY_LOCAL_MACHINE values.
Is there any command line tool available to force HKEY_CURRENT_USER
(for all users) changes to a policy?

What specifically are you trying to achieve?
Changing CURRENT_USER keys is something you normally do with
administrative templates (ADM templates).

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog:http://www.frickelsoft.net/blog.
Use a newsreader!http://www.frickelsoft.net/news.html

I'm documenting hardening a particular Windows 2003 server build.
It's just in a workgroup, no AD, etc.  I have a half dozen or so
hkey_current_user changes I need to force on users.  I realize I can
do that with adm templates, but I'm trying to automate things as much
as possible for the sake of the documentation.  Since I was able to
force so many hkey_current_user changes with secedit, I never have to
have the installer actually manipulate the group policy templates.  If
I had a solution to manipulate hkey_current_user via a command line,
like I have with secedit, I could have those changes done in one click
instead of documenting the changes that need to be made using the gui.

Steve- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -

I've since customized the user portion of a local group policy to
create a registry.pol. To test being able to deploy it to another
system, I simply copied registry.pol to c:\windows\system32\grouppolicy
\user and ran gpupdate /force. When I run gpedit.msc I can see the
options I've enabled in registry.pol. However, none of them are
getting applied to the users. gpedit reflects the change, but no
users are inheriting the policy. I thought there would be some event
logs indicating a problem, but I'm not seeing anything. Not sure
where to start troubleshooting this. Any ideas? Keep in mind there's
no active directory involved here, just a workgroup computer (Windows
2003). Thanks.

Steve
.



Relevant Pages

  • RE: Group policy Administrative Templetes disappear until server reboo
    ... I understand that ADM templates on your SBS ... Please open Group Policy Editor on SBS ... Windows Server 2003 Administration Tools Pack on SBS to re-register the ...
    (microsoft.public.windows.server.sbs)
  • Re: Documentation of proper NTFS ACLs
    ... can open up the Group Policy templates that come with Windows ... > for system folders in Windows 2000 and Windows XP? ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Documentation of proper NTFS ACLs
    ... can open up the Group Policy templates that come with Windows ... > for system folders in Windows 2000 and Windows XP? ...
    (microsoft.public.win2000.security)
  • Re: Adding new ADM templates to Group Policy Edito
    ... I was thinking about the Add/Remove Templates thing in Vista. ... Script Group Policy Settings with the GPExpert Scripting Toolkit for PowerShell! ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policy refresh question
    ... I made a change to Group Policy on the server. ... the WinXP desktop, I typed "gpupdate /force". ... followed by "Your workstation needs to reboot. ... >> sure Group Policy will refresh when you reboot a computer. ...
    (microsoft.public.win2000.active_directory)