PowerGUI Admin Console has the ability to lock down the user interface so you can create custom management consoles specific to job roles (e.g. helpdesk), get these pushed to the corresponding users, and hide from them the functionality which might hurt them (e.g. ability to see the PowerShell code behind the functionality or change anything in the tool.)
See a quick video on the feature here and a related one here.
We want to make it easier to use in the future. So the question is: how granular you want lockdown to be? It can be all the way from item-level (let this user change this node but not the other one) to PowerPack-level to user-level.
I personally like the user-level approach – some people get more functional PowerGUI than others more read-only ones. E.g. if according to your job role you are supposed to be only using PowerPacks from others – you get a locked down version of PowerGUI – regardless of the PowerPacks assigned to you. On the other hand, if you are allowed to change PowerPacks – you can do this. Of course, you might not be able to post your changes to a central distribution point (file share or SharePoint site) but this is a whole different story.
Does this make sense?
Please put your comments to this blog entry and respond to the survey here.
Subscribe by email
