Wisdom SR3 is out!

From the New Hotness dept. Today Sept 28th, RES released the Service Release 3 for Wisdom. There are many fixes in this release. Only enhancement is full support for Windows 7 and Server 2008 R2, which now can be selected in OS related condition.

A related question was asked by one of our community members in regards to the difference between the Wisdom Interim 1 release currently available to our EAP members and this release. Product management has this to offer:

“RES Wisdom 2009 SR3 is newer than RES Wisdom 5.4.1.0 IR1, but SR3 only contains bugfixes and a backport of Windows 7/ Server 2008 R2 support in conditions. All new features built in IR1 are NOT part of SR3. The Windows 7/ Server 2008 R2 support is NOT part of the IR1.”

For the straight dope, download the releasenotes right here: (or here on RapidShare)

/Max R.

SR1 Wisdom update

Okay, this is some old updates which have been sitting in the queue for a while without getting published. Nevertheless, there’s some good info in here on how to upgrade Wisdom.

March 27th, RES Software released an update package for RES Wisdom. The Service Release 1 package for Wisdom 2009 is available for download from the RES Portal. The update can be downloaded here (this requires you to have a valid SA logon).  So, what’s new in this update you might ask? There’s a good deal of fixes:

Have a look here for more info:  

If you havent’ tried upgrading Wisdom before, don’t worry. It’s piece of cake (really, it is! :) Essentially, you fire up your console and point to the update package, which is automagically uploaded and distributed thereafter. All the agents, dispatchers and consoles will upgrade themselves without you having to do anything.

1) You download the .WUP file (Yes, WUP is short for Wisdom Update Pack :). Start your Wisdom console and go to Infrastructure | Datastore | Setup | Components.

2) Here you use the button, and it’s pretty much a next, next finish job from there.

The mere thought of having a production system upgrade itself on a massive parallel scale,  may scare the  living daylights out of you. If it does, it just proves you’re still sane! :) Seriously, Wisdom is one of the most stabile platforms out there and it handles itself very safe and sanitary. One of the very little known facts of the product is that you can actually downgrade to an earlier update package version. So, if something isn’t working right, it’s possible to do a rollback. The version range where this is possible has yet to be determined, but we will ammend this post as soon as this has been clarified.

Happy upgrading

/TRG

PowerFuse 2008 SR4 update 8.0.4.5

Yesterday,  RES Software released an update of the Service Release 4 for PowerFuse 2008. It is now version 8.0.4.5. This update contains many important fixes. At the bottom of this posting, there is a link to download the releasenotes. There are also several cool enhancements to this update. These are mainly some interesting registry keys which you can use to tweak PowerFuse with. Here is an overview of these new settings, quoting from the releasenotes:

Configure cache timer interval. It is now possible to configure the cache timer interval. This interval determines how often the cache checks for changes in the database or for new transactions. The default for this interval is 5 seconds. This interval can be changed by setting the following registry key:

Key   : HKEY_LOCAL_MACHINESoftwareRESPowerFuse

Value : CacheTimerInterval (REG_SZ)

Data  : A value between 5 and 60 (seconds)

Warning: Changing the default of 5 seconds should only be done in special cases, such as a heavy load on the database server. 

Disable screensaver when RES PowerFuse Workspace Extender is active: When a RES PowerFuse session is started from a workstation with the RES PowerFuse Workspace Extender or the RES Subscriber Agent, the RES PowerFuse session will enable a Screensaver by default. It is now possible to change this behavior, by setting the following registry string value in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER

Key   : SOFTWARERESPowerFuse

Value : NoAgentScreensaver (REG_SZ)

Data  : Yes

Force LogOff of disconnected sessions after timeout: It is now possible to force a logoff of disconnected sessions after a specified timeout expires. This can be enabled by setting the following registry keys in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER

Key   : SoftwareRESPowerFuse

Value : ForceLogoffEnabled (REG_SZ)

  Data  : Yes or No (to enable/disable the mechanism)

Value : ForceLogoffTimeout or ForceLogoffTimeoutOnDisconnect (REG_SZ)

  Data: value in minutes

Value : ForceLogoffOnDisconnect

  Data  : Yes or No

If you are already using the ForceLogoffOnIdle mechanism, the timeout in ForceLogoffTimeout can be used to use the same timeout for both mechanisms, or you can use a different timeout to disconnect by setting a value in ForceLogoffTimeoutOnDisconnect.

Silent refresh of RES PowerFuse sessions: A silent refresh of RES PowerFuse will not show a splash screen during a refresh of the Workspace Manager, which in some cases is less intrusive for the user. A silent refresh will only be used when the refresh is a result of a display change, a USB device change or a reconnect of a disconnected session. “Silent refresh” can be enabled by setting the following registry key in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER:

Key   : SOFTWARERESPowerFuse

Value : SilentRefresh (REG_SZ)

Data  : Yes or No 

The release notes for the 8.0.4.5 update can be downloaded here:

Updated desktop shortcut lockdown BB

It was discovered yesterday that there was something missing from the Desktop Shortcut lockdown buildingblock. A part of the BB will redirect the desktop to the homedirectory. As a consequence of this (at least that’s the presumption) you may be met with a very security warning every time you click on a desktop icon. The update consists of a PowerLaunch User Registry hack which will take care of this. This is to be found in a new Step 6 of the technote. The updated technote can be found here

/TRG