none
domain join with unattend.xml failed RRS feed

  • Question

  • Hi All,

    I am failed to join to domain with Sysprep unattend.xml.


    N.A.Malik


    • Edited by N A Malik Friday, February 7, 2014 4:34 PM
    Wednesday, January 29, 2014 8:00 AM

Answers

  • Its solved now... actually PC was trying to join the DC with the computer name like (Win123XYZ).
    When setup reached the OOBE, user is created and hence PC name changed ... and eventually failed to login the PC.

    N.A.Malik

    • Marked as answer by N A Malik Tuesday, February 4, 2014 8:05 PM
    Tuesday, February 4, 2014 8:04 PM

All replies

  • Hi Malik,

    According to your description,you used Unsecure domain join.

    Please upload %WINDIR%\Panther\Unattendgc\setupact.log so that we can help you analyze the issue.

    Meanwhile,I would like to share the following articles with you:

    http://technet.microsoft.com/en-us/library/cc730845(v=ws.10).aspx

    http://technet.microsoft.com/en-us/library/cc732280(v=ws.10)#Image1

    Note: I highly recommend you use SkyDrive to upload collected files and to post screen shots/pictures. Although you might not be used to it, SkyDrive features a lot of free advanced functionality around file storage capacity, sharing, privacy, and collaboration:
    http://skydrive.com

    Regards,


    Kelvin hsu
    TechNet Community Support

    Friday, January 31, 2014 2:25 AM
    Moderator
  • Hi,

    Thanks for reply. I have tested without UNSECURE Join as well, no success.


    N.A.Malik



    • Edited by N A Malik Friday, February 7, 2014 4:35 PM
    Friday, January 31, 2014 8:39 AM
  • Hi,

    ERROR_INVALID_PARAMETER 87 (0x57) means The parameter is incorrect.

    You can also refer to the similar thread about thisissue:

    http://social.technet.microsoft.com/Forums/windows/en-US/3c05780f-4beb-40ad-9f1d-fbeb748b95a9/windows-7-unattended-domain-issues?forum=w7itproinstall

    If the issue persists,please  upload the "%windir%\debug\netsetup.log " file.

    Regards,


    Kelvin hsu
    TechNet Community Support




    Friday, January 31, 2014 9:45 AM
    Moderator
  • Hi,

    I appreciate your support, I have removed the UnSecureJoin and tested, failed .

    Here is the link to the files: http://sdrv.ms/1bcC7bY

    Under the debug dir, I cant see netsetup.log but I have copied the whole dir anyway.


    N.A.Malik

    Friday, January 31, 2014 12:43 PM
  • Is there a special reason you are using the MachinePassword setting? If you remove it from the unattend file that you posted, and let the domain join happen without that setting, does it work then? The MachinePassword article on TechNet states that 'This setting is only valid if UnsecureJoin is set to true. This is also mentioned in the setuperr.log file:
    [DJOIN.EXE] Unattended Join: Passing MachinePassword requires explicitly setting UnsecureJoin
    [DJOIN.EXE] Unattended Join: Failed to load all required input parameters, error occured processing [MachinePassword]: 0x57

    Hope this helps,

    David
    Windows Outreach Team - IT Pro
    The Springboard Series on TechNet

    Friday, January 31, 2014 6:02 PM
    Moderator
  • Hi David,

    Thanks for reply, I will remove MachinePassword and see what happen.


    N.A.Malik




    • Edited by N A Malik Friday, February 7, 2014 4:36 PM
    Friday, January 31, 2014 10:30 PM
  • Hi,

    I am just checking to see how things are going there on this issue. If you would like further assistance, please do not hesitate to let me know. It is my pleasure to help. :)

    Regards,


    Kelvin hsu
    TechNet Community Support

    Monday, February 3, 2014 1:48 AM
    Moderator
  • Hi and Thanks for reply.

    Now I have removed the MachinePassword + UnsecureJoin to False.

    ..... a little bit improvement, now I can see Ctrl+Alt+Del to login to domain.

    Tried to login to domain but received the following message:

    The security Database on the server doesn't have a computer account for this workstation trust relationship.


    N.A.Malik



    • Edited by N A Malik Friday, February 7, 2014 4:35 PM
    Monday, February 3, 2014 7:41 AM
  • Its solved now... actually PC was trying to join the DC with the computer name like (Win123XYZ).
    When setup reached the OOBE, user is created and hence PC name changed ... and eventually failed to login the PC.

    N.A.Malik

    • Marked as answer by N A Malik Tuesday, February 4, 2014 8:05 PM
    Tuesday, February 4, 2014 8:04 PM
  • Fantastic... Glad you have it working.

    Tuesday, February 4, 2014 8:26 PM
    Moderator