Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
It's been very busy in the world of Windows Server. With the launch of Windows Server 2008 R2 Release Candidate, Tech Ed and the announcement of several new Hyper-V R2 capabilities such as 64 logical processor support and processor compatibility, it's been pretty non-stop. In fact, it's been so busy, that we haven't even had a chance to introduce one more really cool new feature in Windows Server 2008 R2, but first, some background.
Windows Server 2008 R1: Core Deployment
In Windows Server 2008, we introduced the ability to deploy Windows Server in a core deployment. Server Core is a minimal server installation option which provides a low-maintenance server environment with limited functionality. Just to be clear, Server Core isn't a SKU. You don't buy "Server Core" it's simply a deployment option presented during Windows Server Setup. For example, here's a screen shot during Windows Server Setup, notice that there are options for Full Installations and Server Core Installations.
The benefits are smaller attack surface, a reduction in patches and reduction of server reboots. If you compare the number of reboots between running a server running Windows Server 2008 core deployment versus Windows Server 2008 a full installation, there's a substantial reduction in the number of reboots which, in turn, helps reduce management costs.
While customers like the idea of core installations, the fact that a server core deployment is a command-line interface (CLI) only (no GUI, no Start Menu, etc) with a very differently deployment mechanism introduces a challenging learning curve for those considering core deployments. For those of you who've never seen a Windows Server 2008 server core deployment it looks like this:
As you can see, there's no Start Menu. It's all command-line all the time. For enterprise customers, this isn't a big deal because very often they deploy Windows Server in an automated fashion. However, for small and mid-sized customers a command-line only interface can make some of the most rudimentary tasks a challenge. For example, here are the commands to rename your computer and then join a domain via a Windows Server 2008 core deployment.
Not the easiest thing to remember. We knew we could do better.
While Windows Server 2008 R1 was in development, a few of us were quietly working on the Hyper-V Server 2008 standalone SKU which also uses a CLI. We spent time working on improving the server configuration experience with an easy to use CLI called HVCONFIG. Within hours of our first private releases of Hyper-V Server 2008 to testers, we received email asking/begging/pleading/cajoling/offering bribes for a similar tool for Windows Server as well.
Happy to oblige.
Introducing SCONFIG for Windows Server 2008 R2 Core Deployments
We are pleased to announce that in Windows Server 2008 R2, there's an easy to use CLI, SCONFIG. SCONFIG dramatically eases server configuration for Windows Server 2008 R2 core deployments. With SCONFIG, you can easily set your system up, get it on the network so you can easily manage the server remotely.
Simple and fast.
With SCONFIG you can easily have a Windows Server 2008 R2 Server Core deployment setup in minutes. I should also mention that SCONFIG is also localized in almost 20 languages.
All you have to do is type sconfig at the command line.
Great! Now What?
Remember, the goal with a server core deployment is to get the server on the network so you can manage it remotely. With SCONFIG this is a snap. Now from another system you can enable roles, run PowerShell scripts, manage it using System Center, manage it using Server Manager from another server running Windows Server 2008 R2, or manage it using the free Remote System Administration Tools (RSAT) for Windows 7.
In short, our goal is to provide customers multiple solutions based on their business needs.
Principal Group Program Manager
Windows Server, Hyper-V
Sorry...while SCONFIG let's you do very basic config work..it is not enough! No way to load device drivers for devices that work with Server 2008 but not Hyper-V Server 2008 R2 - such as raid controllers. Nics...etc...and as always not enough documentation!
A simple but welcome and useful addition that will make Core an easier proposition. Well done.
Nice one. I just found this. However it would be nice if I didn't have to reboot between changing the computer name and adding remote access.
I don't see how why these configurations can't be rolled into a single step.
This has actually ben around for awhile now. Anyone who's downloaded the Free Windows Server Hyper-V has been able to use this, and I have a number of clients who have gone ahead and copied the script onto thier Core distros on other machines.
It's a very nice little script to be sure, but I'm not sure how "anouncement worthy" it is.
@JustinKing - wasn't the old version called hvconfig and only available with Hyper-V Server? I know you could run in on Windows Server 2008 but I don't think it was supported and I'm guessing sconfig can do a bit more?
Your expression in this regard was the perfect picture I congratulate you all had a good working
do I need to download this? because I installed W2K8 core and it's not there.
I checked on the full install of W2K8R2 and it's not there either.
Did a search of the C: drives. No SCONFIG.
Impressive.....looks like we went back to the time when we wrote BATCH files like "echo 1. Supaplex" and then make 1.bat to actually start the game....
Impressive tool ppl.....Nice touch....
Mark did you find sconfig? I installed win2k8 server R2 Core and wasnt able to find sconfig either.
It works on my 2008 R2 Core server but not on a 2008 R2 Full server.
Certainly makes things easier and quicker.
Oh really.. There is no need for reboot after server rename..