Anouncement of new Wyse vWorkspace 8.6

On July 13th Dell announced the next version of vWorkspace 8.6 at the Microsoft WPC. This version will be available end of this month.

It really has a lot of new features that even can save a lot of money when it comes to SCVMM management. Here is the full list:


  • Added Unicode support for vWorkspace core products such as the Connection Broker and Web Access as well as the connectors.
  • Localization
    • Localized connectors for Chinese, Japanese, Korean.
  • WSM
    • Layering support via PowerShell
      • Integrate virtual layers into a vWorkspace virtual desktop to separate departmental applications from the virtual desktop’s operating system.
    • User Profile Layering
      • Captures user profile data in a layer that can be accessed from any device.
    • Hot High Availability
      • Allows client streamed by WSM to seamlessly switch to a different WSM server in the event of failure.
    • Centralized Site Management
      • Provides single management UI for all WSM Sites.
  • Advanced Hyper-v integration
    • Full clone provisioning with Hyper-v
      • This direct integration with Windows Server Hyper-V adds support for provisioning of full, persistent virtual machines where previous versions of vWorkspace HyperDeploy only supported differencing disk clones.
    • High availability of Hyper-V hosts
      • When using a Hyper-V cluster as the compute engine for your vWorkspace virtual desktops you have the option to set the virtual machines to be available across the cluster (High Availability).
  • vWorkspace Connectors
    • Connector for Google ChromeOS
      • This connector for ChromeOS provides a more native user experience than HTML5 and shall be available via the Google Chrome Web Store.
    • Simplification
      • Complete streamline of the vWorkspace Connectors’ user interface to improve end user ease of use.
    • Email-based configuration
      • Only thing user needs to know to obtain a configuration is their email and password.
    • 64-bit
      • Support for 64-bit Remote Desktop extensions (virtual channels)
  • vWorkspace Connector for Windows – drag and drop
    • Allows authorized users to drag files and content from their Windows PC and drop them into vWorkspace desktops and applications.  This simplifies common workflows. For example; insurance agents can now drag files directly into the correct claim record of their hosted CRM application. This functionality is not available in the Windows native Remote Desktop Connection.
  • Monitoring and diagnostics
    • Monitoring of Microsoft Remote Desktop Licensing Service infrastructure
    • Monitoring of vWorkspace WSM infrastructure

Dell anounced Windows 10 IoT Enterprise clients

Dell just announced the launch of two new units.
Starting July 29th Dell has Windows 10 IoT Enterprise units in their portfolio. The units are based on the well-known D90Q and Z90Q hardware. This means they will come with a quad core processor (1.5 GHz and 2.0 GHz), 32GB of MLC flash and optional wireless support.
The first release will only include RDP10 and Citrix Receiver. VMware View, Ericom emulation and even Dell’s own Wyse vWorkspace clients will be missing in this release as they are not Windows 10 ready at the moment. There is an update planed for later this year.
They will be called Wyse 7490-Z90Q10 and 5490-D90Q10.

We HAVE Moved

Looks like we have finally finished the move of the old site to this new CMS system.

I really hope you like the new design and find it easier to use.

Feel free to send me your suggestions, if you have some 😉

I was able to migrate all user accounts but the passwords are lost. Please use the “Forget Password” function to reset yours and get a new one. Sorry for that.

confgen (at) “thissite”

AD Group INI

Starting with ThinOS version 8.0_411 Dell has integrated a new option for INI file handling.

Now you can assign INI files based on AD group membership.
To do this you have to create a new folder beneath the /wnos/ini folder. It is called “adgroup”.
In this folder you can put INI files which are named like AD groups. Each AD group has to start with a predefined prefix.
In your global wnos.ini file you have to define this prefix first. Beside that you have to use SignOn=NTLM.
The full string could look like this:
SignOn=NTLM AdGroupPrefix=”ThinOS-“
Now create new groups in your AD which all start with “ThinOS-“ or whatever you have defined in your wnos.ini. Put the appropriate users in these groups and create the already mentioned INI files like this:
Group nesting is not supported nor the membership in more than one group. The first matching group will be used.