+ Post New Thread
Results 1 to 9 of 9
O/S Deployment Thread, Deployment Workbench - WIM issues in Technical; Hi, I wondered if anyone could help, I am trying to run sysprep and capture through MDT and each time ...
  1. #1

    Join Date
    Mar 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Deployment Workbench - WIM issues

    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.

  2. #2


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    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

  3. #3

    Join Date
    Mar 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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.

  4. #4


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    but are you starting the task by booting from wds or from going to \\server\deploymentshare$\ and running litetouch.vbs?

  5. #5

    Join Date
    Mar 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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.

  6. #6


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    try creating a 2nd deployment share and capturing to that see what happens

  7. #7
    Hedghog's Avatar
    Join Date
    Jul 2006
    Location
    North Wales
    Posts
    194
    Thank Post
    35
    Thanked 17 Times in 16 Posts
    Rep Power
    37
    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.

  8. #8

    Join Date
    Oct 2009
    Location
    London
    Posts
    18
    Thank Post
    1
    Thanked 7 Times in 7 Posts
    Rep Power
    12
    Quote Originally Posted by sted View Post
    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

  9. #9

    Join Date
    Jan 2011
    Location
    London
    Posts
    32
    Thank Post
    11
    Thanked 5 Times in 5 Posts
    Rep Power
    8
    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.

SHARE:
+ Post New Thread

Similar Threads

  1. Deployment Workbench, PowerShell Issue
    By S_Hannah in forum Windows Server 2008
    Replies: 7
    Last Post: 23rd October 2012, 07:06 PM
  2. SCCM XP Deployment - Daily Usage Issues
    By napsburypark in forum O/S Deployment
    Replies: 1
    Last Post: 9th November 2011, 11:14 AM
  3. Replies: 3
    Last Post: 31st October 2011, 12:34 PM
  4. MDT Deployment Workbench
    By cpjitservices in forum Windows Server 2008 R2
    Replies: 5
    Last Post: 26th July 2011, 10:02 PM
  5. Finally deployed, one small issue...
    By mrbios in forum Windows 7
    Replies: 21
    Last Post: 9th February 2010, 11:00 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •