[mdt] Image Capture - MDT 2013

[Manny-Tech]

I seem to be coming up against a few hiccups when capturing an image (see attached image).

 

 

I have also attached the BDD log.

 

I'm not sure where to go on this one. It doesn't stop the WIM being created and I have just attempted to deploy it and it all went through fine apart from getting a yellow background and a warning of 'FAILURE ( 5206 ): The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed.'

bdd.txt

[themightymrp]

Hi there! Sorry I know you sent me a PM about this but I was off yesterday so didn't get to reading it.

 

This error is an annoyance but as you say, doesn't really break the WIM. Are you capturing a machine which was installed using an MDT deploy? If so, before you run your capture task sequence, check that there isn't a BDD.log file inside the c:\MININT folder from when you did the deploy. In fact, before capturing, delete the MININT folder completely (I do). It may be a hidden folder! Sometimes this old log file causes the "WizardComplete" variable to not set to "Y" correctly. No idea why.

 

As for the other thing you mentioned on the PM - from what I can see you already have the correct setting in your .ini file - SkipUserData=Yes - so not sure there?

Edited October 28, 2015 by themightymrp

[Manny-Tech]

I am capturing from an MDT deploy. I have checked the machine I'd like to capture and it doesn't have a C:\MININT in there. I did try capturing a machine that wasn't deployed by MDT and I got the same error messages.

[Manny-Tech]

The error started occurring when I was just deploying a standard task sequence with the OS and a few apps - in the end I reverted my deployment share to Friday's backup when I know it was working. I've since removed any domain join settings from the cs.ini and the capture is working and ending with a white background! I must have had a rogue domain join entry somewhere that was causing the ini file to have a little grumble.

[themightymrp]

Nicely done! Have you compared your working customsettings.ini file with the one that wasn't working? To see what the differences might have been?

 

I thought you might also make use of this file which I found somewhere on a Microsoft site a while back, some troubleshooting info for deployments. It gives you explanations of what a large number of error codes mean which is good!

 

https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB4QFjAAahUKEwi93sHa4unIAhWGuhoKHfpEDqE&url=http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Ftelligent-evolution-components-attachments%2F01-5209-00-00-03-51-93-68%2FTroubleshooting-Windows-Deployments-2012_2D00_09_2D00_11.pdf&usg=AFQjCNGjTOe_IROuFGsSxvkvIj7XbbVyfA

[Manny-Tech]

I had a 'JoinDomain' rule in there which was set, but I didn't have the following DomainAdmin, DomainAdminPassword and DomainAdminDomain configured. As it won't allow you to Sysprep whilst joined to a domain, I guess this is why it was showing options that I didn't expect on the wizard like the UserData and ComputerBackup though these were set to be skipped even when I had the SkipCapture=No configured. The only way to get the capture settings shown was to set the DoCapture=Yes.

 

I think it was a mix of me tampering trying to get it to work how I wanted, and losing track of what had changed and what hadn't.

 

Thanks for the documentation, very handy!

 

I'm not sure if this is achievable but I won't always want to capture an image, and I know it's not too much trouble to select 'Do Not Capture' but in an ideal world I only want the Capture settings to show when I actually want to capture. The only way to do this currently is to remove my domain join credentials and edit the line 'SkipCapture' to Yes, then revert back once I want to remove the capture option. I have seen people use different 'sections' in their Ini files, could this be done so I just have a section for captures?

[LukeC]

@Liam86 why don't you create a Captureshare and deploymentshare and have two different sets of settings relevant to each share. So when your PXE booting you select Deploy or Capture.

[themightymrp]

You can separate bits out in the customsettings.ini file yes.

 

What you could do is change the line under [settings] to read "Priority = TaskSequenceID, Default"

 

Place all of the generic settings (for captures/deploys) under the [Default] section. Then below that create a new section for each of your Task Sequences.

 

Example:

 

[Deploys]

 

SkipCapture=YES

ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

DomainJoin blah-de-blah

 

[Captures]

 

DoCapture=YES

Any specific capture settings

 

 

 

Just make sure that your headings correspond to your Task Sequence ID's. I was lazy and went with the default 0001, 0002 etc

[Manny-Tech]

Just trialling this out now.

 

It all looks correct to me, but each time I select the 001 TS it always defaults to workgroup, also asks me to capture which leads me to think it's maybe not applying the customsettings.ini correctly.

 

[settings]

Priority=TaskSequenceID,Default

Properties=MyCustomProperty

 

 

[Default]

OSInstall=Y

_SMSTSORGNAME=School Name

SkipAdminPassword=Yes

SkipProductKey=Yes

SkipBDDWelcome=Yes

SkipBitLocker=YES

SkipDeploymentType=Yes

SkipComputerBackup=YES

SkipPackageDisplay=Yes

SkipUserData=Yes

SkipWizard=No

SkipSummary=Yes

SkipFinalSummary=No

SkipTimeZone=Yes

SkipLocaleSelection=Yes

WSUSServer=http://SRVWSUS:8530

UserDataLocation=None

FinishAction=Restart

AdminPassword=

SkipDomainMembership=No

 

 

Countrycode=44

TimeZone=085

TimeZoneName=GMT Standard Time

UILanguage=en-GB

UILanguagefallback=0809:00000809

KeyboardLocale=0809:00000809

UserLocale=en-GB

InputLocale=0809:00000809

SystemLocale=0809:00000809

BitsPerPel=32

VRefresh=60

XResolution=1

YResolution=1

 

 

[001]

JoinDomain=domain

DomainAdmin=Deployment

DomainAdminPassword=

DomainAdminDomain=domain

SkipApplications=No

SkipCapture=YES

Edited November 6, 2015 by Manny-Tech

[themightymrp]

Have you tried updating the deploymentshare?

[Manny-Tech]

Yep did that first, though I think I read somewhere it shouldn't matter for the customsettings.ini but I always update it if something doesn't seem to have taken effect.

[Manny-Tech]

Found a work around to this: https://social.technet.microsoft.com/Forums/en-US/84831d92-b69a-493b-8dc8-3e0efb419242/tasksequenceid-not-being-set-trying-to-use-for-customsettingsini-sub-sections?forum=mdt

 

Essentially it's not running ZTIGather following the TS selection. I have edited the DeployWiz_SelectTS.vbs as mentioned in the above link, it does seem to work though there is one minor flaw in that if you select one TS and then want to go back and select another it retains the settings from the first TS you selected.