Automating the world one-liner at a time…
Superstar Dmitry Sotnikov has done the world a great service today by documenting how to get PowerShell running on WS08 Server Core HERE. Just to be clear, this is not a MSFT supported configuration. That does NOT mean that we think it won't work. What it means is that if it doesn't, you have to leverage the community to help you figure it out instead of Microsoft support. [Insert your favorite snarky remark here] :-)
As admins, it is just a simple fact of life that we have to color outside the lines to get our jobs done. Yes - it would be best if we could leverage standard configurations and officially supported components but most days the criteria is "if it works, it works".
Just to be clear - there will be certain .NET classes that do not have the necessary WIN32 APIs to support them. I think you will be hard pressed to find any or more importantly, NEED any. I went out of my way to find one to see what the experience was and you just get a nice error message saying that it could not find the DLL. PowerShell continues to run without a glitch.
You should give it a try and then share your experiences so that we all get this configuration better in focus.
What a great way to start the day!
Jeffrey Snover [MSFT]Windows Management Partner ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Phew...here I got all excited for an official answer...
So when are we going to see the PowerShell configuration, since we have the client configuration one now;)
well one can always hope:)
Very cool. Check this out in the lab tonight!!
Hmm, and does installing .NET 2.0 SP1 then also end up giving you ASP.NET on Server Core?
And, more to the point, what are the licensing implications of this?
Does this mean now SQL can also be installed on server core ;-)
Dmitry Sotnikov is the fine guy behind PowerGUI
He is a powershell star indeed.
Look no further. Quest Software’s Dmitry Sotnikov has got .Net Framework 2.0 and Powershell 1.0
I've been scratching my head as to why the .NET Framework is totally unsupported on 2008 Server Core in the first place. It never made much sense to me and now this post tends to indicate that it is a fairly arbitrary decision. It's clearly technically feasible to run .NET on Server Core.
I realize that there are components that support windowing that won't be there, but making .NET totally unsupported seems like throwing the baby out with the bathwater. It's particularly vexing since Exchange Server, SQL Server and ASP.Net (not just IIS) application server roles are just the thing one might wish to run "headless" and PowerShell is just the technology one might wish use to manage such servers.
Worked like a charm! I always thought it was a big mistake that it was not able to run on Core Server. Now I have much more flexibility in managing the server without a gui
Now I have to see if I can use this technique to make it work on WinPE.
Como sabéis, Windows 2008 Server Core no tiene .NET Framework, y por ende, no se pueden instalar productos
PowerShell evangelist (and Microsoft deployment guru) David Saxon dropped me a note this morning to let