I have a requirement to identify the existing terminal session and use it rather than creating a new terminal session. I have the session id of the terminal session running in the VDI but I am unable to create a terminal connection with this session id. Is there any other way to create a terminal connection if there is an existing session identified?
Check this post
I think you misunderstood the question. I don’t want the procedure after a session is created.
When I trigger the job from the orchestrator, if there are any active terminal sessions then bot should use it(the connection is still not set up) rather than creating a new instance again
Hope I made the question clear now