Deployment Workbench - WIM issues

[LausHHS]

Hi,

 

I wondered if anyone could help, I am trying to run sysprep and capture through MDT and each time I run this on the reference machine it skips from the chosen 'task sequence' to 'begin' before i have a chance to name and locate the save for the WIM image. Any suggestions?

 

Thank You in advance.

[sted]

are you booting windows on the pc or from a boot.wim on the server?

 

you need to run sysprep and capture from windows

 

also in your customsettings.ini file in your deployment share make sure you DONT have a line SkipCapture=YES or it will skip it

[LausHHS]

I have set up the task sequence to use a 64bit windows .wim from the server, my .ini settings are showing No for the skip capture. I am using the BDD_Autorun script from the deployment share folder i.e the reference PC points to \\server name\deploymentshare$

 

if i run the sysprep and capture this seems to lose the current laptop setup.

[sted]

but are you starting the task by booting from wds or from going to \\server\deploymentshare$\ and running litetouch.vbs?

[LausHHS]

I am starting this from \\server\deploymentshare$\ and running litetouch.vbs, I have only ever deployed images but never captured so this is all new to me.

[sted]

try creating a 2nd deployment share and capturing to that see what happens

[Hedghog]

The way I do it (and many of the articles point to this) is to run a sysprep and capture task sequence booted from the network with a base boot image and generic OS load (plus drivers), then build the reference PC as you want it.

Next navigate to the deployment share and run "litetouch.vbs" this will sysprep and capture your image.

If this dos'nt work repost and I will re-run my capture system to see if I've missed anything.

[rdsc]

try creating a 2nd deployment share and capturing to that see what happens

 

I 2nd this - couldn't get capture to work reliably with the custom settings.ini I wanted for my deployment share, and ran out of patience trying to troubleshoot it. I run it with an absolutely minimal custom settings ini and basic bootstrap

 

[settings]

Priority=Default

Properties=MyCustomProperty

 

[Default]

OSInstall=Y

 

SkipAppsOnUpgrade=YES

SkipCapture=NO

SkipAdminPassword=YES

SkipProductKey=YES

 

If you want to keep installed devices during sysprep (and you're absolutely certain your devices have an identical hardware spec) - set PersistAllDevices to true in Pass 3 - amd64_Microsoft-Windows-PnpSysprep_6.1.7601.17514_neutral

[andypitts]

Similar to @rdsc, I ended with 2 custom settings.ini files - one for capturing (very minimal settings) and the other for deploying (with all the gubbins). Our capture/deployment rate is fairly low so I just manually switch them over depending on the task. Capturing against a minimal custom settings.ini file like the one above would be worth trying even if the one you're using appears to have the right settings - if nothing else it could help to rule out this as a reason for the capture problem.