At this point you are ready to login into WVD and access your VMs! 6. Once the devices reboots, you should be prompted with the Microsoft Azure AD login screen as shown below 5. Once the updated WMS policy is received by your device, you should see your new WVD setting reflected on your device as shown belowĤ. Also under, Broker Settings\Global Broker Settings set to – “Windows Virtual Desktop” on your policy as shown below:Ĥ. When you are done, click ‘Save & Publish’.ģ. In my testing, I am using the Azure portal ARM based deployment so I selected the (ARMv2) option. You will chose either the latest WVD ARM (Azure Resource Manager) based deployment model or the ‘classic’ WVD non ARM based deployment. Under the following section you just need to choose the appropriate WVD deployment model you are using. In WMS, edit your ThinOS 9 policy and browse to ‘Advanced –> Broker Settings –> Windows Virtual Desktop Settings’ as shown belowĢ.Note – by default, the WVD client package is pre-installed on 9.1 but incase it’s not or you’re looking for latest you can get from under drivers for your model, for example 5070, search for ‘wvd’. The configuration for ThinOS & WVD is pretty straightforward with the only configuration needed is a Wyse Management Suite (WMS) policy to specify Windows Virtual Desktop under the broker setting which is shown below.
WISE DRIVER CARE CANNOT CONNECT TO THE SERVER HOW TO
ThinOS 9.1 administrators guide here, release notes here, & 8.6 to 9.1 migration guide here.
ThinOS 9.1 & WVD product summary noted here.I’ve covered some details about the configuration below and you can access the official documentation here This is big news as it allows us to use a non-Windows thin client endpoint to connect to your WVD environment! Microsoft posted a quick announcement about this as well here. The Dell Wyse team has recently launched support for Windows Virtual Desktop(WVD) on Dell Wyse ThinOS 9.1.
0 kommentar(er)
