Hi!
End Users encountered a problem launching the chrome browser within RDP sessions on the server.
Classic RDP deployment, with VHD profile disks.
What's weird is when the users click the chrome exe (directly on program files) - it's running just fine, but the shortcuts pointing to that executable (neither on the public desktop or each
individual user) do not. furthermore, while chrome is set as the default browser to handle URL and HTML association, it does not run (not even a proccess...) when a the user triggers it (like clicking on a hyperlink etc).
anyone else experienced the same?
