I am using the scripting from K1000.  Here is what I am doing.

Remediation

Directory: C:\Windows\SysWOW64

File: reg.exe

Paramerers: add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dnscache\Parameters" /v ServerPriorityTimeLimit=dword 00000000


I found this from http://www.itninja.com/question/edit-registry-key-on-windows-8-with-reg-command-via-script

It is not working.  I need someone to let me know what I am doing wrong.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
you are using the 32bit reg.exe by choosing that one use the one in c:\windows\system32 and change the parameters to be correct usage

add "HKLM\SYSTEM\CurrentControlSet\services\Dnscache\Parameters" /v ServerPriorityTimeLimit /t REG_DWORD /d 0 /f

if that does not work use this on x64 machines

add "HKLM64\SYSTEM\CurrentControlSet\services\Dnscache\Parameters" /v ServerPriorityTimeLimit /t REG_DWORD /d 0 /f
Answered 12/03/2015 by: SMal.tmcc
Red Belt

Please log in to comment
1
I have been trying to debug a CIR problem and discovered that I had to use the sysnative call to get reg.exe to work correctly.

ShellCommandTextReturn(c:\windows\sysnative\reg.exe query hklm\software\microsoft\windows\currentversion\run & c:\windows\sysnative\reg.exe query hklm\software\WOW6432Node\microsoft\windows\currentversion\run)
for your situation you may need to do the same thing

Directory: C:\windows\sysnative
File: Reg.exe
Parameters: add "HKLM\SYSTEM\CurrentControlSet\services\Dnscache\Parameters" /v ServerPriorityTimeLimit /t REG_DWORD /d 0 /f
Answered 12/04/2015 by: SMal.tmcc
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity