gotenks98

All machines are dells that came with xp pro, we are just reinstalling windows without all that junk they pre-load on them.

This is the first I have ever heard of on breaking the eula by creating images from oem media. You need to be more specific on what you mean because if what you are saying is true then alot more people are breaking it just by using stuff like symantec ghost. Second I am pretty sure mdt gives instructions on using oem media. I will check the unattend.txt file for mass storage and boot files.

Here is the situation I am trying to deploy windows xp sp3 to some of our dell machines. We do not have enough volumn licenses so we are using the media the machines came with (dell oem sp3). When I install windows from the cd it goes just fine like normal but if I try to install windows by using MDT 2010 it always errors out at the first part of the blue setup screeen saying that nvrd32.sys is missing. I can confirm that the file is there on disc and copied to deployment share. At first I thought it might just be bad media but I have gone through about 5 cds and deleting and re-adding xp to the deployment share each time and all files copy just fine. Its something that gets broken in the txtsetup I think thats causing this. Right now I am clueless as to how to fix this and I am running out of time on getting these images ready. I did a test install in a vm and I still get the same results. If I use retail or volumn license media to test this with I do not get this problem ever. It seems to be a delll media specific thing. Any clues as to how to work past this?

I am having similar issues with this now. Before today this just wasnt a problem with it pointing to a server but now its asking. I have no idea what I changed. As for as the task sequence issue just make sure your selection profile you choose at before creating the media has the task sequence folder selected otherwise you wont see anything.

The thing is I can not setup a server to do all this from. Here is my situation. We do a ton of support for students at my university. I have been trying to come up with a way to reinstall retail/oem versions of vista/7 quickly with them being patched and to cut down the crazy driver hunt we have to do with each reinstall. Since I cant use a server doing an install from usb with MDT seemed like a good option on doing this. I tried integrating updates and drivers into the install media but that ends up with 20+gb worth of drivers eating up space. So driver injection via mdt for only the specific hardware seems to be the easiest non-bloated approach.

Not sure what you mean, but here is what I am doing. I am creating a base install and updating it, writing down all th kb's and manually downloadinging all of them. I put all the x64 updates into a packages folder in mdt. When installing I have the apply patches part of my task sequence to run so I can patch in those updates on my other images. The problem is it usually fails on some update by saying it cant do some kind of offline servicing. Usually its when I find out a certain update cant be installed this way or even integrated into a wim file. I just need a way of knowing this ahead of time so I dont waste hours reading thru tons of setup logs to find where the problem is. I am currently testing this in a virtual machine to make it easier to check the logs by mounting the vhd file. The other images that are being used are untouched wim file from windows 7 sp1 retail disc.

Anyone here use the apply patches as part of their task sequence? I wanted to know just how do you know which updates can and can not be used for this. I am having all kinds of hell keeping this straight because the installs always error out due to some update not working. So rather than testing every single update, is there a way to know ahead of time if this update will or will not work?

I am looking to build a nice utility disc for work and I am looking for some good suggestions. Basically it needs to be able to run scan disc, some sort of password reset app, a file explorer, possibly integrate malwarebytes and/or spybot to be run from the media. A way to capture/restore/edit wim files. The reason I am looking at a version thats built from windows 7 is because its so much easier to add drivers when needed as the newer model laptops come out. Any ideas for this?

Thats just a service pack. The only way you can get the xp iso legally is to have an msdn account or a technet subscription.

I just wanted to ask are you guys testing to see if any of these can be injected via mdt during the install process. I know I had issues in the past with some of the updates because they did something to the language files but this was pre-sp1. I just wanted to ensure the updates all work from a mdt deployment.

What I am trying to do is create a universal windows 7 and windows vista install that has all possible drivers I can install. In the past I have done this but it adds a huge amount of unneeded files to the system once the install is done. Basically what I want to do is integrate drivers but have it only copy the ones it needs to the windows/inf directory instead of everything. Is this possible?