使用AD域用户和windows系统用户安装xen desktop

当使用本地管理员登录windows并使用AD管理员帐户安装xendesktop时，成功了，下面是我所做的：

$adPassword= convertto-securestring "password" -asplaintext -force
$adCredObject = new-object -typename System.Management.Automation.PSCredential -argumentlist "ad.mydomain.com\user",$adPassword
$CurrentProcess = Start-Process -FilePath ".\xendesktop\x64\XenDesktop Setup\XenDesktopServerSetup.exe" -Credential $adCredObject -Wait -PassThru -ArgumentList "/COMPONENTS CONTROLLER,DESKTOPSTUDIO,DESKTOPDIRECTOR,LICENSESERVER,STOREFRONT /NOREBOOT /CONFIGURE_FIREWALL"

但是，当使用puppet自动化脚本（它与windows系统用户一起运行）使用AD管理员帐户执行install xendesktop时，它失败了，下面是我在puppet中运行“exec”所做的操作（与上面的代码相同）：

因此，唯一的区别是使用本地管理员成功运行上述脚本，而使用windows系统用户运行失败。事件日志中显示的失败消息类似（）

---

我也曾尝试使用runasspc来执行此安装，但我得到了相同的结果。任何帮助都将不胜感激。

我不知道到底出了什么问题，但作为进一步研究的提示：子状态0xc000006a解析为状态\u错误\u密码。您是否为用户尝试了UPN语法？(john@domain.com)您是否检查了域控制器的安全事件日志？（这是处理登录请求的地方，而不是本地计算机）谢谢Martin，我刚刚尝试了UPN用户，它返回凭证错误，因此它似乎不支持UPN语法。检查AD服务器事件日志，我发现与我的测试相关的所有日志都是成功的，SID为空的日志：帐户已成功登录。主题：安全ID:NULL SID帐户名：-帐户域：-登录ID:0x0登录类型：3新登录：安全ID:MyDomainName\MyMachineName$帐户名：MyMachineName$帐户域：MyDomainName登录ID:0x4191ac3f登录GUID:{eb7da9d2-31bf-73c1-1ad8-31c65431a5cb}。如果您有更多的见解，我们将不胜感激。

$adPassword= convertto-securestring "password" -asplaintext -force
$adCredObject = new-object -typename System.Management.Automation.PSCredential -argumentlist "ad.mydomain.com\user",$adPassword
$CurrentProcess = Start-Process -FilePath ".\xendesktop\x64\XenDesktop Setup\XenDesktopServerSetup.exe" -Credential $adCredObject -Wait -PassThru -ArgumentList "/COMPONENTS CONTROLLER,DESKTOPSTUDIO,DESKTOPDIRECTOR,LICENSESERVER,STOREFRONT /NOREBOOT /CONFIGURE_FIREWALL"

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:       MyMachineName
    Account Domain:     MyDomainName
    Logon ID:       0x3e7

Logon Type:         3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       Administrator
    Account Domain:     MyMachineName

Failure Information:
    Failure Reason:     Unknown user name or bad password.
    Status:         0xc000006d
    Sub Status:     0xc000006a

Process Information:
    Caller Process ID:  0xd90
    Caller Process Name:    C:\Program Files (x86)\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe

Network Information:
    Workstation Name:   MyMachineName
    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.