UNLOCK SERVER DRIVERS
Any supported operating system that uses UEFI DHCP drivers can be a Network Unlock client.You must be running at least Windows 8 or Windows Server 2012.Network Unlock requires the following mandatory hardware and software configurations before it can automatically unlock domain-joined systems: It's decrypted and returned to the client in a secure session. Instead, the key for Network Unlock is composed from a key that's stored in the TPM and an encrypted network key that's sent to the server. But the StartupKey doesn't need to be read from USB media. Network Unlock works like the TPM+StartupKey at boot. Network Unlock allows BitLocker-enabled systems that use TPM+PIN and that meet the hardware requirements to boot into Windows without user intervention. For enterprises, this setup can make software patches difficult to roll out to unattended desktops and remotely administered servers. Without Network Unlock, operating system volumes that use TPM+PIN protectors require a PIN when a computer reboots or resumes after hibernation (for example, by Wake on LAN). This feature requires the client hardware to have a DHCP driver implemented in its UEFI firmware. Network Unlock helps you manage BitLocker-enabled desktops and servers in a domain environment by automatically unlocking operating system volumes when the system is rebooted and is connected to a wired corporate network. Network Unlock was introduced in Windows 8 and Windows Server 2012 as a BitLocker protector option for operating system volumes.
UNLOCK SERVER HOW TO
This article for IT professionals describes how BitLocker Network Unlock works and how to configure it.
0 kommentar(er)
