asked on

Troubleshooting MDT

Hi I have been setting up a build lab on Hyper V creating a standard task sequence with MDT 8443 and Windows 1607 on a server 2016 (dc01, mdt and wsus) infrastructure, everything apart from the capture is automated and it works well and creates a wim file at the end of the sequence as expected
However if I try to automate the capture sequence by setting skipcapture =yes and supplying details for the location backup folder and file name after the machine has syprepped it starts as if it is loading the PE files and then shuts down my hyper v machine how can I troubleshoot this where to start any help would be greatly appreciated

Thanks

Wafty

Muhammad Burhan

have you enabled logging ?

Andrew Jamieson

ASKER

yes I have logs but I am not sure where to start ,the task sequence says in monitoring it has completed which log will help?
BDD.zip

aravind anche

Download cmtrace tool and then open bdd log with.
Start your task sequence and open cmtrace tool you can see where it is going wrong.

also there will be no spaces in SkipCapture=YES

follow the below link
https://www.scconfigmgr.com/2013/02/14/completely-automate-the-reference-image-creation-process/

once we run the TS everything is automated, some times what I do is disable sysprep in TS.
Also if you use SkipCapture=YES, no wim file is created as you are skipping capture in custom settings

Andrew Jamieson

ASKER

Hi and thanks for your comments as I understand it the Skipcapture variable just doesn't show the capture screen on first boot but you have to provide a location in the custom settings this is a standard task sequence it is just running again now with skipcapture set to no and I am asked location and name of wim file it has just finished and sys prepped and captured image to the captures folder in my build lab deployment share I have CM trace and monitoring but after it sys preps it just shuts down with no error I can see

aravind anche

Can you send me the custom settings
Normally for the capture TS i use these below

DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\server\DeploymentShare$\Captures
BackupDir=%OSDComputerName%

Andrew Jamieson

ASKER

Yes at home but I will do it in the morning

Thanks in advance

Andrew Jamieson

ASKER

Hi this is what is in it,this is a build lab but up until I add the backup directory location and file name, it all works if I select it manually as part of the first boot.

When I select it manually it saves to the same location as the lines below in my customsettings.ini

If I can make it work I can make it fully automatic.

[Settings]
Priority=Default

[Default]
_SMSTSORGNAME=*********
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
AdminPassword=P@ssw0rd
TimeZoneName=Pacific Standard Time
JoinWorkgroup=WORKGROUP
HideShell=NO
FinishAction=SHUTDOWN
ApplyGPOPack=NO
SLSHARE=\\MDT01\Logs$

WSUSServer=http://***********************

SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=YES
TaskSequenceid=W10-X64-001
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=YES

BackupShare=\\MDT01\MDTBuildLab$
BackupDir=Captures
BackupFile=%TaskSequenceID%_#month(date) & "-" & day(date) & "-" & year(date)#.wim

SkipFinalSummary=YES

Bootstrap below

[Settings]
Priority=Default

[Default]
DeployRoot=\\MDT01\MDTBuildLab$
UserDomain=**********
UserID=MDT_BA
UserPassword=P@ssw0rd

SkipBDDWelcome=YES

ASKER CERTIFIED SOLUTION

aravind anche

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Andrew Jamieson

ASKER

I have followed those instructions so far it is Windows Enterprise v1607 it is just a follow on from that to automate, with skipcapture=no it works I can set the tasksequenceid and it works its just the backup location that fails I may try adding the computerbackuplocation=network and see what happens then update tomorrow

thanks

aravind anche

That might work, i will check for more in my lab.
Windows 10 deployment I only have one problem i.e default profile. other than that no issues

Andrew Jamieson

ASKER

Adding the line ComputerBackupLocation=NETWORK solved my issue all the build and capture and naming is automated now thanks for all the comments

Andy

aravind anche

good that solved your issue.
Please select the best answer and close the question