A look forward to Windows Server 2008

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

This evening, I’m planning to be at the inaugural Windows Server UK user group meeting, prompting me to write up my notes from the Windows Server 2008 Technical Overview event held at Microsoft UK last month. Presented by Andy Malone from Quality Training, I’ve already given my (negative, but hopefully constructive) feedback to Microsoft on this event (so I won’t dwell here on why I thought it was so bad – although the presenter seems to think that it went rather well…) but I did at least manage to glean some information about the latest Windows Server release – what follows picks out some of the highlights.

Windows Server 2008 logoFormerly codenamed Longhorn Server, Windows Server 2008 shares a common code base with Windows Vista and, not surprisingly, Microsoft is touting it as the most secure and highest quality version of Windows ever produced.

The first change is the setup; with three distinct phases of:

  • Setup (product installation).
  • Server welcome (initial configuration) – except in upgrades.
  • Role configuration and management.

Whilst looking at deployment, it’s worth mentioning that remote installation services (RIS) has been replaced by Windows Deployment Services (actually, this is also available with Windows Server 2003 SP2) which, unlike ADS, supports client and server operating systems as well as multicast deployment.

Windows Server 2008 also pulls much of the administration into one console – Server Manager (which made me smile, casting my mind back to the old Windows NT Server Manager console). There are some new component concepts to get around – components are now known as roles and features but more significant is Windows Server Core, an installation option consisting of a subset of executable files and libraries, providing a small footprint for a much reduced attack surface. Offering a number of server roles, Server Core provides core functionality in either a standalone (e.g. headless) scenario or as part of a larger Windows Server infrastructure. There are no GUI tools for Server Core – management is via command line tools (local and remote), terminal services (remote) or Microsoft Management Console (MMC) snap-ins (remote). Server core is an installation-time choice (there is no option to convert to a standard installation later) and Server Core will not support application installations (such as SQL Server, Exchange Server, etc.) but I can see it being very useful for running core infrastructure (AD, DNS, DHCP, etc.) servers in a secure fashion.

Other security features (some of which are already present in Windows Vista) include support for the trusted platform module, BitLocker drive encryption, a redesigned TCP/IP stack with native support for IPv6 (alongside IPv4), the updated Windows firewall, new Group Policy settings and Windows Service hardening whereby services run in their own address space and a number of layers are used to separate the kernel, service, administration, user and low-rights program layers. Windows Server 2008 will also (finally) see Microsoft introduce network access protection (NAP).

Some network features are being removed from Windows Server: the file replication service (FRS) is replaced by remote differential compression (RDC); bandwidth allocation protocol (BAP) is out, as is X.25 support, serial line interface protocol (SLIP) support, and services for Macintosh (SFM); there are also a number of changes to routing and remote access with the removal of open shortest path first (OSPF), the basic firewall and static IP filter APIs.

Terminal Services gains new functionality too – including a version 6 of the remote desktop protocol (RDP) and:

  • Terminal Service Gateway – providing RDP over HTTPS support for remote access to corporate applications.
  • Terminal Service Remote Programs – centralised management of line of business applications on a roaming basis, integrated with Terminal Service Web Access.
  • Single sign-on for managed clients.

At least in the beta product, Active Directory sees a number of name changes – some of which make sense and others which seem be be inteded just to cause confusion:

Old name New name
Active Directory Active Directory Domain Services
Active Directory Application Mode (ADAM) Active Directory Lightweight Directory
Windows Rights Management Active Directory Rights Management
Windows Certificate Services Active Directory Certificate Services
Identity Integration Feature Pack Active Directory Metadirectory

(I fully expect at least some of these to change again before product release!)

There are some Active Directory goodies too:

  • Backup domain controllers (BDCs) are back! Except that now they are called read-only domain controllers (with unidirectional replication to offer credential caching and whilst increasing the physical security of remote domain controllers, e.g. in branch offices).
  • dcpromo.exe now supports Server Core (i.e. it will run in command line mode), uses the logged on credentials for promotion and allows the seed method to be chosen (e.g. populate from a specific server offering Active Directory domain services), enables site selection (with automatic detection), provides automatic DNS configuration (for resolvers and delegation), and allows role selection for DNS (on by default), global catalog (on by default) and read-only domain controllers.
  • Active Directory can be restarted without rebooting (e.g. to run ntdsutil.exe with the server online, just stopping and restarting Active Directory services).
  • An attribute editor is available in the Active Directory Users and Computers snap-in with advanced features enabled, avoiding the need to use the ADSIedit support tool.

Of course, Internet Information Services (IIS) gets an overhaul and the new IIS version 7 features a much-improved (MMC v3) administrative interface (as well as application and architectural enhancements). Windows Server 2008 also gains improved Unix interoperability features with authentication integration, Unix scripting and application migration tools, support for both 32 and 64-bit applications and extensions to the AD schema to support UNIX-related attributes (using LDAP as a NIS service – see RFC 2307). Clustering is also improved with a new MMC v3 management interface, enhanced infrastructure (e.g. support for graphically dispersed clusters and for GUID partition table disks in cluster storage) and improved security.

Before I wrap up, I’ll mention that there is a lot of misinformation circulating around Windows Server Virtualization (WSV). WSV is not part of Windows Server 2008 but it has been announced that it will ship as a separate product within 180 days of Windows Server 2008. Some features were recently cut from the initial release (Microsoft prefers to use the term postponed) and may make it into a future service pack or other update.

As one might guess from the name Windows Server 2008, the product looks set to be released late in 2007. Looking further out at the Windows Server roadmap, we can expect a 64-bit only “release 2” in late 2009 and the next major release in 2011. It looks to me as if there’s a lot of good features in Windows Server 2008 – watch this space to learn more just as fast as I do!

Introducing Windows Server 2008

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Windows Server 2008 logoWhen I logged on to the Microsoft Connect site this morning, I noticed that the beta program for Windows Server codenamed Longhorn has been renamed… it seems that I should have checked in on more details from Bill Gates’ WinHEC keynote, where he announced that the product will be called Windows Server 2008 (no surprises there then).  Actually, dull as it sounds, I think that’s the right name - it’s clear and unambiguous (although I expect the product bundling will be confusing as always).

Why Windows Vista was codenamed “Longhorn”

This content is 18 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Blog posts have been a bit thin on the ground recently – between work and home (new baby + toddler = full days / short nights) I’ve not had much time. Even rarer recently has been anything Microsoft-related – apologies, normal service will be resumed shortly – although short of reporting the news (long awaited release of Windows Defender, impending Windows Media 11 release), which is better left to the likes of Paul Thurrott, there’s not been a lot to say as Microsoft UK events have also been a bit sparse – presumably waiting on the Windows Vista release. Talking of the infamously delayed operating system it should be here very soon… one rumoured release to manufacturing (RTM) date of 27 October has now passed but 8 November is another date I’ve heard… so I’m about a month out with my competition entry… I should have stuck with my original instinctive answer!

On the way to work this morning, I was listening to Leo Laporte and Paul Thurrott discuss Windows Vista on the Windows Weekly podcast and was amused to hear where the codename for Windows Vista (Longhorn) came from… quoting from the SuperSite for Windows Windows Longhorn FAQ:

“Remember that Windows XP was code-named Whistler and the next version of Windows, at the time, was code-named Blackcomb. Both of these names come from ski areas in British Columbia, close to Microsoft’s headquarters. At the foot of Whistler Mountain, there is a saloon named Longhorn that serves the local skiing population.”

So, the theory was that you can’t get from Whistler to Blackcomb without passing Longhorn… hence the name for the new operating system version, which was originally planned as a minor release, but soon became a major upgrade.

Microsoft beta madness

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Talk about confusing… the long overdue Windows Vista beta 2 (not a community technology preview but a real beta release) has widely been expected to ship this week and yesterday, Bill Gates announced that beta 2 versions of Windows Vista, Windows Server (codenamed Longhorn) and Office 2007 are available.

The betas are ready! Office

Indeed, late last night I received an e-mail inviting me to download beta 2 of Office 2007 but strangely it said that “The Windows Vista Beta is not yet available. The Beta Experience newsletter will inform you about the availability of the Windows Vista Beta”. Vista beta 2 (build 5384) is clearly available for download from Microsoft Connect but, as usual, the product groups don’t seem to be talking to one another.

x64 finally comes of age

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

To be honest, I got a bit confused with the various 64-bit CPUs (like why didn’t Intel and HP’s Itanium take off, but AMD’s AMD64 did and Itanium 2 looks like it will too), but whatever the hardware issues, it seems that x64 software has finally come of age. Paul Thurrott reports in his Windows IT Pro magazine network WinInfo Daily Update that, at the IT Forum this week, Microsoft announced that the Longhorn Server wave of products will be 64-bit only (except Longhorn Server itself, which will be available in both 32- and 64-bit flavours). That means that, for example, the next version of Exchange Server (codenamed Exchange 12) will only run on a 64-bit platform. There’s no news yet as to what is happening on the desktop (except that it seems, like Windows XP, Windows Vista will be available in both 32- and 64-bit editions) but it looks like I’d better get saving for a new PC…

Bad timing…

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

For the last couple of days, the Microsoft File Transfer Manager has been running on one of my PCs, downloading 5.33Gb of Windows code name “Longhorn” and IE7 beta software from Microsoft Connect (averaging out at about 65kbps). Sometime last night, it all finally completed but then a few minutes ago, DHL delivered a package from Microsoft in Redmond containing… you guessed it… bootable DVDs of Windows Vista Professional Beta 1 and Windows Code Name “Longhorn” Beta 1. Arghhhhh!!!

Windows Vista only a replacement for XP – Windows Server is still codenamed Longhorn

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few days back, I commented on Microsoft’s announcement of Windows Vista (formerly codenamed Longhorn), speculating as to whether this new name included the next generation Windows server product. It seems not, at least according to the Microsoft Windows Vista Beta 1 fact sheet.

I’m one of the 10,000 beta testers for Windows Vista (not a particularly exclusive club I know…) as well as Longhorn Server and Internet Explorer 7 so I guess I’ll blog some more about Vista after I’ve used it for a while – in the meantime Paul Thurrott has a Vista FAQ on his SuperSite for Windows.

No NAP until Longhorn

This content is 20 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last year I commented that network access protection (NAP) had slipped from a planned feature pack for ISA Server 2004 to Windows Server 2003 Release 2 (R2). Well, it seems that has changed. Confirming what I wrote last March, when I blogged about the need for network segmentation and remediation, Steve Lamb commented at last week’s Microsoft Technical Roadshow that NAP will be a feature of the next version of Windows Server (codenamed Longhorn) and not in the R2 release scheduled for later this year.

Apparently the reasons for this are that NAP will require kernel mode changes (and there will be no kernel mode changes in R2) and the extra time will allow Microsoft and Cisco to ensure that NAP (Microsoft) and NAC (Cisco) play nicely together.

Until then we will have to make do with the network access quarantine controls (originally part of the Windows Server 2003 resource kit and productionised as part of the release of Windows Server 2003 service pack 1). The main differences are that network access quarantine control allows quarantining of inbound connections via the Windows routing and remote access service, but NAP will will support quarantine for wired and wireless LAN connections too.

A chance to provide input to some networking features that Microsoft is considering for Windows Longhorn

This content is 20 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Michael Surkan, Microsoft’s Program Manager for Networking and Devices, has asked me to post a link to his survey to gain customer input on some networking features Microsoft is considering in the next version of Windows (codenamed Longhorn):

“The Microsoft network product team is investigating ways of resolving peer-to-peer connectivity problems in Longhorn, and we would like to get customer feedback to help validate some of the design proposals.

Today, there are many situations where users are unable to run such functions as remote assistance, voice/video conversations, and many other peer-to-peer functions because of firewalls, NATs and other network configuration problems. Our goal is to build networking technology into the operating system that will overcome many of these problems, allowing these peer-to-peer scenarios to ‘just work’.

This survey outlines some of the proposals for resolving these connectivity problems, and asks for feedback on them. We would love to get the opinions from a wide range of users, and markets (e.g. consumers, large IT departments, etc) since this would have implications for everyone.”