无法在Windows 8.1上使用WDS和应答文件执行无人参与的域加入

我已经查看了与此相关的其他问题,但没有一个能够帮助我.我已经花了几天时间在这个该死的无人值守的过程中,奇迹般地,我昨天能够让它工作,但是,唉,我做了一个noobish错误,并且在再次编辑之前没有备份文件,现在我是尽管工作了几个小时,却无法让它再次运转.

这是我得到的一些调试输出：

[DJOIN.EXE] Unattended Join: Begin
[DJOIN.EXE] Unattended Join: Loading input parameters...
[DJOIN.EXE] Unattended Join: AccountData = [NULL]
[DJOIN.EXE] Unattended Join: UnsecureJoin = [True]
[DJOIN.EXE] Unattended Join: MachinePassword = [secret not logged]
[DJOIN.EXE] Unattended Join: JoinDomain = [ad.domain.com]
[DJOIN.EXE] Unattended Join: JoinWorkgroup = [NULL]
[DJOIN.EXE] Unattended Join: Domain = [NULL]
[DJOIN.EXE] Unattended Join: Username = [NULL]
[DJOIN.EXE] Unattended Join: Password = [secret not logged]
[DJOIN.EXE] Unattended Join: MachineObjectOU = [NULL]
[DJOIN.EXE] Unattended Join: DebugJoin = [NULL]
[DJOIN.EXE] Unattended Join: DebugJoinOnlyOnThisError = [NULL]
[DJOIN.EXE] Unattended Join: TimeoutPeriodInMinutes = [NULL]
[DJOIN.EXE] Unattended Join: Checking that auto start services have started.
[DJOIN.EXE] Unattended Join: Calling DsGetDcName for ad.domain.com...
[DJOIN.EXE] Unattended Join: Constructed domain parameter [ad.domain.com\PDC.ad.domain.com]
[DJOIN.EXE] Unattended Join: NetJoinDomain attempt Failed: 0x52e,will retry in 10 seconds...

最后一行在退出前的过程中重复几次.

[DJOIN.EXE] Unattended Join: NetJoinDomain Failed error code is [1326]
[DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x52e

和…

NetUseAdd to \\PDC.ad.domain.com\IPC$returned 1326
Trying add to \\PDC.ad.domain.com\IPC$using NULL Session
NetpProvisionComputerAccount:
lpDomain: ad.domain.com
lpHostName: ComputerName
lpMachineAccountOU: (NULL)
lpDcName: PDC.ad.domain.com
lpMachinePassword: (non-null)
lpAccount: ad.domain.com\ComputerName$
lpPassword: (non-null)
dwJoinOptions: 0xe1
dwOptions: 0xc0000003
NetpLdapBind: ldap_bind Failed on PDC.ad.domain.com: 49: Informations d'identification non valides

最后一行转换为“标识信息无效”或“凭据无效”.

NetpJoinCreatePackagePart: status:0x52e
NetpAddProvisioningPackagePart: status:0x52e
NetpJoinDomainOnDs: Function exits with status of: 0x52e
NetpDoDomainJoin: status: 0x52e

我得到错误1326是无效的凭据,我使用不安全的连接方法与％machinepassword％变量,所以我不知道为什么…

这是有问题的无人参与文件：
当我达到30k字符限制时编辑,无论如何它现在都无关紧要

任何帮助将非常感谢.我已经尝试了几十个逐步指南和技术说明,这些指南都相互矛盾或建议使用MDT或者根本不清楚.如果有无人值守部署的专家在那里读到这个,如果你能指出可能是一个非常愚蠢的错误,我将永远感激不尽.

谢谢！

编辑：我没有提到它,因为我没有判断信息重要,但WDS服务器和DC都运行2012 R2.

编辑2：如下面的评论中所述,这是在将UnsecureJoin更改为False并在UnattendJoin组件下添加凭据信息后的相关NetSetup.log信息：

11/11/2014 14:22:54:558 -----------------------------------------------------------------
11/11/2014 14:22:54:558 NetpDoDomainJoin
11/11/2014 14:22:54:558 NetpDoDomainJoin: using new computer names
11/11/2014 14:22:54:558 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0
11/11/2014 14:22:54:558 NetpDoDomainJoin: NetpGetNewHostName returned 0x0
11/11/2014 14:22:54:558 NetpMachineValidToJoin: 'IMAGE-TEST'
11/11/2014 14:22:54:558     OS Version: 6.3
11/11/2014 14:22:54:558     Build number: 9600 (9600.winblue_r3.140827-1500)
11/11/2014 14:22:54:589     SKU: Windows 8.1 Professionnel
11/11/2014 14:22:54:589     Architecture: 64-bit (AMD64)
11/11/2014 14:22:54:589 NetpDomainJoinLicensingCheck: ulLicenseValue=1,Status: 0x0
11/11/2014 14:22:54:589 NetpGetLsaPrimaryDomain: status: 0x0
11/11/2014 14:22:54:589 NetpMachineValidToJoin: status: 0x0
11/11/2014 14:22:54:589 NetpJoinDomain
11/11/2014 14:22:54:589     HostName: IMAGE-TEST
11/11/2014 14:22:54:589     NetbiosName: IMAGE-TEST
11/11/2014 14:22:54:589     Domain: ad.domain.com\PDC.ad.domain.com
11/11/2014 14:22:54:589     MachineAccountOU: (NULL)
11/11/2014 14:22:54:589     Account: domain\wdsclient
11/11/2014 14:22:54:589     Options: 0x23
11/11/2014 14:22:54:589 NetpLoadParameters: loading registry parameters...
11/11/2014 14:22:54:589 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1' 0x2
11/11/2014 14:22:54:589 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/11/2014 14:22:54:589 NetpLoadParameters: status: 0x2
11/11/2014 14:22:54:589 NetpDisableIDNEncoding: no domain dns available - IDN encoding will NOT be disabled
11/11/2014 14:22:54:589 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
11/11/2014 14:22:54:886 NetpJoinDomainOnDs: status of connecting to dc '\\PDC.ad.domain.com': 0x0
11/11/2014 14:22:54:886 NetpJoinDomainOnDs: Passed DC 'PDC.ad.domain.com' verified as DNS name '\\PDC.ad.domain.com'
11/11/2014 14:22:54:886 NetpLoadParameters: loading registry parameters...
11/11/2014 14:22:54:886 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1'     0x2
11/11/2014 14:22:54:886 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/11/2014 14:22:54:886 NetpLoadParameters: status: 0x2
11/11/2014 14:22:54:886 NetpDsGetDcName: status of verifying DNS A record name resolution for     'PDC.ad.domain.com': 0x0
11/11/2014 14:22:54:886 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: ad.domain.com
11/11/2014 14:22:54:902 NetpProvisionComputerAccount:
11/11/2014 14:22:54:902     lpDomain: ad.domain.com
11/11/2014 14:22:54:902     lpHostName: IMAGE-TEST
11/11/2014 14:22:54:902     lpMachineAccountOU: (NULL)
11/11/2014 14:22:54:902     lpDcName: PDC.ad.domain.com
11/11/2014 14:22:54:902     lpMachinePassword: (null)
11/11/2014 14:22:54:902     lpAccount: domain\wdsclient
11/11/2014 14:22:54:902     lpPassword: (non-null)
11/11/2014 14:22:54:902     dwJoinOptions: 0x23
11/11/2014 14:22:54:902     dwOptions: 0x40000003
11/11/2014 14:22:54:917 NetpLdapBind: Verified minimum encryption strength on PDC.ad.domain.com:     0x0
11/11/2014 14:22:54:917 NetpLdapGetLsaPrimaryDomain: reading domain data
11/11/2014 14:22:54:917 NetpGetNCData: Reading NC data
11/11/2014 14:22:54:917 NetpGetDomainData: Lookup domain data for: DC=ad,DC=domain,DC=com
11/11/2014 14:22:54:917 NetpGetDomainData: Lookup crossref data for:     CN=Partitions,CN=Configuration,DC=ad,DC=com
11/11/2014 14:22:54:949 NetpLdapGetLsaPrimaryDomain: result of retrieving domain data: 0x0
11/11/2014 14:22:54:949 NetpCheckForDomainSIDCollision: returning 0x0(0).
11/11/2014 14:22:54:964 NetpGetComputerObjectDn: Cracking DNS domain name ad.domain.com/ into     Netbios on \\PDC.ad.domain.com
11/11/2014 14:22:54:964 NetpGetComputerObjectDn: Crack results:     name = domain\
11/11/2014 14:22:54:964 NetpGetComputerObjectDn: Cracking account name domain\IMAGE-TEST$on     \\PDC.ad.domain.com
11/11/2014 14:22:54:964 NetpGetComputerObjectDn: Crack results:     (Account already exists) DN =     CN=IMAGE-TEST,CN=Computers,DC=com
11/11/2014 14:22:54:964 NetpModifyComputerObjectInDs: Initial attribute values:
11/11/2014 14:22:54:964         objectClass  =  Computer
11/11/2014 14:22:54:964         SamAccountName  =  IMAGE-TEST$
11/11/2014 14:22:54:964         userAccountControl  =  0x1000
11/11/2014 14:22:54:964         DnsHostName  =  IMAGE-TEST.ad.domain.com
11/11/2014 14:22:54:964         ServicePrincipalName  =  HOST/IMAGE-TEST.ad.domain.com      RestrictedKrbHost/IMAGE-TEST.ad.domain.com  HOST/IMAGE-TEST  RestrictedKrbHost/IMAGE-TEST
11/11/2014 14:22:54:964         unicodePwd  =  <SomePassword>
11/11/2014 14:22:54:964 NetpModifyComputerObjectInDs: Computer Object already exists in OU:
11/11/2014 14:22:54:964         objectClass  =  top  person  organizationalPerson  user  computer
11/11/2014 14:22:54:964         SamAccountName  =  IMAGE-TEST$
11/11/2014 14:22:54:964         userAccountControl  =  0x1000
11/11/2014 14:22:54:964         DnsHostName  =
11/11/2014 14:22:54:964         ServicePrincipalName  =
11/11/2014 14:22:54:964         unicodePwd  =  Account exists,resetting password: <SomePassword>
11/11/2014 14:22:54:964 NetpModifyComputerObjectInDs: Attribute values to set:
11/11/2014 14:22:54:964         DnsHostName  =  IMAGE-TEST.ad.domain.com
11/11/2014 14:22:54:964         ServicePrincipalName  =  HOST/IMAGE-TEST.ad.domain.com      RestrictedKrbHost/IMAGE-TEST.ad.domain.com  HOST/IMAGE-TEST  RestrictedKrbHost/IMAGE-TEST
11/11/2014 14:22:54:964         unicodePwd  =  <SomePassword>
11/11/2014 14:22:54:980 NetpMapGetLdapExtendedError: Parsed [0x5] from server extended error     string: 00000005: SecErr: DSID-031A1256,problem 4003 (INSUFF_ACCESS_RIGHTS),data 0
11/11/2014 14:22:54:980 NetpModifyComputerObjectInDs: ldap_modify_s Failed: 0x32 0x5
11/11/2014 14:22:54:980 NetpCreateComputerObjectInDs: NetpModifyComputerObjectInDs Failed: 0x5
11/11/2014 14:22:54:980 NetpProvisionComputerAccount: LDAP creation Failed: 0x5
11/11/2014 14:22:54:980 NetpProvisionComputerAccount: Retrying downlevel per options
11/11/2014 14:22:54:995 NetpManageMachineAccountWithSid: NetUserAdd on 'PDC.ad.domain.com' for     'IMAGE-TEST$' Failed: 0x8b0
11/11/2014 14:22:54:995 SamOpenUser on 1639 Failed with 0xc0000022
11/11/2014 14:22:54:995 NetpManageMachineAccountWithSid: status of attempting to set password on     'PDC.ad.domain.com' for 'IMAGE-TEST$': 0x5
11/11/2014 14:22:54:995 NetpProvisionComputerAccount: retry status of creating account: 0x5
11/11/2014 14:22:54:995 ldap_unbind status: 0x0
11/11/2014 14:22:54:995 NetpJoinCreatePackagePart: status:0x5.
11/11/2014 14:22:54:995 NetpAddProvisioningPackagePart: status:0x5.
11/11/2014 14:22:54:995 NetpJoinDomainOnDs: Function exits with status of: 0x5
11/11/2014 14:22:54:995 NetpJoinDomainOnDs: status of disconnecting from '\\PDC.ad.domain.com':     0x0
11/11/2014 14:22:54:995 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
11/11/2014 14:22:54:995 NetpDoDomainJoin: status: 0x5
11/11/2014 14:23:05:027 -----------------------------------------------------------------

我注意到了“INSUFF_ACCESS_RIGHTS”标记,但使用的帐户是一个Domain Admin帐户,所以我不确定这里还有什么原因.思考？

编辑3：此外,我正在测试它的客户端计算机是Hyper-V VM,它在成像之前有一个检查点.我还原机器,从AD中删除对象,清除已批准设备的WDS服务器,然后每当无人参与安装不起作用时重新启动整个过程.同样,我不认为这是相关的,但它是我能给出的所有信息.

编辑4：我想我已经开始看到发生了什么.在无人参与操作之后,我尝试使用我在无人参与文件中指定的相同帐户信息将工作站添加到域中,只是出现以下错误消息：

"The join operation was not successful. This could be because an existing computer
account having name “IMAGE” was prevIoUsly created using a different set of
credentials. Use a different computer name,or contact your administrator to remove
any stale conflicting account. The error was:

Access is denied."

我尝试了另一个域管理员帐户,我得到了同样的错误.我的猜测是,不知何故,某些东西在AD中没有被正确删除而且它的混乱因为该站之前已经被域加入了.我将通过重新创建一个全新的VM再次尝试,并将回发结果.

编辑5：使用空白硬盘驱动器创建一个全新的VM使用凭据设置给我相同的结果和日志错误.我还尝试添加WDS服务器的复选标记,上面写着“安装后不要将客户端加入域”.认为那里可能存在冲突并且答案文件无效…我已经尝试将UnsecureJoin再次设置为True并使用全新的VM删除凭据设置以便查看但我得到了之前的再次出错……帮忙？

编辑6：我怀疑的另一件事是计算机是UEFI而不是BIOS.

编辑7：使用以下答案文件,我可以在每次取消选中WDS中的“请求管理员批准”复选框时成功加入域.一旦检查,它就会失败并向我发出错误：

"NetpLdapBind: ldap_bind Failed on PDC.ad.domain.com: 49: Informations d'identification non valides".

最后一部分转换为“标识信息无效”.

答案文件的重要部分,如果您还需要其他任何内容,请与我们联系：

<settings pass="specialize">
    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <Identification>
            <UnsecureJoin>true</UnsecureJoin>
        </Identification>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <ComputerName>%MACHINENAME%</ComputerName>
        <RegisteredOrganization>Organization</RegisteredOrganization>
        <RegisteredOwner>Utilisateur</RegisteredOwner>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <InputLocale>0c0c:00001009</InputLocale>
        <SystemLocale>0c0c:00001009</SystemLocale>
        <UILanguage>fr-CA</UILanguage>
        <UserLocale>en-US</UserLocale>
    </component>
</settings>

编辑8

专业部分现在看起来像：

<settings pass="specialize">
    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <Identification>
            <UnsecureJoin>true</UnsecureJoin>
            <JoinDomain>%MACHINEDOMAIN%</JoinDomain>
        </Identification>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <RegisteredOrganization>Organization</RegisteredOrganization>
        <RegisteredOwner>Utilisateur</RegisteredOwner>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <InputLocale>1009:00001009</InputLocale>
        <SystemLocale>en-US</SystemLocale>
        <UILanguage>fr-FR</UILanguage>
        <UserLocale>en-US</UserLocale>
    </component>
</settings>

NetSetup日志反复给我这个：

11/20/2014 14:22:53:596 NetpDoDomainJoin
11/20/2014 14:22:53:612 NetpDoDomainJoin: using new computer names
11/20/2014 14:22:53:612 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0
11/20/2014 14:22:53:612 NetpDoDomainJoin: NetpGetNewHostName returned 0x0
11/20/2014 14:22:53:612 NetpMachineValidToJoin: 'WIN-6PMPRQ5FVI5'
11/20/2014 14:22:53:612     OS Version: 6.3
11/20/2014 14:22:53:612     Build number: 9600 (9600.winblue_r3.140827-1500)
11/20/2014 14:22:53:659     SKU: Windows 8.1 Professionnel
11/20/2014 14:22:53:659     Architecture: 64-bit (AMD64)
11/20/2014 14:22:53:659 NetpDomainJoinLicensingCheck: ulLicenseValue=1,Status: 0x0
11/20/2014 14:22:53:659 NetpGetLsaPrimaryDomain: status: 0x0
11/20/2014 14:22:53:659 NetpMachineValidToJoin: status: 0x0
11/20/2014 14:22:53:659 NetpJoinDomain
11/20/2014 14:22:53:659     HostName: WIN-6PMPRQ5FVI5
11/20/2014 14:22:53:659     NetbiosName: WIN-6PMPRQ5FVI5
11/20/2014 14:22:53:659     Domain: ad.domain.com\PDC.ad.domain.com
11/20/2014 14:22:53:659     MachineAccountOU: (NULL)
11/20/2014 14:22:53:659     Account: (NULL)
11/20/2014 14:22:53:659     Options: 0x61
11/20/2014 14:22:53:659 NetpLoadParameters: loading registry parameters...
11/20/2014 14:22:53:659 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1' 0x2
11/20/2014 14:22:53:659 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/20/2014 14:22:53:659 NetpLoadParameters: status: 0x2
11/20/2014 14:22:53:659 NetpJoinDomainOnDs: Unsecure join requested.
11/20/2014 14:22:53:659 NetpDisableIDNEncoding: no domain dns available - IDN encoding will NOT be disabled
11/20/2014 14:22:53:659 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
11/20/2014 14:22:53:799 [000004e4] NetpGetLsaPrimaryDomain: status: 0x0
11/20/2014 14:22:53:846 NetpJoinDomainOnDs: status of connecting to dc '\\PDC.ad.domain.com': 0x0
11/20/2014 14:22:53:846 NetpJoinDomainOnDs: Passed DC 'PDC.ad.domain.com' verified as DNS name '\\PDC.ad.domain.com'
11/20/2014 14:22:53:846 NetpLoadParameters: loading registry parameters...
11/20/2014 14:22:53:846 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1' 0x2
11/20/2014 14:22:53:846 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/20/2014 14:22:53:846 NetpLoadParameters: status: 0x2
11/20/2014 14:22:53:846 NetpDsGetDcName: status of verifying DNS A record name resolution for 'PDC.ad.domain.com': 0x0
11/20/2014 14:22:53:846 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: ad.domain.com
11/20/2014 14:22:53:862 NetpProvisionComputerAccount:
11/20/2014 14:22:53:862     lpDomain: ad.domain.com
11/20/2014 14:22:53:862     lpHostName: WIN-6PMPRQ5FVI5
11/20/2014 14:22:53:862     lpMachineAccountOU: (NULL)
11/20/2014 14:22:53:862     lpDcName: PDC.ad.domain.com
11/20/2014 14:22:53:862     lpMachinePassword: (null)
11/20/2014 14:22:53:862     lpAccount: ad.domain.com\WIN-6PMPRQ5FVI5$
11/20/2014 14:22:53:862     lpPassword: (null)
11/20/2014 14:22:53:862     dwJoinOptions: 0x61
11/20/2014 14:22:53:862     dwOptions: 0xc0000007
11/20/2014 14:22:53:877 NetpLdapBind: Verified minimum encryption strength on PDC.ad.domain.com: 0x0
11/20/2014 14:22:53:877 NetpLdapGetLsaPrimaryDomain: reading domain data
11/20/2014 14:22:53:877 NetpGetNCData: Reading NC data
11/20/2014 14:22:53:877 NetpGetDomainData: Lookup domain data for: DC=ad,DC=com
11/20/2014 14:22:53:877 NetpGetDomainData: Failed to find the domain data: 0x6e
11/20/2014 14:22:53:877 NetpLdapGetLsaPrimaryDomain: result of retrieving domain data: 0x6e
11/20/2014 14:22:53:893 ldap_unbind status: 0x0
11/20/2014 14:22:53:893 NetpJoinCreatePackagePart: status:0x6e.
11/20/2014 14:22:53:893 NetpAddProvisioningPackagePart: status:0x6e.
11/20/2014 14:22:53:893 NetpJoinDomainOnDs: Function exits with status of: 0x6e
11/20/2014 14:22:53:893 NetpJoinDomainOnDs: status of disconnecting from '\\PDC.ad.domain.com': 0x0
11/20/2014 14:22:53:893 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
11/20/2014 14:22:53:893 NetpDoDomainJoin: status: 0x6e

正如您所看到的,“WIN-6PMPRQ5FVI5”上方的名称是自动生成的,我提供的名称无处可见……更糟糕的是,这在2012 WDS之前工作得很好所以我不确定他们究竟改变了什么在界面外面显示.谢谢你的帮助！

编辑9：
我再次尝试将％MACHINEDOMAIN％和％MACHINENAME％值都放在一起.这也不起作用,但我最终得到了来自NetSetup.log的以下信息：

11/20/2014 16:23:32:232 NetpDoDomainJoin
11/20/2014 16:23:32:232 NetpDoDomainJoin: using new computer names
11/20/2014 16:23:32:232 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0
11/20/2014 16:23:32:232 NetpDoDomainJoin: NetpGetNewHostName returned 0x0
11/20/2014 16:23:32:232 NetpMachineValidToJoin: 'IMAGE-TEST'
11/20/2014 16:23:32:232     OS Version: 6.3
11/20/2014 16:23:32:232     Build number: 9600 (9600.winblue_r3.140827-1500)
11/20/2014 16:23:32:295     SKU: Windows 8.1 Professionnel
11/20/2014 16:23:32:295     Architecture: 64-bit (AMD64)
11/20/2014 16:23:32:295 NetpDomainJoinLicensingCheck: ulLicenseValue=1,Status: 0x0
11/20/2014 16:23:32:295 NetpGetLsaPrimaryDomain: status: 0x0
11/20/2014 16:23:32:295 NetpMachineValidToJoin: status: 0x0
11/20/2014 16:23:32:295 NetpJoinDomain
11/20/2014 16:23:32:295     HostName: IMAGE-TEST
11/20/2014 16:23:32:295     NetbiosName: IMAGE-TEST
11/20/2014 16:23:32:295     Domain: ad.domain.com\dc.ad.domain.com
11/20/2014 16:23:32:295     MachineAccountOU: (NULL)
11/20/2014 16:23:32:295     Account: (NULL)
11/20/2014 16:23:32:295     Options: 0x61
11/20/2014 16:23:32:295 NetpLoadParameters: loading registry parameters...
11/20/2014 16:23:32:295 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1' 0x2
11/20/2014 16:23:32:295 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/20/2014 16:23:32:295 NetpLoadParameters: status: 0x2
11/20/2014 16:23:32:295 NetpJoinDomainOnDs: Unsecure join requested.
11/20/2014 16:23:32:295 NetpDisableIDNEncoding: no domain dns available - IDN encoding will NOT be disabled
11/20/2014 16:23:32:295 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
11/20/2014 16:23:32:482 [0000051c] NetpGetLsaPrimaryDomain: status: 0x0
11/20/2014 16:23:32:498 NetpJoinDomainOnDs: status of connecting to dc '\\dc.ad.domain.com': 0x0
11/20/2014 16:23:32:513 NetpJoinDomainOnDs: Passed DC 'dc.ad.domain.com' verified as DNS name '\\dc.ad.domain.com'
11/20/2014 16:23:32:513 NetpLoadParameters: loading registry parameters...
11/20/2014 16:23:32:513 NetpLoadParameters: DNSNameResolutionrequired not found,defaulting to '1' 0x2
11/20/2014 16:23:32:513 NetpLoadParameters: DomainCompatibilityMode not found,defaulting to '0' 0x2
11/20/2014 16:23:32:513 NetpLoadParameters: status: 0x2
11/20/2014 16:23:32:513 NetpDsGetDcName: status of verifying DNS A record name resolution for 'dc.ad.domain.com': 0x0
11/20/2014 16:23:32:513 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: ad.domain.com
11/20/2014 16:23:32:529 NetpProvisionComputerAccount:
11/20/2014 16:23:32:529     lpDomain: ad.domain.com
11/20/2014 16:23:32:529     lpHostName: IMAGE-TEST
11/20/2014 16:23:32:529     lpMachineAccountOU: (NULL)
11/20/2014 16:23:32:529     lpDcName: dc.ad.domain.com
11/20/2014 16:23:32:529     lpMachinePassword: (null)
11/20/2014 16:23:32:529     lpAccount: ad.domain.com\IMAGE-TEST$
11/20/2014 16:23:32:529     lpPassword: (null)
11/20/2014 16:23:32:529     dwJoinOptions: 0x61
11/20/2014 16:23:32:529     dwOptions: 0xc0000007
11/20/2014 16:23:32:545 NetpLdapBind: Verified minimum encryption strength on dc.ad.domain.com: 0x0
11/20/2014 16:23:32:545 NetpLdapGetLsaPrimaryDomain: reading domain data
11/20/2014 16:23:32:545 NetpGetNCData: Reading NC data
11/20/2014 16:23:32:545 NetpGetDomainData: Lookup domain data for: DC=ad,DC=com
11/20/2014 16:23:32:545 NetpGetDomainData: Failed to find the domain data: 0x6e
11/20/2014 16:23:32:545 NetpLdapGetLsaPrimaryDomain: result of retrieving domain data: 0x6e
11/20/2014 16:23:32:545 ldap_unbind status: 0x0
11/20/2014 16:23:32:545 NetpJoinCreatePackagePart: status:0x6e.
11/20/2014 16:23:32:545 NetpAddProvisioningPackagePart: status:0x6e.
11/20/2014 16:23:32:545 NetpJoinDomainOnDs: Function exits with status of: 0x6e
11/20/2014 16:23:32:545 NetpJoinDomainOnDs: status of disconnecting from '\\dc.ad.domain.com': 0x0
11/20/2014 16:23:32:545 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
11/20/2014 16:23:32:545 NetpDoDomainJoin: status: 0x6e

至少现在使用WDS中给出的名称,但现在突出的错误是：NetpGetDomainData：找不到域数据：0x6e,我不知道为什么.我将尝试硬编码域而不是放置％MACHINEDOMAIN％并将回发结果.

编辑10：目前用MS获得了此票.一旦找到解决方案,就会回复解决方案.到目前为止,似乎是WS2012 WDS中的一个错误.将发布更多信息.

添加信息,这也适用于带有W7 Pro机器的2008 Std R2.

对于可能涉及的所有人,由于此问题仅适用于域管理员组级别,我认为尝试使用帐户通过域根级别的委派控制授予所有权限,这也是有效的,因此不需要去改变每个UEFI计算机对象的安全设置:).

如何：

>我创建了一个用户WDSinstall,其唯一的组成员身份是Domain User.
>然后我只是通过Delegate Control向导(在这种情况下,右键单击根域节点并选择Delegate Control).
>添加新创建的帐户,然后单击“下一步”.
>选择创建要委派的自定义任务,然后单击下一步.
>选中“此文件夹,此文件中的现有对象”,然后单击“下一步”.
>确保勾选“显示这些权限”下的所有3个选项,这意味着：常规,特定于属性以及特定子对象的创建/删除.
>在“权限”框中,只需选中“完全控制”,这也将选择所有其他权限.点击下一步.
>单击“完成”.

现在您拥有一个本质上是Domain Admin帐户的帐户,因此,您可以将其用于所有WDS和部署需求.

我希望这可以帮助别人,就像这个原始帖子帮助我(很多).

无法在Windows 8.1上使用WDS和应答文件执行无人参与的域加入

猜你在找的Windows相关文章