DaCulprit Posted October 14, 2019 Report Share Posted October 14, 2019 I attempting to deploy software out to end users with smartdeploy enterprise. Every time I attempt to push out a software it just kind of stalls out and does not fail or stop, just sits there saying "deploying" with the little icon next to it. Looking through logs on the server I am seeing that the only logs associated with it are "Audit Failures" from a user called "Guest" while I am logged into both machines as a domain administrator: An account failed to log on. Subject: Security ID: Domain\user Account Name: user Account Domain: domain Logon ID: 0xFB0B1 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: Guest Account Domain: LOC-SMARTDEPLOY Failure Information: Failure Reason: Account currently disabled. Status: 0xC000006E Sub Status: 0xC0000072 Process Information: Caller Process ID: 0x1730 Caller Process Name: C:\Windows\explorer.exe Network Information: Workstation Name: LOC-SMARTDEPLOY Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested. Any ideas on how to resolve this? Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now