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 (: