HiperLogic

Virtualization, High Performance Computing, Healthcare IT, Enterprise Computing

April 2011

You are currently browsing the monthly archive for April 2011.

With Unidesk, you don’t rely on Windows Update, individual component patch updaters, or have to mess with Linked Clone operations like Reset, Refresh, Recompose, Rebalance. In a Unidesk world, you just perform the update or patch in the appropriate layer, and schedule a reboot of the desktop during the normal maintenance window.

On reboot the Windows 7 desktop is re-composited on the fly with all the new changes, and preserves all user data, user customizations, user installed applications, and so-called “user pollution” where files are stored all over the c:\ drive.

I prefer this approach because it is clean and simple for desktop administrators to manage. Simply schedule updates during the weekly desktop maintenance window or off hours through the Unidesk scheduler.

Unidesk Deployment Deadline

Unidesk Deployment Deadline

Make sure that your Unidesk management appliance and cache points all have a consistent and correct system time for the system scheduler to work properly, if you did not do this at installation time.

To do this login to the cache points at https://<cachepoint ip>:8003/ with admin and Unidesk1 ( assuming the default login/password) and at your management appliance at https://<management ip>:8004/ with admin and Unidesk1 (assuming the defaults). Go to Configuration->System Time on the left hand side, then validate that the timezone and current system time are correct.

Tags: , ,

A popular use case for VDI is for student labs, call centers, or kiosk type computers where the user does not need to have any of their desktop modifications saved, termed “non-persistent”.

Unidesk offers a perfect solution where the computer is put in its “pristine” state simply by tossing the users personalization layer that Unidesk would otherwise version and store. Below are the steps to use non-persistent desktops with Unidesk 1.2 and Pano Logic Broker and Zero-Client.

Step 1. Tweak the gold image

Before importing your gold image to be used for non-persistent, tweak the following registry key
HKLM\System\CurrentControlSet\services\Netlogon\Parameters
and change the value of DisablePasswordChange to 1

See the Unidesk KB article on this topic for more information.

Import the gold image as you would normally in Unidesk.

Step 2. Create a non-persistent desktop in Unidesk

In Unidesk just check “non-persistent” while creating the desktop:
unidesk nonpersistent

unidesk nonpersistent

Step 3. Create a Pano Pool and Assign the Desktops to It

Unidesk 1.2 relies on the broker to power on the non-persistent desktop after the user logs off and the desktop is powered off. After creating a set of non-persistent desktops in Unidesk, just assign those desktops to a Pano pool.
Pano Non-Persistent

Pano Non-Persistent

Pano will power back on the non-persistent desktop after the user logs off.

Tags: , , ,

© 2006-2010 HiperLogic, LLC.  |  Serving the Ann Arbor, Southeast Michigan, and Ohio region  |  (888)-268-3930  |