Logon Type 4

In recent times, logon type 4 has become increasingly relevant in various contexts. EventID: 4624 - Logon Type 2 missing - social.technet.microsoft.com. Logon type 2 indicates Interactive logon and logon type 10 indicates Remote Interactive logon. To get logon type 2 event, please try to perform a local logon, for example, use Domain Admin account to log onto one DC, then find Event 4624 on this DC. From another angle, to get logon type 10 event, please use Remote Desktop Service to log from a Domain member to the DC.

Concurrent Logon Events - social.technet.microsoft.com. Another key aspect involves, the logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network). The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on. The network fields indicate where a remote logon request originated.

From another angle, user is denied access to a specific server but can authenticate elsewhere. I tried to access the \\server\share using a different account from the user's PC and was able to brose the shares. Using the same tactic I tried to browse the shares of the specific server by logging on with the account in question and trying to access \\server\share.

It registered the 529, and windows told me that there is an account restriction based on logon hours , policy enforcement or ... reporting services service account block by GPO. I tried to authorize "Allow logon locally" directly to the server, but the deny is strong. I also allowed Batch job, Logon as Services, but nothing is unlocking the account.

When I don't have this GPO everything are fine, the reports are generating perfectly. Furthermore, but I must have this GPO, because it is a services Account. Friday, August 24, 2012 7: ... Similarly, interactive Logon Screen vs Powershell (get-wmiobject). Basically, I use Powershell to call get-wmiobject collecting server status.

It works fine for most servers, except a few on another site. Servers on that site have an interactive Login Screen configured via Group Policy, users have to accept "Computer Misuse Act (1990)" message before they are allowed to logon on these servers. It looks this login message caused a bit trouble for the ... GPO Software installation failing %%1612 for Vista.

In hosts file on workstation I wrote line "10.1.1.1 server" and deploy software from "\\server\install$\7z.msi". To the install$ have permissions domain users and domain computers. This work for computers with Windows 7, 8, 8.1 but not for Vista.

No Logon Servers Available to Service Request (after Windows Updates).