That doesn't work so well in a lights-out data center.Ī few new BitLocker protectors were added in Windows Server 2012 (and Windows 8) to allow server administrators to enable disk encryption without all the hassles. Prior to Windows Server 2012, implementing BitLocker on a server meant using either Trusted Platform Module (TPM) chip-only mode, which is the weakest protector in the many offered, or required that a server administrator be present for each boot with a PIN, password, or USB key. Taken together, UEFI and Secure Boot significantly reduce the risk of malicious code, such as rootkits and boot viruses, from taking control of the operating system.ĭata center-ready BitLocker drive encryption BitLocker is finally usable on server systems.
Windows 8 and Windows Server 2012 go further and pick up the trustworthy and verified boot process, extending it to the entire Windows OS boot code with a feature known as Secure Boot. Microsoft is using the security-hardened 2.3.1 version, which prevents boot code updates without appropriate digital certificates and signatures. True UEFI and Secure Boot Like Windows 8, Windows Server 2012 has replaced the traditional ROM-BIOS with the new and improved industry boot standard known as UEFI (Unified Extensible Firmware Interface). Here's a quick walkthrough of the significant new security features found in Windows Server 2012. I would add that security improvements alone may justify the purchase for many enterprises. Windows Server 2012 really does change the game, and that's across all roles: file sharing, identity, storage, virtual desktop infrastructure, and certainly server virtualization and cloud." As InfoWorld's Oliver Rist said in June: "When Microsoft calls this a 'major' release, the company isn't kidding. Those considering an upgrade to Windows Server 2012 should have no such hesitation. With the shift to the new Metro user interface, a lot of people are wondering if Windows 8 is right for them.
0 kommentar(er)
