Posted By: Neil Hutson | Jan 3rd @ 8:00 AM

Server core is a major new capability of the Windows Server 2008, allowing the ITPRO to deploy and configure a “minimal-install” version of the operating system which does not include features like a GUI, browser and other technologies ( some people say baggage) not required to run server or appliance based applications. Once installed you can install a number of services such as Active Directory Domain Services (AD DS), Active Directory Lightweight Directory Services (AD LDS), DHCP Server, DNS Server, File Service, Print Services, Streaming Media Services, Hyper-V (Virtualization) and Web Server (IIS) roles.

The main reason for this capability stemmed from feedback we got from some of our larger customers. They were all moving to global datacenter models, with a very small number of datacenters which needed to be managed 24x7 worldwide. They wanted to be able to procure a new operating system instance quickly, download across the wide-area-network (so it had to be small) and have a reduced attack surface and reduced patching. A Server Core installation only requires about 1 gigabyte (GB) of disk space to install and approximately 2 GB for operations after the installation.

Lets see it in action

To give you an idea of some of the capabilities, we recommend that you first go to Keith Comb’s blog and check out the 8 small screencasts that he has created on the subject.

http://blogs.technet.com/keithcombs/archive/2007/11/04/windows-server-2008-core-screencast-series-watch-all-eight-parts-here.aspx

IIS7 Support

IIS7 and the Web Server role is the most interesting role on server core, but it has one drawback on the full OS version. Server Core does not contain the.NET Framework (this means no PowerShell too). This means that IIS7 on server core can serve up static pages, run classic ASP and PHP, but it is cannot run applications written to take advantage of ASP.NET. To give you an idea of the simplicity of the administration experience for IIS7 on Server Core, you should take a look at the blog article on the IIS team site which provides a lot of details. http://blogs.iis.net/metegokt/archive/2007/06/26/administering-iis7-on-server-core-installations-of-windows-server-2008.aspx

Managing a Server Core instance

The next area is management of server Core as there is not GUI. We have been seeing a lot of questions internally and externally about managing server core machine and then trying to connect to it remotely. Here are some answers if you run into this issue.

C:\>netsh advfirewall set currentprofile settings remotemanagement enable

After which point the firewall should allow all your remote admin tools to connect (computer management and DNS snap-in for example).

If you're looking to instrument your systems using WMI you need to do the following

C:\>netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

The big question

Who is planning to use Windows Server Core and what scenarios are you planning to use it for?  

Tags:
Rating:
0
0

At this point in time I'm planning to use Server Core in a couple of scenario's.
(Please note: some scenario's are based on information not being available)

Hyper-V Cluster
I intend to use Windows Server 2008 Server Core as a Hyper-V Failover cluster, since I believe Server Core is the ideal Hyper-V root partition. (Hyper-V Server might prove to have more performance, but no information is ready yet on the functionality)

Learning platform
I also intend to use Windows Server 2008 Server Core as a learning platform for a couple of UNIX guys at our company to get used to Windows Server while using their own tools, not being all paranoid and not being distracted by Windows eyecandy. SUACore sure looks promising!

Branch Office Server
I also feel Server Core might prove to be hte ultimate Branch Office server. Implemented as a Read Only Domain Controller, Storing data using DFS and being Bitlockered, while at the same time not asking for a lot of hardware and rarely having to be patched (no .Net Framework, no Internet Explorer)... Wow!

 

I feel there's definitely potential for Server Core outside of the large datacenter. I guess we just need to look for the right scenarios.

It's very nice to be able to not worry over security patches at the sever because of client software (ie... IE) and makes perfect sense to keep RAM and CPU focused on the server tasks.  I would love to move our app servers and our web services to Core; only they are .net.  Without the option of the .Net framework this is of no use to me.  I wouldn't run classic ASP and if I was to use PHP, it would be on linux not windows.
I'm planning to initially roll Server 2008 Core into production as RODC's for our branch locations. Then I'll look into using it for other things like IIS and Hyper-V, but my primary concern is reducing the overall attack surface and patching needs of our current boxes at branch locations. As "SanderBerkouwer" said, Server 2008 Core could very well prove to be the ultimate branch office Server!

Well I would have been using Server 2008 Core to host large ASP.NET web applications across several servers. But I can't - no .NET Framework.

Think why people would want to install large clusters of servers with no GUI - for hosting large applications.

Not only can I not run ASP.NET apps, but I can't even run anything built with your flagship development tools either.

You've really dropped the ball here.

Not having the .NET Framework is indeed inconvenient, but I understand that's because it's not componentized yet. As a result, it's still tied to the GUI in some ways. If they rewrite that (which I guess is their intention), .NET support can be made available under Server Core. This would greatly increase the value of the product.

I'd like to run iSCSI targets on Server Core guest OS instances. Last time I checked, the team hadn't yet decided if iSCSI would make it into Core. Is this known now?