Click here to view the article.

The thread can be found here and here’s a direct link for downloading the Visio shapes.

The new article, called RG023 Managing multiple config sets for  one app, also describes how to use the new Registry Tracer feature in PowerFuse 2010.

Click here to read the full article

Go read the full article here.

Go have a look at the updated article

Initially, may I direct your attention to the Corp. Website where you can download alot of PowerFuse 2010 info already. Scroll down to the end of this page and you will find them.

For those already working the RC1, the major deltas are that the [+] PlusMenu now is implemented for the Workspace Model node and Active Directory Sites are now supported as a new PowerZ… erm Location Rule. The new rule looks like shown here on the right.

Over the next couple of months, expect to see many more feature related articles describing how you can put the new features of RES PowerFuse to work for YOU!

Oh, and feel free to download the ReleaseNotes here :

This new feature of PowerFuse 2010 is evident when you it on a target computer for the first time. Here you will get a (somewhat) interesting question, wheather you want to launch the Workspace Composer automatically or manually. What the installer is asking you (in the oldschool terminology) is “Do you want to set PowerFuse as the Shell now?”.  The dialog box looks like this:

So what’s this deal with a Workspace Composer, you may ask? Well, it’s new branding for the Workspace Manager (pfwsmgr.exe) I don’t believe the process name itself has changed though. So just to make sure we are all on the same page, let’s get the terminology straight:

Automatic = Set the value of HKLM\…\Winlogon\Shell to pwrstart.exe, i.e. start a Powerfuse session at logon.

Manual = Set the value of HKLM\…\Winlogon\Shell to explorer.exe, i.e. don’t start PowerFuse

Out of the  box, the value for the installer is manual. The overall idea is for you to be able to dunk PowerFuse into an existing environment, and then centrally switch PowerFuse on across the estate in the tempo you’re comfortable with. Note: When installing RES PowerFuse unattended using a command line, it is now possible to apply the public property AUTORUNCOMPOSER. I presume you set it = YES, but I will have to check.

So great, we can set the shell uppon install, but what about later in the console? That’s also possible. In order to use this, do the following.

1. Start the PowerFuse console and navigate to Setup|Agents
2. Select one or more agents and rightclick on them
3. In the context menu, go to Run Workspace Composer and select Automatic or Manual.

Let’s say you’ve changed an agent to Manual, thereby disabeling PowerFuse. When you’ve changed the setting, the status in the Run Workspace Composer column for the agent, will change to Manual (pending). This means that the agent has not yet picked up the configuration change. The agent will check for the status of the shell in the database and then in turn write the new shell value to the registry locally. This should however happen as quickly as any normal configuration change. You can hit F5 in the agent view at any time to update the status.

• What the heck is Azure?
• Why would I want to consider that?
• What does it do for PowerFuse?
• What would all this cost me then? Are there any savings?
• Right, so how do I setup the darn thing then?

All these questions and more, are adressed in a brand-spankin’ new Technote RG021, which is available for your reading enjoyment in the library.

Click here to read the full article

• PowerFuse Express. This is a free version of the software, limited at 100 CCU’s and about 20% of the featureset (hey, you get what you pay for :-) This version will essentially help you get started with getting rid of your existing login scripts.
• PowerFuse MyWorkSpace edition. MWS was developed to address certain needs in overseas markets. MWS edition does not have the Security (appguard etc), Reliability (cpushield and so on), Integration (Citrix, Wisdom, etc) subsystems available, but the pricing is very affordable.
• PowerFuse Standard edition. Standard is very similar to MWS, except that we throw in a few more features. AppGuard and Removable Disk security within the security subsystem. Second it contains CPUshield and Instant Logoff in reliability. Filters and instant reports are also enabled. Finally it includes all integration options except Citrix integration.
• PowerFuse Enterprise edition. This is the Grand Enchilada with everything including the kitchensink, blender and matching steak knives :) Enterprise gives you the full range of User Workspace Management power at your fingertips in one easy to manage console.
• Platinum Edition. Yeah, so Citrix invented the idea of lobbing everything into one license and we are graciously following suit :) Platinum is not really a product, but it’s a bundeling offer which is currently includes both PowerFuse Enterprise edition and RES Wisdom. For more information about this and pricing informatiom, contact your local RES folks.

In order to help you get a better overview of what feature is in which PowerFuse edition, I’ve dug out a comparison chart out of the corp website. It shows a breakdown of what features are in there, what the benefits are and a checbox field for all 4 editions:

Click here to download the chart:

If you are new to the RES multiverse, perhaps comming from the SCCM side of things, it can sometimes be a bit confusing to figure out if a certain desired functionality is to be found in Wisdom or in PowerFuse. To help you find your way quicker, here’s a set of rule-of-thumbs for you:

• If the functionality you want has to do with the computer itself, it’s Wisdom you want.  Examples of this is rebooting, installing software, printerdrivers, modifying the contens of the system drives, setting HKLM registry settings
• If it has to do with anything within the users session, such as exposing shortcuts to installed software, mapping to printerqueues, modifying the contens of the profile or homedirectory, or setting HKCU registrysettings – then it’s PowerFuse you want to be looking at.

Where things may become a bit iffy for some, is when they discover Wisdom’s ability to provision users, and most go; “Hey, but that’s something to do with the user, why is it in Wisdom then? There is actually a perfectly good explanation for this. Creating a user is something which needs to be done on a Domain Controller, i.e. it’s not something happening within the user’s session. Basically adding a user to AD is essentially just adding a record to some database, a task which RES Wisdom is also perfectly capable of.

Second, PowerFuse has the capability to fire off a Wisdom job, based on user actions or simply event driven (logon, application launch, etc). This is actually an extremely cool feature which enables you to realize install-on-demand scenarios, as the logged in user does not have to be a local admin! Bear in mind however, that PowerFuse is not about application virtualization like App-V. The concept of PowerFuse+Wisdom integration may seem to somewhat blur the line in terms of which RES product does what. It is however quite simple when you look at it top-down: PowerFuse sits with the user in the session “layer”. PowerFuse knows how to talk to Wisdom below, which on-demand then executes machine tasks on behalf of the user in the “os” layer beneath.

To sum things up, the key difference is that Wisdom doesn’t care if the user is logged on or not, even if the target computer is turned on – as we support WOL. PowerFuse on the other hand, springs to life the moment the user initiates a session and stays with him and manages the environment until session end.

While we’re at it, the nice folks at RES.NL supplied a set of Feature Profile documents, which outline the technical capabilities of some of the features found in PowerFuse and Wisdom. The documents can be found here.

Thanks everybody for contributing to the RES community – Keep it commin’! :-)