Resolution when it is not possible to detect audio driver.
- When bot is trigger from Orchestrator, the Robot does not find any audio driver device.
- When job is started from Orchestrator, no audio is detected.
Occasionally, audio drivers are required for text-to-speech tools, but it is not possible to detect them when running via Orchestrator.
Resolution: Consider the below approaches,
Approach #1: Inspect the Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection group policy. If possible, set the policy to "Allow audio and video playback" to "Disabled".
Approach #2: Use Console Session (LoginToConsole="Yes")