/build/static/layout/Breadcrumb_cap_w.png

Trying to add a registry file with k1000

Hey guys, a little stuck here....
Im trying to add this reg file with the K1000...

Windows Registry Editor Version 5.00

;-------------------
;Microsoft Edge
;-------------------
;File Types: .htm, .html
[HKEY_CURRENT_USER\SOFTWARE\Classes\AppX4hxtad77fbk3jkkeerkrm0ze94wjf3s9]
"NoOpenWith"=""
"NoStaticDefaultVerb"=""

;File Types: .pdf
[HKEY_CURRENT_USER\SOFTWARE\Classes\AppXd4nrz8ff68srnhf9t5a8sbjyar1cr723]
"NoOpenWith"=""
"NoStaticDefaultVerb"=""

I did try the 'Registry' under 'Configuration Policies' using only the keys alone and it came back as a fail when I ran it
I called it in a bat & cmd script, it downloaded but did no execute
I tried to import it with the script as well and no luck

I have tried everything i can search for and not having any luck

What am I doing wrong?
Any help is appreciated.

cheers

1 Comment   [ + ] Show comment
  • Unless you are running the script as the logged in user the registry keys will try to import to the SYSTEM user. Keep that in mind when the keys are in HKEY_CURRENT_USER. Also remember that the KACE client is 32bit so 64bit keys are more tricky. - chucksteel 7 years ago

Answers (5)

Posted by: rockhead44 7 years ago
Red Belt
2
I have never done it as gwir suggests but that makes sense. I have always scripted it, uploaded the registry  file and a batch file and run the batch to call the reg file, like

@echo off

regedit /S filename.reg

as Task 1 Verify. Run a batch file

Posted by: gwir 7 years ago
Second Degree Brown Belt
1
If you want to do it with a script add your reg file as an attachement and configure this task :


Hope this help

Posted by: vjc 7 years ago
Senior Yellow Belt
0
thanks guys...
I tried both ways you suggested and they went through as Succeeded. However no changed were actually made in the registry. ...I ran it as 'Chucksteel' suggested as 'Logged in User'. (I actually tried it on all 'Windows Run as') with no joy.

We are using x64 machines, does this differ?
Would have never thought that a simple reg change can be such a challenge.

cheers

Comments:
  • Did you run as logged in user with the /reg:64 flag? The KACE agent is a 32bit application so any child processes will also be in the 32bit context. The /reg:64 flaf gives reg.exe access to the 64bit portion of the registry. - chucksteel 7 years ago
Posted by: anonymous_9363 7 years ago
Red Belt
0
For HKCU, there's no separation for "bitness", so adding /reg:64 makes no difference. Yes, you'll notice some stray crud there in a 'Microsoft\Active Setup' branch (I never have got round to finding out which product puts that there...) but nothing else.
Posted by: vjc 7 years ago
Senior Yellow Belt
0
I tried it as Local and Logged-in user with the /reg:64 and it stated Succeeded, however it didn't change anything.
I know the script works as after it downloads I run it and it does the changes.

I even tried it as Verify "run a batch file" and even 'On Success' and added the text into the script, it stated Succeeded but no changes were made.

I ran a simple notepad.exe at the end of the script to test whether it executes after the download (thinking that it does not execute) but it does, notepad opens fine but no changes to the registry.

So I'm stuck!

Comments:
  • I have the same problem now vjc......
    Did you ever get his resolved ?
    Would you mind sharing if you did.?
    Have tried all the know methods to deploy a ,reg file.....no luck.
    Even though the task says succeeded. - akmagnum 5 years ago

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