staun

We had a working WDS setup to install our clients but for some reason the part where the computer should join the domain it fails <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" 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> <JoinDomain>ourdomain.loc</JoinDomain> <UnsecureJoin>true</UnsecureJoin> </Identification> </component> No changes to the unattend files or the WDS server has been made. The join domain issue also fails on another WDS server located on another site. So it must be something centralized - and the only thing I can come up with is our Active Directory. But I have no idea what to look for. (the only resent change is that we added a ReadOnly Domain Controller, but this RODC is on another network) The error we get in the setupact.log file is 2013-03-15 12:09:54, Info [DJOIN.EXE] Unattended Join: Checking that auto start services have started. 2013-03-15 12:09:54, Info [DJOIN.EXE] Unattended Join: Joining domain [ourdomain]... 2013-03-15 12:09:54, Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for ourdomain... 2013-03-15 12:09:54, Info [DJOIN.EXE] Unattended Join: DsGetDcName returned [DOMAINCONTROLLER_NAME] 2013-03-15 12:09:54, Info [DJOIN.EXE] Unattended Join: Constructed domain parameter [ourdomain\DOMAINCONTROLLER_NAME] 2013-03-15 12:10:06, Warning [DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x6be, will retry in 5 seconds... 2013-03-15 12:10:11, Warning [DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x85a, will retry in 5 seconds... 2013-03-15 12:10:16, Warning [DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x85a, will retry in 5 seconds... 2013-03-15 12:10:21, Warning [DJOIN.EXE] Unattended Join: NetJoinDomain attempt failed: 0x85a, will retry in 5 seconds... If I specify a user (domain admin) to join the domain everything works fine. (using secure domain join) <Identification> <JoinDomain>our_domain</JoinDomain> <UnsecureJoin>false</UnsecureJoin> <DebugJoin>true</DebugJoin> <Credentials> <Domain>our_domain</Domain> <Password>our_password</Password> <Username>our_domainAdminUser</Username> </Credentials> </Identification> Any suggestions how to resolve this? (there is no problem adding the computer to the domain manually.)

You were right - it was a permissions issue. I just added a group with full control on the Computers Container at voila! Now I just need to specify lower permission on this folder - Full permissions must be overkill. Thanks a lot!!

No, I use <ComputerName>*</ComputerName> I attached the XML-file Update. I tried to specify a hardcode computername (gulerod345) and set machinepassword to the same, saw a similar issue that fixed the issue but that did not help me. If I look at det %windir\debug\netsetup.log file if that can help. ----------------------------------------------------------------- 02/23/2012 16:02:07:835 NetpDoDomainJoin 02/23/2012 16:02:07:835 NetpMachineValidToJoin: 'GULEROD345' 02/23/2012 16:02:07:835 OS Version: 6.1 02/23/2012 16:02:07:835 Build number: 7601 (7601.win7sp1_rtm.101119-1850) 02/23/2012 16:02:07:835 ServicePack: Service Pack 1 02/23/2012 16:02:07:835 SKU: Windows 7 Enterprise 02/23/2012 16:02:07:835 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0 02/23/2012 16:02:07:835 NetpGetLsaPrimaryDomain: status: 0x0 02/23/2012 16:02:07:835 NetpMachineValidToJoin: status: 0x0 02/23/2012 16:02:07:835 NetpJoinDomain 02/23/2012 16:02:07:835 Machine: GULEROD345 02/23/2012 16:02:07:835 Domain: company.loc\SRV-DC-NSB3.company.loc 02/23/2012 16:02:07:835 MachineAccountOU: (NULL) 02/23/2012 16:02:07:835 Account: (NULL) 02/23/2012 16:02:07:835 Options: 0xe1 02/23/2012 16:02:07:835 NetpLoadParameters: loading registry parameters... 02/23/2012 16:02:07:835 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2 02/23/2012 16:02:07:835 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2 02/23/2012 16:02:07:835 NetpLoadParameters: status: 0x2 02/23/2012 16:02:07:835 NetpJoinDomain: Unsecure join requested. 02/23/2012 16:02:07:835 NetpJoinDomain: NETSETUP_MACHINE_PWD_PASSED passed, using lpPassword to authenticate as machine 02/23/2012 16:02:07:835 NetpValidateName: checking to see if 'company.loc' is valid as type 3 name 02/23/2012 16:02:08:272 NetpCheckDomainNameIsValid [ Exists ] for 'company.loc' returned 0x0 02/23/2012 16:02:08:272 NetpValidateName: name 'company.loc' is valid for type 3 02/23/2012 16:02:08:272 NetUseAdd to \\SRV-DC-NSB3.company.loc\IPC$ returned 1326 02/23/2012 16:02:08:272 Trying add to \\SRV-DC-NSB3.company.loc\IPC$ using NULL Session 02/23/2012 16:02:08:272 NetpJoinDomain: status of connecting to dc '\\SRV-DC-NSB3.company.loc': 0x0 02/23/2012 16:02:08:288 NetpJoinDomainOnDs: Passed DC 'SRV-DC-NSB3.company.loc' verified as DNS name '\\SRV-DC-NSB3.company.loc' 02/23/2012 16:02:08:288 NetpLoadParameters: loading registry parameters... 02/23/2012 16:02:08:288 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2 02/23/2012 16:02:08:288 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2 02/23/2012 16:02:08:288 NetpLoadParameters: status: 0x2 02/23/2012 16:02:08:288 NetpDsGetDcName: status of verifying DNS A record name resolution for 'SRV-DC-NSB3.company.loc': 0x0 02/23/2012 16:02:08:288 NetpProvisionComputerAccount: 02/23/2012 16:02:08:288 lpDomain: company.loc 02/23/2012 16:02:08:288 lpMachineName: GULEROD345 02/23/2012 16:02:08:288 lpMachineAccountOU: (NULL) 02/23/2012 16:02:08:288 lpDcName: SRV-DC-NSB3.company.loc 02/23/2012 16:02:08:288 lpDnsHostName: (NULL) 02/23/2012 16:02:08:288 lpMachinePassword: (non-null) 02/23/2012 16:02:08:288 lpAccount: company.loc\GULEROD345$ 02/23/2012 16:02:08:288 lpPassword: (non-null) 02/23/2012 16:02:08:288 dwJoinOptions: 0xe1 02/23/2012 16:02:08:288 dwOptions: 0xc0000003 02/23/2012 16:02:08:288 NetpLdapBind: ldap_bind failed on SRV-DC-NSB3.company.loc: 49: Invalid Credentials 02/23/2012 16:02:08:288 NetpJoinDomainOnDs: Function exits with status of: 0x52e 02/23/2012 16:02:08:288 NetpJoinDomainOnDs: status of disconnecting from '\\SRV-DC-NSB3.company.loc': 0x0 02/23/2012 16:02:08:288 NetpDoDomainJoin: status: 0x52e imageUnattend.xml

I have modified the default domain policy : Default Domain Controllers Policy-Admin Templates-System-Net Logon To ENABLED. If that is what your refer to. Update. If I logon to the computer with the local administrator account and try to add the computer to the domain with a domain user I get this error. The join operation was not successful. This could be because an existing computer account having the name “computer name” 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 The computer account does not exist in AD or DNS. If I add the computer to the domain with an admin-user it is succesfully added.

I have a weird issue with our unattended install of Windows 7 clients through WDS 2008R2. During the the initial boot setup we are asked for credentials - If I enter a domain admin account the rest of the process works fine. BUT if I use a standard domain user account the computer will not join the domain later during the first startup, even though I have stated that it should use a ImageUnattend.xml file. <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" 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> <JoinDomain>MYDOMAIN.LOC</JoinDomain> <UnsecureJoin>true</UnsecureJoin> </Identification> </component> I even tried to add a domain admin user credentials in the XML-file but it still fails. <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" 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> <Credentials> <Domain>MYDOMAIN</Domain> <Password>AdminUser</Password> <Username>PASSWORD</Username> </Credentials> <JoinDomain>MYDOMAIN.LOC</JoinDomain> <UnsecureJoin>true</UnsecureJoin> </Identification> </component> The XML-file is processed fine if the user is a domain admin. (tried several standard users and admin users.) Any idea how to allow standard users to install their OS through WDS and have the computer join the domain.?

Hi All, The Product name is correct - it is a retail version I think, the company bought. I tried with the settings you both mentioned but still the same - I am still asked to either Install Now or Customize. BTW the config file is being used- because I can try the customize and can here see that the company name is changed and install options are applied according to the config.xml file and the license dialog is bypassed. The dialog just want me to click Install Now?!?

Trying to do a completely silent install of Office 2010. But it keeps comming up with the Install/ Customize dialog. Here is my config.xml file <Configuration Product="ProPlusr"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> <PIDKEY Value="3243423423423424" /> <Setting Id="AUTO_ACTIVATE" Value="1" /> <USERNAME Value="myuser name" /> <COMPANYNAME Value="company name" /> <DistributionPoint Location="\\server\share\x86\ProPlusr.WW" /> <Setting Id="SETUP_REBOOT" Value="never" /> </Configuration> I had it working once or twice, but now it fails and asks for install etc.. I cannot use the setup /admin command since this is a different version of office 2010. Any idea what is wrong?

Hi, I added the templates, could you see anything that should be wrong with them? I wonder why it works if I run sysprep /generalize /oobe...... and not through the WDS deployment?

I have two XML-files WDSunattend.xml applied to the WDS-server (win 2008 R2) and one unattend.xml applied to the server2008R2 image. It almost works!. The problem is that the unattend.xml is not processed completely, only a few options are applied during a F12 WDS setup. The weird part is that if I run the sysprep manually with the same unattend.xml file it works fine. Any ideas why it only works when running the sysprep manually? and one thing more, the product key cannot be installed - error in unattendGC is - Failed to install product key .The MAK B product key is valid and works if I type it manually Edit: Files attached WDSUnattend.xml unattend.xml

I did add the drivers to the Boot.wim file. The problem was after the boot and install. I had no network. But I figured that I could inject the same drivers into install.wim and this works fine. Now I'm just having problems with the XML-unattend files. Eg.Productkey, language-settings fails (using Windows SIM) Ahhh - Lightbulb!! I just realized what you mean with option 1. Just found the driverpackage possibility :-). Will try this for the next image.

I managed to inject the vmxnet3 drivers into the boot.wim image. But after installing windows 2008 R2 there are no network drivers installed. I can install the VMware tools and then the network is fine. How can I have the network drivers installed during the unattended install? - my unattend.xml file does not get proccesed due to the missing network, at least that is what I think. any advise?

I'm trying to create an upgrade of an existing GPO that deploys an application. (add another MSI-patch to the existing package) When I edit the GPO and click the Upgrades tab I do not get any options here like mentioned in various Microsoft books and guides on the Internet. I have tried with Current Group Policy and A specific GPO but still the same. The window where the package should be is empty. See screendump Any one know what I'm doing wrong here?

Having some problems with deploying a new OS from RIS. The weird part is that it works, but yet don't work. it works on physical hardware machines, but when I try to install a new OS in a VMware server setup it doesn't work. I have another setup where it works fine. The error on the virtuel setup is after getting a DHCP-IP and waiting for a boot-file, it times out with this pxe-e32: TFTP open timeout pxe-e32: TFTP open timeout pxe-e32: TFTP open timeout pxe-M0F: exiting intel PXE ROM In my opinion it should not be a HW-problem since this is virtual HW and it works on the other network. Any idea what could be wrong.

I think it is your OemPnPDriversPath - it is tooooo long, you are only allowed to use 256 characters.

You should be able to create the $oem\$1 folder and place your needed driver-files here and then point to this path in your SIF-file (OemPnpDriversPath)