Running the Agent as a Windows Service
Copia Agent Version 1.0 can run as a Windows service. Running as a service improves agent reliability and enables non-interactive backups of some device types. Non-interactive backups do not require a Windows user to be logged into the agent machine.
Installing Copia Agent Version 1.0
You must manually upgrade to Copia Agent Version 1.0 in order to run as a service and begin executing non-interactive backups. Older versions, such as Version 0.1.72, do not support running as a service and will not automatically upgrade to Version 1.0. The agent will continue to receive automatic software updates once the upgrade is complete.
To upgrade to Copia Agent Version 1.0:
Uninstall the Copia Agent.
Log into Copia in a browser and navigate to the Agents tab in one of your DeviceLink Sites.
Click “Download New Agent Installer.” Do not click "Download Legacy Agent Installer."
Run the installer. This requires Windows Administrator privileges.
The agent should start automatically after installation finishes. If it doesn’t start automatically, search for “Copia Agent” in the Windows search bar and left-click it.
Allow the agent several seconds to start up and sign into Copia. If the agent doesn’t automatically sign in and link itself after 30 seconds, manually sign in and link the agent to Copia.
Enabling the Windows Service
Copia Agent Version 1.0 can run as an interactive application or as a Window service. The agent runs as an application by default in order to minimize disruptions to existing DeviceLink jobs. However, Copia recommends users run the agent as a service unless:
IT policies prohibit the installation of a Windows service on the agent machine, or:
Device backups fail when running as a service and succeed when running as an application. If this happens to you, please contact Copia support as this behavior is unintentional.
To run the agent as a service, tick the "Run as a service" checkbox:
You must have local Administrator privileges to change the "Run as service" setting.
Device Support
The agent can perform interactive backups of all DeviceLink devices regardless of whether it runs as a service or as an application. However, the agent must run as a service to execute non-interactive backups. An interactive backup requires a Windows user to be logged into the agent machine; a non-interactive backup does not.
Enabled
✓ Yes, for all devices
⚠️ Yes, for some devices (see below)
Disabled
✓ Yes, for all devices
✕ No, for all devices
Only some devices support non-interactive backups:
Rockwell Studio/RSLogix 5000
✓ Supported
Siemens Step7 5.x
✓ Supported
Beckhoff TwinCAT 3
🏗️ Unsupported & Planned
CODESYS v3
🏗️ Unsupported & Planned
Copia FTP/sFTP/SCP
🏗️ Unsupported & Planned
Copia Script
🏗️ Unsupported & Planned
FANUC Robot
🏗️ Unsupported & Planned
Schneider Control Expert
🏗️ Unsupported & Planned
Rockwell PanelView ME HMI
✕ Unsupported & Not Planned
Rockwell RSLogix 500
✕ Unsupported & Not Planned
Siemens Step7 TIA Portal
✕ Unsupported & Not Planned
Unsupported devices still must be backed up interactively, even if the agent is running as a service. That means the Agent tray application must be running on an unlocked screen in an active Windows logon session. If these conditions are not met and the Agent starts backing up a device that requires an interactive session, the backup will time out unless you log in and launch the tray application.
If any of the Agent's devices require an interactive session, you must still keep the Agent tray application running and the screen unlocked, even when running as a service. Failure to do so will result in the backup of only those devices that support non-interactive backups.
Changing the Service Logon Account
The Copia Agent executes non-interactive backups in a Windows service. The service logs onto the host as the Local System account. Local System provides the service with the extensive local privileges necessary to execute device backups.
You may change the service logon account but Copia cannot guarantee that backups will succeed. To change the logon account:
Determine the new account. The account should belong to the local Administrators group and posses the "Log on as a service" permission.
Open the Service Control Manager ("services.msc").
Right-click "Copia Agent Service."
Click "Properties."
Click the "Log On" tab.
Click the "This account:" radio button.
Enter the account name and password if applicable.
Click "OK."
If the service is running, it must be restarted for the new account to take effect. Warning: restarting the service will fail an in-progress backup. Right-click "Copia Agent Service" and click "Restart."
Last updated
Was this helpful?