Silent Distribution by IT
Follow these steps to download the Agent and the MSI installers:
Navigate to the Admin Panel.
Download the installer.
Open instructions to see team specific tokens and instructions. Each connected team needs their own invitation tokens and thus separate installation groups in Intune. Replace the MSI file name with the name of the msi package in use.
Three alternatives to set team-specific invitation tokens
As an installation parameter during the installation: separate installation package for each team.
Distribute the system variable before MSI deployment via Powershell script with one installation package for all computers a. Variable name = WORKFELLOW_INVITATION_TOKEN b. Variable value = c. Agents can be also be installed proactively to everyone, and the data collection starts after the system variable is distributed.
Unattended team-token distribution through ProcessMaker Support.
Recommended Intune settings for Windows app (Win32)
Install command: msiexec /i "workfellow-plug-in.msi" /qn INVITATION_TOKEN="INSERT-TOKEN-HERE"
Uninstall command: msiexec /x {GUID} /qn
Detection rules format: Manually configure detection rules
Detection rules: Rule type: Registry Key path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Workfellow Oy\Workfellow Windows Plug-In Value name: Version Detection method: Value exists
Assignments: hide all toast notifications content download in background
Please remember to allow-list the application if custom restriction policies are applied in your organization. A restart is not mandatory.
Unattended team-token distribution (optional)
Customer can deploy team-tokens during the installations as installation parameters or manually by the source-computer users.
Another option is to upload the list of source-computer users emails with the ProcessMaker team. In such case the functionality is as follows:
Agent connects to the Process Intelligence Cloud.
It checks if a new team-token is available with that email.
New team-token is assigned to that computer.
Data-collection starts for that team.
Email is no longer used or linked to the collected data.
Configuring Plug-In to Use a Proxy
This section describes the process of configuring the plug-in to use a proxy. This will allow your application to securely access the internet through an intermediary server. We will also provide information on how to use a Network Tester to check your connection to the cloud and how to restart your computer to ensure the changes take effect.
Plug-in proxy override
PowerShell
export http_proxy=http://{{proxy_url}}:{{port_number}}
export https_proxy=http://{{proxy_url}}:{{port_number}}Configuring web proxy override on windows
To configure the plug-in to use a proxy, you need to set up specific environment variables on your computer. These variables will tell the plug-in to route all its network requests through the proxy server.
Follow these steps to configure the environment variables:
Open the Start menu and search for "Environment Variables."
Click on "Edit the system environment variables."
In the System Properties window, click on "Environment Variables."
Under "System variables," click "New."
Enter "HTTP_PROXY" as the variable name and your proxy server's address as the value (e.g., http://proxy.example.com:8080).
Click "OK" to save the new variable.
If you have https proxy as well: Repeat steps 4-6, but this time use "HTTPS_PROXY" as the variable name.
Click "OK" to close the Environment Variables window, and then click "OK" again to close the System Properties window.
Testing for proper configuration propagation
Using the Network Tester you can check that connection is possible to PI Infrastructure.
If the Network Tester is already running, close it first.
Restart the Network Tester.
The tester will automatically check your connection to the cloud using the configured proxy.
Last updated