Hybrid local profile with RES Workspace Manager

Written by Ingmar Verheij on August 5th, 2013. Posted in Workspace management

In a virtual desktop environment the profile solution provided by Microsoft, the roaming profile,  is not sufficient. With the “Zero Profile Technology” RES Workspace Manager has a feature that captures users settings and injects them whenever needed, offering a more flexible solution than the roaming profile. More importantly only the required settings are captured and profile bloating and corruption is prevented.

Of course RES Software can’t replace the Windows profile so you end up with a hybrid solution, also referred to as a “hybrid profile”. Theoretically you can use any of flavor of the Microsoft profile solutions: local, roaming or mandatory and add the RES feature on top. A common used hybrid solution is a mandatory profile + RES Workspace Manager, but as Wilco van Bragt mentioned in his article about alternatives for the mandatory profile (link) this has it drawbacks.

Certificate enrollment for failed to enroll for a VUserAuthentication certificate with request ID N/A from Issuing 1 CA (The profile for the user is a temporary profile. 0x80090024 (-2146893788)).One of the biggest “challenges” with mandatory profiles, or roaming profiles where cached copies are deleted, is the use of certificates. Especially if you use auto-enrollment of certificates. What we’re looking for in a profile are the following characteristics:

  • Works with certificates – as described above
  • Removed after logoff – to prevent the computer from filling up with garbage
  • Stateless – or non-persistent. In other words, it does not store changes made by the user. Each time a user starts a session it should consist of the exact same settings, the profile solution (RES Workspace Manager) will inject the settings.

As Wilco describes in his article the local profile is the best candidate for a hybrid profile. But the local profile has one drawback: it persists on the computer.

RES Workspace Manager in a non-persistent environment

Written by Ingmar Verheij on April 21st, 2013. Posted in Workspace management

RES Workspace Manager is a user environment manager (UEM) that enables you to centrally manage the user workspace (RES term for the users desktop, start menu and all user related settings) for both virtual and physical machines. UEM products like RES Workspace Manager are common in virtual desktop environments like SBC or VDI (I don’t like the term VDI) because they simplify management and improve consistency between all the machines.

Virtual desktop machines are either persistent or non-persistent. When a machine is non-persistent the machine reverts to the state it was before (also called stateless) as it is stored in the “golden image”. This has a lot of benefits but comes with some challenges.

RES software on MySQL

Written by Ingmar Verheij on March 6th, 2013. Posted in Workspace management

MySQLIf you want to use MySQL as a data source for your RES software you might encounter some difficulties connecting to the database (Data source name not found and no default driver specified).

RES softwareRES software supports ”MySQL 5.0 or higher x86/x64” as a database platform, in order to connect to the database environment you need to meet the following database requirements:

  • MySQL DBA credentials
  • MYSQL ODBC Driver on the database server and on all Agents

The database requirements clearly state you need to install the MySQL ODBC Driver, but which version or architecture you need is not mentioned. Here’s a quick overview of the required drivers.

RES WM11: Workspace Composer hangs at “Preparing applications”

Written by Ingmar Verheij on July 23rd, 2012. Posted in Workspace management

Users who logon with RES Workspace Manager 2011 experienced a long delay ( > 1minute) and mentioned that the Workspace composer hangs at “Preparing Applications”. After the delay the desktop was shown as expected.

RES Workspace Manager - Preparing applications

Short version

The delay was caused by a check  for the existence of executables (forced by the “Hide application if executable was not found”). Since the executable was stored on a non-existing network location the Workspace Composer had to wait until the operating system returned with a negative result.

The issue is described  in Q202451 in the RES knowledge base (login required).

I would recommend not to check for the existence of executables on a network locations if you not really need it, it adds unnecessary overhead.

Be aware, RES is about to unleash WM2012!

Written by Ingmar Verheij on February 18th, 2012. Posted in Workspace management

RES software flagship is Workspace Manager, the successor of PowerFuse. Since 2010 RES releases a new version each year, in may 2012 RES Workspace Manager 2012 will be unleashed to the public.

At the RES PartnerFocus 2012 (on 16th February at the Verkade fabriek) VP Product Management Bob Dekousemaker showed us the new features of RES WM2012.

Donate