Wiki Navigation¶

Powered by you!¶

BDD 2007 FAQS

This page is just a list of frequently and not so frequently asked questions about BDD 2007. Most all of the info was gleaned from the MSSMS Email list.

Q1 - Trying to do the "Update" under my deployment point, and am getting the following error:¶

A1.1 - Try copying C:\Program Files\Windows AIK\Tools\x86\wimgapi.dll into your system32 directory.
A1.2 - The file should normally be in "C:\Program Files\Windows Imaging" and that should be in your system's path. Any chance that got removed from the path?

Q2 - Is it possible to run Queries to a Oracle database instead of SQL during ZTI Installations?¶

A2.1 - The challenge is Windows PE – the necessary OLE DB drivers (and in the case of Oracle, the full Oracle client) would need to be available. That probably would be a difficult task. You could use SQL Server as a gateway, with an OLE DB link from SQL into Oracle so that the queries were relayed by SQL Server.

Q3 - After processing generalize phase Sysprep plugins…¶

Ok so in windows\system32\sysprep\panther I have setupact and setuperr. In setupact the last 3 actions I have are:


In setuperr I have 1 line


OK I also have an Application log error:


A3.1 - Does your computer have a Soundmax driver? That’s the most common cause of sysprep failures.
A3.1.1 - Go to Manage Computer and remove the device manually before you sysprep it. Select to uninstall it when given the option

Q4 - Do i need to create separate ZTI CD for every DP Point?¶

A4.1 - Just be sure to point the CD at the MP that can “see” all the DPs and their boundaries, i.e. the MP at your central site.

Q5 - What is considered the proper way to handle drivers and applications across sites when using OSD to deploy machines in conjunction with BDD? I Would just like to do the drivers and applications.¶

A5.1 - You can create a network deployment point, a separate share, and deselect the stuff that you don’t want (e.g. builds, so you don’t get the OS images). You can use that network share as the SMS package source. Then you can configure ResourceRoot to point to the nearest DP (e.g. ResourceRoot=\\%SMSDP%\SMSDPShare\DriversAndPackages).

Q6 - When trying to deploy a Vista image to a machine, I keep getting this error in the BDD.log file: ¶

A6.1 - Make sure for your source Vista that you choose copy Setup files. When you added the image, did you choose "Copy Setup files" etc as well or Custom image? I can't remember the exact wizard text but you have two radio optionss during the adding of the OS, one will copy the setup files, the other does not..

A6.1.1 - Yep, that was it.
I was thinking to myself, "Self, why can't it find the setup.exe?".
So I ran thru the wizard again and saw that screen (the choices are: No setup or sysprep, Setup for Vista, Sysprep for XP) and chose the second option (Setup for Vista). I had to point to the root of the Vista DVD so that it could find the setup files.
So then I created a 2nd build and then updated (files only) the Deployment Point.
It's now working as expected

Q7 - File adpu320.sys caused an unexpected error (256) at line 3963 in d:\srvrtm\base\boot\setup\setup.c¶

A7.1 - Sysprep Known Issues

Error running Sysprep when Windows Media Player sharing is enabled.
The following error might be encountered when running Sysprep on a computer that has Windows Media Player media sharing enabled:



This error occurs due to issues with Windows Media Digital Rights Management (WMDRM). You must disable Windows Media Player media sharing before running Sysprep. The Windows Media Player media-sharing feature requires individual user consent and must be enabled only by an end user.

Q8 - Just curious what source of Win PE people are using with BDD 2007/OSD (and if anyone knows the differences between them)...¶

A8.1 - Anything (e.g. WDS, OSD deployment point in BDD Workbench, OS Installation CD) involving OSD w/SMS 2003, will require Windows PE 2005. Windows PE 2.0 is not compatible with SMS 2003 OSD FP Update. Windows PE 2.0 is/will only be compatible with OSD in SCCM (e.g. in SCCM, OSD is NOT an addon…but is actually built-in to SCCM).
If you notice, the overall technology(ies) involved with image deployment is in a transitional period. This “imbalance” will remain until SCCM is released. At that time, everything will use Windows PE 2.0.

Q9 - Has anyone had issues with OSD trying to install to this utility partition in refresh scenarios where the drive is not formatted? If so, what was your solution? ¶

A9.1 - There is code in ZTIValidate.wsf that checks to make sure the C: drive is the first partition on the hard-disk on the target computer before continuing with the ZTI deployment process. If C: drive is NOT the first partition on the hard-disk, the ZTI process will stop/error (e.g. error code 80004005 which is access denied).
The reason this occurred is because the computers we are using ALL have Dell Utility partitions as the 1st partition on the hard-disk.
This problem is not exclusive to Dell Computers, but is a standardized disk configuration on almost all computers from any reputable computer manufacturer.
As a quick fix to move forward, we had to comment-out the following block of code from ZTIValidate.wsf, inside the ZTIProcess function-block. After starting the ZTI deployment process again - after commenting-out the code -, the Vista upgrade proceeded successfully without stops or errors.

'If Err then
'     oLogging.CreateEntry "Unable to query WMI, assuming disk is OK: " & Err.Description, LogTypeInfo
'Else
'     For each oAssoc in oAssocs
'           If oAssoc.Index > 0 or oAssoc.DiskIndex > 0 then
'                 oLogging.CreateEntry "ERROR - the C: drive is not the first partition on the disk.  This is not currently supported by BDD 2007.", LogTypeError
'                 ZTIProcess = Failure
'                 Exit Function
'           Else
'                 oLogging.CreateEntry "The C: drive is the first partition on the disk.", LogTypeInfo
'           End if
'     Next
'End if
'On Error Goto 0 ' Let someone else deal with them.

A9.2 - (Specific to BDD 2.5)
If you look at the contents of the original DISKPART.TXT below that comes with BDD 2.5, if you compare yours, you’ll notice that your example is missing select partition=1.

select disk=0
REM //  The "clean" command is required to make sure that
REM //  Diskpart writes out the MBR boot sector. Without this
REM //  the machine may not boot into the new OS if the hard
REM //  drive is new and did not already have a boot sector
clean
REM //  Create a single partition that uses all available
REM //  drive space and make it the C: drive.
create partition primary
select partition=1
assign letter=C
REM //  Set the new partition as the boot partition
active

To see how many partitions your disk has, run diskpart from a command-prompt and type LIST PAR . This will also tell you the partition number of each partititon.

Q10 - About Adding Windows PE 2005 to the workbench¶

When the workbench is calls for you to “add” Windows PE 2005 to the workbench as an operating system, it is asking for the “plain-vanilla” Select/MSDN CD version of Windows PE 2005. To be safe don’t use ANYTHING that you have already created in BDD 2.5…unless it’s the SAME Windows PE 2005 Select/MSDN CD.
Once you properly create the OSD deployment point in the workbench and “deploy” it to the \\\ZTI$, you then use the Generic_x86.iso that created in \Boot as the Windows PE 2005 source for updating Windows PE in the SMS 2003 OSD FP Update.