(Redirected from Windows Storage Server)
Aug 26, 2013 Windows Storage Server 2012 Standard does come with 2 VM licenses that OEMs can use to create their appliances. Storage Server is only available as an integrated appliance, also known as an 'OEM embedded' server. OEMs may choose to ship an appliance that is running WSS as a hypervisor and include 2 VMs running WSS and they can stack the.
Developer | Microsoft |
---|---|
Source model |
|
Initial release | April 24, 2003; 16 years ago |
Latest release | Windows Server, version 1903 (10.0.18362) / 21 May 2019; 53 days ago[1] |
Update method | Windows Update, Windows Server Update Services, SCCM |
Default user interface |
|
License | Trialware, SaaS or volume licensing |
Official website | windowsserver.com |
Windows Server is a brand name for a group of server operating systems released by Microsoft. It includes all Windows operating systems that are branded 'Windows Server', but not any other Microsoft product. The first Windows server edition to be released under that brand was Windows Server 2003. However, the first server edition of Windows was Windows NT 3.1 Advanced Server, followed by Windows NT 3.5 Server, Windows NT 4.0 Server, and Windows 2000 Server; the latter was the first server edition to include Active Directory, DNS Server, DHCP Server, Group Policy, SQL Server, as well as many other popular features used today.
- 1Members
Members[edit]
Long Term Servicing Channel (LTSC)[edit]
Windows Server operating system releases under the Long Term Servicing Channel are supported by Microsoft for 10 years, with five years of mainstream support and an additional five years of extended support. These releases also offer a complete GUI desktop experience, along with GUI-less setups such as Server Core and Nano Server for releases that support them.[2][3]
This channel includes the following operating systems:[4]
- Windows Server 2003 (April 2003)[5][6]
- Windows Server 2003 R2 (December 2005)[7][6]
- Windows Server 2008 (February 2008)[8]
- Windows Server 2008 R2 (October 2009)[8]
- Windows Server 2012 (September 2012)[9]
- Windows Server 2012 R2 (October 2013)[10]
- Windows Server 2016 (September 2016)[11]
- Windows Server 2019 (October 2018)[12]
Semi-Annual Channel (SAC)[edit]
Windows Server operating system releases under the Semi-Annual Channel are supported by Microsoft for 18 months. Microsoft targets two releases of Windows Server per year under this channel. These releases do not offer any GUI desktop environments, and include Server Core and Nano Server.[13][14]
Operating systems from this channel are available as part of subscription services, including Software Assurance, Azure Marketplace, Visual Studio subscriptions, and others.[14]
This channel includes the following operating systems:
- Windows Server, version 1709 (September 2017)
- This version was originally available for Microsoft Software Assurance customers with an active Windows Server 2016 license.[15]
- Windows Server, version 1803
- Windows Server, version 1809
- Windows Server, version 1903
Certain editions of Windows Server have a customized name. For example, all editions of Windows Server to this date had a Windows Storage Server edition. Starting with Windows Server 2012, Windows Storage Server was discontinued, as Microsoft consolidated the editions to Standard and Datacenter. Other examples include Windows Home Server and Windows HPC Server.
Microsoft has also produced Windows Server Essentials (formerly Windows Small Business Server) and the discontinued Windows Essential Business Server, software bundles which include a somewhat restricted Windows Server operating system and some other Microsoft Server products.[16][17][18]
Deployment[edit]
Users of Windows Server may choose to deploy either on-site or using a cloud computing service. Each provides different advantages.
By delegating the managing and upkeep of the server to a cloud computing service such as Microsoft Azure[19] or Amazon Web Services,[20] users get the benefit of paying monthly based on usage rather than a large fixed cost. Furthermore, infrastructure tends to be more reliable and it is easier to scale up as necessary. However, buying and running a server in-house may be a better choice in certain cases when it is more cost effective. Other use cases such as using a Windows server to manage client computers in a facility are also appropriate for running a physical server.[21]
See also[edit]
- NetWare and Novell Open Enterprise Server
References[edit]
- ^https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows%20Server%20version%201903%20(Datacenter%20Standard)
- ^'What is Microsoft Windows Server LTSC (Long-Term Servicing Channel)? - Definition from WhatIs.com'. SearchWindowsServer. Retrieved 2018-03-22.
- ^'Windows Server - Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC) - Thomas Maurer'. Thomas Maurer. 2017-11-19. Retrieved 2018-03-22.
- ^'Previous versions of server and cloud products'. Microsoft Corporation. Retrieved 2016-08-31.
- ^'Windows server 2003 Lifecycle Policy'. Microsoft. March 8, 2008.
- ^ ab'Windows Server 2003 end of support'. Microsoft. Archived from the original on August 2, 2014. Retrieved June 19, 2015.
- ^'Windows Server 2003 Lifecycle Policy'. Microsoft. March 8, 2008.
- ^ abMicrosoft. 'Windows Server 2008 Lifecycle Policy'. Microsoft. Retrieved 2012-09-25.
- ^'Microsoft Product Lifecycle'. Microsoft Support. Microsoft. January 2012. Retrieved October 10, 2012.
- ^'Search product lifecycle – Windows Server 2012 R2'. Microsoft.com. Retrieved December 27, 2018.
- ^'Microsoft Product Lifecycle'. Microsoft Support. Microsoft. Retrieved December 7, 2016.
- ^'Microsoft Product Lifecycle'. Microsoft Support. Microsoft.
- ^'Windows Server - Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC) - Thomas Maurer'. Thomas Maurer. 2017-11-19. Retrieved 2018-03-22.
- ^ abjaimeo. 'Windows Server Semi-Annual Channel overview'. docs.microsoft.com. Retrieved 2018-03-22.
- ^'Introducing Windows Server, version 1709'. Microsoft Docs. Microsoft. Windows Server.
- ^'Windows Essential Business Server'. Microsoft TechNet. Microsoft Corporation. Retrieved 26 September 2011.
- ^'Windows Small Business Server 2008 Technical FAQ'. Microsoft TechNet. Microsoft Corporation. Retrieved 26 September 2011.
- ^Thurrott, Paul (3 September 2011). 'Windows Small Business Server 2011 Essentials'. Supersite for Windows. Penton Media, Inc. Retrieved 26 September 2011.
- ^'Windows Virtual Machines documentation'. Microsoft. Retrieved 7 August 2016.
- ^'Windows Server on AWS'. Amazon Web Services. Retrieved 7 August 2016.
- ^'What is windows server?'. BlogTech. 27 June 2016. Retrieved 7 August 2016.
External links[edit]
Wikiversity has learning resources about Windows Server |
- Official website
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Server&oldid=899221274'
Windows Storage Spaces is a great software-defined solution that has been part of the Microsoft stack since Window Server 2012. It provides enterprise storage features such as tiering storage (SSD with Hard Drive) and a resilient file system such as ReFS. It is a very powerful solution combined with SMB 3 and RDMA which deliver great performance even when compared to other software-defined storage solutions. One of the major complaints against the Windows Server 2012 iteration was complicated hardware replacement procedures which require PowerShell functions. These procedures can be an issue with complex arrays and admin who are not familiar with PowerShell. Windows Server 2016 Storage Spaces addressed some of the complex issues and simplified the procedures. Today we are going to cover how to replace a failed hard drive in Windows Server 2016 Storage Spaces.
How to Replace a Failed Hard Drive in Windows Server 2016 Storage Spaces
The following procedure was based on Windows Server 2016 DataCenter Edition Build 1607 to demonstrate how to replace a failed hard drive. The procedure is not as straightforward as some other software-defined storage solutions, so we wanted to show the procedure.
From Windows Event Viewer, there are system logs indicate bad block from hard drive.
In order to find out the actual hard drive info, we need to run the following command to identify the hard drive from the server:
Get-PhysicalDisk | select deviceid,friendlyname,serialnumber,size,physicallocation | sort -Property deviceid
From this output, we can identify the failed drive 9 is in slot 12. Note, this is working on a SATA hard drive sitting on a SAS infrastructure.
We need to locate the physical drive. The easiest way is to go to Server Manager, Storage Pool, Physical Disk then select the hard drive in slot 12. Choose Toggle Drive Light (if your system supports this feature):
Before we remove the drive, we need to place the same size hard drive in the system, join to the pool and set to automatic mode. If you fail to do this, as many do during their first replacements, you will get the following warning.
Instead, you need to add the new hard drive to the system. Then you will need to rescan storage:
Once this is done, you can add the new hard drive to the Storage Pool.
You will want to add the drive as Automatic for allocation.
After the new drive is in the Storage Pool, then remove failed hard drive.
Do not make any changes to the Storage Pool while repair operation is going on.
After some time, the old hard drive will be removed from the pool and the new drive will be assimilated. For the PowerShell fans, you can use get-storagejob to follow the progress of the repair.
After the operation is completed you can safely remove the failed hard drive.
Final Words
From the procedure above you can see the Microsoft made replace failed hard drive very easy in Windows Server 2016. People with minimum PowerShell knowledge should be able to perform the task without any issues.
Software-defined storage has come a long way in the past couple of years. Hyper-converged storage has become mature with solutions like VMware vSAN, Microsoft Storage Spaces Direct, and Nutanix. We also see how those solution combined with “traditional” software-defined storage such as ZFS and Microsoft Storage Spaces could give the performance, flexibility and reliability to customers who prefer alternative flexible storage solutions from the traditional vendors such as Dell EMC, HPE, and NetApp.
We hope this guide helps a new Microsoft Windows Server 2016 Storage Spaces admin replace a failed hard drive. If you try removing the drive first and get the error shown above it can be an understandably frustrating experience.
@Joswa:
The normal operation such as data writes are fine, but please be caution of pool configuration changes. It will be a good idea to verify backup status as well.