Posted on March 24th, 2010 No comments
From the community hero dept. I just got a LinkedIn update on a new cool article, written by Alain Assaf over at the CDC. He’s created a recipe on how to create a Wisdom module which will look for windows dump files, collect them centrally and report back to you by email. Pretty darn nifty if you ask me!
You can read the full article here: Wisdom-Fu: Email alert when you find a memory dump. There is also a forum thread about this. Wisdom-Fu… Gotta love it! :-) Keep up the great work Alain!
Posted on March 5th, 2010 No comments
A set of 3 new technotes have been published this week, which will help you get more out of PowerFuse. We’ve got a Win7 migration article in the works too, so stay tuned! Here is an overview of the articles, available in the Technote Library.
RG024: Secrets of PWRGATE.EXE (Added March 5th 2010). This document will show some of the less know things you can use the pwrgate.exe process in PowerFuse 2010 to accomplish. For example you can launch the User Installed Applications (PMWS) wizard directly with this tool, and much more. A buildingblock is included for your convenience.
RG023: Managing multiple config sets for one app: (Added March 2nd 2010). Here we will examine how you can have multiple sets of configuration settings all stored under one application, enabeling the users to select which to apply when they start the app. Very usefull for prod/test/dev scenarios. We will also examine the new Registry Tracing feature of PowerFuse 2010 in the same article.
RG022: PRINTERS.LST – The forgotten feature: (Added March 2nd 2010). This is the first article since the release of Powerfuse 2010. From this article you can learn how to create lists of printers which better reflect the geography and physical world, where the printers reside.
Posted on March 4th, 2010 No comments
From the Technotes-R-Us dept. A cool technote has been produced by one of my favorite Support folks, Paulina over on the RES Inside blog. This article covers how you may create a test environment by upgrading an copy of an existing PowerFuse 200x environment to PowerFuse 2010. Two approaches are detailed:
- Exporting all buildingblocks from the existing environment and creating a new database
- Copying the PowerFuse datastore and upgrading it to 2010
Go read the article here and remember to vote on it!