Looking for Enterprise Beta testers

With PowerGUI 1.7 getting closer to beta release we are looking for beta customers who are really willing to push the limits for enterprise deployments of the admin console.

Here’s the scenario which we are going to support in 1.7 and want to beta test:

  1. IT architect/consultant/system integrator/superbright IT genius customizes PowerGUI admin console and leaves only the functionality for a particular role (e.g. helpdesk) within this particular organization needs (for example, it would have a list of users limited to a specific geographic location and only provide actions to reset passwords, change phone numbers, and so on).
  2. PowerGUI admin console (without script editor) gets installed for each helpdesk person in the office.
  3. New functionality is used to lock-down these consoles (so helpdesk people cannot see the PowerShell code behind the actions, or modify the functionality, and so on.)

role-based-powergui-consoles

This helps equip everyone in the IT organization with exact tools they need, get rid of scripting (scripts get turned into admin console UI), and thus reduce risks and associated costs, and make life easier for everyone.

If this is a solution which you would consider deploying in your company – now is the time to influence the way we implement it. The beta program starts really soon and if you want to be in please contact PowerGUI product manager – Darin Pendergraft ( Darin.Pendergraft at quest com ) and let him know some details about your specific scenario so he can chose right candidates for the beta.

Tags: ,

6 Responses to “Looking for Enterprise Beta testers”


  1. 1 Jordi February 26, 2009 at 12:54 pm

    It would be interesting to expand the scenario in order to also distribute and update powerpacks centrally.

    I’m thinking on distributing configuration and powerpacks at the same time, so I can create a powerpack with the required nodes/actions/views, etc., and deploy updates to the powerpack and/or the configuration with the same mechanism.

  2. 2 Dmitry Sotnikov February 26, 2009 at 8:07 pm

    Jordi,

    Most likely we actually have what you need.

    By configuration I actually do mean nodes/links/actions/etc.

    1.7 is out – so give it a try.

    What you need to do is have the Quest.PowerGUI.xml file shared in some central share, and then use redirection.xml on the clients to point to it. We will post more detailed instructions on the wiki in a few days.

    Dmitry


  1. 1 Rebranding PowerGUI console « Dmitry’s PowerBlog: PowerShell and beyond Trackback on February 11, 2009 at 12:40 pm
  2. 2 What’s new in PowerGUI 1.7 « Dmitry’s PowerBlog: PowerShell and beyond Trackback on February 26, 2009 at 12:00 pm
  3. 3 Release: PowerGUI 1.7 « ICT-Freak.nl Trackback on February 26, 2009 at 1:04 pm
  4. 4 PowerGUI 1.7 | Weblog.BassQ.nl Trackback on March 6, 2009 at 1:13 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




My Recent Tweets

Legal

The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

January 2009
M T W T F S S
« Dec   Feb »
 1234
567891011
12131415161718
19202122232425
262728293031  

%d bloggers like this: