Windows Server 2008：修订间差异
跳转到导航
跳转到搜索
→命名
（→Beta 2） |
正义羊-JRJSheep（讨论 | 贡献） （→命名） |
||
| 第 22 行： | 第 22 行： | ||
Windows Server 2008 放弃了从 [[Windows Server 2003]]/[[Windows Server 2003 R2|2003 R2]] 及其 x64 版本之前的版本升级的功能。 | Windows Server 2008 放弃了从 [[Windows Server 2003]]/[[Windows Server 2003 R2|2003 R2]] 及其 x64 版本之前的版本升级的功能。 | ||
== Development history == | |||
Windows Server 2008's client counterpart, Windows Vista, was initially intended to be a minor client-only release that would ship in-between Windows Server 2003 (then known as Windows .NET Server) and the next-generation operating system, then codenamed Blackcomb, but eventually, Longhorn was promoted to a major release that would ship in both client and server releases. By 2004, it was predicted that Longhorn client would ship in 2006 with Longhorn Server shipping a year later, in line with Longhorn SP1. | |||
Little is known about Microsoft's plans for Longhorn Server before the August 2004 development reset, as they didn't speak much about it. The nature of the server market is that upgrade cycles are different than on workstations, and the team that works on features for Windows Server was still focused on Windows Server 2003 (and later Windows Server 2003 R2). The leaked builds that we have of pre-reset Longhorn Server essentially seem to be identical to client versions of Longhorn, merely with the edition branding of Server, and applications/features such as IIS lifted straight from Windows Server 2003, suggesting that development on the server components of the OS had yet to take place. One may speculate as a result of this that at the time of some of these builds, Longhorn Server was still not a serious project, but judging by the fact that build 4031 (July 2003) comes from the build lab dedicated to IIS, it is likely that Longhorn Server development had started, but was not a priority among either the Longhorn or Windows Server groups. | |||
After the development reset, no builds of Longhorn Server are leaked until Beta 1 (build 5112), which was released to Technical Adoption Program (TAP) partners, but two builds of Longhorn Server have been seen online, namely [[Windows Server 2008 build 5077|build 5077]] (May 2005) and [[Windows Server 2008 build 5085|5085]] (June 2005). 5077 shows nothing notable other than Windows Server "Longhorn" branding over the Initial Configuration Tasks applet (pre-reset builds of Longhorn Server typically used either Windows Server 2003 or Windows .Net Server bitmaps for branding purposes), but 5085 shows one of the headline features of Longhorn Server, namely Server Core (then known as Windows Server Foundation), which features a slimmed-down OS with no Explorer shell. Since Server Core depends on Longhorn's componentization, it's likely to have been in the planning stages before the reset, but thanks to the chaos in Microsoft at the time, didn't become a reality until after. | |||
As Windows Longhorn Server development continued, focus shifted as well to another new feature, Windows Server Virtualization, code-named Viridian, first shown at WinHEC 2006. One of Viridian's main advantages over Virtual Server 2005 was support for 64-bit guest operating systems. Viridian did not ship with the RTM build of Windows Server 2008 (which was, as predicted, the same code as Vista SP1), but did become available later as Hyper-V. After Windows Server 2008 released, it and Windows Vista used the same updates, including Service Pack 2 and the Platform Update, reunifying the client and server codebases for Windows. | |||
== 命名 == | == 命名 == | ||