How do you modify (Default) windows registry values in a KACE script?
We are using KACE to push software to our users and need to add and edit some registry keys. Using the Registry script wizard we are able to create and populate the registry keys except for changing the (Default) settings from no value set to what we need.
In the reg file they use @="key value here" to note the change to the Default value but KACE removes this part from the script and notes that it's unable to parse the command. If I manually edit the XML file for the script after this it will create a new key named "@=" but will not replace the default values.
Does anyone know how I can get this to work?
Here's one of the registry entries we are using:
[HKEY_CLASSES_ROOT\TypeLib\{2DF8D04C-5BFA-101B-BDE5-00AA0044DE52}\2.8\0\win32]
@="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\OFFICE15\\MSO.DLL"
When KACE generates the script, this is in the notes:
Parse Errors:
no match for '@="Microsoft Office 15.0 Object Library"'
I have been searching the questions for several days and have not found an answer for this yet. Any help would be appreciated!
Answers (2)
Comments:
-
We are pushing a 3rd party application to all our computers and the vendor did not mention a known issue involving certain versions of MS Office and Skype for Business. They sent us the reg file that corrects the issue and the manager responsible for installing the 3rd party app asked us to use KACE to fix it. I'm trying to create an install script to push the app then update the registry entries as needed. It's not just this one entry that has to be changed but several. So it's not really a broken Office install. Hope that helps explain it. - ScottAday 6 years ago
RegistryValueEquals(HKEY_CLASSES_ROOT\TypeLib\{2DF8D04C-5BFA-101B-BDE5-00AA0044DE52}\2.8\0\win32, , C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\MSO.DLL)
You can query for all keys by using "and" between the different RegistryValueEquals expressions.
Then you can link the .reg file to that software entry and do a "reg.exe IMPORT #filename#.reg" as custom command in an managed installation.
Be aware that the kace agent does run in 32bit when adding values to teh "SOFTWARE" part of the registry - this will require to call the 64 bit reg.exe to write outside the "WOW6432Node" .