Windows server 2012 core и windows server 2012 r2

This is a good article. Click here for more information.

From Wikipedia, the free encyclopedia

Windows Server 2012

Version of the Windows NT operating system

Screenshot of Windows Server 2012, showing the Server Manager application which is automatically opened when an administrator logs on, taskbar, and the blue color of Aero Lite

Developer Microsoft
OS family Windows Server
Working state Current
Source model
  • Closed-source
  • Source-available (through Shared Source Initiative)
Released to
manufacturing
August 1, 2012; 11 years ago
General
availability
September 4, 2012; 11 years ago[1]
Latest release 6.2 (Build 9200) / August 1, 2012; 11 years ago[2]
Marketing target Business
Update method Windows Update, Windows Server Update Services, SCCM
Platforms x86-64
Kernel type Hybrid (Windows NT kernel)
Default
user interface
Windows shell (GUI)
License Commercial proprietary software
Preceded by Windows Server 2008 R2 (2009)
Succeeded by Windows Server 2012 R2 (2013)
Official website Windows Server 2012 (archived at Wayback Machine))
Support status
  • Start date: October 30, 2012[3]
  • Mainstream support ended on October 9, 2018[3]
  • Extended support until October 10, 2023[3]
  • Paid support via the Extended Security Updates program until October 13, 2026, only for volume licensed editions.

Windows Server 2012, codenamed «Windows Server 8», is the sixth version of the Windows Server operating system by Microsoft, as part of the Windows NT family of operating systems. It is the server version of Windows based on Windows 8 and succeeds Windows Server 2008 R2, which is derived from the Windows 7 codebase, released nearly three years earlier. Two pre-release versions, a developer preview and a beta version, were released during development. The software was officially launched on September 4, 2012, which was the month before the release of Windows 8.[4] It was succeeded by Windows Server 2012 R2 in 2013. Mainstream support for Windows Server 2012 ended on October 9, 2018, and extended support will end on October 10, 2023. Windows Server 2012 is eligible for the paid Extended Security Updates (ESU) program, which offers continued security updates until October 13, 2026.

Windows Server 2012 removed support for Itanium and processors without PAE, SSE2 and NX.[5] Four editions were released. Various features were added or improved over Windows Server 2008 R2 (with many placing an emphasis on cloud computing), such as an updated version of Hyper-V, an IP address management role, a new version of Windows Task Manager, and ReFS, a new file system. Windows Server 2012 received generally good reviews in spite of having included the same controversial Metro-based user interface seen in Windows 8, which includes the Charms Bar for quick access to settings in the desktop environment.

Windows Server 2012 is the final version of Windows Server that supports processors without CMPXCHG16b, PrefetchW, LAHF and SAHF. Its successor, Windows Server 2012 R2, requires a processor with CMPXCHG16b, PrefetchW, LAHF and SAHF in any supported architecture.

As of April 2017, 35% of servers were running Windows Server 2012, surpassing usage share of Windows Server 2008.[6]

History[edit]

Windows Server 2012, codenamed «Windows Server 8»,[7] is the fifth release of Windows Server family of operating systems developed concurrently with Windows 8.[8][9]

Microsoft introduced Windows Server 2012 and its developer preview in the BUILD 2011 conference on September 9, 2011.[10] However, unlike Windows 8, the developer preview of Windows Server 2012 was only made available to MSDN subscribers.[11] It included a graphical user interface (GUI) based on Metro design language and a new Server Manager, a graphical application used for server management.[12] On February 16, 2012, Microsoft released an update for developer preview build that extended its expiry date from April 8, 2012 to January 15, 2013.[13]

Before Windows Server 2012 was finalized, two test builds were made public. A public beta version of Windows Server 2012 was released along with the Windows 8 Consumer Preview on February 29, 2012.[8] On April 17, 2012, Microsoft revealed «Windows Server 2012» as the final name for the operating system.[7] The release candidate of Windows Server 2012 was released on May 31, 2012, along with the Windows 8 Release Preview.[9]

The product was released to manufacturing on August 1, 2012 (along with Windows 8) and became generally available on September 4, that year.[4] However, not all editions of Windows Server 2012 were released at the same time. Windows Server 2012 Essentials was released to manufacturing on October 9, 2012[14] and was made generally available on November 1, 2012.[15] As of September 23, 2012, all students subscribed to DreamSpark program can download Windows Server 2012 Standard or Datacenter free of charge.[16]

Windows Server 2012 is based on Windows 8 and is the second version of Windows Server which runs only on 64-bit CPUs.[17] Coupled with fundamental changes in the structure of the client backups and the shared folders, there is no clear method for migrating from the previous version to Windows Server 2012.

Features[edit]

Windows Server 2012 Start screen, including the desktop version of Internet Explorer 11, and the Windows Store. The Windows Store must be manually enabled.

Installation options[edit]

Unlike its predecessor, Windows Server 2012 users can switch between «Server Core» and «Server with a GUI» installation options without a full re-installation. Server Core – an option with a command-line interface only – is now the recommended configuration. There is also a third installation option that allows some GUI elements such as MMC and Server Manager to run, but without the normal desktop, shell or default programs like File Explorer.[12]

User interface[edit]

Server Manager has been redesigned with an emphasis on easing management of multiple servers.[18] The operating system, like Windows 8, uses the Metro-based user interface unless installed in Server Core mode.[19] The Windows Store is available by installing the desktop experience feature from the server manager, but is not installed by default.[20] Windows PowerShell in this version has over 2300 commandlets, compared to around 200 in Windows Server 2008 R2.[21]

Task Manager[edit]

Windows Server 2012 includes a new version of Windows Task Manager together with the old version.[22] In the new version the tabs are hidden by default, showing applications only. In the new Processes tab, the processes are displayed in varying shades of yellow, with darker shades representing heavier resource use.[23] Information found in the older versions are now moved to the new Details tab. The Performance tab shows «CPU», «Memory», «Disk», «Wi-Fi» and «Ethernet» graphs. Unlike the Windows 8 version of Task Manager (which looks similar), the «Disk» activity graph is not enabled by default. The CPU tab no longer displays individual graphs for every logical processor on the system by default, although that remains an option. Additionally, it can display data for each non-uniform memory access (NUMA) node. When displaying data for each logical processor for machines with more than 64 logical processors, the CPU tab now displays simple utilization percentages on heat-mapping tiles.[24] The color used for these heat maps is blue, with darker shades again indicating heavier utilization. Hovering the cursor over any logical processor’s data now shows the NUMA node of that processor and its ID, if applicable. Additionally, a new Startup tab has been added that lists startup applications,[25] however this tab does not exist in Windows Server 2012.[26] The new task manager recognizes when a Windows Store app has the «Suspended» status.

IP address management (IPAM)[edit]

Windows Server 2012 has an IP address management role for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. The IPAM is used for the management and monitoring of Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) servers. Both IPv4 and IPv6 are fully supported.[27]

Active Directory[edit]

Windows Server 2012 has a number of changes to Active Directory from the version shipped with Windows Server 2008 R2. The Active Directory Domain Services installation wizard has been replaced by a new section in Server Manager, and a GUI has been added to the Active Directory Recycle Bin.[28] Multiple password policies can be set in the same domain.[29] Active Directory in Windows Server 2012 is now aware of any changes resulting from virtualization, and virtualized domain controllers can be safely cloned. Upgrades of the domain functional level to Windows Server 2012 are simplified; it can be performed entirely in Server Manager. Active Directory Federation Services is no longer required to be downloaded when installed as a role, and claims which can be used by the Active Directory Federation Services have been introduced into the Kerberos token. Windows Powershell commands used by Active Directory Administrative Center can be viewed in a «Powershell History Viewer».[30][31]

Hyper-V[edit]

Windows Server 2012, along with Windows 8, includes a new version of Hyper-V,[32] as presented at the Microsoft BUILD event.[33] Many new features have been added to Hyper-V, including network virtualization, multi-tenancy, storage resource pools, cross-premises connectivity, and cloud backup. Additionally, many of the former restrictions on resource consumption have been greatly lifted. Each virtual machine in this version of Hyper-V can access up to 64 virtual processors, up to 1 terabyte of memory, and up to 64 terabytes of virtual disk space per virtual hard disk (using a new .vhdx format).[34][35] Up to 1024 virtual machines can be active per host, and up to 8000 can be active per failover cluster.[36] SLAT is a required processor feature for Hyper-V on Windows 8, while for Windows Server 2012 it is only required for the supplementary RemoteFX role.[37]

ReFS[edit]

Main article: ReFS

Resilient File System (ReFS),[38] codenamed «Protogon»,[39] is a new file system in Windows Server 2012 initially intended for file servers that improves on NTFS in some respects. Major new features of ReFS include:[40][41]

Improved reliability for on-disk structures
ReFS uses B+ trees[40] for all on-disk structures including metadata and file data. Metadata and file data are organized into tables similar to a relational database. The file size, number of files in a folder, total volume size and number of folders in a volume are limited by 64-bit numbers; as a result ReFS supports a maximum file size of 16 exabytes, a maximum of 18.4 × 1018 folders and a maximum volume size of 1 yottabyte (with 64 KB clusters) which allows large scalability with no practical limits on file and folder size (hardware restrictions still apply). Free space is counted by a hierarchical allocator which includes three separate tables for large, medium, and small chunks. File names and file paths are each limited to a 32 KB Unicode text string.
Built-in resilience
ReFS employs an allocation-on-write update strategy for metadata,[40] which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata has built-in 64-bit checksums which are stored independently. The file data can have an optional checksum in a separate «integrity stream», in which case the file update strategy also implements allocation-on-write; this is controlled by a new «integrity» attribute applicable to both files and directories. If nevertheless file data or metadata becomes corrupt, the file can be deleted without taking the whole volume offline. As a result of built-in resiliency, administrators do not need to periodically run error-checking tools such as CHKDSK when using ReFS.
Compatibility with existing APIs and technologies
ReFS does not require new system APIs and most file system filters continue to work with ReFS volumes.[40] ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications,[42] symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly[40] integrates with Storage Spaces, a storage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines.[43] ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using background data scrubbing process, which periodically reads all mirror copies and verifies their checksums then replaces bad copies with good ones.

Some NTFS features are not supported in ReFS, including object IDs, short names, file compression, file level encryption (EFS), user data transactions, hard links, extended attributes, and disk quotas.[39][40] Sparse files are supported.[44][45] Support for named streams is not implemented in Windows 8 and Windows Server 2012, though it was later added in Windows 8.1 and Windows Server 2012 R2.[46] ReFS does not itself offer data deduplication.[40] Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces. In Windows Server 2012, automated error-correction with integrity streams is only supported on mirrored spaces; automatic recovery on parity spaces was added in Windows 8.1 and Windows Server 2012 R2.[46] Booting from ReFS is not supported either.

IIS 8.0[edit]

Windows Server 2012 includes version 8.0 of Internet Information Services (IIS). The new version contains new features such as SNI, CPU usage caps for particular websites,[47] centralized management of SSL certificates, WebSocket support and improved support for NUMA, but few other substantial changes were made.[48]

Remote Desktop Protocol 8.0[edit]

Remote Desktop Protocol has new functions such as Adaptive Graphics (progressive rendering and related techniques), automatic selection of TCP or UDP as transport protocol, multi touch support, DirectX 11 support for vGPU, USB redirection supported independently of vGPU support, etc.[49] A «connection quality» button is displayed in the RDP client connection bar for RDP 8.0 connections; clicking on it provides further information about connection, including whether UDP is in use or not.[50]

Scalability[edit]

Windows Server 2012 supports the following maximum hardware specifications.[35][51] Windows Server 2012 improves over its predecessor Windows Server 2008 R2:

Specification Windows Server 2012 Windows Server 2008 R2
Physical processors[a] 64 64
Logical processors
when Hyper-V is disabled
640 256
Logical processors
when Hyper-V is enabled
320[b] 64
Memory 4 TB 2 TB
Failover cluster nodes (in any single cluster) 64 16

System requirements[edit]

Minimum system requirements for Windows Server 2012[53]

Processor 1.4 GHz, x64
Memory 512 MB
Free disk space 32 GB (more if there is at least 16 GB of RAM)

Windows Server 2012 runs only on x86-64 processors. Unlike older versions, Windows Server 2012 does not support Itanium.[5]

Upgrades from Windows Server 2008 and Windows Server 2008 R2 are supported, although upgrades from prior releases are not.[53]

Editions[edit]

Windows Server 2012 has four editions: Foundation, Essentials, Standard and Datacenter.[54][55][56][57][51]

Reception[edit]

Reviews of Windows Server 2012 have been generally positive.[60][61][62] Simon Bisson of ZDNet described it as «ready for the datacenter, today,»[60] while Tim Anderson of The Register said that «The move towards greater modularity, stronger automation and improved virtualisation makes perfect sense in a world of public and private clouds» but remarked that «That said, the capability of Windows to deliver obscure and time-consuming errors is unchanged» and concluded that «Nevertheless, this is a strong upgrade overall.»[61]

InfoWorld noted that Server 2012’s use of Windows 8’s panned «Metro» user interface was countered by Microsoft’s increasing emphasis on the Server Core mode, which had been «fleshed out with new depth and ease-of-use features» and increased use of the «practically mandatory» PowerShell.[63] However, Michael Otey of Windows IT Pro expressed dislike with the new Metro interface and the lack of ability to use the older desktop interface alone, saying that most users of Windows Server manage their servers using the graphical user interface rather than PowerShell.[64]

Paul Ferrill wrote that «Windows Server 2012 Essentials provides all the pieces necessary to provide centralized file storage, client backups, and remote access,»[65] but Tim Anderson contended that «Many businesses that are using SBS2011 and earlier will want to stick with what they have», citing the absence of Exchange, the lack of ability to synchronize with Active Directory Federation Services and the 25-user limit,[66] while Paul Thurott wrote «you should choose Foundation only if you have at least some in-company IT staff and/or are comfortable outsourcing management to a Microsoft partner or solution provider» and «Essentials is, in my mind, ideal for any modern startup of just a few people.»[67]

Windows Server 2012 R2[edit]

A second release, Windows Server 2012 R2, which is derived from the Windows 8.1 codebase, was released to manufacturing on August 27, 2013[68] and became generally available on October 18, 2013, by Microsoft.[69] An updated version, formally designated Windows Server 2012 R2 Update, was released in April 2014.[70][71]

Support Lifecycle[edit]

Microsoft originally planned to end mainstream support for Windows Server 2012 and Windows Server 2012 R2 on January 9, 2018, with extended support ending on January 10, 2023. In order to provide customers the standard transition lifecycle timeline, Microsoft extended Windows Server 2012 and 2012 R2 support in March 2017 by 9 months. Windows Server 2012 reached the end of mainstream support on October 9, 2018 and Extended Support will end on October 10, 2023.[72][73][74]

Microsoft announced in July 2021 that they will distribute Extended Security Updates for Windows Server 2012 and Windows Server 2012 R2 for up to 3 years after the end of Extended Support.[75] For Windows Server 2012 and Windows Server 2012 R2, these updates will last until October 13, 2026. This will mark the final end of the Windows NT 6.2 product line after 14 years, 2 months and 12 days and will also mark the final end of the Windows NT 6.3 product line after 13 years, 1 month and 16 days.

See also[edit]

  • Comparison of Microsoft Windows versions
  • Comparison of operating systems
  • History of Microsoft Windows
  • List of operating systems
  • Microsoft Servers

Notes[edit]

  1. ^ Applies to Windows Server 2008 R2 and 2012 Datacenter and Windows Server 2012 Standard only. Other editions support less.
  2. ^ Each virtualized partition, including the host itself, can use up to 64 processors.[52]
  3. ^ a b Each license of Windows Server 2012 Standard or Datacenter allows up to two processor chips. Each license of Windows Server 2012 Standard allows up to two virtual instances of Windows Server 2012 Standard on that physical server. If more virtual instances of Windows Server 2012 Standard are needed, each additional license of Windows Server 2012 allows up to two more virtual instances of Windows Server 2012 Standard, even though the physical server itself may have sufficient licenses for its processor chip count. Because Windows Server 2012 Datacenter has no limit on the number of virtual instances per licensed server, only enough licenses for the physical server are needed for any number of virtual instances of Windows Server 2012 Datacenter. If the number of processor chips or virtual instances is an odd number, the number of licenses required is the same as the next even number. For example, a single-processor-chip server would still require 1 license, the same as if the server were two-processor-chip and a five-processor-chip server would require 3 licenses, the same as if the server were six-processor-chip, and if 15 virtual instances of Windows Server 2012 Standard are needed on one server, 8 licenses of Windows Server 2012, which can cover up to 16 virtual instances, are needed (assuming, in this example, that the processor chip count does not exceed 16).
  4. ^ For the Standard and Datacenter editions, each user or device accessing the software must have a client access license (CAL) assigned (either per-user or per-device), so there may be no more simultaneous users than the number of client-access licenses, except up to 2 simultaneous users purely to administer the server software, or for running virtualization or web workloads. Remote Desktop Services requires an additional CAL separate from the aforementioned CAL.
  5. ^ If the number of physical processors in a particular server is under 64, the limit is determined by the quantity of licenses assigned to that server. In that case, the number of physical processors cannot exceed twice the number of licenses assigned to the server.

References[edit]

  1. ^ http://blogs.technet.com/b/windowsserver/archive/2012/08/01/windows-server-2012-released-to-manufacturing.aspx
  2. ^ http://blogs.technet.com/b/windowsserver/archive/2012/08/01/windows-server-2012-released-to-manufacturing.aspx
  3. ^ a b c «Microsoft Product Lifecycle». Microsoft Support. Microsoft. January 2012. Archived from the original on February 27, 2013. Retrieved October 10, 2012.
  4. ^ a b Snover, Jeffrey (August 1, 2012). «Windows Server 2012 released to manufacturing!». Windows Server Blog. Microsoft. TechNet blogs. Archived from the original on December 22, 2015. Retrieved January 29, 2013.
  5. ^ a b Foley, Mary Jo (April 5, 2010). «Microsoft pulls the plug on future Itanium support». ZDNet. CBS Interactive. Archived from the original on August 12, 2012. Retrieved January 1, 2012.
  6. ^ «Windows Server 2012 approximately equal to Windows Server 2008». SmartProfile. August 25, 2017.
  7. ^ a b Foley, Mary Jo (April 17, 2012). «Windows Server «8» officially dubbed Windows Server 2012″. ZDNet. CBS Interactive. Archived from the original on November 19, 2014. Retrieved April 17, 2012.
  8. ^ a b Savill, John (February 29, 2012). «Q: Where can I download and get more information on Windows Server «8» Beta and Windows 8 Consumer Preview?». Windows IT Pro. Penton Media. Retrieved February 29, 2012.
  9. ^ a b Snover, Jeffrey (April 24, 2012). «Windows Server 2012 Release Candidate Timing». Windows Server Blog. Microsoft. TechNet blogs. Archived from the original on February 11, 2013. Retrieved January 21, 2013.
  10. ^ Laing, Bill (September 9, 2011). «Windows Server 8: An Introduction». Server & Cloud Blog. Microsoft. TechNet blogs. Archived from the original on October 28, 2012. Retrieved January 23, 2013.
  11. ^ «Download Windows Server 8 Developer Preview via MSDN». Softpedia. SoftNews SRL. September 14, 2011. Archived from the original on May 8, 2012. Retrieved January 25, 2013.
  12. ^ a b Bisson, Simon (September 14, 2011). «Windows 8 Server Developer Preview». ZDNet. CBS Interactive. Archived from the original on December 2, 2014. Retrieved January 1, 2012.
  13. ^ Arghire, Ionut (February 18, 2012). «Windows 8 Developer Preview Expiration Date Gets Postponed». Softpedia. SoftNews SRL. Archived from the original on October 13, 2013. Retrieved July 15, 2013.
  14. ^ Snover, Jeffrey. «Windows Server 2012 Essentials released to manufacturing, available for evaluation today!». Windows Server Blog!. Microsoft. TechNet blogs. Archived from the original on January 17, 2013. Retrieved January 25, 2013.
  15. ^ «Windows Server 2012 Essentials reaches general availability!». Windows Server Blog!. Microsoft. TechNet blogs. Archived from the original on April 29, 2015. Retrieved January 25, 2013.
  16. ^ «Windows Server 2012». Microsoft DreamSpark. Microsoft. Archived from the original on August 19, 2016. Retrieved January 25, 2013.
  17. ^ Joel Hruska (May 18, 2007). «Windows Server 2008 declared 32-bit’s last hurrah». Ars Technica. Archived from the original on August 24, 2021. Retrieved August 24, 2021.
  18. ^ Callaham, John (September 9, 2011). «Windows Server 8 Screenshot Leak Shows New UI». Neowin.net. Neowin LLC. Archived from the original on February 27, 2013. Retrieved January 21, 2013.
  19. ^ Wilhelm, Alex (September 9, 2011). «Windows Server 8 Screenshot leaks». News. The Next Web. Archived from the original on August 28, 2012. Retrieved January 1, 2012.
  20. ^ «Managing Privacy: Windows Store and Resulting Internet Communication». TechNet. Microsoft. Archived from the original on October 6, 2014. Retrieved January 30, 2014.
  21. ^ Thurott, Paul (November 2, 2011). «Windows Server «8» Preview (Unedited, Complete Version)». Paul Thurott’s Supersite for Windows. Penton Media. Archived from the original on March 20, 2012. Retrieved January 1, 2012.
  22. ^ Williams, Mike; Hanson, Matt (October 25, 2012). «Windows 8 tips: mastering the interface». Techradar. Future Publishing. Archived from the original on January 22, 2013. Retrieved January 22, 2013.
  23. ^ Haveson, Ryan (October 13, 2011). Sinofsky, Steven (ed.). «The Windows 8 Task Manager». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on January 25, 2013. Retrieved January 31, 2013.
  24. ^ «Using Task Manager with 64+ logical processors». Building Windows 8. MSDN blogs. Archived from the original on November 6, 2015. Retrieved October 29, 2011.
  25. ^ «How to Get the Most out of New Windows 8 Task Manager?». October 24, 2011. Archived from the original on April 7, 2012. Retrieved October 29, 2011.
  26. ^ Hu, Aaron. «How to disable start-up items in windows server 2012». TechNet Forums. Microsoft. Archived from the original on February 27, 2013. Retrieved October 14, 2012. The Startup tab is not present on Windows Server 2012. It is only on Windows 8.
  27. ^ «IP Address Management (IPAM) Overview». TechNet Library. Microsoft. February 29, 2012. Archived from the original on May 2, 2013. Retrieved January 21, 2013.
  28. ^ Shields, Greg (July 3, 2012). «Quick Guide: What’s New in Windows Server 2012 Active Directory». Redmond magazine. 1105 Redmond Media. Archived from the original on January 21, 2013. Retrieved January 21, 2013.
  29. ^ Sherif Mahmoud, Tamer (May 29, 2012). «Creating fine grained password policies through GUI Windows server (sic) 2012 «Server 8 beta»«. Team blog of MCS @ Middle East and Africa. Microsoft. TechNet blogs. Archived from the original on March 7, 2013. Retrieved January 21, 2013.
  30. ^ Bruzzese, J. Peter (October 26, 2011). «Windows Server 8: The 4 best new Active Directory features». InfoWorld. IDG. Archived from the original on May 12, 2012. Retrieved January 1, 2012.
  31. ^ Deuby, Sean (September 14, 2011). «What’s New in Windows Server 2012 Active Directory». Windows IT Pro. Penton Media. Archived from the original on February 17, 2015. Retrieved July 16, 2013.
  32. ^ Herrmann, Max; Laing, Bill; Vecchiet, Manlio; Neil, Mike (September 14, 2011). «Day 2: Windows Server 8». Channel 9. Microsoft. Archived from the original on March 17, 2012. Retrieved February 2, 2013.
  33. ^ «BUILD2011: Windows Server 8». Channel 9. Anaheim, California: Microsoft. September 13–16, 2011. Archived from the original on October 7, 2012. Retrieved February 2, 2013.
  34. ^ «Server Virtualization Features». Microsoft. Archived from the original on October 4, 2012. Retrieved October 5, 2012.
  35. ^ a b Savill, John (October 28, 2011). «Q: What are Windows Server 8’s Scalability Numbers?». Windows IT Pro. Penton Media. Retrieved November 5, 2011.
  36. ^ Garg, Pankaj; Tan, See-Mong (September 14, 2011). «Day 2: A deep dive into Hyper-V Networking». Channel 9. Microsoft. Archived from the original on March 10, 2012. Retrieved January 22, 2013.
  37. ^ Savil, John (October 21, 2011). «Q: Will Windows Server 8 require the processor to support SLAT?». Windows IT Pro. Penton Media. Retrieved November 5, 2011.
  38. ^ Lucas, Martin (January 1, 2013). «Windows Server 2012: Does ReFS replace NTFS? When should I use it?». Ask Premier Field Engineering (PFE) Platforms. Microsoft. TechNet blogs. Archived from the original on June 2, 2013. Retrieved January 20, 2013.
  39. ^ a b Foley, Mary Jo (January 16, 2012). «Microsoft goes public with plans for its new Windows 8 file system». ZDNet. CBS Interactive. Archived from the original on May 21, 2013. Retrieved January 21, 2013.
  40. ^ a b c d e f g Verma, Surendra (January 16, 2012). Sinofsky, Steven (ed.). «Building the next generation file system for Windows: ReFS». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on May 26, 2013. Retrieved January 20, 2013.
  41. ^ Meyer, David (January 17, 2012). «Microsoft takes wraps off new Windows file system». ZDNet. CBS Interactive. Archived from the original on May 21, 2013. Retrieved January 20, 2013.
  42. ^ «ReadDirectoryChangesW function». MSDN Library. Microsoft. November 8, 2012. Archived from the original on May 4, 2013. Retrieved January 21, 2013.
  43. ^ Nagar, Rajeev (January 5, 2012). Sinofsky, Steven (ed.). «Virtualizing storage for scale, resiliency, and efficiency». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on May 9, 2013. Retrieved January 18, 2013.
  44. ^ «Windows Server 2012: Does ReFS replace NTFS? When should I use it?». January 2, 2013. Archived from the original on June 2, 2013. Retrieved March 31, 2013.
  45. ^ «ReFS (Resilient File System) supports sparse files». Archived from the original on March 15, 2013. Retrieved March 31, 2013.
  46. ^ a b «Resilient File System Overview». TechNet Library. Microsoft. February 29, 2012. Archived from the original on September 1, 2017. Retrieved December 25, 2013.
  47. ^ Mackie, Kurt. «Microsoft Touts IIS 8 Improvements». Redmond magazine. 1105 Redmond Media. Archived from the original on May 15, 2013. Retrieved August 17, 2012.
  48. ^ Anderson, Tim (September 4, 2012). «Windows Server 2012: inside Microsoft’s Enterprise Server OS». Computer Weekly. TechTarget. Archived from the original on January 22, 2013. Retrieved January 21, 2013.
  49. ^ «Windows Server 2012 Remote Desktop Services (RDS) – Windows Server Blog – Site Home – TechNet Blogs». Blogs.technet.com. May 8, 2012. Archived from the original on October 5, 2013. Retrieved February 13, 2014.
  50. ^ «Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2». Support.microsoft.com. Archived from the original on October 25, 2012. Retrieved February 13, 2014.
  51. ^ a b c Seldam, Matthijs ten (October 13, 2012). «Windows Server — Sockets, Logical Processors, Symmetric Multi Threading». Matthijs’s blog. Microsoft. TechNet blogs. Archived from the original on November 2, 2012. Retrieved October 14, 2012.
  52. ^ «Logical Processor count changes after enabling Hyper-V role on Windows Server 2012». March 28, 2013. Archived from the original on May 15, 2013. Retrieved April 1, 2013.
  53. ^ a b «Installing Windows Server 2012». TechNet Library. Microsoft. System requirements. Archived from the original on October 31, 2012. Retrieved June 10, 2012.
  54. ^ Foley, Mary Jo (July 5, 2012). «Microsoft goes public with Windows Server 2012 versions, licensing». ZDNet. CBS Interactive. Archived from the original on November 9, 2012. Retrieved July 5, 2012.
  55. ^ «Purchasing Windows Server 2012». Microsoft. Archived from the original on December 7, 2015. Retrieved December 8, 2015.
  56. ^ «Windows Server 2012 Licensing and Pricing FAQ» (PDF). Microsoft. Archived (PDF) from the original on December 2, 2012. Retrieved July 5, 2012.
  57. ^ «Windows Server 2012 Licensing Data Sheet» (PDF). Microsoft. Archived from the original (PDF) on July 22, 2012.
  58. ^ «Introduction to Windows Server 2012 Foundation». TechNet. Microsoft. Archived from the original on November 5, 2012. Retrieved December 8, 2015.
  59. ^ «Introduction to Windows Server 2012 Foundation». TechNet Library. Microsoft. Archived from the original on November 5, 2012. Retrieved November 4, 2012.
  60. ^ a b Bisson, Simon (September 13, 2012). «Windows Server 2012: RTM review». ZDNet. CBS Interactive. Archived from the original on January 28, 2013. Retrieved January 19, 2013.
  61. ^ a b Anderson, Tim (September 5, 2012). «Windows Server 2012: Smarter, stronger, frustrating». The Register. Situation Publishing. Archived from the original on December 26, 2012. Retrieved January 19, 2013.
  62. ^ Ferrill, Paul (October 3, 2012). «Windows Server 2012 Review: The Bottom Line». ServerWatch. QuinStreet. Archived from the original on January 15, 2013. Retrieved January 19, 2013.
  63. ^ Rist, Oliver (June 27, 2012). «Review: Weighing Windows Server 2012». InfoWorld. IDG. Archived from the original on March 10, 2013. Retrieved January 19, 2013.
  64. ^ Otey, Michael (July 25, 2012). «Is Microsoft Trying to Kill Windows Server?». Windows IT Pro. Penton Media. Archived from the original on January 17, 2013. Retrieved January 19, 2013.
  65. ^ Ferrill, Paul (December 16, 2012). «A Hands-on Look at Windows Server 2012 Essentials». ServerWatch. QuinStreet. Archived from the original on January 15, 2013. Retrieved January 20, 2013.
  66. ^ Anderson, Tim (December 21, 2012). «Windows Server 2012 Essentials review». PC Pro. Dennis Publishing. Archived from the original on January 6, 2013. Retrieved January 20, 2013.
  67. ^ Thurott, Paul (October 2, 2012). «Windows Server 2012: Foundation vs. Essentials». Windows IT Pro. Penton Media. Archived from the original on October 8, 2012. Retrieved January 20, 2013.
  68. ^ «Windows Server 2012 R2 Reaches the Release to Manufacturing (RTM) Milestone». Microsoft Docs. August 27, 2013. Archived from the original on January 14, 2020. Retrieved January 13, 2015.
  69. ^ «Save the date: Windows Server 2012 R2, Windows System Center 2012 R2 and Windows Intune update coming Oct. 18 — The Official Microsoft Blog — Site Home — TechNet Blogs». Microsoft Docs. August 14, 2013. Archived from the original on April 1, 2014. Retrieved February 10, 2014.
  70. ^ «August updates for Windows 8.1 and Windows Server 2012 R2 | Blogging Windows». Archived from the original on September 6, 2015. Retrieved November 14, 2014.
  71. ^ Resseler, Mike (August 27, 2013). «eBook — What’s new in Windows Server 2012 R2 Preview». Veeam Software. Archived from the original on April 5, 2014. Retrieved September 3, 2013.
  72. ^ «Windows Server 2012». Microsoft Docs. Archived from the original on July 28, 2021. Retrieved July 28, 2021.
  73. ^ «Microsoft Extends Windows Server 2012 Support — Redmondmag.com». Redmondmag. Archived from the original on July 28, 2021. Retrieved July 28, 2021.
  74. ^ «Windows Server 2012 Nears End of life». February 3, 2020. Archived from the original on January 26, 2021. Retrieved July 28, 2021.
  75. ^ «Product Lifecycle FAQ — Extended Security Updates». docs.microsoft.com. Archived from the original on July 29, 2021. Retrieved July 28, 2021.

Further reading[edit]

  • Stanek, William (2013). Windows Server 2012 Inside Out. Microsoft Press. ISBN 978-0-7356-6631-3.
  • Stanek, William (2014). Windows Server 2012 R2 Inside Out Volume 1: Configuration, Storage, & Essentials. Microsoft Press. ISBN 978-0-7356-8267-2.
  • Stanek, William (2014). Windows Server 2012 R2 Inside Out Volume 2: Services, Security, & Infrastructure. Microsoft Press. ISBN 978-0-7356-8255-9.

External links[edit]

  • Official website
  • Windows Server 2012 R2 and Windows Server 2012 on TechNet
  • Windows Server 2012 R2 on MSDN
  • Windows Server 2012 on MSDN
  • Tutorials and Lab Manual Articles of Windows Server 2012 R2

Задаваясь вопросом, какую версию Windows Server выбрать для своего бизнеса, пользователи, как правило, сталкиваются с большим разнообразием, и далеко не всегда понятно как выбрать наиболее подходящий вариант. У операционной системы Windows Server существуют не только разные версии, но и разные редакции. Давайте разберемcя в чем же отличия между ними.

Что такое версия Windows Server?

В 90-е годы, во времена Windows NT, каждая версия Windows Server имела уникальный номер. Например, у Windows NT были номера 3.1, 3.51 и 4.0. Но начиная с 2000 года Microsoft вместо номера начала добавлять после названия год запуска операционной системы: Microsoft Windows 2000, Windows Server 2003, 2008 (которая также имела версию R2), 2012 (также с R2), 2016 и 2019, и т.д.

Каждая новая версия Microsoft Windows Server представляет новые функциональные возможности. Например, виртуализация Hyper-V, Server Core и BitLocker были представлены в Windows Server 2008, контейнеры Windows и Nano Server были представлены в Windows Server 2016, а Windows Server 2019 принес с собой Windows Admin Center — новый способ удаленного администрирования серверной инфраструктуры, улучшения гиперконвергентной инфраструктуры и глубокую поддержку подсистемы Linux.

Что такое завершение поддержки?

Как говорится, ничто не вечно. И в определенный момент Microsoft прекращает выпуск патчей для устаревшего программного обеспечения. Дата, до которой Microsoft выпускает обновления для продукта, называется датой окончания поддержки. И после того, как эта дата пройдет, устаревшая версия ОС станет легкой мишенью для вредоносных программ, поскольку она больше не будет получать обновления безопасности и, следовательно, будет уязвима для новых эксплоитов.

Операционные системы Microsoft обычно поддерживаются не менее 10 лет. Например, популярный Windows Server 2003, выпущенный в апреле 2003 года, имел расширенную поддержку, которая закончились в 2015 году. Расширенная поддержка Windows Server 2008 R2 должна закончиться в январе 2020 года, а Windows Server 2012 R2 продолжит получать обновления по крайней мере до октября 2023 года. Версии Server 2016 и 2019 будут получать обновления по 2027 и 2029 год соответственно. Поэтому в целях безопасности организациям на самом деле следует использовать только свежие версии Windows Server.

Что такое редакция Windows Server?

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

То же самое касается выпусков Windows Server. Каждый вариант включает в себя функциональность, которая подходит для разных компаний, в зависимости от их размера и бюджета. Например, разные редакции могут поддерживать разное количество пользователей.

Различия между редакциями Windows Server 2012 R2

Чтобы помочь понять некоторые различия между редакциями ОС, давайте разберем их на примере Windows Server 2012 R2:

  • Foundation — серверная ОС общего назначения, лучше всего подходящая для серверов нижнего уровня. ОС поддерживает только один процессор и 32 ГБ RAM. Редакция Foundation (недоступная в Windows Server 2016) ограничена 15 пользователями, что делает ее пригодной только для небольших офисов. Foundation доступен только через OEM-производителей, что обычно означает, что он предустановлен на компьютерах, которые вы покупаете у таких компаний, как Dell и HPE.
  • Essentials (ранее SBS или Small Business Server) — это простое в настройке серверное решение, которое поддерживает до 25 пользователей и 50 устройств, что делает его подходящим для небольших офисов. Essentials поддерживает более мощное оборудование с объемом оперативной памяти до 64 ГБ и двумя процессорами. В отличие от других выпусков Windows Server, в Essentials предварительно настроены роли, такие как Active Directory, DNS, файловые службы, IIS и удаленный рабочий стол, что делает его идеальным для организаций с менее развитым ИТ-направлением или менее опытным ИТ-персоналом.
  • Standard не ограничивает пользователей, но в отличие от Foundation и Essentials вам придется отдельно приобретать клиентские лицензии (CAL) в зависимости от того, сколько людей вам нужно поддерживать. Standard поддерживает максимум 4 ТБ RAM, а каждая приобретаемая лицензия распространяется на два процессора. Если вы заинтересованы в виртуализации, этот выпуск позволит вам использовать гипервизор Hyper-V для запуска до двух виртуальных экземпляров операционной системы (дополнительные виртуальные экземпляры Windows Server потребуют дополнительных затрат) на одном физическом оборудовании, что делает редакцию Standard подходящей для легкой виртуализированной среды.
  • Datacenter — это самая лучшая и самая дорогая редакция Windows Server. Windows Server 2012 R2 Datacenter практически идентичен стандартной версии с одним большим исключением. С лицензией Datacenter вы можете запускать неограниченное количество виртуальных экземпляров с Windows Server в качестве гостевой ОС на одном двухпроцессорном компьютере. Эта небольшая разница имеет большое влияние, так как компании могут сэкономить, запустив десятки экземпляров ОС на одном сервере.

Различия между редакциями Windows Server 2012 R2

Различия между редакциями Windows Server 2016 и 2019

  • Hyper-V — это бесплатная редакция Windows Server, предназначенная только для запуска роли гипервизора Hyper-V. Его цель — быть гипервизором для вашей виртуальной среды. У него нет графического интерфейса. По сути, это урезанная версия Server Core. Вы будете использовать sconfig.cmd, чтобы включить гипервизор, а затем управлять средой с помощью диспетчера Hyper-V (как часть RSAT) с рабочей станции Windows 10 в вашей сети. Рекомендуется использовать именно эту редакцию для вашего гипервизора, чтобы сохранить чистоту и простоту лицензирования.
  • Essentials — идеально подходит как для малого и среднего бизнеса, так и для людей с потребностями в базовых функциях сервера. Графический интерфейс в значительной степени такой же, как и в Standard, за исключением мастера настройки Essentials.

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

Модель лицензирования
На базе процессора. Клиентские лицензии не требуются, но вы ограничены 25 пользователями и 50 устройствами, подключающимися к серверу.

Аппаратные ограничения
Essentials ограничен до 64 ГБ RAM и 2 CPU на компьютере, на котором он установлен.

  • Standard — идеально подходит для любой компании или для лиц, которым требуются расширенные функции, но при этом они не будут интенсивно виртуализироваться.

Права на виртуализацию
Разрешено запускать до двух виртуальных машин или контейнеров Hyper-V или один физический экземпляр со стандартной лицензией. Если вы используете роль Hyper-V только на физическом экземпляре, то можете использовать ее в качестве хоста Hyper-V, а затем разместить на этом хосте две виртуальные машины Hyper-V. Если вы хотите использовать несколько ролей на физическом экземпляре, вы не можете запускать виртуальную машину поверх с одной и той же лицензией.

Модель лицензирования
Основанная на ядре. Клиентские лицензии необходимы для каждого пользователя или устройства, которые подключаются косвенно или напрямую к серверу. Например, если вы используете сервер в качестве файлового сервера, вам потребуется лицензия CAL для каждой учетной записи пользователя или компьютера, которые обращаются к этому файловому серверу в сети.

Аппаратные ограничения
Стандарт ограничен максимум 24 ТБ оперативной памяти и 512 ядрами.

  • Datacenter — идеально подходит для любой компании с высокой степенью виртуализации. Вы приобретаете лицензию в зависимости от того, сколько ядер есть у ваших хостов, на которых может жить любая виртуальная машина с версией Datacenter (запускаться или потенциально запускаться после Vmotion). Это лицензирование, на первый взгляд, кажется дорогим, но оно позволяет создавать неограниченное количество виртуальных машин, работающих под управлением Datacenter на хостах, которые вы учитывали. Если у вас небольшое количество хостов (а впоследствии и ядер) и большое количество потенциальных виртуальных машин, тогда эта лицензия не представляет никакой сложности.

Права на виртуализацию
Неограниченное количество виртуальных машин или контейнеров Hyper-V. Как было озвучено выше, вы будете покупать лицензии в зависимости от того, сколько ядер у вас на хостах. На этом этапе вы можете запустить на хостах столько угодно виртуальных машин, используя любые роли.

Модель лицензирования
Основанная на ядрах. Убедитесь, что вы случайно не выбрали этот выпуск при установке на физический сервер, на котором не размещаются виртуальные машины. Клиентские лицензии необходимы для каждого пользователя или устройства, которые подключаются косвенно или напрямую к серверам в вашей среде.

Различия в лицензировании Windows Server 2016 и новее

Хотя цены на Windows Server 2012 R2, 2016, 2019 одинаковы, если вы используете стандартную лицензию или лицензию Datacenter на Windows Server 2016 или новее, есть некоторые ключевые изменения, о которых вам необходимо знать. Прежде всего, в то время как лицензии Windows Server исторически продавались для каждого процессора / сокета, в Windows Server 2016 модель лицензирования переключалась на каждое ядро.

Таким образом, если у вас есть сервер, содержащий 2 процессора с 24 ядрами , в Windows Server 2012 вам нужно будет купить только одну лицензию Standard или Datacenter. В Windows Server 2016 вам придется покупать лицензии на все 24 ядра. Это становится довольно сложно, так как есть много правил, но главное — если у вас есть 16-ядерный сервер, затраты будут примерно такими же. Однако лицензирование ОС может быть более дорогим на серверах с более высокой плотностью ядра.

Несмотря на изменение лицензии на ядро, правила виртуализации остаются такими же в Windows Server 2016 и новее. После того, как вы лицензировали все свои ядра на сервере, со стандартной версией вы получаете 2 лицензии гостевой ОС Windows Server по сравнению с неограниченным количеством в версии Datacenter.

Кроме того, набор функций в Windows Server 2012 Standard и Datacenter был одинаковым. Но некоторые функции Windows Server 2016, например, такие, как Storage Spaces Direct или экранированные виртуальные машины, доступны только в выпуске Datacenter.

Сравнение параметров установки Windows Server 2016 и 2019

В редакциях Standard и Datacenter можно выбрать различные варианты установки. Эти варианты влияют на то, какие функции будут доступны после установки, такие как наличие графического интерфейса пользователя и набор сервисов. Присутствуют следующие варианты установки:

  • Desktop Experience (с графическим интерфейсом);
  • Core;
  • Nano.

Desktop Experience — это вариант установки, с которым знакомо большинство людей. Этот параметр устанавливает большинство функций и ролей из коробки, включая интерфейс графического интерфейса рабочего стола. Вы получите Диспетчер серверов, который позволяет добавлять и удалять роли и компоненты. Преимущество в том, что система может быть проще в управлении для людей, привыкших использовать графический интерфейс. Недостаток в том, что у вас появляется больше обновлений, перезагрузок и открытых портов с которыми предстоит иметь дело.

Узнайте больше от Microsoft здесь.

В Server Core отсутствует графический интерфейс и несколько ролей, которые устанавливаются по умолчанию под опцией Desktop Experience. Серверное ядро имеет меньший объем занимаемого дискового пространства и, следовательно, меньшую область атаки из-за меньшей кодовой базы. Здесь также меньше обновлений, перезагрузок и открытых портов для работы. Это отличный вариант для серверов инфраструктуры, таких как контроллеры домена Active Directory и DNS-серверы.

В этой редакции отсутствуют инструменты специальных возможностей, встроенные инструменты настройки сервера и поддержка звука. Эта версия без излишеств. Не лишним будет убедиться, что вы знакомы с администрированием на основе командной строки.

Подробнее об этом можно прочитать на сайте Microsoft.

Nano

Начиная с Windows Server 2019, Nano доступен только как контейнеризированный образ операционной системы. Он предназначен для запуска в качестве контейнера внутри хоста контейнеров, такого как Server Core, упомянутого выше. Если вы опираетесь на контейнерные приложения, предназначенные для серверных ОС, то эту версию вы будете использовать для компиляции этих приложений.

Nano можно развернуть с помощью версий Standard или Datacenter, но у вас должна быть прикреплена Software Assurance к лицензированию хост-сервера. Узнать об этом подробнее можно на сайте Microsoft.

This is a good article. Click here for more information.

From Wikipedia, the free encyclopedia

Windows Server 2012

Version of the Windows NT operating system

Screenshot of Windows Server 2012, showing the Server Manager application which is automatically opened when an administrator logs on, taskbar, and the blue color of Aero Lite

Developer Microsoft
OS family Windows Server
Working state Current
Source model
  • Closed-source
  • Source-available (through Shared Source Initiative)
Released to
manufacturing
August 1, 2012; 11 years ago
General
availability
September 4, 2012; 11 years ago[1]
Latest release 6.2 (Build 9200) / August 1, 2012; 11 years ago[2]
Marketing target Business
Update method Windows Update, Windows Server Update Services, SCCM
Platforms x86-64
Kernel type Hybrid (Windows NT kernel)
Default
user interface
Windows shell (GUI)
License Commercial proprietary software
Preceded by Windows Server 2008 R2 (2009)
Succeeded by Windows Server 2012 R2 (2013)
Official website Windows Server 2012 (archived at Wayback Machine))
Support status
  • Start date: October 30, 2012[3]
  • Mainstream support ended on October 9, 2018[3]
  • Extended support until October 10, 2023[3]
  • Paid support via the Extended Security Updates program until October 13, 2026, only for volume licensed editions.

Windows Server 2012, codenamed «Windows Server 8», is the sixth version of the Windows Server operating system by Microsoft, as part of the Windows NT family of operating systems. It is the server version of Windows based on Windows 8 and succeeds Windows Server 2008 R2, which is derived from the Windows 7 codebase, released nearly three years earlier. Two pre-release versions, a developer preview and a beta version, were released during development. The software was officially launched on September 4, 2012, which was the month before the release of Windows 8.[4] It was succeeded by Windows Server 2012 R2 in 2013. Mainstream support for Windows Server 2012 ended on October 9, 2018, and extended support will end on October 10, 2023. Windows Server 2012 is eligible for the paid Extended Security Updates (ESU) program, which offers continued security updates until October 13, 2026.

Windows Server 2012 removed support for Itanium and processors without PAE, SSE2 and NX.[5] Four editions were released. Various features were added or improved over Windows Server 2008 R2 (with many placing an emphasis on cloud computing), such as an updated version of Hyper-V, an IP address management role, a new version of Windows Task Manager, and ReFS, a new file system. Windows Server 2012 received generally good reviews in spite of having included the same controversial Metro-based user interface seen in Windows 8, which includes the Charms Bar for quick access to settings in the desktop environment.

Windows Server 2012 is the final version of Windows Server that supports processors without CMPXCHG16b, PrefetchW, LAHF and SAHF. Its successor, Windows Server 2012 R2, requires a processor with CMPXCHG16b, PrefetchW, LAHF and SAHF in any supported architecture.

As of April 2017, 35% of servers were running Windows Server 2012, surpassing usage share of Windows Server 2008.[6]

History[edit]

Windows Server 2012, codenamed «Windows Server 8»,[7] is the fifth release of Windows Server family of operating systems developed concurrently with Windows 8.[8][9]

Microsoft introduced Windows Server 2012 and its developer preview in the BUILD 2011 conference on September 9, 2011.[10] However, unlike Windows 8, the developer preview of Windows Server 2012 was only made available to MSDN subscribers.[11] It included a graphical user interface (GUI) based on Metro design language and a new Server Manager, a graphical application used for server management.[12] On February 16, 2012, Microsoft released an update for developer preview build that extended its expiry date from April 8, 2012 to January 15, 2013.[13]

Before Windows Server 2012 was finalized, two test builds were made public. A public beta version of Windows Server 2012 was released along with the Windows 8 Consumer Preview on February 29, 2012.[8] On April 17, 2012, Microsoft revealed «Windows Server 2012» as the final name for the operating system.[7] The release candidate of Windows Server 2012 was released on May 31, 2012, along with the Windows 8 Release Preview.[9]

The product was released to manufacturing on August 1, 2012 (along with Windows 8) and became generally available on September 4, that year.[4] However, not all editions of Windows Server 2012 were released at the same time. Windows Server 2012 Essentials was released to manufacturing on October 9, 2012[14] and was made generally available on November 1, 2012.[15] As of September 23, 2012, all students subscribed to DreamSpark program can download Windows Server 2012 Standard or Datacenter free of charge.[16]

Windows Server 2012 is based on Windows 8 and is the second version of Windows Server which runs only on 64-bit CPUs.[17] Coupled with fundamental changes in the structure of the client backups and the shared folders, there is no clear method for migrating from the previous version to Windows Server 2012.

Features[edit]

Windows Server 2012 Start screen, including the desktop version of Internet Explorer 11, and the Windows Store. The Windows Store must be manually enabled.

Installation options[edit]

Unlike its predecessor, Windows Server 2012 users can switch between «Server Core» and «Server with a GUI» installation options without a full re-installation. Server Core – an option with a command-line interface only – is now the recommended configuration. There is also a third installation option that allows some GUI elements such as MMC and Server Manager to run, but without the normal desktop, shell or default programs like File Explorer.[12]

User interface[edit]

Server Manager has been redesigned with an emphasis on easing management of multiple servers.[18] The operating system, like Windows 8, uses the Metro-based user interface unless installed in Server Core mode.[19] The Windows Store is available by installing the desktop experience feature from the server manager, but is not installed by default.[20] Windows PowerShell in this version has over 2300 commandlets, compared to around 200 in Windows Server 2008 R2.[21]

Task Manager[edit]

Windows Server 2012 includes a new version of Windows Task Manager together with the old version.[22] In the new version the tabs are hidden by default, showing applications only. In the new Processes tab, the processes are displayed in varying shades of yellow, with darker shades representing heavier resource use.[23] Information found in the older versions are now moved to the new Details tab. The Performance tab shows «CPU», «Memory», «Disk», «Wi-Fi» and «Ethernet» graphs. Unlike the Windows 8 version of Task Manager (which looks similar), the «Disk» activity graph is not enabled by default. The CPU tab no longer displays individual graphs for every logical processor on the system by default, although that remains an option. Additionally, it can display data for each non-uniform memory access (NUMA) node. When displaying data for each logical processor for machines with more than 64 logical processors, the CPU tab now displays simple utilization percentages on heat-mapping tiles.[24] The color used for these heat maps is blue, with darker shades again indicating heavier utilization. Hovering the cursor over any logical processor’s data now shows the NUMA node of that processor and its ID, if applicable. Additionally, a new Startup tab has been added that lists startup applications,[25] however this tab does not exist in Windows Server 2012.[26] The new task manager recognizes when a Windows Store app has the «Suspended» status.

IP address management (IPAM)[edit]

Windows Server 2012 has an IP address management role for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. The IPAM is used for the management and monitoring of Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) servers. Both IPv4 and IPv6 are fully supported.[27]

Active Directory[edit]

Windows Server 2012 has a number of changes to Active Directory from the version shipped with Windows Server 2008 R2. The Active Directory Domain Services installation wizard has been replaced by a new section in Server Manager, and a GUI has been added to the Active Directory Recycle Bin.[28] Multiple password policies can be set in the same domain.[29] Active Directory in Windows Server 2012 is now aware of any changes resulting from virtualization, and virtualized domain controllers can be safely cloned. Upgrades of the domain functional level to Windows Server 2012 are simplified; it can be performed entirely in Server Manager. Active Directory Federation Services is no longer required to be downloaded when installed as a role, and claims which can be used by the Active Directory Federation Services have been introduced into the Kerberos token. Windows Powershell commands used by Active Directory Administrative Center can be viewed in a «Powershell History Viewer».[30][31]

Hyper-V[edit]

Windows Server 2012, along with Windows 8, includes a new version of Hyper-V,[32] as presented at the Microsoft BUILD event.[33] Many new features have been added to Hyper-V, including network virtualization, multi-tenancy, storage resource pools, cross-premises connectivity, and cloud backup. Additionally, many of the former restrictions on resource consumption have been greatly lifted. Each virtual machine in this version of Hyper-V can access up to 64 virtual processors, up to 1 terabyte of memory, and up to 64 terabytes of virtual disk space per virtual hard disk (using a new .vhdx format).[34][35] Up to 1024 virtual machines can be active per host, and up to 8000 can be active per failover cluster.[36] SLAT is a required processor feature for Hyper-V on Windows 8, while for Windows Server 2012 it is only required for the supplementary RemoteFX role.[37]

ReFS[edit]

Main article: ReFS

Resilient File System (ReFS),[38] codenamed «Protogon»,[39] is a new file system in Windows Server 2012 initially intended for file servers that improves on NTFS in some respects. Major new features of ReFS include:[40][41]

Improved reliability for on-disk structures
ReFS uses B+ trees[40] for all on-disk structures including metadata and file data. Metadata and file data are organized into tables similar to a relational database. The file size, number of files in a folder, total volume size and number of folders in a volume are limited by 64-bit numbers; as a result ReFS supports a maximum file size of 16 exabytes, a maximum of 18.4 × 1018 folders and a maximum volume size of 1 yottabyte (with 64 KB clusters) which allows large scalability with no practical limits on file and folder size (hardware restrictions still apply). Free space is counted by a hierarchical allocator which includes three separate tables for large, medium, and small chunks. File names and file paths are each limited to a 32 KB Unicode text string.
Built-in resilience
ReFS employs an allocation-on-write update strategy for metadata,[40] which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata has built-in 64-bit checksums which are stored independently. The file data can have an optional checksum in a separate «integrity stream», in which case the file update strategy also implements allocation-on-write; this is controlled by a new «integrity» attribute applicable to both files and directories. If nevertheless file data or metadata becomes corrupt, the file can be deleted without taking the whole volume offline. As a result of built-in resiliency, administrators do not need to periodically run error-checking tools such as CHKDSK when using ReFS.
Compatibility with existing APIs and technologies
ReFS does not require new system APIs and most file system filters continue to work with ReFS volumes.[40] ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications,[42] symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly[40] integrates with Storage Spaces, a storage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines.[43] ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using background data scrubbing process, which periodically reads all mirror copies and verifies their checksums then replaces bad copies with good ones.

Some NTFS features are not supported in ReFS, including object IDs, short names, file compression, file level encryption (EFS), user data transactions, hard links, extended attributes, and disk quotas.[39][40] Sparse files are supported.[44][45] Support for named streams is not implemented in Windows 8 and Windows Server 2012, though it was later added in Windows 8.1 and Windows Server 2012 R2.[46] ReFS does not itself offer data deduplication.[40] Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces. In Windows Server 2012, automated error-correction with integrity streams is only supported on mirrored spaces; automatic recovery on parity spaces was added in Windows 8.1 and Windows Server 2012 R2.[46] Booting from ReFS is not supported either.

IIS 8.0[edit]

Windows Server 2012 includes version 8.0 of Internet Information Services (IIS). The new version contains new features such as SNI, CPU usage caps for particular websites,[47] centralized management of SSL certificates, WebSocket support and improved support for NUMA, but few other substantial changes were made.[48]

Remote Desktop Protocol 8.0[edit]

Remote Desktop Protocol has new functions such as Adaptive Graphics (progressive rendering and related techniques), automatic selection of TCP or UDP as transport protocol, multi touch support, DirectX 11 support for vGPU, USB redirection supported independently of vGPU support, etc.[49] A «connection quality» button is displayed in the RDP client connection bar for RDP 8.0 connections; clicking on it provides further information about connection, including whether UDP is in use or not.[50]

Scalability[edit]

Windows Server 2012 supports the following maximum hardware specifications.[35][51] Windows Server 2012 improves over its predecessor Windows Server 2008 R2:

Specification Windows Server 2012 Windows Server 2008 R2
Physical processors[a] 64 64
Logical processors
when Hyper-V is disabled
640 256
Logical processors
when Hyper-V is enabled
320[b] 64
Memory 4 TB 2 TB
Failover cluster nodes (in any single cluster) 64 16

System requirements[edit]

Minimum system requirements for Windows Server 2012[53]

Processor 1.4 GHz, x64
Memory 512 MB
Free disk space 32 GB (more if there is at least 16 GB of RAM)

Windows Server 2012 runs only on x86-64 processors. Unlike older versions, Windows Server 2012 does not support Itanium.[5]

Upgrades from Windows Server 2008 and Windows Server 2008 R2 are supported, although upgrades from prior releases are not.[53]

Editions[edit]

Windows Server 2012 has four editions: Foundation, Essentials, Standard and Datacenter.[54][55][56][57][51]

Reception[edit]

Reviews of Windows Server 2012 have been generally positive.[60][61][62] Simon Bisson of ZDNet described it as «ready for the datacenter, today,»[60] while Tim Anderson of The Register said that «The move towards greater modularity, stronger automation and improved virtualisation makes perfect sense in a world of public and private clouds» but remarked that «That said, the capability of Windows to deliver obscure and time-consuming errors is unchanged» and concluded that «Nevertheless, this is a strong upgrade overall.»[61]

InfoWorld noted that Server 2012’s use of Windows 8’s panned «Metro» user interface was countered by Microsoft’s increasing emphasis on the Server Core mode, which had been «fleshed out with new depth and ease-of-use features» and increased use of the «practically mandatory» PowerShell.[63] However, Michael Otey of Windows IT Pro expressed dislike with the new Metro interface and the lack of ability to use the older desktop interface alone, saying that most users of Windows Server manage their servers using the graphical user interface rather than PowerShell.[64]

Paul Ferrill wrote that «Windows Server 2012 Essentials provides all the pieces necessary to provide centralized file storage, client backups, and remote access,»[65] but Tim Anderson contended that «Many businesses that are using SBS2011 and earlier will want to stick with what they have», citing the absence of Exchange, the lack of ability to synchronize with Active Directory Federation Services and the 25-user limit,[66] while Paul Thurott wrote «you should choose Foundation only if you have at least some in-company IT staff and/or are comfortable outsourcing management to a Microsoft partner or solution provider» and «Essentials is, in my mind, ideal for any modern startup of just a few people.»[67]

Windows Server 2012 R2[edit]

A second release, Windows Server 2012 R2, which is derived from the Windows 8.1 codebase, was released to manufacturing on August 27, 2013[68] and became generally available on October 18, 2013, by Microsoft.[69] An updated version, formally designated Windows Server 2012 R2 Update, was released in April 2014.[70][71]

Support Lifecycle[edit]

Microsoft originally planned to end mainstream support for Windows Server 2012 and Windows Server 2012 R2 on January 9, 2018, with extended support ending on January 10, 2023. In order to provide customers the standard transition lifecycle timeline, Microsoft extended Windows Server 2012 and 2012 R2 support in March 2017 by 9 months. Windows Server 2012 reached the end of mainstream support on October 9, 2018 and Extended Support will end on October 10, 2023.[72][73][74]

Microsoft announced in July 2021 that they will distribute Extended Security Updates for Windows Server 2012 and Windows Server 2012 R2 for up to 3 years after the end of Extended Support.[75] For Windows Server 2012 and Windows Server 2012 R2, these updates will last until October 13, 2026. This will mark the final end of the Windows NT 6.2 product line after 14 years, 2 months and 12 days and will also mark the final end of the Windows NT 6.3 product line after 13 years, 1 month and 16 days.

See also[edit]

  • Comparison of Microsoft Windows versions
  • Comparison of operating systems
  • History of Microsoft Windows
  • List of operating systems
  • Microsoft Servers

Notes[edit]

  1. ^ Applies to Windows Server 2008 R2 and 2012 Datacenter and Windows Server 2012 Standard only. Other editions support less.
  2. ^ Each virtualized partition, including the host itself, can use up to 64 processors.[52]
  3. ^ a b Each license of Windows Server 2012 Standard or Datacenter allows up to two processor chips. Each license of Windows Server 2012 Standard allows up to two virtual instances of Windows Server 2012 Standard on that physical server. If more virtual instances of Windows Server 2012 Standard are needed, each additional license of Windows Server 2012 allows up to two more virtual instances of Windows Server 2012 Standard, even though the physical server itself may have sufficient licenses for its processor chip count. Because Windows Server 2012 Datacenter has no limit on the number of virtual instances per licensed server, only enough licenses for the physical server are needed for any number of virtual instances of Windows Server 2012 Datacenter. If the number of processor chips or virtual instances is an odd number, the number of licenses required is the same as the next even number. For example, a single-processor-chip server would still require 1 license, the same as if the server were two-processor-chip and a five-processor-chip server would require 3 licenses, the same as if the server were six-processor-chip, and if 15 virtual instances of Windows Server 2012 Standard are needed on one server, 8 licenses of Windows Server 2012, which can cover up to 16 virtual instances, are needed (assuming, in this example, that the processor chip count does not exceed 16).
  4. ^ For the Standard and Datacenter editions, each user or device accessing the software must have a client access license (CAL) assigned (either per-user or per-device), so there may be no more simultaneous users than the number of client-access licenses, except up to 2 simultaneous users purely to administer the server software, or for running virtualization or web workloads. Remote Desktop Services requires an additional CAL separate from the aforementioned CAL.
  5. ^ If the number of physical processors in a particular server is under 64, the limit is determined by the quantity of licenses assigned to that server. In that case, the number of physical processors cannot exceed twice the number of licenses assigned to the server.

References[edit]

  1. ^ http://blogs.technet.com/b/windowsserver/archive/2012/08/01/windows-server-2012-released-to-manufacturing.aspx
  2. ^ http://blogs.technet.com/b/windowsserver/archive/2012/08/01/windows-server-2012-released-to-manufacturing.aspx
  3. ^ a b c «Microsoft Product Lifecycle». Microsoft Support. Microsoft. January 2012. Archived from the original on February 27, 2013. Retrieved October 10, 2012.
  4. ^ a b Snover, Jeffrey (August 1, 2012). «Windows Server 2012 released to manufacturing!». Windows Server Blog. Microsoft. TechNet blogs. Archived from the original on December 22, 2015. Retrieved January 29, 2013.
  5. ^ a b Foley, Mary Jo (April 5, 2010). «Microsoft pulls the plug on future Itanium support». ZDNet. CBS Interactive. Archived from the original on August 12, 2012. Retrieved January 1, 2012.
  6. ^ «Windows Server 2012 approximately equal to Windows Server 2008». SmartProfile. August 25, 2017.
  7. ^ a b Foley, Mary Jo (April 17, 2012). «Windows Server «8» officially dubbed Windows Server 2012″. ZDNet. CBS Interactive. Archived from the original on November 19, 2014. Retrieved April 17, 2012.
  8. ^ a b Savill, John (February 29, 2012). «Q: Where can I download and get more information on Windows Server «8» Beta and Windows 8 Consumer Preview?». Windows IT Pro. Penton Media. Retrieved February 29, 2012.
  9. ^ a b Snover, Jeffrey (April 24, 2012). «Windows Server 2012 Release Candidate Timing». Windows Server Blog. Microsoft. TechNet blogs. Archived from the original on February 11, 2013. Retrieved January 21, 2013.
  10. ^ Laing, Bill (September 9, 2011). «Windows Server 8: An Introduction». Server & Cloud Blog. Microsoft. TechNet blogs. Archived from the original on October 28, 2012. Retrieved January 23, 2013.
  11. ^ «Download Windows Server 8 Developer Preview via MSDN». Softpedia. SoftNews SRL. September 14, 2011. Archived from the original on May 8, 2012. Retrieved January 25, 2013.
  12. ^ a b Bisson, Simon (September 14, 2011). «Windows 8 Server Developer Preview». ZDNet. CBS Interactive. Archived from the original on December 2, 2014. Retrieved January 1, 2012.
  13. ^ Arghire, Ionut (February 18, 2012). «Windows 8 Developer Preview Expiration Date Gets Postponed». Softpedia. SoftNews SRL. Archived from the original on October 13, 2013. Retrieved July 15, 2013.
  14. ^ Snover, Jeffrey. «Windows Server 2012 Essentials released to manufacturing, available for evaluation today!». Windows Server Blog!. Microsoft. TechNet blogs. Archived from the original on January 17, 2013. Retrieved January 25, 2013.
  15. ^ «Windows Server 2012 Essentials reaches general availability!». Windows Server Blog!. Microsoft. TechNet blogs. Archived from the original on April 29, 2015. Retrieved January 25, 2013.
  16. ^ «Windows Server 2012». Microsoft DreamSpark. Microsoft. Archived from the original on August 19, 2016. Retrieved January 25, 2013.
  17. ^ Joel Hruska (May 18, 2007). «Windows Server 2008 declared 32-bit’s last hurrah». Ars Technica. Archived from the original on August 24, 2021. Retrieved August 24, 2021.
  18. ^ Callaham, John (September 9, 2011). «Windows Server 8 Screenshot Leak Shows New UI». Neowin.net. Neowin LLC. Archived from the original on February 27, 2013. Retrieved January 21, 2013.
  19. ^ Wilhelm, Alex (September 9, 2011). «Windows Server 8 Screenshot leaks». News. The Next Web. Archived from the original on August 28, 2012. Retrieved January 1, 2012.
  20. ^ «Managing Privacy: Windows Store and Resulting Internet Communication». TechNet. Microsoft. Archived from the original on October 6, 2014. Retrieved January 30, 2014.
  21. ^ Thurott, Paul (November 2, 2011). «Windows Server «8» Preview (Unedited, Complete Version)». Paul Thurott’s Supersite for Windows. Penton Media. Archived from the original on March 20, 2012. Retrieved January 1, 2012.
  22. ^ Williams, Mike; Hanson, Matt (October 25, 2012). «Windows 8 tips: mastering the interface». Techradar. Future Publishing. Archived from the original on January 22, 2013. Retrieved January 22, 2013.
  23. ^ Haveson, Ryan (October 13, 2011). Sinofsky, Steven (ed.). «The Windows 8 Task Manager». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on January 25, 2013. Retrieved January 31, 2013.
  24. ^ «Using Task Manager with 64+ logical processors». Building Windows 8. MSDN blogs. Archived from the original on November 6, 2015. Retrieved October 29, 2011.
  25. ^ «How to Get the Most out of New Windows 8 Task Manager?». October 24, 2011. Archived from the original on April 7, 2012. Retrieved October 29, 2011.
  26. ^ Hu, Aaron. «How to disable start-up items in windows server 2012». TechNet Forums. Microsoft. Archived from the original on February 27, 2013. Retrieved October 14, 2012. The Startup tab is not present on Windows Server 2012. It is only on Windows 8.
  27. ^ «IP Address Management (IPAM) Overview». TechNet Library. Microsoft. February 29, 2012. Archived from the original on May 2, 2013. Retrieved January 21, 2013.
  28. ^ Shields, Greg (July 3, 2012). «Quick Guide: What’s New in Windows Server 2012 Active Directory». Redmond magazine. 1105 Redmond Media. Archived from the original on January 21, 2013. Retrieved January 21, 2013.
  29. ^ Sherif Mahmoud, Tamer (May 29, 2012). «Creating fine grained password policies through GUI Windows server (sic) 2012 «Server 8 beta»«. Team blog of MCS @ Middle East and Africa. Microsoft. TechNet blogs. Archived from the original on March 7, 2013. Retrieved January 21, 2013.
  30. ^ Bruzzese, J. Peter (October 26, 2011). «Windows Server 8: The 4 best new Active Directory features». InfoWorld. IDG. Archived from the original on May 12, 2012. Retrieved January 1, 2012.
  31. ^ Deuby, Sean (September 14, 2011). «What’s New in Windows Server 2012 Active Directory». Windows IT Pro. Penton Media. Archived from the original on February 17, 2015. Retrieved July 16, 2013.
  32. ^ Herrmann, Max; Laing, Bill; Vecchiet, Manlio; Neil, Mike (September 14, 2011). «Day 2: Windows Server 8». Channel 9. Microsoft. Archived from the original on March 17, 2012. Retrieved February 2, 2013.
  33. ^ «BUILD2011: Windows Server 8». Channel 9. Anaheim, California: Microsoft. September 13–16, 2011. Archived from the original on October 7, 2012. Retrieved February 2, 2013.
  34. ^ «Server Virtualization Features». Microsoft. Archived from the original on October 4, 2012. Retrieved October 5, 2012.
  35. ^ a b Savill, John (October 28, 2011). «Q: What are Windows Server 8’s Scalability Numbers?». Windows IT Pro. Penton Media. Retrieved November 5, 2011.
  36. ^ Garg, Pankaj; Tan, See-Mong (September 14, 2011). «Day 2: A deep dive into Hyper-V Networking». Channel 9. Microsoft. Archived from the original on March 10, 2012. Retrieved January 22, 2013.
  37. ^ Savil, John (October 21, 2011). «Q: Will Windows Server 8 require the processor to support SLAT?». Windows IT Pro. Penton Media. Retrieved November 5, 2011.
  38. ^ Lucas, Martin (January 1, 2013). «Windows Server 2012: Does ReFS replace NTFS? When should I use it?». Ask Premier Field Engineering (PFE) Platforms. Microsoft. TechNet blogs. Archived from the original on June 2, 2013. Retrieved January 20, 2013.
  39. ^ a b Foley, Mary Jo (January 16, 2012). «Microsoft goes public with plans for its new Windows 8 file system». ZDNet. CBS Interactive. Archived from the original on May 21, 2013. Retrieved January 21, 2013.
  40. ^ a b c d e f g Verma, Surendra (January 16, 2012). Sinofsky, Steven (ed.). «Building the next generation file system for Windows: ReFS». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on May 26, 2013. Retrieved January 20, 2013.
  41. ^ Meyer, David (January 17, 2012). «Microsoft takes wraps off new Windows file system». ZDNet. CBS Interactive. Archived from the original on May 21, 2013. Retrieved January 20, 2013.
  42. ^ «ReadDirectoryChangesW function». MSDN Library. Microsoft. November 8, 2012. Archived from the original on May 4, 2013. Retrieved January 21, 2013.
  43. ^ Nagar, Rajeev (January 5, 2012). Sinofsky, Steven (ed.). «Virtualizing storage for scale, resiliency, and efficiency». Building Windows 8. Microsoft. MSDN blogs. Archived from the original on May 9, 2013. Retrieved January 18, 2013.
  44. ^ «Windows Server 2012: Does ReFS replace NTFS? When should I use it?». January 2, 2013. Archived from the original on June 2, 2013. Retrieved March 31, 2013.
  45. ^ «ReFS (Resilient File System) supports sparse files». Archived from the original on March 15, 2013. Retrieved March 31, 2013.
  46. ^ a b «Resilient File System Overview». TechNet Library. Microsoft. February 29, 2012. Archived from the original on September 1, 2017. Retrieved December 25, 2013.
  47. ^ Mackie, Kurt. «Microsoft Touts IIS 8 Improvements». Redmond magazine. 1105 Redmond Media. Archived from the original on May 15, 2013. Retrieved August 17, 2012.
  48. ^ Anderson, Tim (September 4, 2012). «Windows Server 2012: inside Microsoft’s Enterprise Server OS». Computer Weekly. TechTarget. Archived from the original on January 22, 2013. Retrieved January 21, 2013.
  49. ^ «Windows Server 2012 Remote Desktop Services (RDS) – Windows Server Blog – Site Home – TechNet Blogs». Blogs.technet.com. May 8, 2012. Archived from the original on October 5, 2013. Retrieved February 13, 2014.
  50. ^ «Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2». Support.microsoft.com. Archived from the original on October 25, 2012. Retrieved February 13, 2014.
  51. ^ a b c Seldam, Matthijs ten (October 13, 2012). «Windows Server — Sockets, Logical Processors, Symmetric Multi Threading». Matthijs’s blog. Microsoft. TechNet blogs. Archived from the original on November 2, 2012. Retrieved October 14, 2012.
  52. ^ «Logical Processor count changes after enabling Hyper-V role on Windows Server 2012». March 28, 2013. Archived from the original on May 15, 2013. Retrieved April 1, 2013.
  53. ^ a b «Installing Windows Server 2012». TechNet Library. Microsoft. System requirements. Archived from the original on October 31, 2012. Retrieved June 10, 2012.
  54. ^ Foley, Mary Jo (July 5, 2012). «Microsoft goes public with Windows Server 2012 versions, licensing». ZDNet. CBS Interactive. Archived from the original on November 9, 2012. Retrieved July 5, 2012.
  55. ^ «Purchasing Windows Server 2012». Microsoft. Archived from the original on December 7, 2015. Retrieved December 8, 2015.
  56. ^ «Windows Server 2012 Licensing and Pricing FAQ» (PDF). Microsoft. Archived (PDF) from the original on December 2, 2012. Retrieved July 5, 2012.
  57. ^ «Windows Server 2012 Licensing Data Sheet» (PDF). Microsoft. Archived from the original (PDF) on July 22, 2012.
  58. ^ «Introduction to Windows Server 2012 Foundation». TechNet. Microsoft. Archived from the original on November 5, 2012. Retrieved December 8, 2015.
  59. ^ «Introduction to Windows Server 2012 Foundation». TechNet Library. Microsoft. Archived from the original on November 5, 2012. Retrieved November 4, 2012.
  60. ^ a b Bisson, Simon (September 13, 2012). «Windows Server 2012: RTM review». ZDNet. CBS Interactive. Archived from the original on January 28, 2013. Retrieved January 19, 2013.
  61. ^ a b Anderson, Tim (September 5, 2012). «Windows Server 2012: Smarter, stronger, frustrating». The Register. Situation Publishing. Archived from the original on December 26, 2012. Retrieved January 19, 2013.
  62. ^ Ferrill, Paul (October 3, 2012). «Windows Server 2012 Review: The Bottom Line». ServerWatch. QuinStreet. Archived from the original on January 15, 2013. Retrieved January 19, 2013.
  63. ^ Rist, Oliver (June 27, 2012). «Review: Weighing Windows Server 2012». InfoWorld. IDG. Archived from the original on March 10, 2013. Retrieved January 19, 2013.
  64. ^ Otey, Michael (July 25, 2012). «Is Microsoft Trying to Kill Windows Server?». Windows IT Pro. Penton Media. Archived from the original on January 17, 2013. Retrieved January 19, 2013.
  65. ^ Ferrill, Paul (December 16, 2012). «A Hands-on Look at Windows Server 2012 Essentials». ServerWatch. QuinStreet. Archived from the original on January 15, 2013. Retrieved January 20, 2013.
  66. ^ Anderson, Tim (December 21, 2012). «Windows Server 2012 Essentials review». PC Pro. Dennis Publishing. Archived from the original on January 6, 2013. Retrieved January 20, 2013.
  67. ^ Thurott, Paul (October 2, 2012). «Windows Server 2012: Foundation vs. Essentials». Windows IT Pro. Penton Media. Archived from the original on October 8, 2012. Retrieved January 20, 2013.
  68. ^ «Windows Server 2012 R2 Reaches the Release to Manufacturing (RTM) Milestone». Microsoft Docs. August 27, 2013. Archived from the original on January 14, 2020. Retrieved January 13, 2015.
  69. ^ «Save the date: Windows Server 2012 R2, Windows System Center 2012 R2 and Windows Intune update coming Oct. 18 — The Official Microsoft Blog — Site Home — TechNet Blogs». Microsoft Docs. August 14, 2013. Archived from the original on April 1, 2014. Retrieved February 10, 2014.
  70. ^ «August updates for Windows 8.1 and Windows Server 2012 R2 | Blogging Windows». Archived from the original on September 6, 2015. Retrieved November 14, 2014.
  71. ^ Resseler, Mike (August 27, 2013). «eBook — What’s new in Windows Server 2012 R2 Preview». Veeam Software. Archived from the original on April 5, 2014. Retrieved September 3, 2013.
  72. ^ «Windows Server 2012». Microsoft Docs. Archived from the original on July 28, 2021. Retrieved July 28, 2021.
  73. ^ «Microsoft Extends Windows Server 2012 Support — Redmondmag.com». Redmondmag. Archived from the original on July 28, 2021. Retrieved July 28, 2021.
  74. ^ «Windows Server 2012 Nears End of life». February 3, 2020. Archived from the original on January 26, 2021. Retrieved July 28, 2021.
  75. ^ «Product Lifecycle FAQ — Extended Security Updates». docs.microsoft.com. Archived from the original on July 29, 2021. Retrieved July 28, 2021.

Further reading[edit]

  • Stanek, William (2013). Windows Server 2012 Inside Out. Microsoft Press. ISBN 978-0-7356-6631-3.
  • Stanek, William (2014). Windows Server 2012 R2 Inside Out Volume 1: Configuration, Storage, & Essentials. Microsoft Press. ISBN 978-0-7356-8267-2.
  • Stanek, William (2014). Windows Server 2012 R2 Inside Out Volume 2: Services, Security, & Infrastructure. Microsoft Press. ISBN 978-0-7356-8255-9.

External links[edit]

  • Official website
  • Windows Server 2012 R2 and Windows Server 2012 on TechNet
  • Windows Server 2012 R2 on MSDN
  • Windows Server 2012 on MSDN
  • Tutorials and Lab Manual Articles of Windows Server 2012 R2

Корпорация Microsoft в конце октября выпустила свою новую операционную систему для серверов Windows Server 2012, которая имеет несколько редакций. Системные администраторы могут выбрать те преимущества решения, которые являются для них наиболее значимыми и удовлетворяют их финансовым и функциональным требованиям. Рассмотрим эти редакции Windows Server 2012 подробнее

Николай Печенкин — старший преподаватель учебного центра «Микротест» по направлению Microsoft

.

1. Редакция Windows Server 2012 Standard. Включает в себя все роли и компоненты, доступные для платформы Windows Server 2012, поддерживает до 64 процессорных разъемов, до 4 Тбайт оперативной памяти и предусматривает две лицензии для виртуальных машин.

2. Редакция Windows Server 2012 Datacenter. Включает все роли и компоненты, доступные для платформы Windows Server 2012, поддерживает до 64 процессорных разъемов, до 640 ядер процессоров и до 4 Тбайт оперативной памяти. Предусматривает неограниченное количество лицензий для запуска виртуальных машин на этом же оборудовании.

3. Редакция Windows Server 2012 Foundation. Поставляется только вместе с серверным аппаратным обеспечением, поддерживает 15 пользователей; сервер не может быть включен в домен. Поддерживает один процессор, 32 Гбайт оперативной памяти и только часть служебных ролей сервера.

4. Windows Server 2012 Essentials. Служит в качестве замены редакции Small Business Server в предыдущих версиях. Не может запускать роль Hyper-V, участвовать в формировании отказоустойчивого кластера, устанавливаться в режиме ядра server core или быть сервером служб удаленных рабочих столов remote desktop services. Поддерживает подключение до 25 пользователей и 50 устройств, два процессора и 64 Гбайт оперативной памяти. Сервер с этой редакцией должен быть основным (root) сервером в домене.

5. Microsoft Hyper-V Server 2012. Автономная редакция Hyper-V для виртуальных машин без пользовательского интерфейса. Не требует лицензии для хостовой операционной системы, виртуальные машины при этом лицензируются как обычно. Поддерживает 64 процессорных разъема и 4 Tбайт оперативной памяти. Может подключаться к домену. Не поддерживает другие роли Windows Server 2012.

6. Windows Storage Server 2012 Workgroup. Поставляется только вместе с аппаратным обеспечением. Система хранения начального уровня. Поддерживает до 50 пользователей, один процессор и 32 Гбайт оперативной памяти. Возможно подключение к домену.

7. Windows Storage Server 2012 Standard. Поддерживает 64 процессора, но лицензируется с шагом в два. Поддерживает 4 Tбайт оперативной памяти. Включает две лицензии на виртуальные машины. Предполагает включение в домен. Поддерживает некоторые роли, например DNS и DHCP Server, но не поддерживает: Active Directory Domain Services (AD DS), Active Directory Certificate Services (AD CS) и Active Directory Federation Services (AD FS).

8. Windows MultiPoint Server 2012 Standard. Предусматривает доступ нескольких пользователей к одному хостовому компьютеру напрямую, при этом каждый из них использует свою мышь, клавиатуру и монитор. Поддерживает один процессор, 32 Гбайт оперативной памяти и максимум 12 сессий. Поддерживает некоторые роли, например DNS и DHCP Server roles, но не поддерживает AD DS, AD CS и AD FS. Включение в домен невозможно.

9. Windows MultiPoint Server 2012 Premium. Поддерживает доступ нескольких пользователей к одному хостовому компьютеру напрямую, при этом каждый работает со своей мышью, клавиатурой и монитором. Поддерживает 2 процессора, 4 Тбайт оперативной памяти и максимум 22 сессии. Предполагается использование некоторых ролей, например DNS и DHCP Server; не поддерживаются AD DS, AD CS и AD FS. Допускается подключение к домену.

Требования к аппаратной части Windows Server 2012 зависят от количества ролей и пользователей, подключающихся к серверу. Каждая роль и каждый установленный компонент, в свою очередь, увеличивают общую нагрузку на жесткий диск, процессор, память. При установке Windows Server 2012 в виртуальной среде требования к аппаратной части не меняются, установка возможна на платформу виртуализации Hyper-V, а также на некоторые платформы сторонних разработчиков. Минимальные требования к аппаратному обеспечению представлены в таблице.

Минимальные требования к аппаратному обеспечению для Windows Server 2012

При рассмотрении вопроса об обновлении или миграции на Windows Server 2012 следует учитывать особенности, описанные ниже.

Установка через обновление

При установке методом обновления сохраняются файлы, настройки и приложения, установленные на исходном сервере. Вы выполняете обновление в случае, если хотите продолжать использовать то же самое серверное оборудование. Вы можете обновить имеющуюся версию до Windows Server 2012 только с x64 версий Windows Server 2003, Windows Server 2003 R2, Windows Server 2008 и Windows Server 2008 R2.

Установка посредством миграции

Используйте миграцию, когда вы хотите перейти от x86 версии Windows Server 2003, Windows Server 2003 R2 или Windows Server 2008. При миграции можно задействовать компонент Windows Server Migration Tools, входящий в состав Windows Server 2012 для переноса файлов и настроек с компьютеров, работающих под управлением Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2.

Кроме представленных выше редакций Windows Server 2012 поддерживает установку в режимеServer Core (минимальный вариант установки Windows Server 2012). При этом работа с сервером осуществляется из командной строки либо с удаленного компьютера, с помощью установленных средств администрирования. Подобный подход имеет ряд преимуществ.

-Поскольку сервер в режиме Server Core имеет меньшее количество компонентов, он требует меньшего количества обновлений, что сокращает время обслуживания сервера системными администраторами.

-Набор функций минимален, требуется меньшее количество оперативной памяти и меньше места на диске.

-Меньшее количество приложений сокращает площадь атаки на сервер.

Возможны два варианта установки Server Core. Первый — стандартный вариант установки. По умолчанию все графические инструменты администрирования находятся в состоянии «Удалены» (Removed). Управление осуществляется локально, только из командной строки, либо путем подключения с удаленной системы с помощью графических средств. Вы можете преобразовать Server Core до полной версии Windows Server 2012 с графическими инструментами администрирования только при наличии всех файлов установки.

Второй вариант — установка в режиме Server Core с инструментами управления. Этот вариант также известен как Server Core-Full Server. Данная редакция работает подобно Windows Server 2012 с графическими инструментами управления. При этом все графические компоненты уже скопированы на диск, но не установлены. Вы можете конвертировать Server Core-Full Server до Windows Server 2012 без дополнительных файлов установки.

Пробежимся по установке

Обычная установка Windows Server 2012 (если вы ее осуществляете без использования файла ответов) включает следующие шаги.

1.Подключение к источнику установки. При этом возможны варианты:

*начать установку с DVD-ROM;

*начать установку с диска USB;

*произвести загрузку по сети (PXE boot), после чего подключиться к серверу WDS и начать установку.

2.На первой странице Windows Setup Wizard необходимо выбрать:

*язык установки;

*формат времени и валюты;

*раскладку и методы ввода.

3.На второй странице мастера Windows Setup Wizard следует выбрать вариант «Установить» (Install now). Также на этой странице вы можете выбрать вариант «Восстановить» (Repair Your Computer). Эту возможность следует выбирать в том случае, если вы не можете загрузить уже установленную версию Windows Server 2012.

4.На странице выбора версии операционной системы указывается версия для установки. По умолчанию задан режим Server Core.

5.На странице лицензионного соглашения необходимо ознакомиться с ним и принять для продолжения установки.

6.На странице выбора типа установки доступны следующие варианты:

*обновление (Upgrade); выбирайте этот вариант, если требуется выполнить обновление до Windows Server 2012 с уже установленной версии Windows Server;

*Custom; выбирайте этот вариант, если нужно выполнить новую установку.

7.На странице выбора места для установки укажите диск, на который необходимо произвести установку. На данном этапе вы можете отформатировать диск, разбить его на разделы, создать диск VHD для установки операционной системы на него. После нажатия кнопки «Далее» начнется процесс копирования файлов, и компьютер будет несколько раз перезагружен. Время установки в первую очередь зависит от аппаратных характеристик компьютера.

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

От ядра

Одной из новых функций Windows Server 2012 является возможность перехода от версии Core к полноценной версии с графическим интерфейсом без переустановки всей операционной системы. Для этого потребуется выполнить следующие действия:

-создать папку для монтирования образа. Для этого в командной строке выполним команду mkdir c:\mount

-смонтировать образ полной версии Windows Server 2012 — dism.exe /mount-image /ImageFile:d:\sources\install.wim /Index:4 /Mountdir:c:\mount /readonly

-импортировать графические модули, выполнив следующие команды:

*PowerShell.exe

*Import-Module ServerManagerInstall-WindowsFeature -IncludeAllSubfeature User-Interfaces-Infra -Source:c:\mount\windows\

и далее выполнить перезагрузку — Shutdown /r /t 5

После проведения этой процедуры вы получите полноценную версию Windows Server 2012 с графическими инструментами управления (см. экран).

Окно Windows Server 2012 с графическими инструментами управления
Экран. Окно Windows Server 2012 с графическими инструментами управления

Для обратного преобразования необходимо выполнить следующие команды:

— Powershell.exe;

— Import-Module ServerManager;

— Uninstall-WindowsFeature User-Interfaces-Infra;

— Shutdown /r /t 5.

Overview

Graphical user interfaces consume a lot of system resources. For most servers, those resources could be better utilized serving what ever service the host was deployed for. They also have a tendancy to create a lot of security holes, for which an almost constant stream of patches are required to fix. To add insult to injury, the GUI goes unused for most of the server’s life, which begs the question “Why are we even installing it?” Well, that’s because up until Windows Server 2008, Microsoft has always forced us to have one on our servers.

With the release of Windows Server 2008, Microsoft finally decided to give us the option of installing the operating system without a grahpical interface. The problem was, unlike Linux and Unix, one could not add the GUI later on if needed, or remove one after it was no longer necessary to have. This meant that if your server’s requirements changed, you had to start all over again with a new installation.

Windows Server 2012 changes all of that. We now can switch between core and full installation, and we can do so on-the-fly. There’s really no more reason why, you should be using a full installation for a server, unless it’s due to an installed application’s or role’s requirements. Unfortunately, there are still a few roles that require the GUI to be installed.

Convert Full to Core

  1. Log onto the server with an account that has administrative permissions.
  2. If it isn’t already open, launch the Server Manager console.
    Launch Server Manager
  3. From the Server Manager console, click the Manage menu.
  4. Click Remove Roles and Features.
    Remove Roles and Features
  5. On the Before You Begin screen, click Next.
  6. On the Select Destination Server screen, ensure the server is selected in the server pool, and then click Next.
  7. On the Remove Server Roles screen, click Next
  8. On the Remove Features screen, scroll down the list until you see User Interfaces and Infrastructure and expand it.
  9. Uncheck Graphical Management Tools and Infrastructure and Server Graphical Shell, and then click Next.
    Remove Roles and Features
  10. On the Confirmation screen, review the changes and then click Remove.
  11. When the removal process completes, click Close. The server will now need to be rebooted. During the reboot phase, the remaining components will be removed. Do not power off the server.
  12. After the server reboots, log back in.
  13. Once you’re logged in, you’ll notice that only a command-prompt window is open. You have successfully removed the graphical interface from Windows Server 2012 R2.
    Windows Command-Line

Convert Core to Full

  1. Log onto the server with an account that has administrative privileges.
  2. Check to see if any graphical user interface components are installed. 
    Get-WindowsFeature -Name "Server-Gui-Mgmt-Infra","Server-Gui-Shell"
    

    The output should look like the following, unless you are running in a minimal install, where only Graphical Management Tools and Infrastructure is installed, giving the admin access to Server Manager in server core.
    PowerShell: Get-WindowsFeature output

  3. We can that no components are installed, in the figure above. Now we need to install both of the features listed above.
    Install-WindowsFeature -Name "Server-Gui-Mgmt-Infra","Server-Gui-Shell"
  4. When the features are installed, a warning will be displayed telling you that the server must be restarted. Go ahead and restart the server now.
  5. When the server completes the reboot process, log in. You should now have a fully functional graphical user interface presented to you.
    Windows Server 2012 R2 Graphical User Interface

Conclusion

Being able to switch between the two installation types at any time makes it easier to justify using the Core installation. A full installation is a lot easier to configure than a core installation, so ideally you will intially install the GUI with Server 2012 R2. Once the server is fully configured and ready for production, remove the GUI. We can do all of the administrative work remotely from our Windows 8.1 workstations, as is best practice.


  • Windows server 2012 cal rds cal
  • Windows server 2012 and windows server 2012 r2
  • Windows server 2012 activation keys
  • Windows server 2010 скачать торрент
  • Windows server 2008 создать пользователя