none
join to domain and firstTimeLogin commands RRS feed

  • Question

  • I am using mdt2013 update 2 and surface accelerator

    surface accelerator is installed and created the deployment share properly with drivers, the 2 tasks deploy and capture;

    I have uploaded into the deployment share the windows 10 iso;

    I have captured a wim image customized properly with the suspend task

    I am now testing deploying the captured wim to a new vm

    the deployment share is the same (don't know why surface accelerator doesn't create 2 since you need 2 different customsettings.ini and/or 2 unattend.xml - you'll see what I mean lower)

    anyway, I used the same deployment share and changed the settings in the customsettings.ini to include the following

    JoinDomain=xxxxxxx.xx
    DomainAdmin=xxxxxx\xxxxx
    DomainAdminPassword=xxxxxxxx
    MachineObjectOU=OU=xxxx,OU=xxxxx,OU=xxx xxx,OU=xx,DC=xxxxxx,DC=xx

    I have booted the vm with the iso created from the deployment share; join to domain does not occur

    next, I have added a command line to the deploy task sequence

    script.exe %SCRIPTROOT%\CUSTOM\ZTIDomainJoin.wsf

    positioned in the state restore after the windows updates (post application installation)

    tested; join to domain does not occur

    next I removed the settings from the rules (thus automatically from customsettings.ini) and the command line from the task sequence and added the same details in the unattend.xml manually , positioned in the specialize / amd64_microsoft-windows-unattendedjoin_neutral;

    save tested ; join to domain does not occur

    help ?

    -------------------------------------------------------------------------------------------------------------------------------

    the other mystery is the firstTimeLogon comands

    I have saved a batch file in the captured wim

    the batch is launching some executables also saved in the captured wim files and also runs some regedit commands

    these have to be ran at the deployment time and have nothing to do with applications in mdt , outside of the wim file;

    they have to be executer from inside the image and reference local paths

    I have added the path manually in the unattend.xml positioned at step 7 oobe system / amd64_microsoft-windows-shell-setup_neutral / firstlogoncommands

    there was already one created by default so I've added a new one

    order 2

    command line   :   cmd /c   c:\batchfile.bat

    it's not being launched

    help ?

    ---------------------------------------------------------------------------------------------------------------------------

    end of transmission (:

    Thursday, November 3, 2016 10:44 PM

All replies

  • why is unattend.xml not updated by ZTIConfigure.wsf using the rules bellow ?

    JoinDomain=xxxxxxx.xx
    DomainAdmin=xxxxxx\xxxxx
    DomainAdminPassword=xxxxxxxx
    MachineObjectOU=OU=xxxx,OU=xxxxx,OU=xxx xxx,OU=xx,DC=xxxxxx,DC=xx

    https://social.technet.microsoft.com/Forums/en-US/3b3856fe-70c2-4415-b1fd-602e5ff742db/unattendxml-vs-deplymentshares-rules?forum=mdt

    I am looking at the bdd.log and no domain join related properties are updated. No wonder ...

    example:"//unattend:settings[@pass="specialize"]/unattend:component[@name="Microsoft-Windows-UnattendedJoin"]/unattend:Identification/unattend:JoinDomain not found in C:\MININT\Unattend.xml, unable to update."

    Tuesday, November 8, 2016 12:46 AM
  • another attempt

    I've stopped using iso to boot the vm and started using wds after uninstalling sccm (couldn't boot pxe while sccm was installed on the same machine as wds, mdt); anyway this is a lab and pxe booting from sccm is another story

    so I've came back to the origins , how it should work "as designed ?":

    I have the rules on the deployment share

    JoinDomain=xxxxxxx.xx
    DomainAdmin=xxxxxx\xxxxx
    DomainAdminPassword=xxxxxxxx
    MachineObjectOU=OU=xxxx,OU=xxxxx,OU=xxx xxx,OU=xx,DC=xxxxxx,DC=xx

    I have the recover from domain in the task sequence enabled

    I have a new unattended.xml untouched in the specialize / amd64_microsoft-windows-unattendedjoin_neutral

    and

    I've added the path manually in the unattend.xml positioned at step 7 oobe system / amd64_microsoft-windows-shell-setup_neutral / firstlogoncommands

    as

    c:\batchfile.bat     (c being the c drive on the new vm to be imaged, not the c drive of the mdt server)

    I've started deployment and it failed again for both things;

    however I can see now the unattended.xml file in the c:\windows\panther   and it contains both the information for domain joining from the rules and the firsttimelogon command

    not bad.

    however the file is not processed for some reason.

    I looked in bdd.log and I see

    "

    Looking for Sysprep.inf in C:\sysprep\Sysprep.inf

    The sysprep.inf file was not found.

    Property OSDAnswerFilePathSysprep is now =

    The unattend.txt file was not found.

    "

    could that be the reason ?

    Tuesday, November 8, 2016 8:23 PM