Menu
How can I deploy with an MSI package through group policies? 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 (available for, and ).
The only needed component during installation is Tools, located under Microsoft Windows Installer SDK. Agent files are architecture specific. You must create separate transform files for 32 bit and 64 bit agents.
Note: This option is designed specifically for group policy deployment. If you want to deploy the agent manually or via command prompt and script, select the Download SysAid Agent for Windows option in Settings Network Discover Downloads. To deploy the agent with a group policy using MSI:. Open SysAidAgent.msi using Orca and click Transform New Transform. On the Tables pane, click Property.
Software installation startup-script via GPO. Ask Question 1. The install packages are.exe and not.msi, hence we are not able to distribute via the normal 'Computer Configuration Policies Software Settings Software Installation' policy. Hence, we thought about using a startup script under 'Computer Configuration Policies Windows.
You should find the same parameters described above. You should modify at least the ACCOUNT, SERIAL and SERVERURL parameters, and you can also modify the optional parameters in the list below. Note: The following default values are applied, but are displayed as 'NULL'. It is not necessary to add in the default values and attempts to add them again can lead to user error.
While I can not for sure say what is going on with Group Policy. The duplicate session I can help with. Currently the software keeps a list of all sessions for 24 hours (its a configuration setting in web.config) even the ones that have been uninstalled or are disconnected. Now that duration can be changed to be shorter or longer. What a lot of customers wanted was a way to quickly remove those from the list. In 4.1 we are introducing a new end button for unattended that will remove uninstalled clients from the list.
It currently does not uninstall the client so if not uninstalled you would want to do that before removing from the list. Other changes around this use model will be released in 4.1 and will be documented in our output stream. Oakleyross - genius - there are a few minor bugs in it. If anyone else is having trouble with it all the '%logshare%%ComputerName%.log' lines need a - ie '%logshare%%ComputerName%.log' REM IF EXIST '%SYSTEMDRIVE% Program Files (x86) ScreenConnect Client.' set CustomConfig=exists REM IF EXIST '%SYSTEMDRIVE% Program Files ScreenConnect Client.' set CustomConfig=exists shouldn't be REM'd out other than that:-) I ran into issues using this script this week.
I had used it before, and made changes to get it to work, but had forgotten the changes I had to make. I am re-posting the script, in it's entirety, with changes I had to make to get it to run.