"Fewer installed features means fewer features to patch and maintain. Server Core has been available since Windows Server 2008, and historically we've noted as much as 35-45% fewer patches needed on Server Core installations!"

Additionally, Server Core requires less reboots after patching because the files being patched aren't necessarily in use.

It should motivate those that aren't already, to start running server core when possible. Plus, it makes the whole hate the new GUI argument invalid. ;)

I read a quote in a Linux book once, "Going from GUI to Command Line is like graduating from picture books to novels." Get to reading...

5 Replies

Running Hyper-V Server 2012 now with corefig v1.1.1 and one of my two DC's will be converted to what I like to call quasi core (gui features removed from full installation). Updates are super fast and most so far haven't required a reboot from what I have seen.

Corefig is the bomb, there's another similar product out there but it's like $100 and I think it runs mostly ps scripts as HTA's anyways.

I wish I could have found this tool a year or so ago when I had a problem with a 2008 R2 core w/ Hyper-v server. Would have saved me a couple of hours worth of network reconfig, and VM troubleshooting.

I have to agree; but I suspect that there are a lot of sysadmins that still haven't started working with PowerShell and they would be very reluctant to start working in that way.

I was talking to someone recently and it was clear from their response to my comments on Server 2012 that they have made absolutely no progress towards using the CLI; and at this stage have no plans to do so. (I'm not sure that they have even considered it; one of their key staff managing servers didn't even know what I was talking about)

Just feeling a bit grumpy this morning; very frustrated at what I see as too many companies with the wrong strategy, the wrong people and no understanding of just how much better they could be if they had the right leadership.

I started tinkering with powershell 1.0 way back but didn't really find too many resources at the time that helped me understand it so I passed on it a little. It wasn't until 2.0 and a couple of years ago that I got back into powershell and trying to use it more. Just last night I was working on a couple of new 2012 servers I had to join to a domain, instead of doing the old way, I ran get-help add-computer -examples | more and added two of them to the domain that way. To me tasks like that are the best way to get acquainted with cmdlets and their usage.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.