Sorry, it definitely does not. There are ways to get PowerShell to run on it using app-V or similar techniques, but until we get to 2008 R2 Core, it's shoehorning at best.

I know it's not really practical right now.  I'm just checking to see if anybody knows what the situation will be when we do get to R2.

Server Core will *not* allow you to run anything like PowerGUI, although R2 will inclue PowerShell (and ASP.NET I think) this time, which is a huge advance over 2008 base. But once you get familiar with it (a headless windows box), and more importantly, PowerShell v2 remoting, it should not matter much.

OK.  I'm confortable with using PS to manage Server Core, but it would be nice to be able to use it to delegate some stuff to people who aren't yet.

I think you missed my point. If you are logging into your servers locally in order to manage them--don't. Best practices would be to use config management tools and remote scripting to get the job done rather than interactive logins.

Dmitry Sotnikov (Quest) recently released a .ps1 script that can pull out all of the scripts in a PowerPack. I would say one can use these scripts to automate the same tasks... It also depends on what the tasks/PowerPack is/are because some can connect to remote systems.