Laughed yourself a think method, figuring vdi to implement a main machine more users system of square case, using the Windows server 2016 t p 4 new added into the multipoint server, the service, can allow a main machine, as long as plus a u s b hub, u s b sound card, indicator, key mouse, you can set into a one meter calculate machine, almost didn't have a phase locked tutorial on the net, touch the rope all the way, the current can be used in real is more than a master machine sheet system (server 2016) independent operation, a management interface, under the multipoint server WMS manager, its a vdi, in this way can be implemented quickly create a virtual machine, the hyper - on actual v, through the vdi boundary surface create a virtual table surface template, generate win10 virtual machine, the click create virtual workstation, ideal will create virtual workstation allocation to the user, the user's start at the beginning of boundary surface is connected to the win10 virtual machine,
Problems come, when using the virtual machine w in10, will always stay in connection, and then in the blue of a few seconds interface, by another virtual machine monitor log on Windows server system, the background show win10 that one has an exclamation point, prompt connection timeout, collecting system log shows that the effect is dependent on the hyper - v wcifs service did not start, can't find the service, the switch back to the Windows server system, can the normal connection again,
For help,

CodePudding user response:

Is not a virtual machine, do not need to create a virtual machine, I wms2011, 2012 are used, the production system of 2012 used for 3 years now, you see the document, each display corresponding to a station, the keyboard mouse to usb hub connected to the computer or use local site, I use M320