我們正在使用Visual Studio 2013的發佈管理,並且部署在DEV,QA和登臺服務器中運行正常,這些服務器與RM/Build服務器。Visual Studio 2013的發佈管理 - 部署代理「未知用戶名或密碼錯誤」
試圖在RM服務器域之外的服務器上設置生產部署代理並遇到問題。
在RM服務器和生產服務器上創建了一個本地「影子」帳戶,兩者都使用相同的用戶名/密碼。部署代理安裝在生產服務器上,並且使用「./shadow_user」格式爲用戶名設置成功。
發佈管理客戶端未顯示生產服務器,並且RM服務器上的事件查看器顯示來自部署代理的大量安全審覈失敗。失敗詳細信息顯示域的生產服務器名稱,而不是RM服務器名稱(模擬失敗)。具體的訊息是:
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
任何建議來解決這個問題?
我們嘗試過使用RM服務器影子帳戶憑據的Windows憑據管理器,但沒有任何區別。
您是否已將兩個影子帳戶都添加到RM客戶端(需要使用計算機\帳戶格式),併爲RM帳戶和**服務用戶授予了**服務用戶**和**發佈管理器**權限**生產服務器帳戶的權限? –
@GrahamSmith是 – user2966445
是prod服務器上的本地管理員組中的影子帳戶? –