This idea has been merged into another idea. The merged idea is not visible in this portal.
We deploy the jump client to all systems on our network. Currently, if an end-user initiates a chat session from the portal, they are prompted to click through a bunch of script installs. This seems unnecessary when the jump client is already installed. It would be more efficient if the chat portal would recognize that the jump client is already installed and leverage that instead of installing an ad-hoc agent that just gets removed when finished.
|Submitter Name||Jason Perry|