Windows 2003 server 32 bit количество поддерживаемой памяти

Screenshot of Windows Server 2003, showing the Server Manager application which is automatically opened when an administrator logs on
Windows Server 2003

Version of the Windows NT operating system
Windows Server 2003 Logo and Wordmark.png
Windows Server 2003.png

Screenshot of Windows Server 2003, showing the Server Manager application which is automatically opened when an administrator logs on
Developer Microsoft
OS family Microsoft Windows
Working state No longer supported
Source model
  • Closed-source
  • Source-available (through Shared Source Initiative)
Released to
manufacturing		 March 28, 2003; 19 years ago[1]
General
availability		 April 24, 2003; 19 years ago[2]
Latest release Service Pack 2 (5.2.3790.3959) / March 13, 2007; 15 years ago[3]
Marketing target Business and Server
Update method Windows Update
Platforms IA-32, x86-64, Itanium
Kernel type Hybrid (Windows NT kernel)
Default
user interface		 Windows shell (Graphical)
License Trialware[4] and volume licensing,[5] with client access licenses[6]
Preceded by Windows 2000 Server (1999)
Succeeded by Windows Server 2008 (2008)
Official website Windows Server 2003
Support status
All editions except Windows Storage Server 2003 and Windows Small Business Server 2003 (including R2):
Mainstream support ended on July 13, 2010
Extended support ended on July 14, 2015[7][8][9]
Windows Storage Server 2003 (including R2):
Mainstream support ended on October 11, 2011
Extended support ended on October 9, 2016[10][11]
Windows Small Business Server 2003 (including R2):

Mainstream support ended on April 12, 2011
Extended support ended on April 12, 2016[12][13]

Installing a Service Pack is Required for Continued Support after April 10, 2007[14]

Windows Server 2003 is the sixth version of Windows Server operating system produced by Microsoft. It is part of the Windows NT family of operating systems and was released to manufacturing on March 28, 2003[15] and generally available on April 24, 2003.[16] Windows Server 2003 is the successor to the Server editions of Windows 2000 and the predecessor to Windows Server 2008.[17][18] An updated version, Windows Server 2003 R2, was released to manufacturing on December 6, 2005.[19] Windows Server 2003 is based on the consumer operating system, Windows XP.[20]

Windows Server 2003’s kernel has also been used in Windows XP 64-bit Edition and Windows XP Professional x64 Edition, and was the starting point for the development of Windows Vista.[21]

Overview[edit]

Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000, Windows Server 2003’s default installation has none of the server components enabled, to reduce the attack surface of new machines. Windows Server 2003 includes compatibility modes to allow older applications to run with greater stability. It was made more compatible with Windows NT 4.0 domain-based networking. Windows Server 2003 brought in enhanced Active Directory compatibility and better deployment support to ease the transition from Windows NT 4.0 to Windows Server 2003 and Windows XP Professional.[22]

Windows Server 2003 is the first server edition of Windows to support the IA64 and x64 architectures.[23]

The product went through several name changes during the course of development. When first announced in 2000, it was known by its codename «Whistler Server»; it was named «Windows 2002 Server» for a brief time in mid-2001, followed by «Windows .NET Server» and «Windows .NET Server 2003». After Microsoft chose to focus the «.NET» branding on the .NET Framework, the OS was finally released as «Windows Server 2003».[24]

Development[edit]

Windows Server 2003 was the first Microsoft Windows version which was thoroughly subjected to semi-automated testing for bugs with a software system called PREfast[25] developed by computer scientist Amitabh Srivastava at Microsoft Research.[26] The automated bug checking system was first tested on Windows 2000 but not thoroughly.[25] Amitabh Srivastava’s PREfast found 12% of Windows Server 2003’s bugs, the remaining 88% being found by human computer programmers.[25] Microsoft employs more than 4,700 programmers who work on Windows, 60% of whom are software testers[26] whose job is to find bugs in Windows source code. Microsoft co-founder Bill Gates stated that Windows Server 2003 was Microsoft’s «most rigorously tested software to date.»[26]

Microsoft used Windows Server 2003’s kernel in the development of Windows Vista.[21]

Changes[edit]

Several improvements and new features have been added to Windows Server 2003.

Internet Information Services (IIS) has been upgraded to v6.0.[27]There have also been significant improvements to Message Queuing and to Active Directory, such as the ability to deactivate classes from the schema, or to run multiple instances of the directory server (ADAM).[28] There was also a notable change in the ability to create a rescue disk, which was removed in favor of Automated System Recovery (ASR).[29]Other Improvements to Group Policy handling and administration[30] have also been made. For the first time in the history of Windows Server, a backup system to restore lost files has been created[31] together with improved disk management, including the ability to back up from shadows of files, allowing the backup of open files.[32]Another important area where improvements have been made are the scripting and command line tools, with the improvements being part of Microsoft’s initiative to bring a complete command shell to the next version of Windows.[33] Other notable new features include support for a hardware-based «watchdog timer», which can restart the server if the operating system does not respond within a certain amount of time.[34] On this version of Windows Server the Themes service is disabled by default, defaulting to the appearance of previous Windows versions (such as Windows 2000).[35]

Editions[edit]

Windows Server 2003 comes in a number of editions, each targeted towards a particular size and type of business.[36][37] In general, all variants of Windows Server 2003 have the ability to share files and printers, act as an application server, host message queues, provide email services, authenticate users, act as an X.509 certificate server, provide LDAP directory services, serve streaming media, and to perform other server-oriented functions.[38][39][40][41]

Supported hardware capabilities across editions of Windows Server 2003[42]

Criteria Web Standard Enterprise Datacenter
Maximum physical CPUs 2 4 8 64
Maximum RAM IA-32 x86 2 GB 4 GB 64 GB
x64 — 32 GB 1 TB
IA-64 Itanium — — 2 TB

Web[edit]

Windows Server 2003 Web is meant for building and hosting Web applications, Web pages, and XML web services. It is designed to be used primarily as an IIS web server[43] and provides a platform for developing and deploying XML Web services and applications that use ASP.NET technology. Domain controller and Terminal Services functionality are not included on Web Edition. However, Remote Desktop for Administration is available. Only 10 concurrent file-sharing connections are allowed at any moment.[citation needed] It is not possible to install Microsoft SQL Server and Microsoft Exchange software in this edition without installing Service Pack 1[citation needed]. Despite supporting XML Web services and ASP.NET, UDDI cannot be deployed on Windows Server 2003 Web[citation needed]. The .NET Framework version 2.0 is not included with Windows Server 2003 Web, but can be installed as a separate update from Windows Update.[citation needed]

Windows Server 2003 Web supports a maximum of 2 physical processors and a maximum of 2 GB of RAM.[42] It is the only edition of Windows Server 2003 that does not require any client access license (CAL) when used as the internet facing server front-end for Internet Information Services and Windows Server Update Services. When using it for storage or as a back-end with another remote server as the front-end, CALs may still be required.[43][clarification needed]

Standard[edit]

Microsoft Windows Server 2003 Standard is aimed towards small to medium-sized businesses. Standard Edition supports file and printer sharing, offers secure Internet connectivity, and allows centralized desktop application deployment. A specialized variant for the x64 architecture was released in April 2005.[44] The IA-32 variants supports up to four physical processors and up to 4 GB RAM;[42] the x64 variant is capable of addressing up to 32 GB of RAM[42] and also supports Non-Uniform Memory Access.

Enterprise[edit]

Windows Server 2003 Enterprise is aimed towards medium to large businesses. It is a full-function server operating system that supports up to 8 physical processors and provides enterprise-class features such as eight-node clustering using Microsoft Cluster Server (MSCS) software and support for up to 64 GB of RAM through PAE.[42] Enterprise Edition also comes in specialized variants for the x64 and Itanium architectures. With Service Pack 2 installed, the x64 and Itanium variants are capable of addressing up to 1 TB and 2 TB of RAM,[42] respectively. This edition also supports Non-Uniform Memory Access (NUMA). It also provides the ability to hot-add supported hardware. Windows Server 2003 Enterprise is also the required edition to issue custom certificate templates.[citation needed]

Datacenter[edit]

Windows Server 2003 Datacenter is designed[45] for infrastructures demanding high security and reliability. Windows Server 2003 is available for IA-32, Itanium, and x64 processors. It supports a maximum of 32 physical processors on IA-32 platform or 64 physical processors on x64 and IA-64 hardware. IA-32 variants of this edition support up to 64 GB of RAM.[42] With Service Pack 2 installed, the x64 variants support up to 1 TB while the IA-64 variants support up to 2 TB of RAM.[42] Windows Server 2003 Datacenter also allows limiting processor and memory usage on a per-application basis.

This edition has better support for storage area networks (SANs): It features a service which uses Windows sockets to emulate TCP/IP communication over native SAN service providers, thereby allowing a SAN to be accessed over any TCP/IP channel. With this, any application that can communicate over TCP/IP can use a SAN, without any modification to the application.[citation needed]

The Datacenter edition, like the Enterprise edition, supports 8-node clustering.[citation needed] Clustering increases availability and fault tolerance of server installations by distributing and replicating the service among many servers. This edition supports clustering with each cluster having its own dedicated storage, or with all cluster nodes connected to a common SAN.

Derivatives[edit]

Windows Compute Cluster Server[edit]

Windows Compute Cluster Server 2003 (CCS), released in June 2006, is designed for high-end applications that require high performance computing clusters. It is designed to be deployed on numerous computers to be clustered together to achieve supercomputing speeds. Each Compute Cluster Server network comprises at least one controlling head node and subordinate processing nodes that carry out most of the work.[46]

Compute Cluster Server has a built-in Message Passing Interface, the Microsoft Messaging Passing Interface v2 (MS-MPI) which is used to communicate between the processing nodes on the cluster network. Alternative MPI Stacks can also be used with the OS. [47]It ties nodes together with a powerful inter-process communication mechanism which can be complex because of communications between hundreds or even thousands of processors working in parallel.

The application programming interface consists of over 160 functions. A job launcher enables users to execute jobs to be executed in the computing cluster. MS MPI was designed to be compatible with the reference open source MPI2 specification which is widely used in High-performance computing (HPC). With some exceptions because of security considerations, MS MPI covers the complete set of MPI2 functionality as implemented in MPICH2, except for the planned future features of dynamic process spawn and publishing.[48]

Windows Storage Server[edit]

Windows Storage Server 2003, a part of the Windows Server 2003 series, is a specialized server operating system for network-attached storage (NAS).[49] Launched in 2003 at Storage Decisions in Chicago, it is optimized for use in file and print sharing and also in storage area network (SAN) scenarios. It is only available through Original equipment manufacturers (OEMs).[50] Unlike other Windows Server 2003 editions that provide file and printer sharing functionality, Windows Storage Server 2003 does not require any CAL.[51]

Windows Storage Server 2003 NAS equipment can be headless, which means that they are without any monitors, keyboards or mice, and are administered remotely.[52] Such devices are plugged into any existing IP network and the storage capacity is available to all users. Windows Storage Server 2003 can use RAID arrays to provide data redundancy, fault-tolerance and high performance.[53] Multiple such NAS servers can be clustered to appear as a single device, which allows responsibility for serving clients to be shared in such a way that if one server fails then other servers can take over (often termed a failover) which also improves fault-tolerance.[54]

Windows Storage Server 2003 can also be used to create a Storage Area Network, in which the data is transferred in terms of chunks rather than files, thus providing more granularity to the data that can be transferred. This provides higher performance to database and transaction processing applications. Windows Storage Server 2003 also allows NAS devices to be connected to a SAN.[citation needed]

Windows Storage Server 2003 led to a second release named Windows Storage Server 2003 R2. This release adds file-server performance optimization, Single Instance Storage (SIS), and index-based search. Single instance storage (SIS) scans storage volumes for duplicate files, and moves the duplicate files to the common SIS store. The file on the volume is replaced with a link to the file. This substitution reduces the amount of storage space required, by as much as 70%.[55]

Windows Storage Server 2003 R2 provides an index-based, full-text search based on the indexing engine already built into Windows server.[55] The updated search engine speeds up indexed searches on network shares. This edition also provides filters for searching many standard file formats, such as ZIP archives, AutoCAD models, XML documents, MP3 audio files, PDF documents, and all Microsoft Office file formats.

Windows Storage Server 2003 R2 includes built in support for Windows SharePoint Services and Microsoft SharePoint Portal Server, and adds a Storage Management snap-in for the Microsoft Management Console. It can be used to manage storage volumes centrally, including DFS shares, on servers running Windows Storage Server R2.

Windows Storage Server 2003 R2 can be used as an iSCSI target with standard and enterprise editions of Windows Storage Server 2003 R2, incorporating WinTarget iSCSI technology which Microsoft acquired in 2006 by from StringBean software.[56][57] This will be an add-on feature available for purchase through OEM partners as an iSCSI feature pack, or is included in some versions of WSS as configured by OEMs.

Windows Storage Server 2003 can be promoted to function as a domain controller; however, this edition is not licensed to run directory services. It can be joined to an existing domain as a member server.[58]

Features[edit]

  • Distributed File System (DFS): Allows multiple network shares to be aggregated as a virtual file system.
  • Support for SAN and iSCSI: Allows computers to connect to a Storage Server over the LAN, without the need for a separate fibre channel network, thus a Storage Area Network can be created over the LAN itself. iSCSI uses the SCSI protocol to transfer data as a block of bytes, rather than as a file. This increases performance of the Storage network in some scenarios, such as using a database server.
  • Virtual Disc Service: Allows NAS devices, RAID devices and SAN shares to be exposed and managed as if they were normal hard drives.
  • JBOD systems: JBOD (Just a bunch of discs) systems, by using VDS, can manage a group of individual storage devices as a single unit. There is no need for the storage units to be of the same maker and model.
  • Software and Hardware RAID: Windows Storage Server 2003 has intrinsic support for hardware implementation of RAID. In case hardware support is not available, it can use software enabled RAID. In that case, all processing is done by the OS.
  • Multi Path IO (MPIO): It provides an alternate connection to IO devices in case the primary path is down.

Editions[edit]

Windows Storage Server 2003 R2 was available in the following editions:[59][60]

Express Workgroup Standard Enterprise
Number of physical CPUs[i] 1 1–4 1–64
x64 variants available Yes Yes Yes Yes
Numbers of disk drives 2 4 Unlimited
NICs 1 2
Print service No Yes Yes Yes
CALs required No No No No
iSCSI target support Optional Optional Optional Optional
Clustering No No No Yes
  1. ^ Microsoft defines a physical CPU/processor as a single socket/node on the systemboard. For O/S licensing purposes, a dual-socket single-core (Intel Pentium/4 Xeon, AMD Athlon/64) system counts as a total of 2 processors, whereas a single-socket quad-core CPU (such as AMD’s Opteron and Intel’s Xeon) counts as 1 processor. Microsoft’s policy has no bearing on how third-party software vendors (such as Oracle) administer CPU licensing for its server applications.

Windows Unified Data Storage Server is a variant of Windows Storage Server 2003 R2 with iSCSI target support standard, available in only the standard and enterprise editions.[61]

Windows Small Business Server[edit]

Windows Small Business Server (SBS) is a software suite which includes Windows Server and additional technologies aimed at providing a small business with a complete technology solution.

The Standard edition of SBS includes Microsoft Remote Web Workplace, Windows SharePoint Services, Microsoft Exchange Server, Fax Server, Active Directory, a basic firewall, DHCP server and network address translation capabilities. The Premium edition of SBS adds Microsoft SQL Server 2000 and Microsoft ISA Server 2004.

SBS has its own type of CAL that is different and costs slightly more than CALs for the other editions of Windows Server 2003. However, the SBS CAL encompasses the user CALs for Windows Server, Exchange Server, SQL Server and ISA Server, and hence is less expensive than buying all other CALs individually.

SBS has the following design limitations, mainly affecting Active Directory:[62]

  • Only one computer in a Windows Server domain can be running SBS
  • SBS must be the root of the Active Directory forest
  • SBS cannot trust any other domains
  • SBS is limited to 75 users or devices depending on the type of CAL
  • SBS is limited to a maximum of 4 GB of RAM (Random Access Memory)
  • SBS domains cannot have any child domains
  • Terminal Services only operates in remote administration mode on SBS, meaning that only two simultaneous RDP sessions are allowed[63]

To remove the limitations from an instance of SBS and upgrade to regular Windows Server, Exchange Server, SQL and ISA Server, there is a Windows Small Business Server 2003 R2 Transition Pack.[64]

Windows Home Server[edit]

Windows Home Server is an operating system from Microsoft based on Windows Small Business Server 2003 SP2.[65] Windows Home Server was announced on January 7, 2007, at the Consumer Electronics Show by Bill Gates and is intended to be a solution for homes with multiple connected PCs to offer file sharing, automated backups, and remote access.[66]

Windows Home Server began shipment to OEMs on September 15, 2007.[67]

Windows Server for Embedded Systems[edit]

Windows Server 2003 for Embedded Systems replaced «Windows 2000 Server for Embedded Systems». Intended use was for building firewall, VPN caching servers and similar appliances.[68] Variants were available with «Server Appliance Software» and with «Microsoft Internet Security and Acceleration Server» [69]

Availability of the original version ended May 28, 2003. Availability of R2 ended March 5, 2006. End of extended support was July 14, 2015 (all variants except Storage Server[10]), and End of Licence was May 28, 2018 (R2 and original).[70] The End of Licence date is the last date that OEM’s may distribute systems using this version. All variants continued to receive Critical security updates until the end of extended support:[71]

Release 2 for Embedded Systems was available in 32 and 64 bit variants, Standard (1-4 CPU) and Enterprise (1-8 CPU):[72]

Windows XP Professional x64 Edition[edit]

Windows XP Professional x64 Edition was released less than a month after Windows Server 2003 SP1,[73] and used the same kernel and source code tree. While many features of the 32-bit variant of Windows XP were brought over into Windows XP Professional x64 Edition, other limitations imposed by constraints such as only supporting 64-bit drivers, and support for 16-bit programs being dropped led to incompatibilities with the 32-bit Windows XP editions available. It later received a Service Pack update as part of the release of Windows Server 2003 SP2.[citation needed]

Updates[edit]

Service Pack 1[edit]

On March 30, 2005, Microsoft released Service Pack 1 for Windows Server 2003. Among the improvements are many of the same updates that were provided to Windows XP users with Service Pack 2. Features that are added with Service Pack 1 include:

  • Security Configuration Wizard, which is a tool that allows administrators to more easily research, and make changes to, security policies.[74]
  • Hot Patching, a feature made to extend Windows Server 2003’s ability to take DLL, Driver, and non-kernel patches without a reboot.
  • IIS 6.0 Metabase Auditing, a feature allows the tracking of metabase edits.[75]
  • Windows Firewall, which brings many of the improvements from Windows XP Service Pack 2 to Windows Server 2003; also with the Security Configuration Wizard, it allows administrators to more easily manage the incoming open ports, as it will automatically detect and select default roles.
  • Other networking improvements include support for Wireless Provisioning Services, better IPv6 support, and new protections against SYN flood TCP attacks.[76]
  • Post-Setup Security Updates, a panel which is shown only when the operating system is first installed. This window allows you to configure and update your server, and halts incoming connections until it is closed.
  • Data Execution Prevention (DEP), a feature to add support for the No Execute (NX) bit which helps to prevent buffer overflow exploits that are often the attack vector of Windows Server exploits.[77]
  • Windows Media Player version 10
  • Internet Explorer 6 SV1[78] (e.g. ‘IE6 SP2’)
  • Support for fixed disks bearing data organized using the GUID Partition Table system[79]

A full list of updates is available in the Microsoft Knowledge Base.[80]

Service Pack 2[edit]

Service Pack 2 for Windows Server 2003 was released on March 13, 2007.[81] The release date was originally scheduled for the first half of 2006.[81] On June 13, 2006, Microsoft made an initial test version of Service Pack 2 available to Microsoft Connect users, with a build number of 2721. This was followed by build 2805, known as Beta 2 Refresh. The final build is 3790.

Microsoft has described Service Pack 2 as a «standard» service pack release containing previously released security updates, hotfixes, and reliability and performance improvements.[82] In addition, Service Pack 2 contains Microsoft Management Console 3.0, Windows Deployment Services (which replaces Remote Installation Services), support for WPA2, and improvements to IPsec and MSConfig. Service Pack 2 also adds Windows Server 2003 Scalable Networking Pack (SNP),[83] which allows hardware acceleration for processing network packets, thereby enabling faster throughput. SNP was previously available as an out-of-band update for Windows Server 2003 Service Pack 1.

Windows Server 2003 R2[edit]

Windows Server 2003 R2 is an updated release of Windows Server 2003, which contains a copy of Windows Server 2003 SP1 on one CD and a host of optionally installed new features on another disc, similar to Microsoft Plus! for Windows 95.[84] It was released to manufacturing on December 6, 2005, for IA-32 and x64 platforms, but not for IA-64.[85] It was succeeded by Windows Server 2008.

New features of Windows Server 2003 R2 include:[86]

  • .NET Framework 2.0, which replaces the .NET Framework 1.0 included with the standard releases
  • Active Directory Federation Services, a single sign-on solution for Active Directory Services
  • Microsoft Management Console version 3.0. Additionally, several new snap-ins are included:
    • Print Management Console, for managing print servers
    • File Server Resource Manager, for managing disk quotas on file servers
    • Storage Manager for SANs, for managing LUNs
  • A new version of Distributed File System that includes remote differential compression technology
  • Microsoft Virtual Server 2005, a hypervisor and the precursor to Hyper-V
  • Windows Services for UNIX, a UNIX environment for Windows

Support lifecycle[edit]

On July 13, 2010, Windows Server 2003’s mainstream support expired and the extended support phase began. During the extended support phase, Microsoft continued to provide security updates; however, free technical support, warranty claims, and design changes are no longer being offered.[87] Extended support lasted until July 14, 2015.[87]

Although Windows Server 2003 is unsupported, Microsoft released an emergency security patch in May 2017 for the OS as well as other unsupported versions of Windows (including Windows XP, Windows Vista and Windows 7 RTM without a service pack), to address a vulnerability that was being leveraged by the WannaCry ransomware attack.[88][89]

Microsoft in 2020 announced that it would disable the Windows Update service for SHA-1 endpoints and since Windows Server 2003 did not get an update for SHA-2, Windows Update Services are no longer available on the OS as of late July 2020.[90] However, as of April 2021, the old updates for Windows Server 2003 are still available on the Microsoft Update Catalog.[91]

Source code leak[edit]

On September 23, 2020, the Windows XP Service Pack 1 and Windows Server 2003 source code was leaked onto the imageboard 4chan by an unknown user. Anonymous users from managed to compile the Windows Server 2003 source code, as well as a Twitter user who posted videos of the process on YouTube proving that the code was genuine,[92] but was removed from the platform on copyright grounds by Microsoft. The leak was incomplete as it was missing the Winlogon source code and some other components.[93][94] The original leak itself was spread using magnet links and torrent files whose payload originally included Server 2003 and XP source code and which was later updated by additional files among which were previous leaks of Microsoft products, its patents, media about conspiracy theories about Bill Gates by anti-vaccination movements and an assortment of PDF files on different topics.[95]

Microsoft issued a statement stating that it was investigating the leaks.[96][97][98]

See also[edit]

  • BlueKeep (security vulnerability)
  • Comparison of Microsoft Windows versions
  • Comparison of operating systems
  • History of Microsoft Windows
  • List of operating systems
  • Microsoft Servers

References[edit]

  1. ^ «Microsoft Windows Server 2003 Released to Manufacturing». News Center. Microsoft. March 28, 2003. Archived from the original on January 13, 2015.
  2. ^ «Microsoft Windows Server 2003 Is Available Worldwide Today». News Center. San Francisco: Microsoft. April 24, 2003.
  3. ^ «SP2 Goes Live». Windows Server Blog. Microsoft. 13 March 2007.
  4. ^ «Windows Server 2003 Evaluation Kit». microsoft.com. Microsoft. 6 November 2003. Archived from the original on 1 January 2005.
  5. ^ «Volume Licensing Programs for Windows Server 2003». microsoft.com. Microsoft. 15 June 2004. Archived from the original on 13 January 2005.
  6. ^ «Windows Server 2003 Pricing». microsoft.com. Microsoft. 6 February 2004. Archived from the original on 29 December 2004.
  7. ^ «Windows Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  8. ^ «Windows Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  9. ^ «Windows Server 2003 end of support». Microsoft. Retrieved 19 June 2015.
  10. ^ a b «Windows Storage Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  11. ^ «Windows Storage Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  12. ^ «Windows Small Business Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  13. ^ «Windows Small Business Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  14. ^ «Windows Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  15. ^ «Microsoft Windows Server 2003 Released to Manufacturing». News Center. Microsoft. 28 March 2003.
  16. ^ «Microsoft Windows Server 2003 Is Available Worldwide Today». News Center. San Francisco: Microsoft. 24 April 2003. Retrieved 1 April 2013.
  17. ^ Mosley, Dion (2023-01-02). «Windows Server Basics — Learning Windows Server 2003». Windows Server Brain. Retrieved 2023-01-14.
  18. ^ «Difference Between Windows Server 2003 And 2008». blogs.siliconindia.com. Retrieved 2023-01-14.
  19. ^ GitHub-Name. «Windows Server 2003 R2 — Microsoft Lifecycle». learn.microsoft.com. Retrieved 2023-01-13.
  20. ^ «Windows XP Server 2003 Overview». www.free-online-training-courses.com. Retrieved 2023-01-13.
  21. ^ a b «Rob Short (and kernel team) — Going deep inside Windows Vista’s kernel architecture — Going Deep — Channel 9». Channel 9. Microsoft.
  22. ^ Petri, Daniel (2009-01-08). «Overview of Windows Server 2003 — Standard Edition | Petri IT Knowledgebase». petri.com. Retrieved 2023-01-14.
  23. ^ Team, Microsoft Windows Server (2005-04-05). «Windows Server 2003 SP1 and X64 Editions — A Historical Perspective». Microsoft Windows Server Blog. Retrieved 2023-01-14.
  24. ^ «Windows Server’s identity crisis». CNET. CBS Interactive. 9 January 2003. Retrieved 16 August 2019.
  25. ^ a b c «The Exterminator — Forbes.com». forbes.com. Archived from the original on February 24, 2004.
  26. ^ a b c «The Exterminator — Forbes.com». forbes.com. Archived from the original on January 2, 2004.
  27. ^ Thomas, Guy (2005-11-01). «Windows Server 2003 IIS v 6.0». Computer Performance. Retrieved 2023-01-14.
  28. ^ Muehlberger, Bryan (2003-12-08). «What’s new in Windows Server 2003 — ADAM». Computerworld. Retrieved 2023-01-14.
  29. ^ Thomas, Guy (2004-03-27). «Disaster Recovery — System State Windows Server 2003». Computer Performance. Retrieved 2023-01-14.
  30. ^ «Group Policy Changes in Windows Server 2003». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-09-15. Retrieved 2023-01-14.
  31. ^ Petri, Daniel (2009-01-07). «Backup Windows Server 2003 Active Directory | Petri IT Knowledgebase». petri.com. Retrieved 2023-01-14.
  32. ^ Posey, Brien (2004-06-24). «Working with the Windows Server 2003 Volume Shadow Copy Service». TechGenix. Retrieved 2023-01-14.
  33. ^ «Windows Server 2003 Command-Line Utilities». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-03-25. Retrieved 2023-01-14.
  34. ^ «Watchdog Timer Hardware Requirements for Windows Server 2003». WHDC. Microsoft. January 14, 2003. Archived from the original on November 18, 2006. Retrieved May 13, 2006.
  35. ^ SARL, LUTEUS. «Enabling XP themes on Windows Server 2003». www.loriotpro.com. Retrieved 2023-01-14.
  36. ^ «Compare the Editions of Windows Server 2003». Microsoft. Archived from the original on 19 April 2012.
  37. ^ Holme, Dan; Thomas, Orin (2004). «1: Introducing Microsoft Windows Server 2003». Managing and maintaining a Microsoft Windows Server 2003 environment. Redmond, WA: Microsoft Press. pp. 1–5. ISBN 0-7356-1437-7.
  38. ^ BetaFred. «Costruire una rete wireless locale sicura con Windows Server 2003 Certificate Services». learn.microsoft.com (in Italian). Retrieved 2023-01-14.
  39. ^ «Enable LDAP over SSL (LDAPS) on Windows Sever 2003 Domain Controller». www.mysysadmintips.com. Retrieved 2023-01-14.
  40. ^ Mosley, Dion (2022-12-23). «Streaming Media Server — Managing Security Windows Server 2003». Windows Server Brain. Retrieved 2023-01-14.
  41. ^ «Install and Configure the Email Server in Windows Server 2003». www.it-notebook.org. Retrieved 2023-01-14.
  42. ^ a b c d e f g h «Memory Limits for Windows Releases». Msdn.microsoft.com. Retrieved November 22, 2011.
  43. ^ a b «Licensing Windows Server 2003, Web Edition». Microsoft.com. Retrieved November 22, 2011.
  44. ^ «Microsoft Raises the Speed Limit with the Availability of 64-Bit Editions of Windows Server 2003 and Windows XP Professional» (Press release). Microsoft. April 25, 2005. Retrieved September 10, 2015.
  45. ^ «Microsoft documentation for Windows Server 2003, Datacenter Edition». Microsoft.com. Retrieved November 22, 2011.
  46. ^ «Microsoft Releases Windows Compute Cluster Server 2003, Bringing High-Performance Computing to the Mainstream». Stories. 2006-06-09. Retrieved 2023-01-14.
  47. ^ «Windows Compute Cluster Server 2003 and Windows Compute Cluster Edition Operating Systems for IBM System x and BladeCenter blade servers» (PDF). IBM. January 15, 2008. Retrieved 14 January 2023.{{cite web}}: CS1 maint: url-status (link)
  48. ^ «Using Microsoft Message Passing Interface — whitepaper». November 2005. Archived from the original on 4 June 2017. Retrieved 14 January 2023.
  49. ^ Posey, Brien (2003-11-03). «Microsoft does NAS with Windows Storage Server 2003». TechRepublic. Retrieved 2023-01-14.
  50. ^ «Microsoft Windows Storage Server 2003 Is Now Available, Offering Customers Dependability, Seamless Integration and Great Economics». Stories. 2003-09-10. Retrieved 2023-01-14.
  51. ^ «What You Need to Know About Windows Storage Server 2003». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-11-25. Retrieved 2023-01-14.
  52. ^ «1. Introducing Windows Server 2003 — Learning Windows Server 2003 [Book]». www.oreilly.com. Retrieved 2023-01-14.
  53. ^ «1. Introducing Windows Server 2003 — Learning Windows Server 2003 [Book]». www.oreilly.com. Retrieved 2023-01-14.
  54. ^ «How to configure a failover cluster using Microsoft Windows 2003/2008». Resource Library. 2010-10-28. Retrieved 2023-01-14.
  55. ^ a b Chernicoff, David (April 17, 2006). «Storage Server R2 Boasts Search and File-Access Improvements». IT Pro. Archived from the original on April 4, 2012. Retrieved September 2, 2006.
  56. ^ Kolakowski, Nicholas (2011-09-07). «HP TouchPad Needs 6 to 8 Weeks for Additional Shipments». Eweek.com. Retrieved 2013-01-09.
  57. ^ «Microsoft Corporation Acquires WinTarget Technology from String Bean Software». Microsoft.com. Retrieved November 22, 2011.
  58. ^ «Windows Storage Server 2003 R2 – Frequently Asked Questions». Microsoft.
  59. ^ (PDF) https://download.microsoft.com/download/3/d/4/3d42bdc2-6725-4b29-b75a-a5b04179958b/percorelicensing_definitions_vlbrief.pdf. CS1 maint: url-status (link)
  60. ^ «Microsoft® Windows® Storage Server 2003 R2 x64 Editions Important Information» (PDF). Retrieved 2023-01-14.{{cite web}}: CS1 maint: url-status (link)
  61. ^ Microsoft Windows Unified Data Storage Server 2003 whitepaper — Microsoft Corporation (October 2006)
  62. ^ «Windows Small Business Server 2003 R2: Frequently Asked Questions». Microsoft. July 11, 2006. Retrieved September 2, 2006.
  63. ^ «Licensing – Windows Small Business Server 2003 R2: Frequently Asked Questions». Microsoft. Retrieved September 2, 2006.
  64. ^ «Windows Server 2003». Microsoft. Archived from the original on 2020-10-03. Retrieved 2006-12-07.
  65. ^ «History Lesson, Part 2: Windows Home Server | Bruceb Consulting». 2010-11-18. Retrieved 2023-01-14.
  66. ^ «Bill Gates Unveils Windows Home Server at the 2007 International Consumer Electronics Show». Stories. 2007-01-08. Retrieved 2023-01-14.
  67. ^ Hill, Brandon (August 22, 2007). «Windows Home Server Systems to Ship 15 September». DailyTech.com. DailyTech. Archived from the original on October 12, 2007. Retrieved October 11, 2007.
  68. ^ «Windows Server with Embedded Licensing». Zoliherczeg.files.wordpress.com. Retrieved 2017-01-27.
  69. ^ «Archived copy». Archived from the original on 2014-10-24. Retrieved 2014-06-15.{{cite web}}: CS1 maint: archived copy as title (link)
  70. ^ «Product Lifecycles & Support». Microsoft. Retrieved 2017-01-27.
  71. ^ Massy, Dave (February 17, 2014). «What does the end of support of Windows XP mean for Windows Embedded?». Windows Embedded Blog.
  72. ^ «Embedded Total Solution — Windows Embedded OS |Industrial Storages and Motherboards| Cloning and Recovery Solutions Development, Analysis and Testing Solutions». MDS Pacific. Retrieved 2017-01-27.
  73. ^ GitHub-Name. «Windows XP — Microsoft Lifecycle». learn.microsoft.com. Retrieved 2023-01-14.
  74. ^ «Security Configuration Wizard for Windows Server 2003». Microsoft. Retrieved September 2, 2006.
  75. ^ «Metabase Auditing (IIS 6.0)». Microsoft. Retrieved September 2, 2006.
  76. ^ «The Cable Guy – December 2004: New Networking Features in Microsoft Windows Server 2003 Service Pack 1». Microsoft TechNet. December 1, 2004. Retrieved September 2, 2006.
  77. ^ «A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows Server 2003 (KB 875352)». Microsoft. Retrieved September 2, 2006.
  78. ^ SV1 stands for «Security Version 1», referring to the set of security enhancements made for that release [1] Archived 2010-01-24 at the Wayback Machine. This version of Internet Explorer is more popularly known as IE6 SP2, given that it is included with Windows XP Service Pack 2, but this can lead to confusion when discussing Windows Server 2003, which includes the same functionality in the SP1 update to that operating system.
  79. ^ «Windows and GPT FAQ». Microsoft.com. June 15, 2011. Retrieved November 22, 2011.
  80. ^ «Windows Server 2003 Service Pack 1 list of updates (KB 824721)». Microsoft. Retrieved September 2, 2006.
  81. ^ a b «Windows Service Pack Road Map». Microsoft. July 10, 2008. Retrieved September 15, 2008.
  82. ^ Ralston, Ward (August 1, 2006). «Windows Server 2003 and XP x64 Editions Service Pack 2». Windows Server Blog. Microsoft.
  83. ^ «Windows Server 2003 gets second update». Retrieved March 13, 2007.
  84. ^ «Windows Server 2003 R2 installation help». Microsoft. Retrieved February 23, 2013.
  85. ^ «New Version Of Windows Server Is On The Way». InformationWeek. UBM. 6 December 2005. Archived from the original on 2007-12-12. Retrieved May 30, 2022.
  86. ^ Otey, Michael (24 April 2006). «New Features in Windows Server 2003 R2». IT Pro. Penton. Archived from the original on 30 May 2022.
  87. ^ a b «Microsoft Support Lifecycle». Support. Microsoft. Retrieved April 11, 2014.
  88. ^ «Microsoft issues ‘highly unusual’ Windows XP patch to prevent massive ransomware attack». The Verge. Vox Media. 13 May 2017. Retrieved 13 May 2017.
  89. ^ «Customer Guidance for WannaCrypt attacks». Microsoft. Retrieved 13 May 2017.
  90. ^ «Windows Update SHA-1 based endpoints discontinued for older Windows devices». support.microsoft.com. Retrieved 2021-04-06.
  91. ^ «Microsoft Update Catalog». www.catalog.update.microsoft.com. Retrieved 2021-04-06.
  92. ^ Cimpanu, Catalin. «Windows XP leak confirmed after user compiles the leaked code into a working OS». ZDNet. Retrieved 2020-10-01.
  93. ^ Warren, Tom (2020-09-25). «Windows XP source code leaks online». The Verge. Retrieved 2020-10-01.
  94. ^ September 2020, Paul Alcorn 30 (30 September 2020). «Windows XP Source Code Leaked, Posted to 4chan (Update, It Works)». Tom’s Hardware. Retrieved 2020-10-01.
  95. ^ «Windows XP Source Code Leaked By Apparent Bill Gates Conspiracist». Gizmodo. 25 September 2020. Retrieved 2020-10-01.
  96. ^ September 2020, Paul Alcorn 30 (30 September 2020). «Windows XP Source Code Leaked, Posted to 4chan (Update, It Works)». Tom’s Hardware. Retrieved 2021-03-26.
  97. ^ «The Windows XP and Windows Server 2003 source code leaks online». Graham Cluley. 2020-09-25. Retrieved 2021-03-26.
  98. ^ «Windows XP source code leaked online». www.computing.co.uk. 2020-09-28. Retrieved 2021-03-26.

External links[edit]

  • Windows Server 2003 on Microsoft TechNet
  • Windows Server 2003 Downloads on Microsoft TechNet
  • Windows Server Performance Team Blog Archived 2010-05-04 at the Wayback Machine
  • Kernel comparison with Linux 2.6 by David Solomon, Mark Russinovich, and Andreas Polze
Источник
Windows Server 2003

Version of the Windows NT operating system
Windows Server 2003 Logo and Wordmark.png
Windows Server 2003.png

Screenshot of Windows Server 2003, showing the Server Manager application which is automatically opened when an administrator logs on
Developer Microsoft
OS family Microsoft Windows
Working state No longer supported
Source model
  • Closed-source
  • Source-available (through Shared Source Initiative)
Released to
manufacturing		 March 28, 2003; 19 years ago[1]
General
availability		 April 24, 2003; 19 years ago[2]
Latest release Service Pack 2 (5.2.3790.3959) / March 13, 2007; 15 years ago[3]
Marketing target Business and Server
Update method Windows Update
Platforms IA-32, x86-64, Itanium
Kernel type Hybrid (Windows NT kernel)
Default
user interface		 Windows shell (Graphical)
License Trialware[4] and volume licensing,[5] with client access licenses[6]
Preceded by Windows 2000 Server (1999)
Succeeded by Windows Server 2008 (2008)
Official website Windows Server 2003
Support status
All editions except Windows Storage Server 2003 and Windows Small Business Server 2003 (including R2):
Mainstream support ended on July 13, 2010
Extended support ended on July 14, 2015[7][8][9]
Windows Storage Server 2003 (including R2):
Mainstream support ended on October 11, 2011
Extended support ended on October 9, 2016[10][11]
Windows Small Business Server 2003 (including R2):

Mainstream support ended on April 12, 2011
Extended support ended on April 12, 2016[12][13]

Installing a Service Pack is Required for Continued Support after April 10, 2007[14]

Windows Server 2003 is the sixth version of Windows Server operating system produced by Microsoft. It is part of the Windows NT family of operating systems and was released to manufacturing on March 28, 2003[15] and generally available on April 24, 2003.[16] Windows Server 2003 is the successor to the Server editions of Windows 2000 and the predecessor to Windows Server 2008.[17][18] An updated version, Windows Server 2003 R2, was released to manufacturing on December 6, 2005.[19] Windows Server 2003 is based on the consumer operating system, Windows XP.[20]

Windows Server 2003’s kernel has also been used in Windows XP 64-bit Edition and Windows XP Professional x64 Edition, and was the starting point for the development of Windows Vista.[21]

Overview[edit]

Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000, Windows Server 2003’s default installation has none of the server components enabled, to reduce the attack surface of new machines. Windows Server 2003 includes compatibility modes to allow older applications to run with greater stability. It was made more compatible with Windows NT 4.0 domain-based networking. Windows Server 2003 brought in enhanced Active Directory compatibility and better deployment support to ease the transition from Windows NT 4.0 to Windows Server 2003 and Windows XP Professional.[22]

Windows Server 2003 is the first server edition of Windows to support the IA64 and x64 architectures.[23]

The product went through several name changes during the course of development. When first announced in 2000, it was known by its codename «Whistler Server»; it was named «Windows 2002 Server» for a brief time in mid-2001, followed by «Windows .NET Server» and «Windows .NET Server 2003». After Microsoft chose to focus the «.NET» branding on the .NET Framework, the OS was finally released as «Windows Server 2003».[24]

Development[edit]

Windows Server 2003 was the first Microsoft Windows version which was thoroughly subjected to semi-automated testing for bugs with a software system called PREfast[25] developed by computer scientist Amitabh Srivastava at Microsoft Research.[26] The automated bug checking system was first tested on Windows 2000 but not thoroughly.[25] Amitabh Srivastava’s PREfast found 12% of Windows Server 2003’s bugs, the remaining 88% being found by human computer programmers.[25] Microsoft employs more than 4,700 programmers who work on Windows, 60% of whom are software testers[26] whose job is to find bugs in Windows source code. Microsoft co-founder Bill Gates stated that Windows Server 2003 was Microsoft’s «most rigorously tested software to date.»[26]

Microsoft used Windows Server 2003’s kernel in the development of Windows Vista.[21]

Changes[edit]

Several improvements and new features have been added to Windows Server 2003.

Internet Information Services (IIS) has been upgraded to v6.0.[27]There have also been significant improvements to Message Queuing and to Active Directory, such as the ability to deactivate classes from the schema, or to run multiple instances of the directory server (ADAM).[28] There was also a notable change in the ability to create a rescue disk, which was removed in favor of Automated System Recovery (ASR).[29]Other Improvements to Group Policy handling and administration[30] have also been made. For the first time in the history of Windows Server, a backup system to restore lost files has been created[31] together with improved disk management, including the ability to back up from shadows of files, allowing the backup of open files.[32]Another important area where improvements have been made are the scripting and command line tools, with the improvements being part of Microsoft’s initiative to bring a complete command shell to the next version of Windows.[33] Other notable new features include support for a hardware-based «watchdog timer», which can restart the server if the operating system does not respond within a certain amount of time.[34] On this version of Windows Server the Themes service is disabled by default, defaulting to the appearance of previous Windows versions (such as Windows 2000).[35]

Editions[edit]

Windows Server 2003 comes in a number of editions, each targeted towards a particular size and type of business.[36][37] In general, all variants of Windows Server 2003 have the ability to share files and printers, act as an application server, host message queues, provide email services, authenticate users, act as an X.509 certificate server, provide LDAP directory services, serve streaming media, and to perform other server-oriented functions.[38][39][40][41]

Supported hardware capabilities across editions of Windows Server 2003[42]

Criteria Web Standard Enterprise Datacenter
Maximum physical CPUs 2 4 8 64
Maximum RAM IA-32 x86 2 GB 4 GB 64 GB
x64 — 32 GB 1 TB
IA-64 Itanium — — 2 TB

Web[edit]

Windows Server 2003 Web is meant for building and hosting Web applications, Web pages, and XML web services. It is designed to be used primarily as an IIS web server[43] and provides a platform for developing and deploying XML Web services and applications that use ASP.NET technology. Domain controller and Terminal Services functionality are not included on Web Edition. However, Remote Desktop for Administration is available. Only 10 concurrent file-sharing connections are allowed at any moment.[citation needed] It is not possible to install Microsoft SQL Server and Microsoft Exchange software in this edition without installing Service Pack 1[citation needed]. Despite supporting XML Web services and ASP.NET, UDDI cannot be deployed on Windows Server 2003 Web[citation needed]. The .NET Framework version 2.0 is not included with Windows Server 2003 Web, but can be installed as a separate update from Windows Update.[citation needed]

Windows Server 2003 Web supports a maximum of 2 physical processors and a maximum of 2 GB of RAM.[42] It is the only edition of Windows Server 2003 that does not require any client access license (CAL) when used as the internet facing server front-end for Internet Information Services and Windows Server Update Services. When using it for storage or as a back-end with another remote server as the front-end, CALs may still be required.[43][clarification needed]

Standard[edit]

Microsoft Windows Server 2003 Standard is aimed towards small to medium-sized businesses. Standard Edition supports file and printer sharing, offers secure Internet connectivity, and allows centralized desktop application deployment. A specialized variant for the x64 architecture was released in April 2005.[44] The IA-32 variants supports up to four physical processors and up to 4 GB RAM;[42] the x64 variant is capable of addressing up to 32 GB of RAM[42] and also supports Non-Uniform Memory Access.

Enterprise[edit]

Windows Server 2003 Enterprise is aimed towards medium to large businesses. It is a full-function server operating system that supports up to 8 physical processors and provides enterprise-class features such as eight-node clustering using Microsoft Cluster Server (MSCS) software and support for up to 64 GB of RAM through PAE.[42] Enterprise Edition also comes in specialized variants for the x64 and Itanium architectures. With Service Pack 2 installed, the x64 and Itanium variants are capable of addressing up to 1 TB and 2 TB of RAM,[42] respectively. This edition also supports Non-Uniform Memory Access (NUMA). It also provides the ability to hot-add supported hardware. Windows Server 2003 Enterprise is also the required edition to issue custom certificate templates.[citation needed]

Datacenter[edit]

Windows Server 2003 Datacenter is designed[45] for infrastructures demanding high security and reliability. Windows Server 2003 is available for IA-32, Itanium, and x64 processors. It supports a maximum of 32 physical processors on IA-32 platform or 64 physical processors on x64 and IA-64 hardware. IA-32 variants of this edition support up to 64 GB of RAM.[42] With Service Pack 2 installed, the x64 variants support up to 1 TB while the IA-64 variants support up to 2 TB of RAM.[42] Windows Server 2003 Datacenter also allows limiting processor and memory usage on a per-application basis.

This edition has better support for storage area networks (SANs): It features a service which uses Windows sockets to emulate TCP/IP communication over native SAN service providers, thereby allowing a SAN to be accessed over any TCP/IP channel. With this, any application that can communicate over TCP/IP can use a SAN, without any modification to the application.[citation needed]

The Datacenter edition, like the Enterprise edition, supports 8-node clustering.[citation needed] Clustering increases availability and fault tolerance of server installations by distributing and replicating the service among many servers. This edition supports clustering with each cluster having its own dedicated storage, or with all cluster nodes connected to a common SAN.

Derivatives[edit]

Windows Compute Cluster Server[edit]

Windows Compute Cluster Server 2003 (CCS), released in June 2006, is designed for high-end applications that require high performance computing clusters. It is designed to be deployed on numerous computers to be clustered together to achieve supercomputing speeds. Each Compute Cluster Server network comprises at least one controlling head node and subordinate processing nodes that carry out most of the work.[46]

Compute Cluster Server has a built-in Message Passing Interface, the Microsoft Messaging Passing Interface v2 (MS-MPI) which is used to communicate between the processing nodes on the cluster network. Alternative MPI Stacks can also be used with the OS. [47]It ties nodes together with a powerful inter-process communication mechanism which can be complex because of communications between hundreds or even thousands of processors working in parallel.

The application programming interface consists of over 160 functions. A job launcher enables users to execute jobs to be executed in the computing cluster. MS MPI was designed to be compatible with the reference open source MPI2 specification which is widely used in High-performance computing (HPC). With some exceptions because of security considerations, MS MPI covers the complete set of MPI2 functionality as implemented in MPICH2, except for the planned future features of dynamic process spawn and publishing.[48]

Windows Storage Server[edit]

Windows Storage Server 2003, a part of the Windows Server 2003 series, is a specialized server operating system for network-attached storage (NAS).[49] Launched in 2003 at Storage Decisions in Chicago, it is optimized for use in file and print sharing and also in storage area network (SAN) scenarios. It is only available through Original equipment manufacturers (OEMs).[50] Unlike other Windows Server 2003 editions that provide file and printer sharing functionality, Windows Storage Server 2003 does not require any CAL.[51]

Windows Storage Server 2003 NAS equipment can be headless, which means that they are without any monitors, keyboards or mice, and are administered remotely.[52] Such devices are plugged into any existing IP network and the storage capacity is available to all users. Windows Storage Server 2003 can use RAID arrays to provide data redundancy, fault-tolerance and high performance.[53] Multiple such NAS servers can be clustered to appear as a single device, which allows responsibility for serving clients to be shared in such a way that if one server fails then other servers can take over (often termed a failover) which also improves fault-tolerance.[54]

Windows Storage Server 2003 can also be used to create a Storage Area Network, in which the data is transferred in terms of chunks rather than files, thus providing more granularity to the data that can be transferred. This provides higher performance to database and transaction processing applications. Windows Storage Server 2003 also allows NAS devices to be connected to a SAN.[citation needed]

Windows Storage Server 2003 led to a second release named Windows Storage Server 2003 R2. This release adds file-server performance optimization, Single Instance Storage (SIS), and index-based search. Single instance storage (SIS) scans storage volumes for duplicate files, and moves the duplicate files to the common SIS store. The file on the volume is replaced with a link to the file. This substitution reduces the amount of storage space required, by as much as 70%.[55]

Windows Storage Server 2003 R2 provides an index-based, full-text search based on the indexing engine already built into Windows server.[55] The updated search engine speeds up indexed searches on network shares. This edition also provides filters for searching many standard file formats, such as ZIP archives, AutoCAD models, XML documents, MP3 audio files, PDF documents, and all Microsoft Office file formats.

Windows Storage Server 2003 R2 includes built in support for Windows SharePoint Services and Microsoft SharePoint Portal Server, and adds a Storage Management snap-in for the Microsoft Management Console. It can be used to manage storage volumes centrally, including DFS shares, on servers running Windows Storage Server R2.

Windows Storage Server 2003 R2 can be used as an iSCSI target with standard and enterprise editions of Windows Storage Server 2003 R2, incorporating WinTarget iSCSI technology which Microsoft acquired in 2006 by from StringBean software.[56][57] This will be an add-on feature available for purchase through OEM partners as an iSCSI feature pack, or is included in some versions of WSS as configured by OEMs.

Windows Storage Server 2003 can be promoted to function as a domain controller; however, this edition is not licensed to run directory services. It can be joined to an existing domain as a member server.[58]

Features[edit]

  • Distributed File System (DFS): Allows multiple network shares to be aggregated as a virtual file system.
  • Support for SAN and iSCSI: Allows computers to connect to a Storage Server over the LAN, without the need for a separate fibre channel network, thus a Storage Area Network can be created over the LAN itself. iSCSI uses the SCSI protocol to transfer data as a block of bytes, rather than as a file. This increases performance of the Storage network in some scenarios, such as using a database server.
  • Virtual Disc Service: Allows NAS devices, RAID devices and SAN shares to be exposed and managed as if they were normal hard drives.
  • JBOD systems: JBOD (Just a bunch of discs) systems, by using VDS, can manage a group of individual storage devices as a single unit. There is no need for the storage units to be of the same maker and model.
  • Software and Hardware RAID: Windows Storage Server 2003 has intrinsic support for hardware implementation of RAID. In case hardware support is not available, it can use software enabled RAID. In that case, all processing is done by the OS.
  • Multi Path IO (MPIO): It provides an alternate connection to IO devices in case the primary path is down.

Editions[edit]

Windows Storage Server 2003 R2 was available in the following editions:[59][60]

Express Workgroup Standard Enterprise
Number of physical CPUs[i] 1 1–4 1–64
x64 variants available Yes Yes Yes Yes
Numbers of disk drives 2 4 Unlimited
NICs 1 2
Print service No Yes Yes Yes
CALs required No No No No
iSCSI target support Optional Optional Optional Optional
Clustering No No No Yes
  1. ^ Microsoft defines a physical CPU/processor as a single socket/node on the systemboard. For O/S licensing purposes, a dual-socket single-core (Intel Pentium/4 Xeon, AMD Athlon/64) system counts as a total of 2 processors, whereas a single-socket quad-core CPU (such as AMD’s Opteron and Intel’s Xeon) counts as 1 processor. Microsoft’s policy has no bearing on how third-party software vendors (such as Oracle) administer CPU licensing for its server applications.

Windows Unified Data Storage Server is a variant of Windows Storage Server 2003 R2 with iSCSI target support standard, available in only the standard and enterprise editions.[61]

Windows Small Business Server[edit]

Windows Small Business Server (SBS) is a software suite which includes Windows Server and additional technologies aimed at providing a small business with a complete technology solution.

The Standard edition of SBS includes Microsoft Remote Web Workplace, Windows SharePoint Services, Microsoft Exchange Server, Fax Server, Active Directory, a basic firewall, DHCP server and network address translation capabilities. The Premium edition of SBS adds Microsoft SQL Server 2000 and Microsoft ISA Server 2004.

SBS has its own type of CAL that is different and costs slightly more than CALs for the other editions of Windows Server 2003. However, the SBS CAL encompasses the user CALs for Windows Server, Exchange Server, SQL Server and ISA Server, and hence is less expensive than buying all other CALs individually.

SBS has the following design limitations, mainly affecting Active Directory:[62]

  • Only one computer in a Windows Server domain can be running SBS
  • SBS must be the root of the Active Directory forest
  • SBS cannot trust any other domains
  • SBS is limited to 75 users or devices depending on the type of CAL
  • SBS is limited to a maximum of 4 GB of RAM (Random Access Memory)
  • SBS domains cannot have any child domains
  • Terminal Services only operates in remote administration mode on SBS, meaning that only two simultaneous RDP sessions are allowed[63]

To remove the limitations from an instance of SBS and upgrade to regular Windows Server, Exchange Server, SQL and ISA Server, there is a Windows Small Business Server 2003 R2 Transition Pack.[64]

Windows Home Server[edit]

Windows Home Server is an operating system from Microsoft based on Windows Small Business Server 2003 SP2.[65] Windows Home Server was announced on January 7, 2007, at the Consumer Electronics Show by Bill Gates and is intended to be a solution for homes with multiple connected PCs to offer file sharing, automated backups, and remote access.[66]

Windows Home Server began shipment to OEMs on September 15, 2007.[67]

Windows Server for Embedded Systems[edit]

Windows Server 2003 for Embedded Systems replaced «Windows 2000 Server for Embedded Systems». Intended use was for building firewall, VPN caching servers and similar appliances.[68] Variants were available with «Server Appliance Software» and with «Microsoft Internet Security and Acceleration Server» [69]

Availability of the original version ended May 28, 2003. Availability of R2 ended March 5, 2006. End of extended support was July 14, 2015 (all variants except Storage Server[10]), and End of Licence was May 28, 2018 (R2 and original).[70] The End of Licence date is the last date that OEM’s may distribute systems using this version. All variants continued to receive Critical security updates until the end of extended support:[71]

Release 2 for Embedded Systems was available in 32 and 64 bit variants, Standard (1-4 CPU) and Enterprise (1-8 CPU):[72]

Windows XP Professional x64 Edition[edit]

Windows XP Professional x64 Edition was released less than a month after Windows Server 2003 SP1,[73] and used the same kernel and source code tree. While many features of the 32-bit variant of Windows XP were brought over into Windows XP Professional x64 Edition, other limitations imposed by constraints such as only supporting 64-bit drivers, and support for 16-bit programs being dropped led to incompatibilities with the 32-bit Windows XP editions available. It later received a Service Pack update as part of the release of Windows Server 2003 SP2.[citation needed]

Updates[edit]

Service Pack 1[edit]

On March 30, 2005, Microsoft released Service Pack 1 for Windows Server 2003. Among the improvements are many of the same updates that were provided to Windows XP users with Service Pack 2. Features that are added with Service Pack 1 include:

  • Security Configuration Wizard, which is a tool that allows administrators to more easily research, and make changes to, security policies.[74]
  • Hot Patching, a feature made to extend Windows Server 2003’s ability to take DLL, Driver, and non-kernel patches without a reboot.
  • IIS 6.0 Metabase Auditing, a feature allows the tracking of metabase edits.[75]
  • Windows Firewall, which brings many of the improvements from Windows XP Service Pack 2 to Windows Server 2003; also with the Security Configuration Wizard, it allows administrators to more easily manage the incoming open ports, as it will automatically detect and select default roles.
  • Other networking improvements include support for Wireless Provisioning Services, better IPv6 support, and new protections against SYN flood TCP attacks.[76]
  • Post-Setup Security Updates, a panel which is shown only when the operating system is first installed. This window allows you to configure and update your server, and halts incoming connections until it is closed.
  • Data Execution Prevention (DEP), a feature to add support for the No Execute (NX) bit which helps to prevent buffer overflow exploits that are often the attack vector of Windows Server exploits.[77]
  • Windows Media Player version 10
  • Internet Explorer 6 SV1[78] (e.g. ‘IE6 SP2’)
  • Support for fixed disks bearing data organized using the GUID Partition Table system[79]

A full list of updates is available in the Microsoft Knowledge Base.[80]

Service Pack 2[edit]

Service Pack 2 for Windows Server 2003 was released on March 13, 2007.[81] The release date was originally scheduled for the first half of 2006.[81] On June 13, 2006, Microsoft made an initial test version of Service Pack 2 available to Microsoft Connect users, with a build number of 2721. This was followed by build 2805, known as Beta 2 Refresh. The final build is 3790.

Microsoft has described Service Pack 2 as a «standard» service pack release containing previously released security updates, hotfixes, and reliability and performance improvements.[82] In addition, Service Pack 2 contains Microsoft Management Console 3.0, Windows Deployment Services (which replaces Remote Installation Services), support for WPA2, and improvements to IPsec and MSConfig. Service Pack 2 also adds Windows Server 2003 Scalable Networking Pack (SNP),[83] which allows hardware acceleration for processing network packets, thereby enabling faster throughput. SNP was previously available as an out-of-band update for Windows Server 2003 Service Pack 1.

Windows Server 2003 R2[edit]

Windows Server 2003 R2 is an updated release of Windows Server 2003, which contains a copy of Windows Server 2003 SP1 on one CD and a host of optionally installed new features on another disc, similar to Microsoft Plus! for Windows 95.[84] It was released to manufacturing on December 6, 2005, for IA-32 and x64 platforms, but not for IA-64.[85] It was succeeded by Windows Server 2008.

New features of Windows Server 2003 R2 include:[86]

  • .NET Framework 2.0, which replaces the .NET Framework 1.0 included with the standard releases
  • Active Directory Federation Services, a single sign-on solution for Active Directory Services
  • Microsoft Management Console version 3.0. Additionally, several new snap-ins are included:
    • Print Management Console, for managing print servers
    • File Server Resource Manager, for managing disk quotas on file servers
    • Storage Manager for SANs, for managing LUNs
  • A new version of Distributed File System that includes remote differential compression technology
  • Microsoft Virtual Server 2005, a hypervisor and the precursor to Hyper-V
  • Windows Services for UNIX, a UNIX environment for Windows

Support lifecycle[edit]

On July 13, 2010, Windows Server 2003’s mainstream support expired and the extended support phase began. During the extended support phase, Microsoft continued to provide security updates; however, free technical support, warranty claims, and design changes are no longer being offered.[87] Extended support lasted until July 14, 2015.[87]

Although Windows Server 2003 is unsupported, Microsoft released an emergency security patch in May 2017 for the OS as well as other unsupported versions of Windows (including Windows XP, Windows Vista and Windows 7 RTM without a service pack), to address a vulnerability that was being leveraged by the WannaCry ransomware attack.[88][89]

Microsoft in 2020 announced that it would disable the Windows Update service for SHA-1 endpoints and since Windows Server 2003 did not get an update for SHA-2, Windows Update Services are no longer available on the OS as of late July 2020.[90] However, as of April 2021, the old updates for Windows Server 2003 are still available on the Microsoft Update Catalog.[91]

Source code leak[edit]

On September 23, 2020, the Windows XP Service Pack 1 and Windows Server 2003 source code was leaked onto the imageboard 4chan by an unknown user. Anonymous users from managed to compile the Windows Server 2003 source code, as well as a Twitter user who posted videos of the process on YouTube proving that the code was genuine,[92] but was removed from the platform on copyright grounds by Microsoft. The leak was incomplete as it was missing the Winlogon source code and some other components.[93][94] The original leak itself was spread using magnet links and torrent files whose payload originally included Server 2003 and XP source code and which was later updated by additional files among which were previous leaks of Microsoft products, its patents, media about conspiracy theories about Bill Gates by anti-vaccination movements and an assortment of PDF files on different topics.[95]

Microsoft issued a statement stating that it was investigating the leaks.[96][97][98]

See also[edit]

  • BlueKeep (security vulnerability)
  • Comparison of Microsoft Windows versions
  • Comparison of operating systems
  • History of Microsoft Windows
  • List of operating systems
  • Microsoft Servers

References[edit]

  1. ^ «Microsoft Windows Server 2003 Released to Manufacturing». News Center. Microsoft. March 28, 2003. Archived from the original on January 13, 2015.
  2. ^ «Microsoft Windows Server 2003 Is Available Worldwide Today». News Center. San Francisco: Microsoft. April 24, 2003.
  3. ^ «SP2 Goes Live». Windows Server Blog. Microsoft. 13 March 2007.
  4. ^ «Windows Server 2003 Evaluation Kit». microsoft.com. Microsoft. 6 November 2003. Archived from the original on 1 January 2005.
  5. ^ «Volume Licensing Programs for Windows Server 2003». microsoft.com. Microsoft. 15 June 2004. Archived from the original on 13 January 2005.
  6. ^ «Windows Server 2003 Pricing». microsoft.com. Microsoft. 6 February 2004. Archived from the original on 29 December 2004.
  7. ^ «Windows Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  8. ^ «Windows Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  9. ^ «Windows Server 2003 end of support». Microsoft. Retrieved 19 June 2015.
  10. ^ a b «Windows Storage Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  11. ^ «Windows Storage Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  12. ^ «Windows Small Business Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  13. ^ «Windows Small Business Server 2003 R2 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  14. ^ «Windows Server 2003 — Microsoft Lifecycle». Microsoft Docs. Retrieved November 6, 2021.
  15. ^ «Microsoft Windows Server 2003 Released to Manufacturing». News Center. Microsoft. 28 March 2003.
  16. ^ «Microsoft Windows Server 2003 Is Available Worldwide Today». News Center. San Francisco: Microsoft. 24 April 2003. Retrieved 1 April 2013.
  17. ^ Mosley, Dion (2023-01-02). «Windows Server Basics — Learning Windows Server 2003». Windows Server Brain. Retrieved 2023-01-14.
  18. ^ «Difference Between Windows Server 2003 And 2008». blogs.siliconindia.com. Retrieved 2023-01-14.
  19. ^ GitHub-Name. «Windows Server 2003 R2 — Microsoft Lifecycle». learn.microsoft.com. Retrieved 2023-01-13.
  20. ^ «Windows XP Server 2003 Overview». www.free-online-training-courses.com. Retrieved 2023-01-13.
  21. ^ a b «Rob Short (and kernel team) — Going deep inside Windows Vista’s kernel architecture — Going Deep — Channel 9». Channel 9. Microsoft.
  22. ^ Petri, Daniel (2009-01-08). «Overview of Windows Server 2003 — Standard Edition | Petri IT Knowledgebase». petri.com. Retrieved 2023-01-14.
  23. ^ Team, Microsoft Windows Server (2005-04-05). «Windows Server 2003 SP1 and X64 Editions — A Historical Perspective». Microsoft Windows Server Blog. Retrieved 2023-01-14.
  24. ^ «Windows Server’s identity crisis». CNET. CBS Interactive. 9 January 2003. Retrieved 16 August 2019.
  25. ^ a b c «The Exterminator — Forbes.com». forbes.com. Archived from the original on February 24, 2004.
  26. ^ a b c «The Exterminator — Forbes.com». forbes.com. Archived from the original on January 2, 2004.
  27. ^ Thomas, Guy (2005-11-01). «Windows Server 2003 IIS v 6.0». Computer Performance. Retrieved 2023-01-14.
  28. ^ Muehlberger, Bryan (2003-12-08). «What’s new in Windows Server 2003 — ADAM». Computerworld. Retrieved 2023-01-14.
  29. ^ Thomas, Guy (2004-03-27). «Disaster Recovery — System State Windows Server 2003». Computer Performance. Retrieved 2023-01-14.
  30. ^ «Group Policy Changes in Windows Server 2003». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-09-15. Retrieved 2023-01-14.
  31. ^ Petri, Daniel (2009-01-07). «Backup Windows Server 2003 Active Directory | Petri IT Knowledgebase». petri.com. Retrieved 2023-01-14.
  32. ^ Posey, Brien (2004-06-24). «Working with the Windows Server 2003 Volume Shadow Copy Service». TechGenix. Retrieved 2023-01-14.
  33. ^ «Windows Server 2003 Command-Line Utilities». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-03-25. Retrieved 2023-01-14.
  34. ^ «Watchdog Timer Hardware Requirements for Windows Server 2003». WHDC. Microsoft. January 14, 2003. Archived from the original on November 18, 2006. Retrieved May 13, 2006.
  35. ^ SARL, LUTEUS. «Enabling XP themes on Windows Server 2003». www.loriotpro.com. Retrieved 2023-01-14.
  36. ^ «Compare the Editions of Windows Server 2003». Microsoft. Archived from the original on 19 April 2012.
  37. ^ Holme, Dan; Thomas, Orin (2004). «1: Introducing Microsoft Windows Server 2003». Managing and maintaining a Microsoft Windows Server 2003 environment. Redmond, WA: Microsoft Press. pp. 1–5. ISBN 0-7356-1437-7.
  38. ^ BetaFred. «Costruire una rete wireless locale sicura con Windows Server 2003 Certificate Services». learn.microsoft.com (in Italian). Retrieved 2023-01-14.
  39. ^ «Enable LDAP over SSL (LDAPS) on Windows Sever 2003 Domain Controller». www.mysysadmintips.com. Retrieved 2023-01-14.
  40. ^ Mosley, Dion (2022-12-23). «Streaming Media Server — Managing Security Windows Server 2003». Windows Server Brain. Retrieved 2023-01-14.
  41. ^ «Install and Configure the Email Server in Windows Server 2003». www.it-notebook.org. Retrieved 2023-01-14.
  42. ^ a b c d e f g h «Memory Limits for Windows Releases». Msdn.microsoft.com. Retrieved November 22, 2011.
  43. ^ a b «Licensing Windows Server 2003, Web Edition». Microsoft.com. Retrieved November 22, 2011.
  44. ^ «Microsoft Raises the Speed Limit with the Availability of 64-Bit Editions of Windows Server 2003 and Windows XP Professional» (Press release). Microsoft. April 25, 2005. Retrieved September 10, 2015.
  45. ^ «Microsoft documentation for Windows Server 2003, Datacenter Edition». Microsoft.com. Retrieved November 22, 2011.
  46. ^ «Microsoft Releases Windows Compute Cluster Server 2003, Bringing High-Performance Computing to the Mainstream». Stories. 2006-06-09. Retrieved 2023-01-14.
  47. ^ «Windows Compute Cluster Server 2003 and Windows Compute Cluster Edition Operating Systems for IBM System x and BladeCenter blade servers» (PDF). IBM. January 15, 2008. Retrieved 14 January 2023.{{cite web}}: CS1 maint: url-status (link)
  48. ^ «Using Microsoft Message Passing Interface — whitepaper». November 2005. Archived from the original on 4 June 2017. Retrieved 14 January 2023.
  49. ^ Posey, Brien (2003-11-03). «Microsoft does NAS with Windows Storage Server 2003». TechRepublic. Retrieved 2023-01-14.
  50. ^ «Microsoft Windows Storage Server 2003 Is Now Available, Offering Customers Dependability, Seamless Integration and Great Economics». Stories. 2003-09-10. Retrieved 2023-01-14.
  51. ^ «What You Need to Know About Windows Storage Server 2003». ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More. 2003-11-25. Retrieved 2023-01-14.
  52. ^ «1. Introducing Windows Server 2003 — Learning Windows Server 2003 [Book]». www.oreilly.com. Retrieved 2023-01-14.
  53. ^ «1. Introducing Windows Server 2003 — Learning Windows Server 2003 [Book]». www.oreilly.com. Retrieved 2023-01-14.
  54. ^ «How to configure a failover cluster using Microsoft Windows 2003/2008». Resource Library. 2010-10-28. Retrieved 2023-01-14.
  55. ^ a b Chernicoff, David (April 17, 2006). «Storage Server R2 Boasts Search and File-Access Improvements». IT Pro. Archived from the original on April 4, 2012. Retrieved September 2, 2006.
  56. ^ Kolakowski, Nicholas (2011-09-07). «HP TouchPad Needs 6 to 8 Weeks for Additional Shipments». Eweek.com. Retrieved 2013-01-09.
  57. ^ «Microsoft Corporation Acquires WinTarget Technology from String Bean Software». Microsoft.com. Retrieved November 22, 2011.
  58. ^ «Windows Storage Server 2003 R2 – Frequently Asked Questions». Microsoft.
  59. ^ (PDF) https://download.microsoft.com/download/3/d/4/3d42bdc2-6725-4b29-b75a-a5b04179958b/percorelicensing_definitions_vlbrief.pdf. CS1 maint: url-status (link)
  60. ^ «Microsoft® Windows® Storage Server 2003 R2 x64 Editions Important Information» (PDF). Retrieved 2023-01-14.{{cite web}}: CS1 maint: url-status (link)
  61. ^ Microsoft Windows Unified Data Storage Server 2003 whitepaper — Microsoft Corporation (October 2006)
  62. ^ «Windows Small Business Server 2003 R2: Frequently Asked Questions». Microsoft. July 11, 2006. Retrieved September 2, 2006.
  63. ^ «Licensing – Windows Small Business Server 2003 R2: Frequently Asked Questions». Microsoft. Retrieved September 2, 2006.
  64. ^ «Windows Server 2003». Microsoft. Archived from the original on 2020-10-03. Retrieved 2006-12-07.
  65. ^ «History Lesson, Part 2: Windows Home Server | Bruceb Consulting». 2010-11-18. Retrieved 2023-01-14.
  66. ^ «Bill Gates Unveils Windows Home Server at the 2007 International Consumer Electronics Show». Stories. 2007-01-08. Retrieved 2023-01-14.
  67. ^ Hill, Brandon (August 22, 2007). «Windows Home Server Systems to Ship 15 September». DailyTech.com. DailyTech. Archived from the original on October 12, 2007. Retrieved October 11, 2007.
  68. ^ «Windows Server with Embedded Licensing». Zoliherczeg.files.wordpress.com. Retrieved 2017-01-27.
  69. ^ «Archived copy». Archived from the original on 2014-10-24. Retrieved 2014-06-15.{{cite web}}: CS1 maint: archived copy as title (link)
  70. ^ «Product Lifecycles & Support». Microsoft. Retrieved 2017-01-27.
  71. ^ Massy, Dave (February 17, 2014). «What does the end of support of Windows XP mean for Windows Embedded?». Windows Embedded Blog.
  72. ^ «Embedded Total Solution — Windows Embedded OS |Industrial Storages and Motherboards| Cloning and Recovery Solutions Development, Analysis and Testing Solutions». MDS Pacific. Retrieved 2017-01-27.
  73. ^ GitHub-Name. «Windows XP — Microsoft Lifecycle». learn.microsoft.com. Retrieved 2023-01-14.
  74. ^ «Security Configuration Wizard for Windows Server 2003». Microsoft. Retrieved September 2, 2006.
  75. ^ «Metabase Auditing (IIS 6.0)». Microsoft. Retrieved September 2, 2006.
  76. ^ «The Cable Guy – December 2004: New Networking Features in Microsoft Windows Server 2003 Service Pack 1». Microsoft TechNet. December 1, 2004. Retrieved September 2, 2006.
  77. ^ «A detailed description of the Data Execution Prevention (DEP) feature in Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows Server 2003 (KB 875352)». Microsoft. Retrieved September 2, 2006.
  78. ^ SV1 stands for «Security Version 1», referring to the set of security enhancements made for that release [1] Archived 2010-01-24 at the Wayback Machine. This version of Internet Explorer is more popularly known as IE6 SP2, given that it is included with Windows XP Service Pack 2, but this can lead to confusion when discussing Windows Server 2003, which includes the same functionality in the SP1 update to that operating system.
  79. ^ «Windows and GPT FAQ». Microsoft.com. June 15, 2011. Retrieved November 22, 2011.
  80. ^ «Windows Server 2003 Service Pack 1 list of updates (KB 824721)». Microsoft. Retrieved September 2, 2006.
  81. ^ a b «Windows Service Pack Road Map». Microsoft. July 10, 2008. Retrieved September 15, 2008.
  82. ^ Ralston, Ward (August 1, 2006). «Windows Server 2003 and XP x64 Editions Service Pack 2». Windows Server Blog. Microsoft.
  83. ^ «Windows Server 2003 gets second update». Retrieved March 13, 2007.
  84. ^ «Windows Server 2003 R2 installation help». Microsoft. Retrieved February 23, 2013.
  85. ^ «New Version Of Windows Server Is On The Way». InformationWeek. UBM. 6 December 2005. Archived from the original on 2007-12-12. Retrieved May 30, 2022.
  86. ^ Otey, Michael (24 April 2006). «New Features in Windows Server 2003 R2». IT Pro. Penton. Archived from the original on 30 May 2022.
  87. ^ a b «Microsoft Support Lifecycle». Support. Microsoft. Retrieved April 11, 2014.
  88. ^ «Microsoft issues ‘highly unusual’ Windows XP patch to prevent massive ransomware attack». The Verge. Vox Media. 13 May 2017. Retrieved 13 May 2017.
  89. ^ «Customer Guidance for WannaCrypt attacks». Microsoft. Retrieved 13 May 2017.
  90. ^ «Windows Update SHA-1 based endpoints discontinued for older Windows devices». support.microsoft.com. Retrieved 2021-04-06.
  91. ^ «Microsoft Update Catalog». www.catalog.update.microsoft.com. Retrieved 2021-04-06.
  92. ^ Cimpanu, Catalin. «Windows XP leak confirmed after user compiles the leaked code into a working OS». ZDNet. Retrieved 2020-10-01.
  93. ^ Warren, Tom (2020-09-25). «Windows XP source code leaks online». The Verge. Retrieved 2020-10-01.
  94. ^ September 2020, Paul Alcorn 30 (30 September 2020). «Windows XP Source Code Leaked, Posted to 4chan (Update, It Works)». Tom’s Hardware. Retrieved 2020-10-01.
  95. ^ «Windows XP Source Code Leaked By Apparent Bill Gates Conspiracist». Gizmodo. 25 September 2020. Retrieved 2020-10-01.
  96. ^ September 2020, Paul Alcorn 30 (30 September 2020). «Windows XP Source Code Leaked, Posted to 4chan (Update, It Works)». Tom’s Hardware. Retrieved 2021-03-26.
  97. ^ «The Windows XP and Windows Server 2003 source code leaks online». Graham Cluley. 2020-09-25. Retrieved 2021-03-26.
  98. ^ «Windows XP source code leaked online». www.computing.co.uk. 2020-09-28. Retrieved 2021-03-26.

External links[edit]

  • Windows Server 2003 on Microsoft TechNet
  • Windows Server 2003 Downloads on Microsoft TechNet
  • Windows Server Performance Team Blog Archived 2010-05-04 at the Wayback Machine
  • Kernel comparison with Linux 2.6 by David Solomon, Mark Russinovich, and Andreas Polze
Источник
   covox

26.09.11 — 09:54

Использовал ли кто память более 4 Гб на сервере 2003 стандарт 32-бит?

Апгрейд на 64бит или адвансед — невозможен.

Попробовал несколько вариантов всяких ram-дисков — не видят :(

Попробовал ebooster (дисковый кэш) — он эту память видит и вроде использует, но пока не особо чувствуется эффект.

Есть ли примеры реального использования?

   ЧеловекДуши

1 — 26.09.11 — 09:56

(0)Если сервер работает, то не трогая, христа ради, не трогай сервер :)

Чем тебе 32ух битность мешает?

И счего ты решил, что 64-рех битный сервак будет работать стабильней и быстрее?

И где технические характеристики железа, на котором у тебя винда крутится? (телепаты нынче в отгуле)

   ЧеловекДуши

2 — 26.09.11 — 09:58

+(0)Для справки, если даже ты сделаешь 64-рех битным сервер, то любое 32-ух битное приложение будет использовать 2 Гб памяти.

   VladZ

3 — 26.09.11 — 10:02

(0) Начни сначала: зачем тебе более 4 гигов?

   popcorn

4 — 26.09.11 — 10:06

(3) возможно у него там сервер 1С или БД крутится…

   andrewks

5 — 26.09.11 — 10:07

mssql умеет вроде

   covox

6 — 26.09.11 — 10:07

to ЧеловекДуши:

спасибо за участие, но все-таки вопрос про реальное использование рам-дисков и кешировщиков видящих unmanaged memory.

Этих программ не так уж много, штук 5-6, но разные версии, разные глюки, вплоть до bsod..

Вдруг кто опытом поделится :)

А 64бит — не стабильнее, просто памяти больше чем у 32 доступно..

to VladZ:

Терминалка w2003 std 32bit, кол-во пользователей выросло, проверяю варианты повышения быстродействия. Установленная память — 8Гб, хотелось бы неприкаянные 4Гб использовать.

to popcorn:

да

   Господин ПЖ

7 — 26.09.11 — 10:09

>Апгрейд на 64бит или адвансед — невозможен.

>кол-во пользователей выросло

или крестик или трусы…

   covox

8 — 26.09.11 — 10:12

to Господин ПЖ:

)

ну не невозможен, а скажем так — очевиден.

Вместе с сопутствующими затратами.

   Kreont

9 — 26.09.11 — 10:13

(6) А чем проверил что для «повышения быстродействия» нехватает именно РАМ, а не например скорости записи/чтения винчестера, процерного времени?

Как вариант, сделай в сервере 1С, два рабочих процесса, они отдельно тогда будут память брать

   andrewks

10 — 26.09.11 — 10:13

какими такими затратами? с чего ты решил, что ключ на 64-бит отдельно надо покупать?

   VladZ

11 — 26.09.11 — 10:14

Почему бы не поставить нормальную ось? Поднять ОСь для терминала — делов максимум на час. Или у тебя есть какая-нибудь шняга, которая не взлетит на 64-рех битах?

   covox

12 — 26.09.11 — 10:16

сервер в датацентре.

переустановка ОС — отдельная услуга, да и с учетом необходимости непрерывной работы вообще проще брать уж другой сервер с другой ОС..

   Fragster

13 — 26.09.11 — 10:16

всем, кто думает, что 32битная ось не видит более 4 гигов — срочно читать про PAE.

автору — это искусственное ограничение конкретно версии «стандарт». либо меняй версию винды, либо загоняй ее в виртуалку с 4 гигами, а остальную память юзай под другие виртуалки

   Fragster

14 — 26.09.11 — 10:17

(12) можно апгрейд удаленно сделать

   Kraft

15 — 26.09.11 — 10:19

(13) PAE это тоже костыль, если памяти реально много, то х64 однозначно

   Fragster

16 — 26.09.11 — 10:25

(15) ты вживую видел серваки с >64 гигов оперативки?

   Fragster

17 — 26.09.11 — 10:27

для сервера терминалов, например — нафиг не надо х64, чтобы не иметь проблем с дровами на принтеры всякие

   Kraft

18 — 26.09.11 — 12:55

(16) при чем здесь это?

   Kraft

19 — 26.09.11 — 12:56

+(18) даже с использованием PAE, на процесс больше 4Гигов не выделить (для х32).

   Aleksey

20 — 26.09.11 — 12:57

(16) Недавно тут хвастался один. У него более 100 гигов озу

   Aleksey

21 — 26.09.11 — 12:58

   Fragster

22 — 26.09.11 — 14:26

(19) блин, а MS SQL сервер-то и не знает…

   ws_mason

23 — 26.09.11 — 19:31

(0) если win2k3 лицензия, то переход на 64 бита бесплатен.

(6) нестабильность — это ваш …

(13) баран это диагноз

   ws_mason

24 — 26.09.11 — 19:33

(22) тоже баран

   NS

25 — 26.09.11 — 19:34

(2) Для начала — приложение умеющее использовать AWE будет использовать всю память, потом суммарно для всех (32 битных) приложений будет использоваться вся память, и под системный кеш будет отведена вся память.

   NS

26 — 26.09.11 — 19:37

(13) 32битным пиложениям не использующим AWE плевать на твое /PAE, и будут они все крутиться в нижней памяти. И соответсвенно в терминале на все сеансы памяти хватать не будет.

   Fragster

27 — 26.09.11 — 19:56

(23)(24) это что это за высер?

(26) не понятно… 100 сеансов 1с по 250 метров вполне себе будут жить безо всяких AWE на 32битной винде. Ты ж сам так в (25) и сказал, возражения не понимаю.

   NS

28 — 26.09.11 — 20:42

(27) Я сказал в (25) про 64-битную винду, и 32-битные приложения в ней.

100 сеансов на 32-битной винде жить не могут.

3 Гига на все сеансы вместе — максимально возможная доступная память под 32-битную винду.

   vde69

29 — 26.09.11 — 21:15

AVE не предлагать?

   NS

30 — 26.09.11 — 21:19

(29) Ты хочешь предложить 1С-у дописать использование AWE-памяти?

   vde69

31 — 26.09.11 — 21:24

(30) почему 1с, SQL это умеет

   NS

32 — 26.09.11 — 21:27

(31) 1С это не умеет в среднем (7.7) сеанс жрет 50 метров памяти, что-то нужно системе. В итоге 50 юзеров в терминале — практически предел для 32 битной винды. А awe (наверно всё-таки включение /PAE в винде) тут ну никак не поможет.

   NS

33 — 26.09.11 — 21:27

После 1С это не умеет — точка.

   volodiia

34 — 27.09.11 — 09:48

А на сервере только 1с крутится?  И сколько сетаки юзеров там работает?

   ws_mason

35 — 27.09.11 — 20:37

Все же ТС — баран!

   ws_mason

36 — 27.09.11 — 20:39

(27) Высер в том, что хоть AWE мария пой, не более 4 гигабайт.

Еще про 3 Тб винты поинтересуйся.

   iithethethe

37 — 27.09.11 — 20:41

32 до 4ГБ, 64 больше 4ГБ

   ws_mason

38 — 27.09.11 — 20:43

32 бита

   Fragster

39 — 27.09.11 — 20:50

http://www.microsoft.com/Rus/WindowsServer2003/evaluation/features/compareeditions.mspx

читаем:

32-разрядная версия Enterprise Edition и 64-разрядная версия Standard Edition поддерживают до 32 ГБ оперативной памяти.

32-разрядная версия Datacenter Edition поддерживает до 64 ГБ оперативной памяти.

врут?

   val

40 — 27.09.11 — 21:04

(36)(40) Не о чем спорить.

На 32-разрядной версии Win2003 Enterprise Edition с ключем PAE SQL Enterprise 2000 в режиме AWE легко берет больше 4ГБ, что хорошо видно на счетчиках в PERFMON. Я это делал неоднократно. Правда, эту память, подключенную по AWE, SQL использует для кеширования, но таки использует.

Собственно AWE и PAE именно для таких вещей и придумали.

   NS

41 — 27.09.11 — 21:07

(40) Речь о приложениях умеющих использовать awe вроде не шла.

   val

42 — 27.09.11 — 21:18

(41) Речь шла о принципиальной возможности для приложений использовать память более 4 ГБ на 32-разр. сервере.

Если я правильно понял предмет спора.

   NS

43 — 27.09.11 — 21:32

(42) Речь шла о том что терминальные сеансы сжирают всю память. О принципиальной возможности и так всё ясно, только в PAE памяти невозможно запустить приложение, и она может выделяться только приложениям умеющим использовать AWE по запросу, больше ни на что она негодна.

   Fragster

44 — 27.09.11 — 21:34

(43) можно все запустить. приложение вообще ничего не знает о памяти, в которой оно запущено, у него свои виртуальные 4 гига адресуемые (2 для винды в общем случае).

   Fragster

45 — 27.09.11 — 21:35

1 32битный процесс — да, без АВЕ не может, но много процессов — легко. наблюдал сие на сервере 1с с 8 рабочими процессами на 32битной винде — суммарно кушали 7 гигов

   NS

46 — 27.09.11 — 21:36

(44) Чего?

Не приложение ничего не знает о PAE памяти, а винда, и выделяет её только исключительно по AWE запросу.

   NS

47 — 27.09.11 — 21:36

(45) Открой для сенбя виртуальную память :)

   Fragster

48 — 27.09.11 — 21:42

(46) чем же это рае память отличается?

   Fragster

49 — 27.09.11 — 21:43

аве позволяет одному процессу больше жрать. и это именно свойство процесса.

AWE не зависит от расширения Physical Address Extension и не препятствует его использованию[1].

   NS

50 — 27.09.11 — 21:44

Наврал я, винда всё-таки её использует для избежания свопа.

(48) Тем что она не используется для исполняемого кода, и соответственно в терминале наступает кирдык при большом количестве сеансов. Точно так-же как и наступает кирдых и без PAE, когда перестает хватать максимальных 3 Гигов выделяемой памяти.

   Fragster

51 — 27.09.11 — 21:45

(50) ЕМНИП только в XP она для неисполняемого кода юзается

   Fragster

52 — 27.09.11 — 21:46

(50) 2(3 с ключем /3гб) гига — ограничение на процесс, а не на систему

   NS

53 — 27.09.11 — 21:47

(49) AWE позволяет 32-битному процессу использовать память сверх 4 Гигов, которая на 32 битной винде доступна только при использовании /PAE. Без режима /PAE в 32-битной винде в принципе доступны только нижние 4 гига.

   NS

54 — 27.09.11 — 21:48

(52) Я не понимаю о чем ты.

   Fragster

55 — 27.09.11 — 21:49

(54) ограничение идет не на систему в целом, а на один процесс. ядро же, собранное с PAE внутри имеет 36битные указатели, и позволяем каждому процессу выделять его виртуальную память в нужной области прямо адресуемой физической памяти

   Fragster

56 — 27.09.11 — 21:51

а AWE все-таки (по докам) не зависит от рае и эти опции загрузки в винде независимы

   Fragster

57 — 27.09.11 — 21:52

   Fragster

58 — 27.09.11 — 21:53

PAE, 4-gigabyte tuning (4GT), and Address Windowing Extensions (AWE) serve different purposes and can be used independently of each other:

   NS

59 — 27.09.11 — 21:53

(55) Органичение на невыгружаемый пул, который не может быть перенесен ни в виртуальную память, ни в /PAE

(56) Еще раз повторю — использовать любым способом память сверх нижних четырех гигов в винде невозможно без ключа /PAE.

   Fragster

60 — 27.09.11 — 21:53

When neither 4GT nor AWE are being used, the amount of physical memory that a single 32-bit process can use is limited by the size of its address space (2 GB). In this case, a PAE-enabled system can still make use of more than 4 GB of RAM to run multiple processes at the same time or to cache file data in memory.

  

   Fragster

61 — 27.09.11 — 21:54

(59) соскакиваешь.

ну и невыгружаемый пул — это не «всем процессам 4 гига»

   NS

62 — 27.09.11 — 21:59

(61) не четыре, а максимум три.

   NS

63 — 27.09.11 — 22:03

Ты меня запутал.

   NS

64 — 27.09.11 — 22:09

   Fragster

65 — 27.09.11 — 22:15

(64) блин, сколько человек под твоим ником пишет? ты сам сказал про невыгружаемый пул, который тут действительно не причем, ибо это память ядра и еще кой чего, что к процессам в юзерспейсе имеет мало отношения

   Fragster

66 — 27.09.11 — 22:17

(65) «PAE без AWE не существует» дальше не читал, ибо бред, который противоречит официальным докам от MSDN

   Fragster

67 — 27.09.11 — 22:17

еще раз, если с английским нормально — почитай (57),все закладки слева

   NS

68 — 27.09.11 — 23:18

(67)  http://msdn.microsoft.com/en-us/library/windows/desktop/aa366796(v=vs.85).aspx

Вот читаю и понимаю, если Майкрософт пытался написать так, чтоб никто не понял — им это удалось.

Из их текста следует что включается NUMA, DEP на 64-битных процах, и для AWE становится доступна память сверх четырех гигов.

   NS

69 — 27.09.11 — 23:20

(65) С невыгружаемым пулом меня переклинило.

   NS

70 — 27.09.11 — 23:22

(67) Какие все закладки? Что такое AWE я знаю, ибо использовал в программах, 4GB тут вообще не при чем, а LP — нерабочая вещь абсолютно.

   Fragster

71 — 27.09.11 — 23:23

(68) фигово у тебя с английским

   NS

72 — 27.09.11 — 23:25

(71) Ничего не фигово.

   Fragster

73 — 27.09.11 — 23:28

(72) тогда переведи «AWE does not require PAE»

   NS

74 — 27.09.11 — 23:29

написано еще на изменение адресации PTE и PDE.

На самом деле, на серваке которые видит в PAE 16 гигов, при 50 сеансах в терминале вылазит ошибка о нехватке памяти.

(73) AWE не требуется PAE — я это отлично знаю.

Ты о чем?

   Fragster

75 — 27.09.11 — 23:34

(74) при 50 сеансах может вылезти сообщение о нехватке памяти из-за нехватки дескрипторов GDI (если 7.7 юзать, например, было не раз). ну а так — приложения, если включен рае, использовать могут в сумме намного больше 4 гигов.

   NS

76 — 27.09.11 — 23:39

(75) И без включенного PAE могут использовать больше 4 гигов, за счет виртуальной памяти. И проблемы начинаются примерно в тот-же момент что и с PAE.

   NS

77 — 27.09.11 — 23:40

(75) Хорошо, уговорил. Мне правда негде проверить — везде 64-битные системы на серваках.

   ws_mason

78 — 28.09.11 — 07:51

Ну вы дали, ТС же про Standart 32 бита спрашивал, а там только 4Гб.

   NS

79 — 29.09.11 — 00:35

(78) Вот как интересней — убить одним постом ветку, или почти сотню постов пообщаться ниочем?

   Ангел-Хоронитель

80 — 29.09.11 — 00:55

а мышки все грызут кактус… невозможно использовать 4 и более гига на 32-битной системе, невозможно.

(80) полноценно — конечно невозможно.

Источник

User-mode virtual address space for each 32-bit process

Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)

4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

User-mode virtual address space for each 64-bit process

With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared

Kernel-mode virtual address space

From 1 GB to a maximum of 2 GB with 4GT

Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value.

Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory.

75% of RAM up to a maximum of 128 GB

System cache virtual address space (physical size limited only by physical memory)

Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Always 1 TB regardless of physical RAM

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows 7 Ultimate

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit in 64-bit Windows
Windows Server 2008 R2 Datacenter
Windows Server 2008 R2 Enterprise
Windows Server 2008 R2 for Itanium-Based Systems
Windows Server 2008 R2 Foundation
Windows Server 2008 R2 Standard

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows Server 2008 Datacenter
Windows Server 2008 Enterprise
Windows Server 2008 HPC Edition
Windows Server 2008 for Itanium-Based Systems
Windows Small Business Server 2008

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows Vista Ultimate

Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition

Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition

Windows Storage Server 2003, Enterprise Edition

Windows Storage Server 2003

Windows Server 2003 R2 Datacenter Edition

Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition

Windows Server 2003 R2 Enterprise Edition

Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition

Windows Server 2003 R2 Standard Edition

Windows Server 2003, Standard Edition SP1

Windows Server 2003, Standard Edition SP2

Windows Server 2003, Datacenter Edition

Windows Server 2003, Enterprise Edition

Windows Server 2003, Standard Edition

Windows Server 2003, Web Edition

Windows Small Business Server 2003

Windows Compute Cluster Server 2003

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version Limit in 32-bit Windows Limit in 64-bit Windows

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.

Cколько оперативной памяти поддерживает Windows server 2003 x86 ?

Windows Server 2003 доступен в четырёх основных изданиях, каждое из которых ориентировано на определённый сектор рынка.

Все эти издания, за исключением Web Edition, доступны также в 64-разрядных вариантах (AMD64 и IA-64). Включение поддержки 64-разрядных процессоров даёт системам возможность использовать большее адресное пространство и увеличивает их производительность.

* Web Edition,- серверная система, оптимизированная для Web- служб и Web- узлов, -(издание для World Wide Web) представляет собой «облегчённую» версию Windows Server 2003 специально для использования на веб-серверах. Это издание не способно выполнять функции контроллера домена и не поддерживает некоторые другие важные возможности прочих изданий, но содержит службы IIS и стоит значительно дешевле. Поддерживает до 2* гигабайт оперативной памяти и до четырёх процессоров на компьютер.

* Standard Edition (стандартное издание) ориентировано на малый и средний бизнес. Оно содержит все основные возможности Windows Server 2003, но в нём недоступны некоторые функции, которые, по мнению Microsoft, необходимы только крупным предприятиям. Поддерживает до 4* гигабайт оперативной памяти и до четырех процессоров на компьютер.

* Enterprise Edition (издание для предприятий) ориентировано на средний и крупный бизнес. В дополнение к возможностям Standard Edition, оно позволяет использовать больший объём оперативной памяти (до 32*(если на 64 БИТ) гигабайт оперативной памяти) и SMP на 8 процессоров (Standard Edition поддерживает лишь 4). Это издание также поддерживает кластеризацию и добавление оперативной памяти «на лету» .

* Datacenter Edition (издание для центров данных) ориентировано на использование в крупных предприятиях при большой нагрузке. Windows Server 2003, Datacenter Edition может одновременно поддерживать в определённых ситуациях больше 10000 пользователей и кластеры, содержащие до восьми узлов. Эта система поддерживает до 64 процессоров и 128* Гб оперативной памяти.

Максимальные объемы памяти для ОС Windows

↑ следующая новость | предыдущая новость ↓

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows XP
Сменить шрифт на обычный короткая ссылка на новость:
Максимальные объемы памяти и адресного пространства зависят от платформы, операционной системы, а также от значения параметра IMAGE_FILE_LARGE_ADDRESS_AWARE в структуре LOADED_IMAGE и настроек 4GT (4-gigabyte tuning), если они используются. Параметр IMAGE_FILE_LARGE_ADDRESS_AWARE может принимать значения «set» (установка) или «cleared» (сброс) – в зависимости от выбранной опции /LARGEADDRESSAWARE. 4GT (или технология настройки памяти для приложений, или переключатель /3GB switch) – это технология (применяемая только в 32-битных системах), с помощью которой можно изменять объем виртуального адресного пространства, доступного для пользовательских приложений. Применение этой технологии позволяет уменьшить общий объем системного виртуального адресного пространства и за счет этого максимизировать ресурс системы.

Физические ограничения на объем памяти для 32-битных платформ также зависят от поддержки технологии Physical Address Extension (PAE), которая позволяет 32-битным версиям Windows использовать более 4 ГБ физической памяти.

Максимальные объемы памяти и адресного пространства

В таблице ниже приведены значения максимальных объемов памяти и адресного пространства для поддерживаемых версий Windows. Если не оговорено иное, указанные значения распространяются на все поддерживаемые версии.

Тип памяти Версии Windows x32 Версии Windows x64
Виртуальное адресное пространство пользовательских приложений для каждого
32-битного процесса		 2 ГБ.

До 3 ГБ при использовании IMAGE_FILE_LARGE_ADDRESS_AWARE и 4GT

 2 ГБ при значении IMAGE_FILE_LARGE_ADDRESS_AWARE «cleared» (используется по умолчанию).

4 ГБ при значении IMAGE_FILE_LARGE_ADDRESS_AWARE «set»
Виртуальное адресное пространство пользовательских приложений для каждого
64-битного процесса		 Не применяется При значении IMAGE_FILE_LARGE_ADDRESS_AWARE «set» (по умолчанию):

  • x64 – 8 ТБ;
  • ОС на базе Intel Itanium – 7 ТБ;
  • Windows 8.1 и Windows Server 2012 R2 – 128 TB.

2 ГБ при значении IMAGE_FILE_LARGE_ADDRESS_AWARE «cleared»
Виртуальное адресное пространство системных приложений 2 ГБ.

От 1 до 2 ГБ при использовании 4GT

 8 ТБ.

Windows 8.1 и Windows Server 2012 R2 – 128 ТБ
Выгружаемый стек (Paged pool) 384 ГБ или назначенный лимит системы, который в любом случае меньше.

Windows 8.1 и Windows Server 2012 R2 – 15,5 ТБ или назначенный лимит системы, который в любом случае меньше.

Windows Server 2008 R2, Windows 7, Windows Server 2008 и Windows Vista – лимитируется объемом доступного виртуального адресного пространства для системных приложений. Начиная с Windows Vista с пакетом Service Pack 1 (SP1), объем выгружаемого стека также может лимитироваться значением ключа реестра PagedPoolLimit.

Windows Home Server и Windows Server 2003 – 530 МБ.

Windows XP – 490 МБ

 384 ГБ или назначенный лимит системы, который в любом случае меньше.

Windows 8.1 и Windows Server 2012 R2 – 15,5 ТБ или назначенный лимит системы, который в любом случае меньше.

Windows Server 2008 R2, Windows 7, Windows Server 2008 и Windows Vista – 128 ГБ или назначенный лимит системы, который в любом случае меньше.

Windows Server 2003 и Windows XP – до 128 ГБ в зависимости от конфигурации и RAM.
Невыгружаемый стек (Nonpaged pool) 75% RAM или 2 ГБ (заведомо меньше).

Windows 8.1 и Windows Server 2012 R2 – объем RAM или 16 ТБ (заведомо меньше); объем адресного пространства лимитирован двойным объемом RAM.

Windows Vista – лимитируется только объемами виртуального адресного пространства для системных приложений и физической памяти. Начиная с Windows Vista с пакетом SP1, объем невыгружаемого стека также может лимитироваться значением ключа реестра NonPagedPoolLimit.

Windows Home Server, Windows Server 2003 и Windows XP – 256 МБ; при использовании 4GT – 128 МБ.

 Объем RAM или 128 ГБ (заведомо меньше); объем адресного пространства лимитирован двойным объемом RAM.

Windows 8.1 и Windows Server 2012 R2 – объем RAM или 16 ТБ (заведомо меньше); объем адресного пространства лимитирован двойным объемом RAM.

Windows Server 2008 R2, Windows 7 и Windows Server 2008 – 75% RAM (не более 128 ГБ).

Windows Vista – 40% RAM (не более 128 ГБ).

Windows Server 2003 и Windows XP – до 128 ГБ в зависимости от конфигурации и RAM.
Виртуальное адресное пространство системного кэша (физически ограничено только физической памятью) Лимитируется доступным объемом виртуального адресного пространства для системных приложений или значением ключа реестра SystemCacheLimit.

Windows 8.1 и Windows Server 2012 R2 – 16 ТБ.

Windows Vista – лимитируется только доступным объемом виртуального адресного пространства для системных приложений. Начиная с Windows Vista с пакетом SP1, объем виртуального адресного пространства системного кэша может также лимитироваться значением ключа реестра SystemCacheLimit.

Windows Home Server, Windows Server 2003 и Windows XP – 860 МБ при установке значения «set» ключа реестра LargeSystemCache и без использования 4GT; до 448 МБ – при использовании 4GT.

 1 TB независимо от объема физической RAM.

Windows 8.1 и Windows Server 2012 R2 – 16 ТБ.

Windows Server 2003 и Windows XP – до 1 ТБ в зависимости от конфигурации и RAM.

Максимальные объемы оперативной памяти для версий ОС Windows

Операционная система Максимальный объем памяти
Windows 10 Enterprise x32 4 ГБ
Windows 10 Enterprise x64 2 ТБ
Windows 10 Education x32 4 ГБ
Windows 10 Education x64 2 ТБ
Windows 10 Pro x32 4 ГБ
Windows 10 Pro x64 2 ТБ
Windows 10 Home x32 4 ГБ
Windows 10 Home x64 128 ГБ
Windows Server 2016 Datacenter 24 ТБ
Windows Server 2016 Standard 24 ТБ
Windows 8.1 x32 4 ГБ
Windows 8.1 x64 128 ГБ
Windows 8.1 Pro x32 4 ГБ
Windows 8.1 Pro x64 512 ГБ
Windows 8.1 Enterprise x32 4 ГБ
Windows 8.1 Enterprise x64 512 ГБ
Windows 8 x32 4 ГБ
Windows 8 x64 128 ГБ
Windows 8 Professional x32 4 ГБ
Windows 8 Professional x64 512 ГБ
Windows 8 Enterprise x32 4 ГБ
Windows 8 Enterprise x64 512 ГБ
Windows Server 2012 R2 Foundation x64 32 ГБ
Windows Server 2012 R2 Essentials x64 64 ГБ
Windows Server 2012 R2 Standard x64 4 ТБ
Windows Server 2012 R2 Datacenter x64 4 ТБ
Windows Server 2012 Foundation x64 32 ГБ
Windows Server 2012 Essentials x64 64 ГБ
Windows Server 2012 Standard x64 4 ТБ
Windows Server 2012 Datacenter x64 4 ТБ
Windows Storage Server 2012 Workgroup x64 32 ГБ
Windows Storage Server 2012 Standard x64 4 ТБ
Hyper-V Server 2012 x64 4 ТБ
Windows 7 Starter x32 2 ГБ
Windows 7 Home Basic x32 4 ГБ
Windows 7 Home Basic x64 8 ГБ
Windows 7 Home Premium x32 4 ГБ
Windows 7 Home Premium x64 16 ГБ
Windows 7 Professional x32 4 ГБ
Windows 7 Professional x64 192 ГБ
Windows 7 Enterprise x32 4 ГБ
Windows 7 Enterprise x64 192 ГБ
Windows 7 Ultimate x32 4 ГБ
Windows 7 Ultimate x64 192 ГБ
Windows Server 2008 R2 Foundation x64 8 ГБ
Windows Server 2008 R2 Standard x64 32 ГБ
Windows Server 2008 R2 Enterprise x64 2 ТБ
Windows Server 2008 R2 Datacenter x64 2 ТБ
Windows HPC Server 2008 R2 x64 128 ГБ
Windows Web Server 2008 R2 x64 32 ГБ
Windows Server 2008 R2 for Itanium-Based Systems 2 ТБ
Windows Server 2008 Foundation x64 8 ГБ
Windows Server 2008 Standard x32 4 ГБ
Windows Server 2008 Standard x64 32 ГБ
Windows Server 2008 Enterprise x32 64 ГБ
Windows Server 2008 Enterprise x64 1 ТБ
Windows Server 2008 Datacenter x32 64 ГБ
Windows Server 2008 Datacenter x64 1 ТБ
Windows Server 2008 HPC Edition x64 128 ГБ
Windows Server 2008 for Itanium-Based Systems 2 ТБ
Windows Small Business Server 2008 x32 4 ГБ
Windows Small Business Server 2008 x64 32 ГБ
Windows Web Server 2008 x32 4 ГБ
Windows Web Server 2008 x64 32 ГБ
Windows Vista Starter x32 1 ГБ
Windows Vista Home Basic x32 4 ГБ
Windows Vista Home Basic x64 8 ГБ
Windows Vista Home Premium x32 4 ГБ
Windows Vista Home Premium x64 16 ГБ
Windows Vista Business x32 4 ГБ
Windows Vista Business x64 128 ГБ
Windows Vista Enterprise x32 4 ГБ
Windows Vista Enterprise x64 128 ГБ
Windows Vista Ultimate x32 4 ГБ
Windows Vista Ultimate x64 128 ГБ
Windows Home Server x32 4 ГБ
Windows Server 2003 R2 Web Edition x32 2 ГБ
Windows Server 2003 R2 Standard Edition x32 4 ГБ
Windows Server 2003 R2 Standard Edition x64 32 ГБ
Windows Server 2003 R2 Enterprise Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 R2 Enterprise Edition x64 1 ТБ
Windows Server 2003 R2 Datacenter Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 R2 Datacenter Edition x64 1 ТБ
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition x64 1 ТБ
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition IA64 2 ТБ
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition x64 1 ТБ
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition IA64 2 ТБ
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition x32 4 ГБ
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition x64 32 ГБ
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition x64 1 ТБ
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition IA64 1 ТБ
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition x64 1 ТБ
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition IA64 1 ТБ
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition x32 4 ГБ
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition x64 32 ГБ
Windows Server 2003, Datacenter Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003, Datacenter Edition IA64 512 ГБ
Windows Server 2003, Enterprise Edition x32 64 ГБ (16 ГБ с 4GT)
Windows Server 2003, Enterprise Edition IA64 512 ГБ
Windows Server 2003, Standard Edition x32 4 ГБ
Windows Server 2003, Web Edition x32 2 ГБ
Windows Small Business Server 2003 x32 4 ГБ
Windows Compute Cluster Server 2003 IA64 32 ГБ
Windows Storage Server 2003, Enterprise Edition x32 8 ГБ
Windows Storage Server 2003 x32 4 ГБ
Windows XP x32 4 ГБ
Windows XP x64 128 ГБ
Windows XP Starter Edition x32 512 МБ
Windows XP Home Edition 4 ГБ
Windows XP Professional Edition 4 ГБ
Windows XP Professional x64 Edition 128 ГБ
Windows XP Embedded x32 4 ГБ
Windows Embedded Standard 2009 x32 4 ГБ
Windows Embedded Standard 7 x32 4 ГБ
Windows Embedded Standard 7 x64 192 ГБ

Примечание – для 32-битных версий Windows Server 2008, Windows Server 2003 R2, Windows Server 2003 with Service Pack 2 (SP2), Windows Server 2003 with Service Pack 1 (SP1), Windows Server 2003 лимит памяти свыше 4 ГБ предполагает использование PAE.

Влияние ограничений памяти на использование видеокарт и других устройств

Для обеспечения совместимости устройств с версиями Windows, не оснащенными PAE, используемая память устройств не должна превышать 4 ГБ. То есть, если система имеет 4 ГБ RAM, избыточная память некоторых устройств или не будет использоваться, или будет переформатирована BIOS’ом. С переформатированной памятью устройств могут работать 64-битные версии Windows. 32-битные пользовательские версии Windows не поддерживают физическую память свыше 4 ГБ, поэтому они не могут обращаться к переформатированным разделам, в отличие от 32-битных серверных версий или любых 64-битных версий.

Читайте также:  Настройка apple mac os

Adblock
detector

Источник

Максимальный объём оперативной памяти в Windows

Речь сегодня пойдет о том — Сколько оперативной памяти поддерживает Windows XP, 7, 8.1 и 10?
Допустим вы захотели в свой компьютер установить дополнительные линейки оперативки. Предположим было у вас 4 Гб, воткнули еще 4 Гб. Включаем комп, а в свойствах все те-же 4Гб (Да и то это округленный показатель, на деле максимум 3.750 Гб). Почему так? О ужас.

Почему остались те-же 4 Гб. оперативы? Давайте разберемся с этими вопросами, раз и навсегда.

Все операционные системы Windows с разрядностью x86 (32 bit) не важно какая версия, все они видят только до 4 Гб. памяти. Вы хоть истыкайте памятью весь компьютер, как ежика с иголками, он будет видеть только до 4 гигабайта. Связано это с внутренними архитектурными ограничениями.

Если вы установите на компьютере 64 битную операционную систему, то все ваши линейки памяти система и увидит.

Сколько оперативной памяти максимально видит разная версия Windows

Windows XP
• Windows XP x86 (32 bit): 4 гб
• Windows XP x64 (64 bit): 128 Гб

Windows 7
• Windows 7 Starter x86 (32 bit): 2 Гб
• Windows 7 Home Basic x86 (32 bit): 4 Гб
• Windows 7 Home Premium x86 (32 bit): 4 Гб
• Windows 7 Professional x86 (32 bit): 4 Гб
• Windows 7 Enterprise x86 (32 bit): 4 Гб
• Windows 7 Ultimate x86 (32 bit): 4 Гб
• Windows 7 Home Basic x64 (64 bit): 8 Гб
• Windows 7 Home Premium x64 (64 bit): 16 Гб
• Windows 7 Professional x64 (64 bit): 192 Гб
• Windows 7 Enterprise x64 (64 bit): 192 Гб
• Windows 7 Ultimate x64 (64 bit): 192 Гб

Windows 8 / 8.1
• Windows 8 x86 (32 bit): 4 Гб
• Windows 8 Professional x86 (32 bit): 4 Гб
• Windows 8 Enterprise x86 (32 bit): 4 Гб
• Windows 8 x64 (64 bit): 128 Гб
• Windows 8 Professional x64 (64 bit): 512 Гб
• Windows 8 Enterprise x64 (64 bit): 512 Гб

Windows 10
• Windows 10 Home x86 (32 bit): 4 Гб
• Windows 10 Home x64 (64 bit): 128 Гб
• Windows 10 Pro x86 (32 bit): 4 Гб
• Windows 10 Pro x64 (64 bit): 512 Гб

Как видите, 64-битные редакции поддерживает огромный объем оперативной памяти, а вот в случае с 32-битной версией нужно быть внимательным с выбором: зачастую система не поддерживает даже указанные 4 Гб.

Итог: Максимальное количество оперативной памяти, которые способны «увидеть» 32 разрядные версии Windows — это 4 Гб. Таким образом, если у вас больший объем RAM, следует установить 64-разрядную версию, чтобы воспользоваться этой памятью. Для того, чтобы узнать, какая версия Windows установлена на вашем компьютере, откройте пункт «Система» в панели управления (или кликните по «Мой компьютер» правой кнопкой мыши и выберите «Свойства»).

Источник

Сколько ОЗУ поддерживает ваша версия Windows?

Один из наиболее часто задаваемых вопросов, которые поступают нам от подписчиков в социальных сетях — сколько оперативной памяти будет поддерживать конкретная версия Windows.

После того, как я получил еще один такой вопрос сегодня утром, я подумал, что, возможно, стоит разместить эту информацию на сайте. Поэтому предлагаю вашему вниманию список, в котором вы найдете, сколько оперативной памяти поддерживает конкретная версия Windows.

Сколько ОЗУ поддерживают различные версии Windows 10

  • Windows 10 Home — 128 ГБ
  • Windows 10 Pro — 2 ТБ
  • Windows 10 Pro для рабочих станций — 6 ТБ
  • Windows 10 Enterprise — 6 ТБ
  • Windows 10 Education — 2 ТБ
  • Все 32-разрядные версии Windows 10 — 4 ГБ

Сколько ОЗУ поддерживает Windows Server 2016

Сколько ОЗУ поддерживают различные версии Windows 8.1

  • Windows 8.1 RT — 4 ГБ
  • Windows 8.1 — 128 ГБ
  • Windows 8.1 Pro — 512 ГБ
  • Windows 8.1 Корпоративная — 512 ГБ
  • Все 32-разрядные версии Windows 8.1 — 4 ГБ

Сколько ОЗУ поддерживают различные версии Windows 8

  • Windows 8 — 128 ГБ
  • Windows 8 Pro — 512 ГБ
  • Windows 8 Enterprise — 512 ГБ
  • Все 32-разрядные версии Windows 8 — 4 ГБ

Сколько ОЗУ поддерживают различные версии Windows 7

  • Windows 7 Starter Edition — 2 ГБ (Примечание: 64-разрядная версия Win 7 Starter Edition отсутствует)
  • Windows 7 Home Basic — 8 ГБ
  • Windows 7 Home Premium — 16 ГБ
  • Windows 7 Pro — 192 ГБ
  • Windows 7 Enterprise — 192 ГБ
  • Windows 7 Ultimate — 192 ГБ

Сколько ОЗУ поддерживают различные версии Windows Vista

  • Windows Vista Starter Edition — 1 ГБ (Примечание: 64-разрядная версия Win Vista Starter Edition отсутствует)
  • Windows Vista Home Basic — 8 ГБ
  • Windows Vista Home Premium — 16 ГБ
  • Windows Vista Business — 128 ГБ
  • Windows Vista Enterprise — 128 ГБ
  • Windows Vista Ultimate — 128 ГБ
  • Все 32-разрядные версии Windows Vista, кроме Win Vista Starter Edition — 4 ГБ

Сколько ОЗУ поддерживают различные версии Windows XP

  • Windows XP Starter Edition — 512 МБ (Примечание: 64-разрядная версия Win XP Starter Edition отсутствует)
  • Все 32-разрядные версии Windows XP (кроме Win XP Starter) — 4 ГБ
  • Все 64-разрядные версии Windows XP — 128 ГБ

Хотя каждая версия Windows имеет свое собственное ограничение на объем ОЗУ, то же самое можно сказать о многих комбинациях ЦП и материнской платы, установленных как на старых, так и на новых компьютерах.

Следовательно, если ваша конкретная версия Windows поддерживает определенный объем ОЗУ, то ЦП / материнская плата вашего компьютера может поддерживать больше или меньше этого объема.

Возможно, вам будет интересно:

Спасибо за внимание, надеемся наша статья была вам полезна.

Приглашаем вас в наши группы в социальных сетях Одноклассники и Вконтакте , подписывайтесь, чтобы не пропустить новые полезные советы и новости из мира IT.

Не забываем подписаться на канал « IT знания » и поставить лайк, у нас для вас еще масса интересного.

Источник

Ограничения размера памяти для разных версий Windows

This topic describes memory limits for supported Windows releases:

Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.

Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.

User-mode virtual address space for each 32-bit process

Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)

4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

User-mode virtual address space for each 64-bit process

With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared

Kernel-mode virtual address space

From 1 GB to a maximum of 2 GB with 4GT

Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value.

Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory.

75% of RAM up to a maximum of 128 GB

System cache virtual address space (physical size limited only by physical memory)

Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Always 1 TB regardless of physical RAM

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows 7 Ultimate

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit in 64-bit Windows
Windows Server 2008 R2 Datacenter

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows Server 2008 Datacenter

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows Vista Ultimate

Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition

Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition

Windows Storage Server 2003, Enterprise Edition

Windows Storage Server 2003

Windows Server 2003 R2 Datacenter Edition

Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition

Windows Server 2003 R2 Enterprise Edition

Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition

Windows Server 2003 R2 Standard Edition

Windows Server 2003, Standard Edition SP1

Windows Server 2003, Standard Edition SP2

Windows Server 2003, Datacenter Edition

Windows Server 2003, Enterprise Edition

Windows Server 2003, Standard Edition

Windows Server 2003, Web Edition

Windows Small Business Server 2003

Windows Compute Cluster Server 2003

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version Limit in 32-bit Windows Limit in 64-bit Windows

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.

Источник

Adblock
detector

Version Limit in 32-bit Windows Limit in 64-bit Windows
Windows XP
Источник

Понравилась статья? Поделить с друзьями:
  • Windows 2003 group policy management console
  • Windows 2003 32 bit максимальный размер памяти
  • Windows 2000 создать загрузочную флешку windows
  • Windows 2000 скачать с официального сайта microsoft
  • Windows 2000 скачать с ключом активации