Locate the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.Ĭreate a subkey under Protocols for TLS 1.2: HKLM\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2.Ĭreate a Client subkey under the TLS 1.2 protocol version subkey you created earlier. If you're installing on an operating system without TLS 1.2 enabled by default, then you should configure TLS 1.2 using the steps below.
TLS 1.2 protocol ensures the security of data in transit for communication between the Windows agent and the Log Analytics service. See Log Analytics agent overview for the network requirements for the Windows agent. We recommend that you configure the agent to use TLS 1.2. Update to the latest version of the Windows agent (version 7). Install the SHA-2 signing Windows updates for your OS as described in 2019 SHA-2 code signing support requirement for Windows and WSUS.
Install the latest service pack for your OS. Customers running on a legacy OS version were required to take the following actions on their machines before August 17, 2020, or their agents stopped sending data to their Log Analytics workspaces: The change doesn't require any customer action unless you're running the agent on a legacy OS version, such as Windows 7, Windows Server 2008 R2, and Windows Server 2008.
This change affected customers using the Log Analytics agent on a legacy OS as part of any Azure service, such as Azure Monitor, Azure Automation, Azure Update Management, Azure Change Tracking, Microsoft Defender for Cloud, Microsoft Sentinel, and Windows Defender Advanced Threat Protection. The Windows agent began to exclusively use SHA-2 signing on August 17, 2020. Requirements Supported operating systemsįor a list of Windows versions supported by the Log Analytics agent, see Overview of Azure Monitor agents. Installing the Log Analytics agent typically won't require you to restart the machine.
0 kommentar(er)
