Software Deployment

This is assuming you're using Wise Package Studio 4.x or 5.x:

In Windows Installer Editor (WIE), opened to the WSI you want to add the Wise script to, go into the MSI Script part of the editor (your other choices are Installation Expert and Setup Editor.) Click on the Execute Deferred tab and scroll down to the very bottom. Drag the "Run WiseScript from Installation" action to just above the last remark on this page, the one right above "InstallFinalize." You'll see a dialog box with two tabs; unless you're doing something different than the way I do it, you won't need to do anything on the "Properties" tab, so just stay on the "Details" tab. Type in something descriptive in the "Custom Action Name" field if you want, doesn't matter what, then click on the "Options" button. Click on "Browse for WiseScript" and select your Wise script. Finally, add any necesary commands in the "Command Line" field, though I usually don't do that, instead I let the Wise script take care of that. Click "OK."

You can also do a "Run WiseScript from Installed Files" if you prefer, though that of course entails leaving the Wise script EXE on your target machine. It will also create a component that you should remove the key path for.

If that single cacls command line is all you need to run, you could also just choose "Execute Program from Installation" (or, again, "...Installed Files"), then put the cacls switches, etc. in the "Command Line" field in the dialog box.

Awesome!! That worked. Thanks! Although now...
When I try to package the wise script .exe into my package (b/c I don't want to have to rely on a mapped drive to a server somewhere), I get this error: Internal Error 2919
On Google, I find that this error refers to not having a cab file with the exe.
I get this as soon as I add the permissions.exe into a folder in my package, can you not do that?

You stated that you don't package your wisescipts into the msi, how do you point to them? We deploy software via GPO, so we don't have any drive mappings when the software is being installed at boot.

Thanks for your help!!!

If you do the "Run WiseScript from Installation," you shouldn't need to add the permissions.exe as part of the package. When you select that action and browse for the EXE (which can be anywhere), it should add the EXE to the MSI package when you go to compile.

If you chose "Run WiseScript from Installed Files," you WOULD have to add the file as part of the package. Like the example above, your permissions.EXE WiseScript would be incorporated into the MSI at compile time, but unlike above doing this would also copy the permissions.exe script to the target system, then execute it from there. I've used that option many times too and have not seen your particular error at any time.

Ok, I didn't realize that Wise would add the exe automatically when compiled. That makes sense now.

Well thank you for your help. You helped me out very very much.