BDD 2007 – New BDD blog


Richard Smith one of my fellow Microsoft consultants from the UK has started a blog (finally!). Richard is very knowledgeable on everything about BDD and operating system deployment so I am sure you will find his blog very useful. 


Richard has started his blog with two great video walk through’s covering Lite Touch and Zero Touch deployment. This are very informative and should prove particularly useful to those new to BDD.


It looks like I will have too put together my own video walk through’s now just too keep up!


I recommend that you subscribe to his blog as there is bound to be lots more great stuff coming… No pressure Richard;)


http://blogs.technet.com/richardsmith


Disclaimer: The information on this site is provided “AS IS” with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use.

Comments (44)

  1. Anonymous says:

    Hi Emilios,

    Have you set the DeployRoot or ResourceRoot values anywhere?

    Also are any of the applications launching CMD or BAT files?

    Thanks,

    Ben

  2. Anonymous says:

    Can you send me a copy of the BDD.log file from this server. That will help me troubleshoot the problem. My email address is ben dot hunter at microsoft dot com.

    Thanks,

    Ben

  3. Anonymous says:

    Hi Ricky,

    The install path looks correct. Are you having the same problem with all applications?

    Thanks,

    Ben

  4. Anonymous says:

    No Idea 😉

  5. Anonymous says:

    Ok. Thanks again. Do you know of a quick way to hide the initial cmd windows on start up (running wpeinit)? From memory, I think it is possible under WinPE 1.1, can’t remember the setting though? Just a cosmetic one… Thanks

  6. Anonymous says:

    Hi Bill,

    This issue has not been solved by MDT. The only suggestion I have is that maybe you look at deploying these images using a USB stick or similar device.

    Thanks,

    Ben

  7. Anonymous says:

    Hi Nick,

    Can you post a copy of your Customsettings.ini file?

    Thanks,

    Ben

  8. Anonymous says:

    Hi Ben,

    I have managed to capture the image whilst booting from a USB or CD. The options are now available.

    Many Thanks

    Nick

  9. Anonymous says:

    Hi Leo,

    This is generally caused by one of two issues:

    1. The account you specified in the wizard or customsettings does not have access to the applications share.

    2. The working directory for the application is not correct. This should look like:

         %DEPLOYROOT%ApplicationsAppName

    Thanks,

    Ben

  10. Anonymous says:

    If you put the msp file in the updates folder then you only need to run the following command:

    setup

    This is because it will automatically find the MSP file.

    Thanks,

    Ben

  11. Anonymous says:

    The Update function is required only when changes have been made to the bootstrap.ini file or when new drivers have been imported into the Deployment Workbench.

    This process creates two files in the DeployBoot directory called LiteTouchPE_x86.iso and LiteTouchPE_x86.wim.

    The reason the the update(files only) takes so long is because of the image creation process.

  12. Anonymous says:

    Hey Ben…New to the Blog, but I have been working with BDD for about a week and half now.  Right now I am only deploying Vista Business and trying to get Office 2007 to work.  Vista works great, it is just Office 2007 that errors out.  I get the following error: "Application Microsoft Office 2007 returned an unexpected return code 87".  I try to Google and none of the results are even relevant.

    I am thinking that my problem lies within "My Quiet Install command".  I honestly do not know what to do here as funny as it sounds.  I’ve tried using the OCT tool and point to where it is on my distribution share.  I am next going to try the config.xml file.  

    Any and all will be greatly appreciated!!

    Thanks,

    Greg

  13. Anonymous says:

    Ok thanks Ben. One other weird thing I am still looking into is when I create a media deployment point based on an (enabled) build, the settings in the custom settings.ini file that appeat in the Rules tab for the LAB deployment point don’t seem to be imported to the Media build (again in the rules tab). Have you come across this? Also, great video walkthrough from Richard Smith too…

  14. Anonymous says:

    Hi Ben. Thanks for the last post, worked a treat. Installed patch 1 for BDD today. I’m running into a problem during the lite touch where install fails when I have multiple patches in OS Packages. Fails on Unattend.xml?? Then lite touch throws a message saying that the build fails and halts at that point.

  15. Anonymous says:

    I did, all fixed now!

  16. Anonymous says:

    A previous post discussed setting Multiple Keyboard locales my modifying ZTIGather.xml. That proved very useful. I now have the build defaulting to the required Locale and Keyboard. However, I cannot get the "Set time zone" selection to Default to the required setting. I have SystemLocale=en-AU in customsettings.ini, but it appears to not process this. Any ides with the Time Zone in customsettings.ini?? Many Thanks.

  17. Anonymous says:

    When I run the wizard I do not get any questions with regards to capturing an image. I get;

    Choose migration Type – Refresh

    Configure the Computer Name – Default

    Join the Computer to a domain or workgroup – Workgroup

    Specify where to save your data and settings – default

    Specify where to save a complete computer backup – default

    Select an Operating system to install

    Set Time Zone

    Select one or more applications to install

    Specify credentials for connecting to network shares

    I am using the administrator account for everything.

  18. Anonymous says:

    Hi Glenn,

    You are right this is written to the Windows PE registry.

    Thanks,

    Ben

  19. Anonymous says:

    Hi Niatross,

    There is no way around this as the boot disks use different scripts.

    Thanks,

    Ben

  20. Anonymous says:

    Assuming you are using Vista then try using the following in the customsettings.ini:

    TimeZoneName=AUS Eastern Standard Time

  21. Anonymous says:

    Hi Amanda,

    This would suggest that you do not have the correct network drivers for Windows PE.

    Windows PE 2.0 is based on Vista so you must import the correct Vista network driver into the workbench. Then you will need to update the deployment point (creating a new WinPE bootimage) and update WDS with the new WinPE image.

    Thanks,

    Ben

  22. Anonymous says:

    Hi Bret,

    To help you with your problems I would need to see the log files. These are located in c:minint. You can send me them at ben dot hunter at microsoft dot com.

    You should create a $OEM$ folder in the build folder located in distributioncontrol folder. this will then be copied during the build process.

    Thanks,

    Ben

  23. Anonymous says:

    Hi Brian,

    Thanks for the tip, I will have to give it a go when I get some spare time. Although I have no idea when that may be :).

    The update option re-creates the Windows PE ISO image every time you use it, that is why it takes so long. It will update the ISO even if you have made no changes.

    Thanks,

    Ben

  24. Anonymous says:

    There is a known issue with the patch – KB933566 Security Update. Try removing that patch and see what happens.

    BEN

  25. Anonymous says:

    Rules are created on a per deployment point basis. You will need to create a new setof rules for the Media deployment point.

    Yes Richard has done a fantastic job with his walkthroughs!

  26. Anonymous says:

    The wizard at the begining of the deployment should ask you where to save the captured image. Does it do this?

    You also need to make sure that the account you used to connect to the distribution point has rights the location that you specified.

    Thanks,

    Ben

  27. Anonymous says:

    How did you create a quite install command. Did you run "setup /admin" and create an MSP file?

    Thanks,

    Ben

  28. Anonymous says:

    Ben,

    Thanks for help with the quiet install command.  I am going to try it here in a few minutes, I will let you know how it goes.

    One more question and it is more of a general question.  Everytime I add a OS or an App, to I have to burn a new LiteTouch_x86.iso?

    Thanks Ben,

    Greg

  29. Anonymous says:

    Ben, New to the blog. I am working on deploying a custom Vista image to stand-alone computers. I would like to use a lite touch deployment with the removable media option. The obstacle I have run up against is that the image is 6 GB and growing. Lite touch works great over a networkd, but when I create a "Removable Media" deployment point and try to update it, I get an error message stating that the image is too large to fit on a DVD. I know how to split images, but the Lite Touch Deployment point doesn’t seem to work with .swm files. Is it possible to create a multiple DVD Lite Touch Deployment? Does the new MD address this? I would greatly appreciate any suggestions/help

    Thanks,

    BillH

  30. Anonymous says:

    Per TechEd broadcasts I seen should add the Ubberbug.reg file in task sequencer > First PreInstall task. So I did and don’t see the registry entry in Windows XP image. My guess why not is it is written to PE. Is this correct?

    Thanks!

    Glenn Aurelius

  31. Anonymous says:

    Hi Ben,

    I am having a small issue with removable deplyoment points running from a 16GB usb memory stick.

    I get all the screens that i expect to see for the LTI process but once i have selected apps right at the end in the deployment summary I get errors saying "Warning unable to set working directory: (-2147024893) Then the i get "Application – Name of app  returned an unexpected return code 2"

    Do you have any ideas?

    Thanks

    Emilios Theori

  32. Anonymous says:

    Within in BDD I created the msp file from the OCT tool (There is a button there).  Then in my quiet command I put in the following: setup /adminfile \servershareupdatescustom.msp.  And it is not working for me.

    Thanks for responding!  As before all help will be greatly appreciated.

    Thanks Again,

    Greg

  33. Anonymous says:

    Ben,

    Using "setup" as my quiet install command worked perfectly.  Thanks again for pointing me in the right direction on that.

    The other question I sent you about having to burn the Litetouch_x86.iso after every time you add an OS/App to the distribution, I think I answered on my own.  

    Once again thanks for everything.

    Greg

  34. Anonymous says:

    Hi Ben. I’ve been using BDD for a couple of weeks now mainly for lite touch. Can’t find any info on the difference between update and update files when updating either deployment points ot media dist points? Any thoughts?? Thanks

  35. Bret says:

    I have tried elsewhere and have gotten nowhere. I hope you can help.

    I have been trying for two weeks now to first capture an image and then simply get something to complete successfully. I have not gotten the slightest part of BDD to work.

    Three times I have built brand new infrastructures in order to start integrating on a new clean, environment. Each time I have encountered a new, completely different set of errors that I have not been able to solve.

    Enough rambling and whining…..

    The latest problem is that when I boot my light touch cd, I get all the right prompts, and it applies my wim image to the workstation and reboots. Am I supposed to keep it from booting to the new os I just installed, or back to the light touch winpe cd? Booting to the os does not seem to do anything but sit there. When I boot to the winpe cd, it continues the install and then fails almost immediately at the post-apply part and gives me the error that it was "unable to find CustomSettings.ini, rc=1."  I have never seen this error before and when I open the Z: drive I can find that file in the control directory.

    Previously to this it would never, ever, ever, copy my $OEM$ dir to the workstation and I ptu a copy in almost every directory I could think of. Also, my sysprep folder only had the sysprep.inf file in it without the sysprep.exe.

    I have a ton more problems but I will try to fix these two first and then see where I get.

    Any, ANY, help would be appreciated.

    Thanks,

    Bret

  36. Brian Larsen says:

    Hi Ben  

    First thanks for a GREAT blog!!! Priceless.

    My question is about the update and update (files only) in BDD. You write that the reason update (files only) takes so long is because of the image creation process. I just want to make sure that I got it right. Update (files only) only takes a long time the first time you press it, if you haven’t already press update once, right? Because normal the image creation only happens if you press update?

    # pmenham

    If want to hide the initial shell windows (cmd.exe) on startup, you can do this.

    1)You need a shell that support the hidden feature. I use cmdow.exe which is a freeware product. You can download it from here: http://www.commandline.co.uk/cmdow/

    2) Then you need to make a Winpeshl.ini file from were you call your “new“ shell (cmdow.exe). And in the same Winpesshl.ini file you make a call to wpeinit. Read more details about the structure of Winpeshl.ini here: http://technet2.microsoft.com/WindowsVista/en/library/45563a61-155e-48a5-a833-b6cd5119ad4c1033.mspx?mfr=true

    My Winpeshl.ini file looks like this:

    [LaunchApp]

    AppPath = %SYSTEMDRIVE%WindowsSystem32cmdow.exe

    [LaunchApps]

    %SYSTEMDRIVE%Windowssystem32wpeinit.exe

    3)Before you can use cmdow.exe and Winpeshl.ini, you need to copy them to your boot image made by BDD. You do this by mounting the image LiteTouchPE_x86.wim with imagex.exe. You need to make the folder first, before you can mount the image to the folder. I have called my folder “c:Mounted_WimImage”.  I have made a bat file:

    REM @ECHO OFF

    PATH=C:DistributionToolsx86

    imagex.exe /mountrw c:DistributionBootLiteTouchPE_x86.wim 1 c:Mounted_WimImage

    copy c:DistributionToolsx86Winpeshl.ini c:Mounted_WimImagewindowssystem32

    copy c:DistributionToolsx86cmdow.exe c:Mounted_WimImagewindowssystem32

    imagex.exe  /unmount /commit c:Mounted_wimimage

    4)Now you just copy the boot image to WDS or a MEDIA. If you want to hide the minimized shell windows that appears in the bottom of the screen as well, then all you need to do is edit the LiteTouch.wsf script. Go to the section called “If in PE, fix some things”. You can do two things. Remove the hole section, since you don’t want to use it, or just change the number 2 to a 0, in this line “iRetVal = oShell.Run(sCmd, 0, false)”. Then the window won’t show.

    Thanks

  37. Niatross says:

    Ben,

    Have you noticed that a BDD2007 Lite Touch ISO and MDT Lite Touch ISO are not compatible, even when your Deploy Root is the same in "Bootstrap.ini" for both BDD and MDT?

    Try taking a BDD2007 Lite Touch ISO and booting to a MDT Workbench. It throws an error. Try taking a MDT Lite Touch ISO and booting to the BDD Workbench. It throws a different error. This is true even when the Deploy Root/Distribution point is set to the same path. You would think MDT would be backward compatible.

    I don’t want to have to make separate Lite Touch ISO’s for each platform. Is there a way around this?

    Thanks, Niatross

  38. Nick Davis says:

    Hi Ben,

    I have only just started using BDD 2007 and have run into a problem when trying to capture an image. I can successfully deploy Windows XP and Office 2003 but no captured WIM image appears in my DistributionCaptures folder.

    I am deploying as a workgroup via Litetouch.vbs but am not prompted to capture an image although ‘Ask if an image should be captured’ is ticked on my Deployment Point.

    Any help or advice would be most welcome.

    Thanks

  39. Nick Davis says:

    Hi Ben,

    Here are the details from DistributionControlCustomsettings.ini

    [Settings]

    Priority=Default

    Properties=MyCustomProperty

    [Default]

    OSInstall=Y

    SkipAppsOnUpgrade=NO

    SkipCapture=NO

    SkipAdminPassword=YES

    SkipProductKey=YES

  40. jo092008 says:

    Ben, New to the blog. I am working on deploying a custom Vista image to stand-alone computers. I would like to use a lite touch deployment with the removable media option. The obstacle I have run up against is that the image is 6 GB and growing. Lite touch works great over a networkd, but when I create a "Removable Media" deployment point and try to update it, I get an error message stating that the image is too large to fit on a DVD. I know how to split images, but the Lite Touch Deployment point doesn’t seem to work with .swm files. Is it possible to create a multiple DVD Lite Touch Deployment? Does the new MD address this? I would greatly appreciate any suggestions/help

    Thanks,

    BillH

    # re: BDD 2007 – New BDD blog

    Wednesday, November 14, 2007 2:03 PM by BenHunter

    Hi Bill,

    This issue has not been solved by MDT. The only suggestion I have is that maybe you look at deploying these images using a USB stick or similar device.

    Thanks,

    Ben

    If the combination of MDT and Imagex would do away with third party imaging software, why are we limit to 4 gig .wim files. Adding the compability of using .swm files to MDT would great enhance the MDT. The current version only allows the deployment of a few bare bones images on one dvd. Does anyone know when this feature will be added to MDT? Knowing that MDT and imagex are designed replace software that has this same feature seems odd.

  41. Leo says:

    Ben,

    I’m tryint go apply applications using Microsoft Deployment thorough Quiet Installation. However, I’m getting a return error message: "Warning-unable to set working directory (-2147024875). Please advise if you have any ideas. Thanks.

  42. Amanda Muenks says:

    Hi Ben,

    We are currently using RIS in about 1/2 our sites and BDD/WDS in the other 1/2.  We are deploying Windows XP Professional sp2 through BDD/WDS.  I am trying to add a new model to the BDD build.  I have already successfully added this same model to our RIS build.  Here are the steps that I have taken to add the machine to BDD:

    1. Created new out of the box drivers for the network card.

    2. Edited unattend.txt to include the new drivers

    3. Edited txtsetup.oem to include the new drivers

    4. Updated (full, not files only) the deployment point.

    I am getting an error immediately after Win PE starts that says the machine cannot connect to the distribution share…  Am I missing something?

  43. Ricky says:

    Hello Ben, I’m having trouble installinn applications using deployment workbench. I’ve tried to resolve the problem after reading your blobs but no success. The error I get is "Warning unable to set working directory: (-2147024893) Then the i get "Application – Name of app  returned an unexpected return code 2".

    In my quiet install command box it looks like this setup.exe /Q(e.g)and the working looks like this .applicationsappname. I also tried %DEPLOYROOT%applicationsappname. I granted  the distribution folder with everyone full right. Any suggestion?