Does anyone deploy the Webagent via SCCM? We are facing issues, as since the move to Windows 11 we no longer use roaming profiles, and there is not a local copy of a profile kept within c:\users\. All desktops are stored on the users OneDrive that is scripted at login.
How do other NHS Trusts have this software setup, as it always installs on the local users path and not like normal software..
Hi there, @jake.pearce sorry for the delay in coming back to you.
By design, the Agent Desktop App installs under the user’s local profile path (e.g.
C:\Users\Username\AppData\Local\Netcall\ContactCentre Web Agent) rather than a shared location. This is to avoid permission issues and allow the app to self-update without requiring admin rights.
If you’re deploying via SCCM, the MSI installer supports command-line arguments, so you can specify an alternative install directory if needed. For example:
msiexec /I "Netcall ContactCentre Web Agent.msi"
If you don’t specify a directory, it will default to the user’s home folder. If you do change the location, make sure the user account has write permissions to that folder—otherwise settings and updates won’t work.
You can also pre-configure the server name by copying a WebAgent.settings file into the installation folder.
Full details are in our guide here: https://docs.netcall.com/docs/liberty-converse/5.14/liberty-converse/technical-information/on-premise-deployments/agent-desktop-app
If you’re still running into issues after following this, the best next step is to email support@netcall.com so we can help with your specific setup.
Kind Regards
Jonathan