The content of this article or any related information is under the Creative Commons license BY, you can republish this content freely but you must mention the author of this article and indicate the URL of this page: https://www.exabyteinformatica.com/tienda/foro/5-reasons-to-install-windows-server-2016-t1436.html
Listed here I will be able to clarify why I feel that you should definitely accept as true with deploying the now often obtainable home windows Server 2016 (WS2016) on your network.
Smaller and faster
Every edition of home windows Server makes strides in enhancing the efficiency of the working device (OS). home windows Server 2008 (W2008) introduced a brand new installing option called Server Core; Microsoft removed the home windows from windows Server and left us with a server OS that most effective had a command immediate and a PowerShell instant. This smaller installing required much less RAM, had a smaller footprint, and had less of a floor environment for attackers to target.
Windows Server 2012 endured this circulation, and saw the kernel be more desirable with historical code being transformed or removed.
And in WS2016, sure, we continue to get Server Core as an installation alternative, however we also get whatever thing newer, smaller, and with an expanded emphasis on remote administration and automation. Nano Server (an installation choice, no longer an edition) doesn’t simply eradicate the GUI, it gets rid of the UI completely! Nano Server is a headless server OS, with the smallest disk requirement i can be aware seeing with windows Server, and consumes less than 200MB RAM when sitting idle!
if you are looking to run Hyper-V or Storage spaces/Direct then which you could use Nano Server, but where I see Nano Server being foremost used is for born-in-the-cloud purposes, where you are looking to lower resource usage, OS patching, and security vulnerabilities essentially the most.
Greater service availability
Lots of the advancements in WS2016 were driven by improvements in Azure. Azure, Microsoft’s public cloud, has a lot of service-level agreements (SLAs) that dictate certain uptime, so Microsoft is relatively sensitive to the issues that also have an effect on us:
• Transient storage considerations that crash virtual machines.
• Community glitches that remaining for seconds, but create minutes of downtime when digital machines are failed over inside a Hyper-V cluster.
• OS upgrades that require painful cluster-to-cluster migrations in case you want a more modern version of Hyper-V.
Microsoft in-built a few new points to enrich carrier uptime. The primary is rolling cluster enhancements, permitting us to painlessly upgrade Hyper-V clusters from WS2012 R2 to WS2016. A cluster can temporarily run both versions of Hyper-V, with digital machines in a position to reside migrating or failing over across the combined-stage cluster.
The process of performing a rolling upgrade on a Hyper-V cluster [Source: Microsoft]
New resiliency solutions were brought to take care of transient network or storage mistakes, accordingly making certain that virtual machines don’t crash within the adventure of a SAN glitch or a community cable being wrongly pulled/changed, and hosts are automatically quarantined if they delivery to “flap” between in shape and isolated states.
Storage Resiliency prevents Hyper-V digital computing device crashing all the way through transient storage outages [Image Credit: Microsoft]
Availability is more than only a cluster; many mid-tremendous businesses have stretched clusters throughout sites for disaster recuperation (DR) factors. WS2016, in my opinion (it’s been possible for a long time), is the primary edition of windows Server that really is equipped for doing DR the usage of failover clustering. Here’s as a result of clustering now is aware the concept of a site/location, and you may constrain storage/reside migration/failover to inside a site except a real disaster occurs. Microsoft also made stretch clusters less difficult with a cloud witness hosted in Azure (in its place of having a file share in a third website) and built-in storage replication (see below).
A true hybrid cloud
Microsoft argues that a hybrid cloud is more than just a network connection between a client’s LAN and a cloud, similar to Azure. Hyper-V is the standard basis of on-premises private clouds, hosted public/deepest clouds, and Azure. Utility-defined storage and networking abstract the problems of actual infrastructure. in terms of deployment and administration, the Azure Portal and Azure aid supervisor (ARM) can be made attainable to customers by the use of a brand new product (in mid-2017) known as Microsoft Azure Stack. The solution will imply that builders and operators can use the identical equipment, the same architectures, and the same templates (solutions and digital machines) no remember where they decide to set up new services.
The hybrid cloud, in line with Microsoft [Image Credit: Microsoft]
I am a Hyper-V nerd, so I cannot faux to ignore the incontrovertible fact that this is the greatest and most beneficial unencumber of Hyper-V yet. Microsoft is making it feasible to construct a utility-defined facts centre, on good of the most relaxed, open, fastest, and most desirable version of Hyper-V yet.
Secure & trusted
You’re already planning your deployment of WS2016 if safety is essential to you. Some features have made their means over from home windows 10 enterprise; Credential protect hides LSASS in a unique Hyper-V partition referred to as VSM, protecting saved administrator rights from malware at the back of a hardware-supported protection boundary. Equipment preserve protects essential elements of the kernel in opposition t rogue application, guaranteeing that what's working is what is meant to be operating.
People that are operating Hyper-V in a sensitive atmosphere can installation some very exciting functionality. a bunch Guardian carrier (HGS) can also be deployed into an remoted atmosphere; this makes it possible for a Hyper-V feature called shielded digital machines. a number is checked for health (as an instance, root package malware) when it boots up, and digital machines are best allowed to delivery on or reside migrate to suit and certified hosts — this prevents virtual machines being run on unauthorized or compromised environments. Shielding can also stay away from KVPs (host-guest integrations) and console access to a digital desktop. Owners of digital machines could be sensitive to undesirable or unauthorized peeking with the aid of directors; digital TPM enables the tenant to encrypt their digital computing device’s disks the use of BitLocker so that no one without visitor admin rights can peek at the OS, programs, or facts in the digital challenging disk info.
The HGS authorizing hosts to run Hyper-V Shielded virtual Machines [Image Credit: Microsoft]
Solving storage challenges
Typhoon Sandy made quite the influence in 2012 on the U.S. and on Microsoft; the utility maker mentioned that many SAN purchasers didn’t have DR solutions. Microsoft asked why this was, and those affected consumers observed that the licensing to allow replication for their seller’s SAN became too high priced. WS2016 provides Storage reproduction (SR), enabling you to replicate volumes at a block degree from one storage system to a different (each the same or distinct) the use of synchronous (brief distance, no facts loss) or asynchronous (longer distances, small statistics loss) replication. The solution is thoroughly supported by way of Failover Clustering, so it permits from some enjoyable stretch-cluster designs. Admittedly, some storage systems (similar to these by way of Dell) include free or very comparatively cheap licensing, so SR may not be attractive (firstly, but wait to peer what Azure might offer later) to these valued clientele, however there are horror studies with other brands of SAN.
The massive news in WS2016 storage is Storage areas Direct, which is the newest version of Microsoft’s software-described storage device that turned into introduced in WS2012 and more suitable in WS2012 R2. This is an extended conversation, however I’ll preserve it brief. that you could deploy a hyper-converged infrastructure the usage of WS2016 Hyper-V, devoid of giving greater than $60,000 to a few hardware company for each and every Hyper-V node, and get more advantageous and greater solid performing solutions than many have offered in fresh years. For instance, DataON currently introduced that it hit 2.four million IOPS on a 4-node cluster. If you desire less difficult, extra cost-efficient, and more desirable performing Hyper-V/cloud storage, then WS2016 has something to provide you with.
Tagged with Azure Stack, bitlocker, Failover Clustering, Host Guardian carrier, Hyper-V, Nano, Nano Server, private Cloud, S2D, shielded digital machines, SR, Storage replica, Storage spaces Direct, virtual TPM, vTPM, home windows Server 2016, WS2016
No te pierdas el tema anterior: How to build a home FTP server with FileZilla Server