Package Boot Editor - Adding a regedit.exe

pigeon

Is this an acceptable use of the Package Boot Editor ? (I've attached a screenshot)

These are the key points.

1. I've added a file (custom.reg) to the package.

2. I'm using the variable %MODULEPATH% in the Command-line parameters.

3. I'm executing regedit.exe from the %WINDIR%

packagebooteditor.JPG

Find more posts tagged with

3rd_party_patch_management

sam12345

packageboot

patch_manager

third_party_patches

custom_package

Accepted answers

pigeon

I went through with testing this custom package and have confirmed that the package deployed successfully and the custom registry keys were also added. So %MODULEPATH% (and other variables?) can be used in the 'Command-line parameters'.

All comments

ascoyne

The way I added registry is to add reg.exe to my package. I then used Run Program reg.exe with the command line import <filename>.reg.

pigeon

dkeyser

Great information guys, Thanks!

andrewm.

Yep, perfectly acceptable. Even some of the SolarWinds third party packages do this - See the Java x86 on x64 update packages which run a couple of packaged batch files by calling cmd.exe from %windir%\system32 and passing the %MODULEPATH% variable