We're using Release Management for Visual Studio 2013 and deployments are working smoothly in DEV, QA and Staging servers, which are all in the same domain as the RM/Build server.
Trying to setup Production deployment agent on a server that is outside the RM server domain and having issues.
A local "shadow" account was created on the RM server and Production server, both with same username/password. Deployment agent was installed on the Production server and setup was successful using "./shadow_user" format for the username.
Release Management client isn't showing the Production server, and Event Viewer on the RM server shows numerous security audit failures from the deployment agent. Failure detail shows the Production server name for the domain instead of the RM server name (impersonation is failing). Specific message is:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: shadow_User
Account Domain: PROD-SVR
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: PROD-SVR
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
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 suggestions to solve this issue?
We've tried Windows Credential manager, using the RM server shadow account credentials, but no difference.
The solution was to login with the shadow account on the Production server and add credentials to Credential Manager. Was previously logged in with a different account, and the Deployment Agent didn't see entries in the other Credential Manager instance.