Now that a build of Windows Server 2008 R2 has been released, I can start talking about what we have been working on. In a Windows Server 2008 R2 Server Core installation we have:
· Active Directory Certificate Services is now an available Server Role.
· WoW64 support for 32bit applications is now an optional feature in Server Core and is not installed by default. This enables you to further reduce the footprint of Server Core if you remove it from the image. I’m interested in hearing feedback on our decision to not install this by default – is this a good idea, or will you always need to install this because you have 32bit code you need to run?
· Added the following as optional features:
The important thing to note about all of the above is that they are all optional so if you won’t be using them you don’t need to install, manage, and maintain them.
In later posts I’ll get into more details on how to install these, what I mean by subsets of .NET, as well as other topics.
PingBack from http://windows2008security.com/win-security/server-core-changes-in-windows-server-2008-r2/
This was posted on the Server Core blog today and seems interesting enough to share here as well... Server
I would hope that Microsoft would still install this by default. There are still 3rd party development tools that are still not 64 bit. Making this change would make our product incompatible with R2 Server Core. With zero way (until early 2009) for us to make it work right now. This would make us re-live the Vista experience all over again. Why not wait until Windows 8 to go 64 bit only by default...or R3?
As I said in my last post I have a whole stack of things to talk about in the aftermath of Tech.ed in
Great to see a new post Andrew...it has been way too long.
I think the 32-bit code should be loaded because of the amount of applications companies use. Perhaps a lot of people have been complaining about space limitations on these servers but I doubt it.
A couple points of clarificaion I'd like from you...are you telling me .NET 2.0 is now on Server Core and I can finally run PowerShell on it????
I would suggest making 32-bit support an option at install time--it's important enough and a simple enough on-off option to put it there. Or perhaps even make it one of the selections--W2k8R2 Standard Server Core w/32 bit support, W2k8R2 Standard Server Core w/out 32 bit support, etc. A lot of these Server Core installs are for things like file & print, AD, etc., with no 3rd party software.
I don't see how it would make 3rd party software incompatible--a lot of software has prerequisites that are not installed by default. IIS is a great example of that. Exchange has a whole checklist of stuff that you need to do before install. IT pros are used to this.
At Tech∙Ed last week some information emerged on Windows Server 2008 R2. Specifically some information
If you are a Server Core fan, and wished you could host ASP.NET websites in Server Core, then feel better,
If you are a Server Core fan, and wished you could host ASP.NET websites in Server Core, then feel better
Quando anunciamos, durante o lançamento do Windows Server 2008, a opção “ Server Core ”, a reação (pelo
" If you are a Server Core fan, and wished you could host ASP.NET websites in Server Core, then
Windows Server 2008 R2 Server Core安装可以配置更多的角色。.NET freamwork的部分功能在Server Core得到支持，包括：.NET 2/3/3.5的子集和ASP.NET。另外，PowerShell也在Server Core上可用。IIS7在Server Core上缺少的功能仅仅是本地的管理GUI
.NET Subset??? By not allowing all of .NET to be an optional installable component in R1, the Windows Server team has completely disenfranchised the entire .NET ISV community!!
What gives?? Our Java-based competitors can run day one on Windows Server Core and we now have to wait until 2010 for a subset???
This situation is NOT acceptable. It seems to be based on some perverse view that all .NET applications look like those silly IT demos that we see at PDC. Real ISVs have real applications and many of them are headless network services or network monitoring tools that do not require IIS presentation services.
Why should we continue to build managed code if we can't run it in all roles? Having to jettison managed code to run on Windows Server Core makes no sense.
If I wanted to run on a subset, I suppose I could port to Mono, but then I could just run on Linux and not need Windows Core.
100% .NET support is essential and should be in SP1 early next year and not in R2 sometime 2 years from now.
In case you haven’t already heard the news, ASP.NET will now be enabled on Windows Server Core starting