Windows Server 2003 R2 Standard

1. Windows Server

Windows Server 2003 is a serveroperating system produced by Microsoft and released on April 24, 2003.^[8] It is the successor to Windows 2000 Server and the predecessor to Windows Server 2008. An updated version, Windows Server 2003 R2, was released to manufacturing on December 6, 2005. Windows Server 2003's kernel was later adopted in the development of Windows Vista.^[9]

• 4Editions
• 5Derivatives
  • 5.2Windows Storage Server
• 6Updates

I have been already installed windows server 2003 r2 standard edition sp2 32 bit on to the server but want to upgrade 64 bit using same. Where can I get ISO file for Windows Standard server 2003 R2 64 bit. I have licensing key but no setup disk. I can no longer download the image from Licensing page, but I can download Server 2008 and 2012 and most other new things.

Overview[edit]

Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000 Server, 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.

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'.^[10]

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^[11] developed by computer scientistAmitabh Srivastava at Microsoft Research.^[12] The automated bug checking system was first tested on Windows 2000 but not thoroughly.^[11] Amitabh Srivastava's PREfast found 12% of Windows Server 2003's bugs, the remaining 88% being found by human computer programmers.^[11] Microsoft employs more than 4,700 programmers who work on Windows, 60% of whom are software testers^[12]Nintendo eshop free download codes. 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.'^[12]

Microsoft later used Windows Server 2003's kernel in the development of Windows Vista.^[9]

Changes[edit]

The following features are new to Windows Server 2003:

• Internet Information Services (IIS) v6.0
• Significant improvements to Message Queuing
• Manage Your Server – a role management administrative tool that allows an administrator to choose what functionality the server should provide
• Improvements to Active Directory, such as the ability to deactivate classes from the schema, or to run multiple instances of the directory server (ADAM)
• Improvements to Group Policy handling and administration
• Provides a backup system to restore lost files
• Improved disk management, including the ability to back up from shadows of files, allowing the backup of open files.
• Improved scripting and command line tools, which are part of Microsoft's initiative to bring a complete command shell to the next version of Windows
• 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.^[13]

The ability to create a rescue disk was removed in favor of Automated System Recovery (ASR).

Editions[edit]

Windows Server 2003 comes in a number of editions, each targeted towards a particular size and type of business.^[14][15] 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.

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^[17] 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. It is not possible to install Microsoft SQL Server and Microsoft Exchange software in this edition without installing Service Pack 1. Despite supporting XML Web services and ASP.NET, UDDI cannot be deployed on Windows Server 2003 Web. 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.

Windows Server 2003 Web supports a maximum of 2 physical processors and a maximum of 2 GB of RAM.^[16] 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.^{[17][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 version for the x64 architecture was released in April 2005.^[18] The IA-32 version supports up to four physical processors and up to 4 GB RAM;^[16] the x64 version is capable of addressing up to 32 GB of RAM^[16] 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.^[16] Enterprise Edition also comes in specialized versions for the x64 and Itanium architectures. With Service Pack 2 installed, the x64 and Itanium versions are capable of addressing up to 1 TB and 2 TB of RAM,^[16] 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.

Datacenter[edit]

Windows Server 2003 Datacenter is designed^[19] 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 versions of this edition support up to 64 GB of RAM.^[16] With Service Pack 2 installed, the x64 versions support up to 1 TB while the IA-64 versions support up to 2 TB of RAM.^[16] 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.

The Datacenter edition, like the Enterprise edition, supports 8-node clustering. 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 computingclusters. 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.

Compute Cluster Server uses the Microsoft Messaging Passing Interface v2 (MS-MPI) to communicate between the processing nodes on the cluster network. 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.

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). 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). Unlike other Windows Server 2003 editions that provide file and printer sharing functionality, Windows Storage Server 2003 does not require any CAL.

Windows Storage Server 2003 NAS equipment can be headless, which means that they are without any monitors, keyboards or mice, and are administered remotely. 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. 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.

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.

Windows Storage Server 2003 R2, as a follow-up to Windows Storage Server 2003, 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%.^[20]

Windows Storage Server 2003 R2 provides an index-based, full-text search based on the indexing engine already built into Windows server.^[20] 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, AutoCAD, XML, MP3, and .pdf, 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.^[21][22] 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.^[23]

Features[edit]

• Distributed File System (DFS): DFS allows multiple network shares to be aggregated as a virtual file system.
• Support for SAN and iSCSI: Computers can connect to a Storage Server over the LAN, and there is no 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: It 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:

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 version of Windows Storage Server 2003 R2 with iSCSI target support standard, available in only the standard and enterprise editions.

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:^[24]

Windows Server

• 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^[25]

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.^[26]

Windows Home Server[edit]

Windows Home Server is an operating system from Microsoft based on Windows Small Business Server 2003 SP2 (this can be seen in the directory listings of the installation DVD). 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.

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

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.^[28] Versions were available with 'Server Appliance Software' and with 'Microsoft Internet Security and Acceleration Server' ^[29]

Availability of the original version ended May 28, 2003. Availability of R2 ended March 5, 2006. End of Support is scheduled for July 14, 2015 (R2 and original), and End of Licence is scheduled for May 28, 2018 (R2 and original).^[30] The end of support date indicates that the supported service pack was dated July 14, 2005. The End of Licence date is the last date that OEM's may distribute systems using this version. All versions continue to receive Critical security updates until the end of support:^[31] Microsoft has not announced extended support dates for Windows Server 2003 for Embedded Systems.

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

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: A tool that allows administrators to more easily research, and make changes to, security policies.^[33]
• Hot Patching: This feature is set to extend Windows Server 2003's ability to take DLL, Driver, and non-kernel patches without a reboot.
• IIS 6.0 Metabase Auditing: Allowing the tracking of metabase edits.^[34]
• Windows Firewall: 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.^[35]
• Post-Setup Security Updates: A default mode that is turned on when a Service Pack 1 server is first booted up after installation. It configures the firewall to block all incoming connections, and directs the user to install updates.
• Data Execution Prevention (DEP): Support for the No Execute (NX) bit which helps to prevent buffer overflow exploits that are often the attack vector of Windows Server exploits.^[36]
• Windows Media Player version 10
• Internet Explorer 6 SV1^[37] (e.g. 'IE6 SP2')
• Support for fixed disks bearing data organized using the GUID Partition Table system^[38]

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

Service Pack 2[edit]

Service Pack 2 for Windows Server 2003 was released on March 13, 2007.^[40] The release date was originally scheduled for the first half of 2006.^[40] 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.^[41] 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),^[42] 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 the title of a complementary offering by Microsoft. It consists of a copy of Windows Server 2003 SP1 on one CD and a host of optionally installed new features (reminiscent of Microsoft Plus!) on another.^[43] It was released to manufacturing on December 6, 2005 for IA-32 and x64 platforms, but not for IA-64.^[44] It was succeeded by Windows Server 2008.

New features of Windows Server 2003 R2 include:^[45]

• 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

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.^[46] Extended support lasted until July 14, 2015.^[46]

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 and Windows 8 RTM), to address a vulnerability that was being leveraged by the WannaCry ransomware attack.^[47][48]

See also[edit]

References[edit]

1. ^'Microsoft Windows Server 2003 Is Available Worldwide Today'. News Center. San Francisco: Microsoft. April 24, 2003.
2. ^'SP2 Goes Live'. Windows Server Blog. Microsoft.
3. ^'Windows Server 2003 Evaluation Kit'. microsoft.com. Microsoft. 6 November 2003. Archived from the original on 1 January 2005.
4. ^'Volume Licensing Programs for Windows Server 2003'. microsoft.com. Microsoft. 15 June 2004. Archived from the original on 13 January 2005.
5. ^'Windows Server 2003 Pricing'. microsoft.com. Microsoft. 6 February 2004. Archived from the original on 29 December 2004.
6. ^'Windows server 2003 Lifecycle Policy'. Microsoft. March 8, 2008.
7. ^'Windows Server 2003 end of support'. Microsoft. Retrieved 19 June 2015.
8. ^'Microsoft Windows Server 2003 Is Available Worldwide Today'. News Center. San Francisco: Microsoft. 24 April 2003. Retrieved 1 April 2013.
9. ^ ^ab'Rob Short (and kernel team) - Going deep inside Windows Vista's kernel architecture - Going Deep - Channel 9'. Channel 9. Microsoft.
10. ^'Windows Server's identity crisis'. CNET News. CBS Interactive. 9 January 2003. Retrieved 1 April 2013.
11. ^ ^abc'The Exterminator - Forbes.com'. forbes.com.
12. ^ ^abc'The Exterminator - Forbes.com'. forbes.com.
13. ^'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.
14. ^'Compare the Editions of Windows Server 2003'. Microsoft. Archived from the original on 19 April 2012.
15. ^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. ISBN0-7356-1437-7.
16. ^ ^abcdefgh'Memory Limits for Windows Releases'. Msdn.microsoft.com. Retrieved November 22, 2011.
17. ^ ^ab'Licensing Windows Server 2003, Web Edition'. Microsoft.com. Retrieved November 22, 2011.
18. ^'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.
19. ^'Microsoft documentation for Windows Server 2003, Datacenter Edition'. Microsoft.com. Retrieved November 22, 2011.
20. ^ ^abDavid Chernicoff (April 17, 2006). 'Storage Server R2 Boasts Search and File-Access Improvements'. Windows IT Pro. Retrieved September 2, 2006.
21. ^Nicholas Kolakowski (2011-09-07). 'HP TouchPad Needs 6 to 8 Weeks for Additional Shipments'. Eweek.com. Retrieved 2013-01-09.
22. ^'Microsoft Corporation Acquires WinTarget Technology from String Bean Software'. Microsoft.com. Retrieved November 22, 2011.
23. ^'Windows Storage Server 2003 R2 – Frequently Asked Questions'. Microsoft.
24. ^'Windows Small Business Server 2003 R2: Frequently Asked Questions'. Microsoft. July 11, 2006. Retrieved September 2, 2006.
25. ^'Licensing – Windows Small Business Server 2003 R2: Frequently Asked Questions'. Microsoft. Retrieved September 2, 2006.
26. ^Windows Server 2003
27. ^Hill, Brandon (August 22, 2007). 'Windows Home Server Systems to Ship 15 September'. DailyTech.com. DailyTech. Retrieved October 11, 2007.
28. ^'Windows Server with Embedded Licensing'. Zoliherczeg.files.wordpress.com. Retrieved 2017-01-27.
29. ^'Archived copy'. Archived from the original on 2014-10-24. Retrieved 2014-06-15.CS1 maint: Archived copy as title (link)
30. ^'Product Lifecycles & Support'. Microsoft. Retrieved 2017-01-27.
31. ^Massy, Dave (February 17, 2014). 'What does the end of support of Windows XP mean for Windows Embedded?'. Windows Embedded Blog.
32. ^'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.
33. ^'Security Configuration Wizard for Windows Server 2003'. Retrieved September 2, 2006.
34. ^'Metabase Auditing (IIS 6.0)'. Retrieved September 2, 2006.
35. ^'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.
36. ^'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.
37. ^SV1 stands for 'Security Version 1', referring to the set of security enhancements made for that release [1]. 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.
38. ^'Windows and GPT FAQ'. Microsoft.com. June 15, 2011. Retrieved November 22, 2011.
39. ^'Windows Server 2003 Service Pack 1 list of updates (KB 824721)'. Microsoft. Retrieved September 2, 2006.
40. ^ ^ab'Windows Service Pack Road Map'. Microsoft. July 10, 2008. Retrieved September 15, 2008.
41. ^Ralston, Ward (August 1, 2006). 'Windows Server 2003 and XP x64 Editions Service Pack 2'. Windows Server Blog. Microsoft.
42. ^'Windows Server 2003 gets second update'. Retrieved March 13, 2007.
43. ^'Windows Server 2003 R2 installation help'. Microsoft. Retrieved February 23, 2013.
44. ^'New Version Of Windows Server Is On The Way'. InformationWeek. UBM. Archived from the original on 2007-12-12. Retrieved September 2, 2006.
45. ^Otey, Michael (24 April 2006). 'New Features in Windows Server 2003 R2'. Windows IT Pro. Penton.
46. ^ ^ab'Microsoft Support Lifecycle'. Support. Microsoft. Retrieved April 11, 2014.
47. ^'Microsoft issues 'highly unusual' Windows XP patch to prevent massive ransomware attack'. The Verge. Vox Media. Retrieved 13 May 2017.
48. ^'Customer Guidance for WannaCrypt attacks'. Microsoft. Retrieved 13 May 2017.

External links[edit]

• Windows Server 2003 on Microsoft TechNet
• Windows Server 2003 Downloads on Microsoft TechNet
• Kernel comparison with Linux 2.6 by David Solomon, Mark Russinovich, and Andreas Polze

This topic describes the memory limits for supported Windows and Windows Server 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.

4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.

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.

Physical Memory Limits: Windows 10

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

Physical Memory Limits: Windows Server 2016

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

Physical Memory Limits: Windows 8

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

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.

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.

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.

Physical Memory Limits: Windows Vista

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

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 R2

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

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

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.

Physical Memory Limits: Windows XP

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

Physical Memory Limits: Windows Embedded

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

How graphics cards and other devices affect memory limits

Devices have to map their memory below 4 GB for compatibility with non-PAE-aware Windows releases. Therefore, if the system has 4GB of RAM, some of it is either disabled or is remapped above 4GB by the BIOS. If the memory is remapped, X64 Windows can use this memory. X86 client versions of Windows don’t support physical memory above the 4GB mark, so they can’t access these remapped regions. Any X64 Windows or X86 Server release can.

X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space. The limit that these versions impose is the highest permitted physical RAM address, not the size of the IO space. That means PAE-aware drivers can actually use physical space above 4 GB if they want. For example, drivers could map the 'lost' memory regions located above 4 GB and expose this memory as a RAM disk.

Related topics