|
|
| 第 27 行: |
第 27 行: |
| Windows Server 2008 的客户端版本,即 Windows Vista,最初是打算作为一个仅限于客户端的次要版本,它将在 Windows Server 2003(当时称为 Windows .NET Server)和下一代操作系统(当时的代号为 Blackcomb)之间提供,但最终,Longhorn 被提升为一个主要版本,此版本将同时提供客户端和服务器版本。到 2004 年,预测 Longhorn 客户端将在 2006 年发布,Longhorn Server 将在一年后发布,与 Longhorn SP1 一致。 | | Windows Server 2008 的客户端版本,即 Windows Vista,最初是打算作为一个仅限于客户端的次要版本,它将在 Windows Server 2003(当时称为 Windows .NET Server)和下一代操作系统(当时的代号为 Blackcomb)之间提供,但最终,Longhorn 被提升为一个主要版本,此版本将同时提供客户端和服务器版本。到 2004 年,预测 Longhorn 客户端将在 2006 年发布,Longhorn Server 将在一年后发布,与 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.在 2004 年 8 月开发重置之前,人们对 Microsoft 的 Longhorn Server 计划知之甚少,因为他们没有过多谈论它。服务器市场的本质是升级周期与工作站不同,且负责 Windows Server 功能的团队仍然专注于 Windows Server 2003(以及更高的 Windows Server 2003 R2)。目前拥有的泄露的重置前 Longhorn Server 版本似乎与 Longhorn 的客户端版本基本相同,只是使用 Server 的 SKU 版本品牌,以及直接从 Windows Server 2003 中提取的应用程序/功能(如IIS),这表明操作系统的服务器组件尚未进行开发。因此,人们可能会推测,在其中一些版本编译时,Longhorn Server 仍然不是一个严肃的项目,但从 Build 4031(2003 年 7 月)来自专用于 IIS 的内部版本实验室这一事实来看,Longhorn Server 开发可能已经开始,但不是 Longhorn 或 Windows Server 组的优先事项。
| | 在 2004 年 8 月开发重置之前,人们对 Microsoft 的 Longhorn Server 计划知之甚少,因为他们没有过多谈论它。服务器市场的本质是升级周期与工作站不同,且负责 Windows Server 功能的团队仍然专注于 Windows Server 2003(以及更高的 Windows Server 2003 R2)。目前拥有的泄露的重置前 Longhorn Server 版本似乎与 Longhorn 的客户端版本基本相同,只是使用 Server 的 SKU 版本品牌,以及直接从 Windows Server 2003 中提取的应用程序/功能(如IIS),这表明操作系统的服务器组件尚未进行开发。因此,人们可能会推测,在其中一些版本编译时,Longhorn Server 仍然不是一个严肃的项目,但从 Build 4031(2003 年 7 月)来自专用于 IIS 的内部版本实验室这一事实来看,Longhorn Server 开发可能已经开始,但不是 Longhorn 或 Windows Server 组的优先事项。 |
|
| |
|
| 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.
| | 在开发重置后,在向技术采用计划(TAP)合作伙伴发布的 Beta 1(Build 5112)之前,没有泄露 Longhorn Server 的版本,但已在网上看到 Longhorn Server 的两个版本,即 [[Windows Server 2008 Build 5077.0.vbl_core_setup.050530-1400|Build 5077]](2005 年 5 月)和 [[Windows Server 2008 Build 5085.0.vbl_srv.050610-2000|5085]](2005 年 6 月)。5077 在初始配置任务小程序上除了 Windows Server“Longhorn”品牌外没有其他值得注意的内容(Longhorn Server 的重置前版本通常使用 Windows Server 2003 或 Windows .Net Server 位图进行品牌推广),但 5085 显示了 Longhorn Server 的主要功能之一,即 Server Core(当时称为 Windows Server Foundation),它拥有精简的操作系统,没有资源管理器 shell。由于 Server Core 依赖于 Longhorn 的组件化,因此在重置前很可能一直处于规划阶段,但由于当时 Microsoft 的混乱,直到重置后才成为现实。 |
|
| |
|
| 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.
| | 随着 Windows Longhorn Server 开发的继续,重点也转移到了另一个新功能上,Windows Server Virtualization(Windows Server 虚拟化),代号为 Viridian,首次在 WinHEC 2006 上展示。与 Virtual Server 2005 相比,Viridian 的主要优势之一是支持 64 位来宾操作系统。Viridian 没有随 Windows Server 2008 的 RTM 版本一起提供(正如预测的那样,它与 Vista SP1 的代码相同),但后来确实作为 Hyper-V 提供。Windows Server 2008 发布后,它和 Windows Vista 使用相同的更新,包括 Service Pack 2 和 Platform Update(平台更新),重新统一了 Windows 的客户端和服务器代码库。 |
|
| |
|
| == 命名 == | | == 命名 == |