Some parts within your infrastructure resides on the same technology for many years. Where software vendors introduce many fancy new features and enhancements some parts will remain quite the same for a relative long period. Lucky for us IT administrators, we don’t have to redesign everything when upgrading the infrastructure.

The last decade using an ICA passthrough session was easily configured within RES PowerFuse, relying on a Citrix passtrough client, the good old Program Neighborhood, where we launched an ICA file for starting the passthrough application.

Nowadays more customers are migrating to the newest Citrix XenApp version, and subsequently introducing the Citrix online plugin as passthrough client.
At our Support department we have seen some side effects, therefore some new  tweaks had to be found to let our customers do what they are used to do for many years.

The Citrix online plugin used as passthrough client introduced two issues with the same root cause. Because of the intelligence of the Citrix online plugin the passthrough session is now started with the client name of the original client, not the client name of the server where the first session was started.

This is causing two issues:
1. SessionGuard fails where “Always allow passthrough sessions” is incorrectly detected
2. Zones (Powerzones) not passed through to the second session: “Backtrack passthrough sessions  to originating client for zones” not applied

We have found a tweak to let the Citrix Online plugin pass the local server name instead of the original client name:

x32 Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\PASS THROUGH
x64 Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\PASS THROUGH
Value Name: PASS THROUGH
Value Type: REG_DWORD
Value: 0 (default value is 1)

Now you will see:

And within RES PowerFuse User Workspace Analysis passthrough is detected:

Also SessionGuard is now behaving as expected for passthrough sessions.
This behavior will be further investigated to create a nice solution but in the meantime this can be helpful for you.
As far in our test environment I have seen no side effects of this change (please let me know if there are..), but as always: TEST before applying in your production environment.

The following intellectual question has plagued mankind for years: Which came first, the chicken or the egg? This question is quickly followed by:  Which should come first, managed desktops or VDI? Okay, so maybe they aren’t related at all, but at this point, hopefully you’re thinking about it. You’ll probably quickly realize that in both cases there is no single right answer. But for the big technology question, there is an easy explanation.

Managed desktops have countless cost savings and user productivity benefits, both in the physical and virtual environments.  So how do we get to a managed desktop?  One way is to move to a dynamic desktop model that breaks down the desktop into independent components, separating a user’s workspace from the underlying OS and hardware.  These components are much smaller and more cost effective to manage, giving IT more time to focus on strategy than daily troubleshooting and helpdesk calls. And once a desktop is fully managed with a separated workspace, it becomes easier to make any major migration—like in the case of VDI.

Whether you’ve already taken the desktop virtualization route (or plan to soon), it’s never too late to take advantage of transforming a desktop into a managed workspace.  One key benefit is context-aware personalization without the use of heavy roaming profiles.  A personalized desktop dynamically composes for a user at each instance of log in, without taking up valuable data center storage. This balances the flexibility wanted by the user through personalization with the cost benefits of standardization that IT, and the overall organization, is looking for.

If the physical environment is more your thing, there is still a great opportunity to benefit from context-aware workspaces. They allow organizations to create an IT environment that supports change because users’ workspaces are isolated from the hardware and underlying operating systems. 

What do we mean by change?  Change could include migrating to new OS, updating hardware, or even making the switch to desktop virtualization. Coincidentally, at the upcoming VMworld event, Bob Janssen, CTO, will outline how RES Software can help organizations manage their desktop environment to prepare for a smoother switch to VDI.

When it comes down to it, it makes no difference whether you are running a virtual, physical or mixed desktop environment.  There are still plenty of opportunities to benefit from user workspace management.

Now if only it could be so simple to justify the chicken vs. egg debate …

Check out “How to move to VMware View with Minimal User Impact” by CTO Bob Janssen on Wednesday September 1, 2010 at 12pm in breakout room 310 at VMworld San Francisco.

Context-aware computing seems to be on the fast track, and a hot topic of conversation. While it has become evident that the possibilities within the mobile space are virtually endless, enterprise companies are also taking note of how the technology can benefit their own daily business practices. Gartner even recently predicted that 40 percent of Global 2000 enterprises will have context-aware computing projects focused on the user experience underway by 2013. Dynamic, context-aware desktops seem like the most logical first pit stop for these organizations. 

A user’s context  plays a monumental role on their desktop experience. After all most of them are in front of their device for 8+ hours a day. And while they may not be the ones in the driver’s seat, it can’t hurt for users to feel like they are. No matter where they are or what device they are using, users should have access to the appropriate data, applications, printers, settings, and more.  They shouldn’t have  to waste time adjusting settings every time they log onto a new machine, or contacting the IT help desk with access issues. A context-aware desktop also increases security because users can have limited accesses to data depending on the location of their device.  For users, all of this means less frustration, but for organizations as a whole, it means more productivity and—if executed properly — a simpler IT infrastructure.

A context-aware desktop environment is dynamic, and adaptive. It composes each time a user logs in based on who they are, where they are and what they need to do their jobs properly.

While the race may not be on just yet, context-aware computing is gaining as a method for improving business operations by focusing on the user.  Dynamic, context-aware desktops are a great head start.

This article will explain how Novell ZENworks Application Virtualization 8 (powered by Spoon) works together with RES PowerFuse.

Introduction
Novell ZENworks virtualized applications run in an isolated environment that’s immune to conflicts with internal applications. Each virtualized application is packaged with all application files, settings, runtimes, and components needed to run immediately. Applications act just like they would if they were installed locally, but your operating system, registry and run-time environments remain unchanged.

Packaging
The Novell ZENworks Application Virtualization Studio is used to create virtual application packages that can be launched as normal applications. During the capture process of an application, the user registry (HKEY_CURRENT_USER) and the user profile (%USERPROFILE%) are set to MERGE isolation by default. This setting takes care of writing personalization outside the sandbox in the registry and profile directory.

The sandbox itself can be found in %LOCALAPPDATA%\Novell\Sandbox\<Application Name>. Files are untouched, while the registry changes are encapsulated in a file called Xregistry.bin.

Tested applications
PSPad 4.5.4 with default settings.  This application uses the user profile to save personalization.
Wink 2.0 with default settings. This application uses the user registry to save personalization.

Below some screendump of the Wink 2.0 package:

Wink 2.0 Filesystem Isolation

Wink 2.0 Registry Isolation

RES PowerFuse
Because all personalization is written outside the sandbox, configuration of a managed application will function by default. Also the Zero Profile mode: track specified settings will function as usual.

Be sure not to select Generic Isolation Integration:

Have fun with RES PowerFuse and Novell ZENworks Application Virtualization 8.

You can’t work with them but you can absolutely not work without them. In this blog I intend to give you more information regarding licenses and learn you how to control your licenses.

Before we can start, I need to explain the there is an ‘old’ license model and a ‘new’ license model for RES PowerFuse. In RES PowerFuse 2005 and earlier, license key’s where used. In RES PowerFuse 2008 and later, xml files are used. In this blog, I will only discuss the model of 2008 and later. I will inform you about upgrading your licenses from 2005 to 2008 or later.

==========================================================
Content of this blog:

- The general license process (registering your licenses)
- Upgrading your licences
- What if… (FAQ)?
      * You want to rename your RES PowerFuse or RES Wisdom Site?
     * You requested activation but have not received your activation files yet?
     * You lost/can’t find/never received your license files (or your dog ate them)?
     * Your licenses appear expired?
     * Your license appear expired after upgrade
     * Your evalution licenses are about to expire?
     * You need NFR licenses?
     * You want to register on the RES Support Portal but the Site license doesn’t work?
- Contacting RES Software about your licenses

==========================================================

The general license process

In general, you will receive license files from your reseller after ordering them. You should receive a reslicxxxx.xml and the license certificate. To apply the licenses in your RES PowerFuse/Wisdom environment:

1: Import the license(s)

Save the license file that you received by e-mail to an accessible location. This file should be named: reslicxxxxxxxxxxxxx.xml. Open the License Wizard and follow the prompts to upload the licenses to the Datastore. At the end of the process, you will be prompted to register your licenses.

2: Register the license(s)

Open the License Wizard again and follow the prompts.

The name of your RES Wisdom or RES PowerFuse Site can be any name. Most customers use their company name.

There are three ways to submit the request for license activation to RES Software:

Web: e-mail the activation request to RES Software from the RES Software website.

E-mail: e-mail the activation request to RES Software directly from an e-mail client on the computer running the RES Wisdom or RES PowerFuse Management Console (requires a configured MAPI-compliant e-mail client).

Save to file: save the activation request as a text file that you send to activation@ressoftware.com.

After registration, you will receive a single activation file (resactxxxxx.xml) by e-mail within 24 hours after completion of the process, on working days only. This is because we still register licenses manually. Generally, you will receive your activation within 1 maybe 2 hours. If you haven’t received anything after 24hours, something may have gone wrong. If this is the case, please send an email to backoffice@ressoftware.com or give us a call.

3. Activate the license(s)

Save the activation file that you received by e-mail to an accessible location. Open the License Wizard again and follow the prompts. When the licensing process is completed, the default Site ID is automatically replaced by a true Site ID that links your licenses to your business.

Upgrading
RES PowerFuse 2005 has a different license format than RES PowerFuse 2008 and later. When upgrading your production environment, you will need an upgrade license. The Servicepack will download this automatically when running the upgrade on your first machine. When you do not have an internet connection, you can download your upgrade license from the RES Support Portal. http://support.ressoftware.com

Note: You need to be logged on as the current owner of the license!

If you are building a new environment, you will need your full license. Please request your full license at backoffice@ressoftware.com


So what if…

- You want to rename your RES PowerFuse or RES Wisdom Site?
Start the Activation wizard, choose the second option (Register and request activation) and a few ‘next’s’ later, you will be able to edit your site name. You have to wait for the activation files to arrive and import for the change will be applied.

- You requested activation but have not received your activation files yet?
It may take a few hours, during working days, to process your activation. However, if you are waiting for a long time, something may have gone wrong. Please give us a call of send an email to our backoffice.

- You lost/can’t find/never received your license files (or your dog ate them)?
Don’t panic! If you need them, just give us a call or send an email to our backoffice. Let us know who you are, for which company you work and (if applicable) send along your license certificate or Site ID if you don’t have a certificate either.

- Your licenses appear expired?
Did you already activate your licenses and import the activation file? If you did and your licenses still appear as expired, please contact us!

- Your license appear expired after upgrade?
Woops! Are you sure that you are allowed to upgrade? Please note that only customers with valid SA over all licenses in the console are allowed to upgrade. If you are convinced that something may have gone wrong, please let contact us a.s.a.p.

- Your evalution licenses are about to expire?
Please contact us so we can discuss the best solution in your specific situation.

- You need NFR licenses?
NFR licenses are Not For Resale licenses, meant for RES Software partners. Not a partner yet? Visit www.ressoftware.com for more information!

- You want to register on the RES Support Portal but the Site license doesn’t work?
Only activated sites can register. Please make sure that you have registered and activated your licenses.

Contacting RES Software about your licenses
We are happy to help you with your license troubles. If you can not find your answer here, please do not hesitate to contact us. Our Backoffice is there for all administrative questions and you can reach them at backoffice@ressoftware.com. Our Support Department is happy to help you with all your technical issues regarding licensing, support@ressoftware.com.

Of course you can always give us a call!

Zero profiling explained.

One of the new features of RES PowerFuse 2010 is the Zero Profiling technology. The technology handles the personal settings of a user when using Mandatory, Roaming, or Local profiles. Of course companies want to get rid of roaming profiles because of the well known issues of this profiling technology. As we all know, roaming profiles get corrupted, or grow so large, login times get compromised.

I guess you all read Paulina’s article about creating a mandatory profile in your environment, and a quick peek into zero profiling technology. This article dives a little deeper into the RES Software Zero Profiling technology, and especially, when to use which Mode.

Maybe you were already familiar with User Preferences in RES PowerFuse 2008. In RES PowerFuse 2010 we built in the ability to preserve application specific settings. When you dive some further in this technology you’ll notice these settings are saved in the %HOMEDRIVE%\pwrmenu\Userpref folder (remind that by default the pwrmenu folder is hidden)

When you take a better look at the contents of this folder you’ll notice there are a couple of types of files in this folder. I’ll explain them to you:
.upf: in this file type the global User Preferences are stored
.upr2: in this file type application specific HKCU registry settings are being store
.upf2:  in this file type application specific files are being stored (i.e. placing a favorite shortcut in your Internet Explorer)

Application based user settings are loaded in the background after a session has started, so no logon delay will occur, only application start may possibly result in a delay when background loading of the user settings is still busy when starting the application.

The {GUID} before the extension equals the GUID of the managed application in your RES PowerFuse environment:

In RES PowerFuse 2010 you have the ability to use User Settings in several ways:
• Track any setting changed by application immediately
• Track specified settings on application/session start/end

These are two totally different settings, and you need to fully understand the difference on how to use them:

Track any settings is a useful setting to use when you simply don’t know where settings of a particular application are stored. When you enable this setting RES PowerFuse is triggered to capture all changes in the HKCU key and all changes to files and folders in %APPDATA% and %LOCALAPPDATA%, invoked by the application. These settings are stored in your userpref folder and will be restored, the next time you start an application. This Mode is for example very useful for applications which store their settings in HKCU\Software\APPName key.

Track specified settings is a useful setting when you know in which HKCU key the application is storing its settings. This enables you to only save specific keys with your user settings, which results in smaller files, quicker application startup time and clear understanding of how an application stores its settings.

The big dilemma here is why shouldn’t you just use track any settings at all your applications, this seems easy, and you don’t need to bother which keys to preserve? Well there is no simple answer to that question, as in many IT dilemmas: it depends….

For example when you want to preserve settings from Microsoft Word, probably you don’t want all settings to be stored, since Microsoft Word does a lot of settings in the HKCU key even without specifically changing a setting. So a best practice for an application such as Microsoft Word is to find out which settings are stored in which keys. In RES PowerFuse 2010 you can do this by running the application in sampling mode for clarifying which keys to preserve.

When you run your application into sampling mode, all setting which are preserved are stored on your sampling mode tab. Simply choose here which settings you want to preserve for this application and put them into the targeted items section when switching your application into Track specified settings Mode.

Put these keys in targeted items:

All these settings are loaded onto your profile when starting a session, after the logon process is done!

When you want specific settings not to be preserved by the users (i.e. blue background, white text), just put in an exclusion on the targeted item.