Workaround: Reset the application on the remote desktop. This issue only occurs after you log back in to the desktop. When you try to print from the nested application, the expected printer list might not appear. Virtual printing might not work if you connect to a remote desktop using RDP, open Horizon Client on the remote desktop, launch a nested application session, and then log off and log back in to the desktop. Workaround: Log off the desktop running on the Windows Server host and reconnect to it. The printers shown within applications are correct, however. This issue can occur with desktops provided by Windows Server 2012 RDS hosts. Sometimes the virtual printing feature and location-based printing feature are not able to display the correct list of printers in the Devices and Printers window of a remote, session-based desktop. This issue does not occur on Windows 8.x clients. On Windows 7 clients, Windows Media Foundation does not have the proper codec to support Dolby AC3 audio files. On Windows 7 client systems, you cannot use the Windows Media MMR feature with videos that use Dolby AC3 audio. However, the printing problem might still occur because the client might use a temporary address, which is not in the specified range. Workaround: Use the location-based printing group policy setting IP Range to include the multiple addresses. Anytime the client connects, it can use any one of the addresses. In an IPv6 environment, if you configure IP address mapping for location-based printing, users might encounter a problem accessing the printer because the client can have multiple IPv6 addresses.
#Vmware horizon client portable serial#
With serial port redirection, at a high baud rate such as 115200, the performance of VMware Blast is significantly worse than PCoIP, and the connection might sometimes hang. Workaround: Use third-party software to limit the bandwidth. The serial port redirection group policy setting Bandwidth Limit does not set a limit on the bandwidth.
0 kommentar(er)
