In Vista's UAC model, you don't enable your Administrator rights for an
application until you've gone through an elevation prompt. So yes, this
means that you will be required to type in your credentials (or click "OK")
whenever you want to load an elevated program (powershell included.) If
there are aspects of this that frustrate you, then the best bet is to
provide your feedback to the Vista UAC team --
http://blogs.msdn.com/windowsvistasecurity/ may be a good starting point.
As for your second point, double-clicking a script doesn't start PowerShell
unless you've specifically modified your system to enable that. In that
case, you may want to create a right-click menu option to execute the script
using the Elevated PowerShell link that Daymon spoke about.
That said, Michael Murgolo (who wrote "PowerShell Here"
http://www.leeholmes.com/blog/PowerShellPromptHerePowerToy.aspx) will soon
be releasing a little utility pack to make some of these scenarios easier.
In terms of the safety of running PowerShell as administrator -- it's
definitely a best practice to run without Administrator rights whenever
possible. If you're just navigating the filesystem, changing files, running
utility scripts, etc -- then I would advise running those in a regular
PowerShell window. If you need to modify administrative data on the
computer, then by all means perform that action in an elevated window.
Lee Holmes [MSFT]
Windows PowerShell Development
This posting is provided "AS IS" with no warranties, and confers no rights.
UAC is a core feature of Vista, so