In a nutshell Microsoft's Windows Server 2008 is more forgiving then W2K3, in particular
it
requires less work to install and configure the server's role on the network. I hope
that you enjoy exploring the new 'Longhorn' features as much as I did.
Hyper-V Windows Server 2008 introduces Hyper-V (V for Virtualization) but only
on 64bit versions. More and more companies are seeing this as a way of
reducing hardware costs by running
several 'virtual' servers on one physical machine. If you like this
exciting technology, make sure that you buy an edition of Windows Server 2008
that includes Hyper-V, then launch the Server Manger, add Roles.
64bit
The five years between W2K3 and Windows Server 2008 is a relatively long time in computing. Perhaps the
64bit verses 32bit
debate is a good bellwether for the changes. In W2K3 most servers were
32bit with 64bit an option, whereas for Windows Server 2008 almost all servers will be
64bit.
Another trend in the Microsoft Windows family of servers has been improved scalability,
the desire to take on jobs previously associated with main-frame computers.
For this high-end role, Windows Server 2008 has better support for failover
clustering than W2K3.
Windows Server 2008 with Vista
Even though servers have always been more secure, and less flashy, than clients
like Vista,
Microsoft have made security their number one priority for Windows Server 2008.
To gain maximum benefits I have always preached match clients and server, thus
XP and W2K3, and now, match Windows Server 2008 with Vista. Perhaps the killer
reason for the latter association is DHCPv6 and IPv6. At present Windows
Server 2003 does not support DHCP for IPv6.
Because Windows Server 2008 gains in speed, efficiency and security over W2K3, so
there will be knock-on improvements for their clients, particularly for Vista.
Talking of Vista, features such as NAP (Network Access Protection), BitLocker and UAC are as relevant for Windows
Server 2008 as they are for Vista.
Group Policy Preferences W2K3 Group Policies are great, especially if you want to tattoo
settings and enforce a corporate desktop. Windows Server 2008 introduces
an additional or parallel idea; you set the initial preference, but allow uses
to amend these less critical settings. Take the time to review Group
Policy Preferences.
PowerShell
Although Microsoft have created more GUIs than ever, it is perceived to be quicker, to configure
Windows Server 2008 from the command line using PowerShell. The vision behind PowerShell is to provide cmdlets
(scripts) which automate repetitive tasks, much like UNIX administrators use
BASH in their UNIX shells.
Guy Recommends: The Orion Network Performance Monitor (NPM) 9.5
Orion's performance monitor is designed for detecting network outages.
This NPM will guide you
through troubleshooting by indicating whether the root cause is a broken link,
faulty equipment or resource overload. Because it produces
network-centric views, it is intuitive to navigate, and as result you can
see easily what's working and what's not.
Perhaps Orion's best feature is the way it suggests solutions. Moreover, if
problems arise out of the blue, then you can configure Orion NPM 9.5 to notify
members of your team what's changed and how to fix it.
Review of New Technologies Related to
Microsoft's Windows Server 2008
Here are code words which became more recognisable features of Windows Server
2008. Else they were part of a project, which has been abandoned or placed on the
back-burner.
(Here is a page is to help those whose typing
fingers are slightly dyslexic - Windows Sever 2008)
Train Signal has
now released their
Windows Server 2008 Training Course. As an MCT
trainer, I am a huge advocate of Train Signals products. What particularly
impresses is me is the demonstrations. If
you are looking for a complete DETAILED coverage of Windows Server 2008, then I highly recommend that you give this course a try. I have reviewed their
6 hours plus of videos myself, and I guarantee that you will
not be disappointed!