On Feb 6, 2008 2:46 PM, Mike Cunningham <mcunning@xxxxxxx> wrote:
Did Microsoft/Windows just take a step towards the i5/OS model?
The "server runs no GUI" isn't i5/OS specific. Every Unix out there
does the same. The only two Server OS that have shipped with a GUI as
the "normal" way to administrate was Windows and OS X Server.
Don't waste server CPU cycles providing a GUI to just server admins.
Offload that to a client PC running something like iSeries Navigator and just provide a command line interface in the server itself. What a revolutionary idea!
Interactive work on the server using RDP isn't required for day-to-day
tasks. Most Windows Server utilities can be installed on any
Workstation and be used to administrate a server much like iSeries
Navigator. For Windows Server 2003, adminpak.msi was used for this
task. It connected to the Server using RPC and allows you to configure
almost everything. This is what is usually used in larger,
professional Windows deployments to administrative Servers.
Windows Server Core is mostly about reducing the attack surface by
running a very stripped down version of Windows. Server Core is
perfect for running infrastructure services like Domain Controllers,
WINS Servers, DNS Servers, Fileservers, Static Webservers, etc.
Windows Server Core does not support the .NET Framework, a step which
i would describe as "questionable" or "WTF were they thinking?". As
such, many applications do not run on Windows Server Core. One of
these applications is Microsoft PowerShell, which is the new
commandline and scripting language to be used.
There is one other thing that Windows Server Core was designed to be:
The OS hosting the primary partition when using Hyper-V (which is
Microsoft's new Hypervisor based Virtualization Solution, similar to
Vmware GSX).
midrange.com
