/build/static/layout/Breadcrumb_cap_w.png

I am using K1000 6.4. I am trying to push a *.reg file.

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

Answers (2)

Posted by: SMal.tmcc 8 years ago
Red Belt
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
Posted by: SMal.tmcc 8 years ago
Red Belt
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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ