Lucid

What's the Command Line in the SCCM Package's Program that you are deploying? If it's just "setup.exe" you need to add some switches to have it install silently...

Have you made sure the BIOS on the machine is up to date?

Did you get this resolved? If not, when you say you reboot... What are you rebooting? The workstation that has the SCCM console installed?

Did this problem just recently crop up, and have you been capturing your image using this method previously? With the Software Update option enabled in your task sequence?

Just curious, but... Have you tried using the numbers without the quotation marks? So 255 instead of "255"...

Did you go through the log files stored on the failed capture machine to see if anything else jumps out at you? And I'd suggest making a separate task sequence and a separate OS image to contain things. It prevents "uh oh" type of problems from happening. Oh, and you can take a quick look at the screen shots at the bottom of this post: http://myitforum.com/cs2/blogs/rbennett806/pages/using-sccm-to-capture-and-deploy-windows-7.aspx to see if that helps in setting up your Build and Capture TS. If that doesn't help, try temporarily disabling the Software Updates sections and running it - to help narrow down if that's really the culprit...

Can't automate certain packages? Hmmm in cases where I've run into those types of apps, a quick VBScript wrapper did the trick. Most were poorly packaged and turned out to just needed me to grab the installed files from a manual install and then let the script copy them over and populate a few registry keys. Anyway, like I said, just tossing it out there...

Sorry about that, I must have missed that line in your original post. So what's the VBScript code you're using when you use the numbers?

Does the info from Step 3 on located here: http://www.windows-noob.com/forums/index.php?/topic/446-how-can-i-setup-wds-in-windows-server-2008/ help to double-check that you didn't miss a configuration setting? And I'll toss these quick steps in here just because I've got them right on hand: 1. Extract the contents of your SCCM boot media .ISO to C:\InstallCD 2. Use Imagex to mount the C:\InstallCD\Sources\boot.wim to a folder (C:\Mount in this example): imagex /mountrw C:\InstallCD\Sources\boot.wim 1 C:\mount 3. Copy the C:\InstallCD\SMS\DATA folder to C:\Mount\SMS. 4. Use Imagex to unmount the image and commit the changes. imagex /unmount /commit C:\Mount 5. Add the C:\InstallCD\Sources\boot.wim as a boot image on the WDS Server.

Also make sure to check out the book SMS 2003 Recipes (yes, many still apply to SCCM): http://books.google.com/books?id=14hWq8NNggwC&printsec=frontcover&dq=sms+2003+recipes+online&hl=en&ei=IyBbTaWXH4K8lQfIvNTIDA&sa=X&oi=book_result&ct=result&resnum=1&ved=0CEAQ6AEwAA#v=onepage&q&f=false And an easy way to get some of those settings is to configure a package as desired, and then use a script to check out the package's property flag (saves time trying to add up numbers and figure out what you need to input to check BoxA, but not BoxB)...

With a script wrapper you can return a basic Success/Failure code. For example, in VBScript, this returns success "Wscript.Quit" and this returns failure "Wscript.Quit(1)". As for your collection query question, take a look at the Office 2007 query here: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx , keeping in mind that you'd have to check two different spots if you've got a mix of 32-bit and 64-bit operating systems...

Look in the registry on a machine that has it installed and see if it's registering an UninstallString key. For example, for Java Update 25 you can look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{26A24AE4-039D-4CA4-87B4-2F86416025FF} and view the UninstallString key entry to see that "MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F86416025FF}" could be used. Sometimes you need to adjust these as they may not be 100% correct - depending on who coded and packaged the software - but it should get you in the right direction. Then, once you get the needed command, simply have SCCM execute it for you...

One other alternative to keep in mind... Tweak your scripts so they can run from SCCM so there's no need to auto login. When a packaged script is set to run with administrative rights they're running as SYSTEM so they can do pretty much whatever you need. And you can populate the registry keys for new users by loading the default user profile's registry hive, making changes, then unloading it. Just a thread with a quick example: http://www.windows-noob.com/forums/index.php?/topic/3379-configure-default-user-profile-while-deploying-windows-7/

In the SCCM console, expand the Operating System Images node for that particular image. Expand the image's node. Right-click on "Package Status". Select Show Messages | All. See if that helps you figure out why it's failing. If not, try giving us any other related info and someone can try to help...

Since nobody has chimed in, I thought I'd ask... Have you tried using the numbers for the time zones instead of the names? So you'd use "255" instead of "A.U.S. Eastern Standard Time". I don't have to mess with time zones, so just tossing it out there...

Are you PXE booting from that same server, or from a different one? And was PXE previously working fine and this is a hiccup, or have you not gotten it to work before?

Sounds like you either want to pre-populate the SCCM database with a resource object with the MAC address and desired computer name (so it gets picked automatically when imaging), or add a script/HTA to your OS deployment process. Does this sound like what you're wanting? http://www.windows-noob.com/forums/index.php?/topic/2140-osd-using-vbs-for-machine-name-for-uknown-computers/

If nobody else chimes in, you can start by poking around AppDeploy.com to see if they have the info you need: http://www.appdeploy.com/packages/detail.asp?id=2032

It also depends about WHEN you're talking about. Deploying an application to an existing client machine versus during OS deployment are different methods. If to existing machines, you can use a membership query on your collection to only populate it with machines that need the application - so ones that already have the right version won't show up. Here's some queries to help illustrate: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx And a "script wrapper" is using whatever scripting language you like to first check it the application is installed, and if it isn't, to go ahead and install it. So instead of deploying the .EXE or .MSI file, you deploy the .CMD, .BAT, .VBS, or whatever file (make sure it's part of your package of course). This script then makes the choice to install or not. And lastly.. You can use Task Sequences to deploy things other than OS images. There are some guides on this site, and I'm sure your favorite search engine can help you find other useful examples...

When setting up the XP VMware machine, make sure to select "Windows XP Professional" from the OS drop-down menu. Then, once you get it finished, go to the Hardware tab and select the NIC. Try switching it to "Bridged:Connected directly to the physical network". See if that helps. Other than that, I pretty much use the same steps that I use for setting up my Win7 VMs (http://myitforum.com/cs2/blogs/rbennett806/pages/using-sccm-to-capture-and-deploy-windows-7.aspx) And concerning the INF note... You're not looking for a subfolder, but "OEM#.inf" and "OEM#.pnf" files within the "C:\Windows\INF" directory....

Do you have an option of using a virtual machine to capture your image from? The problem I'd assume is that the image has version x.x.x of the driver, and the older devices have to have an older version and simply can't run the newer one. Even though you may not have intentionally installed a driver when capturing your image, Windows may have in order to function. If using a VM is not an option, try using your oldest machine to capture the image. You should have better luck with newer drivers overwriting older ones. Also, when I used to capture XP images I always blew away any C:\Windows\inf\oem*.inf files (where "*" is a single digit number) that had gotten added as I set up the reference system. So you might try deleting those from the .WIM and see what happens (first back up your .WIM somewhere of course) And lastly, since XP is phasing out, decide how much time you need to spend on it, and maybe skip some work and retain two images - one for older stuff that the first image won't work with. Just my two cents though...

You're going to probably have better luck making the script and associated files into an SCCM Package and then deploying that just like you would say... Adobe Reader, or something. On the package's Program, under the Environment tab, set it to "Run with administrative rights". Or if you want to try using a task sequence, you might take a look at this: http://www.windows-noob.com/forums/index.php?/topic/2758-how-can-i-copy-files-from-a-package

You say you created a Build and Capture task sequence following the guide on this site. Did that successfully capture an image for you? if not, where in the process (what was on the screen) did it fail? Also, have you added any drivers (NIC, SATA, video, etc) to SCCM for the models you're using? And lastly, XP is hardware dependent, so when testing, try to deploy it to the same machine model as the one you used to capture. Otherwise you can run into HAL issues...

You add the NIC driver to the SCCM driver repository. After that you add it to the chosen boot image in the SCCM console. Once you do that you generate a new .ISO file from the SCCM console and then use that to create the physical boot media (CD/DVD/USB). If you want more details than that, post and I'm sure one of us can toss out some more specific steps for you...

Is this what you're wanting? http://deploywindows.net/archives/970