- get started
When deploying the agent using a group policy, you need to create a configuration file to include your unique parameters. You can create this file using Microsoft Orca
a) Open SysAidAgent.msi using Orca and click Transform -> New Transform.
b) Click on Property on the Table pane, and you should find the same parameters described above.
c) You should modify at least the ACCOUNT, SERIAL and SERVERURL parameters, and you can also modify the optional parameters (as specified below).
d) When you finish, click on Transform -> Generate Transform and save the file as SysAidAgent.mst.
This MST file will be useful for future versions as well, so make sure to keep a copy of it.
Now you can use the MSI and MST files to publish the agent using a group policy.
Some more optional parameters (with the default values) are as follows:
ALLOWREMOTECONTROL (default value="Y")
ALLOWSUBMITSR (default value="Y")
CONFIRMRC (default value="Y")
ENABLESYSAIDPS (default value="N")
FIRSTTIME (default value="Y")
HOTKEY (default value="122")
INTERVAL (default value="30")
LOGLEVEL (default value="0")
PROXYPORT (default value="0")
PROXYSERVER (default value="none")
RANDOMMACHINEID (default value="N")
SUBMITSRSHORTCUT (default value="SysAid")
To deploy the MSI package with the MST file you created, you should add that to Computer Configuration part in group policy. To do that, open group policy object editor, expand Computer Configuration -> Software Settings, right click on Software Installation -> New -> Package...
Point to the SysAidAgent.msi file. It is very important that the path would not be local or through a network drive, but through a network share which will be accessible from everywhere in your network and to which everyone has at least read permissions on.
Under deployment method, choose Advanced. If you choose otherwise, you won't be able to apply the MST file you created. Switch to the Modifications tab, click Add and then point to the MST file. Again, it is very important to use a UNC to the file (to the network share), rather than a local/network drive path.