How to set up Pre-Engine and Post-Engine scripts (4225230)

How to set up Pre-Engine and Post-Engine scripts

Pre-Engine and Post-Engine script elements are used to deploy custom Kixtart(.kix), PowerShell(.ps1) and VBScript(.vbs) scripts that would run either before (pre) the Desktop Authority engine processes defined configuration settings for the manager, or after (post).

Pre-Engine Script

From the Desktop Authority Manager console

1. Select Profiles | User

2. Select the desired profile

3. Select “Pre-Engine Scripts”

NOTE: Pre-engine custom scripts are launched after the defined configuration settings are read into memory but before these configuration settings are applied. This allows you to "override" variables defined by Desktop Authority with your own custom settings. 

1. Select “Add”

2. Browse for the Kixtart script file

3. Click on “Save”

Click To See Full Image.

 

Post-Engine Script

From the Desktop Authority Manager console

1. Select Profiles | User

2. Select the desired profile

3. Select “Post-Engine Scripts”

NOTE: Post-engine custom scripts are launched after the Desktop Authority engine processes the manager defined configuration settings.

1. Select “Add”

2. Browse for the Kixtart script file

3. Click on “Save”

 

Click To See Full Image.

To run the element as an administrator type /admin after the file name. Example: AddVPN.ps1 /admin 
In case the /admin cannot the added directly, open a Notepad copy and paste the file name from the KDA console AddVPN.ps1 then type /admin. It will look like this AddVPN.ps1 /admin copy the entire line AddVPN.ps1 /admin and paste it into the File name box in the KDA console, Save and replicate.