Recently got involved in designing and building a new awesome blistering fast Omnissa Horizon environment for a hospital. This new environment is based on the latest Horizon ESB, DEM, AppVolumes, Windows 11 etc. And as many hospitals do, they use Imprivata OneSign. We ran into a bug. When logging in to the desktop (either Imprivata Client or Horizon client directly) we got confronted by the Imprivata GINA screen. Once again entering credentials and the desktop continues. Reco

Ran into a little bug yesterday while implementing VMware Horizon and Imprivata. Appliances rolled out, configured the site, policy's etc. etc. On the regular Windows endpoints this worked as expected. Login went fine, tabbed a badge, entering additional credentials if required by policy and the session would beautifully start, locking, roaming, smooth as silk.. Pushed the Imprivata agent to the Thin Clients (Dell Wyse based on Windows 10 IoT, although the brand does not matt

A while ago I got asked by a customer how they can auto turn off the monitor when they move away from the workstation. These workstations are located on an Intensive Care unit so when they need to access these machines at night, they want the monitors "on time" limited to a minimum to not wake up the patient too much. First thought: Manually turning off these monitors with the power button? (Smile and wave. No, we can do better!) Second thought: Power settings and the monitor

Lately a lot has been written about the EOL of VMware Verify. But… what if you are already used to Imprivata and maybe have the Confirm ID for remote access licenses around? Can we use this instead? Yes you can! How? By connecting to Imprivata with RADIUS. Is this new? Nope… they even call this the legacy experience. But sometimes legacy is just what you might need so he ho, let’s go! Of course: As an alternative to this you can use the VMware Authenticator or Intelligent HU

When using VMware Horizon, VMware Workspace One Access, TrueSSO and Imprivata you need to enable Kerberos Authentication within Imprivata. For this to work you also need to create a keytab file. In this blog I will explain how to create one and as a bonus.. can we use a custom account for this instead of the default created by the tool? Imprivata has a built in utility to facilitate this: ISXKerbUtil.exe. Normally you can find this utility in the OneSign Agent install directo