Windows远程计算机账户交互式登录（类型2）失败问题咨询

Great question—let’s break down the most common scenarios that could lead to this unusual event:

• Misconfigured Services or Scheduled Tasks
  It’s possible someone on Server B set up a service or scheduled task to run under the Server A$ computer account, and the task/service requires interactive desktop access (common with older legacy applications that depend on a visible UI). When the task triggers or the service starts, the system attempts an interactive logon (Type 2) instead of a network logon, since it needs to load a desktop session for the process.

• Accidental Interactive Logon Attempt
  A user might have mistakenly tried to log into Server B interactively (via RDP or local console) using Server A$ as the username—maybe confusing the computer account name with a user account. Even though computer accounts aren’t meant for this kind of logon, the attempt itself will generate this event.

• Malicious Testing or Lateral Movement Attempts
  Attackers often test lateral movement paths, and computer accounts are a common target. While by default computer accounts are denied interactive logon rights, an attacker might try using Server A$ to initiate an interactive logon on Server B to see if permissions were misconfigured. Your failed logon event suggests the default restrictions are still in place, which is good.

• Unusual System or Third-Party Tool Behavior
  In rare cases, a Windows system component (like an update process or repair tool) or a third-party management utility might incorrectly initiate an interactive logon request using a computer account instead of a network logon. This is usually a bug or edge-case behavior in the software.

Also, remember that computer accounts are explicitly denied interactive logon rights by default (via local security policy’s Deny log on locally setting or domain-level group policy), which is exactly why you’re seeing the "user has not been granted the requested logon type" error.

内容的提问来源于stack exchange，提问作者Limpid.Security