Published Applications Utility Updated - Not Free Anymore |
Tuesday, 08 April 2008
by Michel Roth
|
One of the tools that I consider to be very valuable is the Published Applications Utility or PAU for short. Well, there's good news and bad news about this tool. The good news is that it has been updated packing new features. The bad news is that it is no longer free.
So the Gourami team decided that the Published Application Utility is no longer free: a shame but understandable. To be able to keep improving the software, Gourami is going to ask a modest amount for the software (€100 per farm). This new version of the tool incorporates several new features such as: a Farm reporter, Policy tools and a build-in TSPE. These additions create the following feature set:
Bulk Application management
All the options below can be applied to a large number of applications at once, something that you definitely can not do with the "default" Citrix management tools.
Documentation
Create a full detailed report of every aspect of your Citrix farm.
Migration aid
If you start PAU in farm A, export your applications to files. Run PAU in farm B, and import your applications. This can save your hours of work creating the applications manually.
Saving your applications can be useful to migrate, or to set up a development/acceptance/test environment. This way you can easy generate a ‘production like’ test environment.
Policy tools
With the policy tools you can easily export and import your policies. Policies are saved to an XML file. Restoring policies is done by pre loading the XML file. You can select what policies to import and apply them to your farm. Where did it see that before?
TSPE
Terminal Server Properties Editor with AD browser. PAU features a easy way to configure your terminal server properties for your domain users. The properties you can set are: terminal server profile path, terminal server home folder and terminal server home drive.
Detailed log
Every significant action is logged to the log file. It’s very advisable to read the log before applying changes to the datastore. Sometimes actions are not possible because accounts are missing. Viewing the log is also a good way to determine your actions are carried out the way you have planned it before you save your changes to the datastore.
Read more about the new version of the updated Published Applications Utility.
|