The issue I'm having is once a Windows XP SP2 virtual computer has been upgraded to SP3 will be blue screen when I try to access it for the Wyse terminal after his last accessed from VMware VDM Web Access. We run ESX 3.5 and Virtual Center 2.5 times with update 3. The connection and the agent server is at version 2.1.1 build-663. XP SP3 causes BSOD during the passage of the WYSE Thin Client session to session VMware VDM Web Accessįor our VDI environment, we use both clients Wyse thin (Thin OS 6.2.0_16) and VMware VDM Web Access to access Windows XP virtual machines that are available through the VMware VDM connection server. You have the broker actually part, which is why the option full screen is grayed out, it has recived the default settings of the broker. If this is the case, the devices wil inherent of the user or the GPO settings when using logs, launch your default desktop, full-screen if configured. There is nothing there, on the next, WYSE thin client make sure that the connection broker View Manager is configured, which can be done manually, using DHCP options or management of WYSE software. He gets the parameters of the broker using our API.
He does not receive the settings for connections from ini files. If you follow one of these two steps the WYSE thin client will inherent parameters. I found some discussions on similar problems, but no resolution. Now I see my inventory on the desktop to wyse as icons, but I want one of them starts automatically. How to configure a start of the connection. How to configure the session of 'full screen '? I tried fullscreen = yes in the wnos.ini, but this makes no difference, I still see the wyse "taskbar" on the bottom. I'm testing a wyse computer V10 Thinclient (6.3.0_12) with our Infrastructure perspective (3.0.1 build-142034). Wyse thin client: autostart and full screen
0 kommentar(er)
