I concur with both of the above. Also, make sure that if you created new driver packages for the new models that you update them at least once so that their version is 2 -- there is a known "issue" with driver packages being at version 1. Are you using "Auto Apply" or "Apply Driver Package" tasks in your TS?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I have setup a task sequence that deploys a .WIM file (win 7 32 bit), and then some software on top of it. The task sequence is pretty much default. It's mostly used when installing new PCs. When deploying, we manually add the computers in Computer Association, and then boot them from a bootable CD, and it has been working perfectly for some time. When using this task sequence on for example a Dell Latitude E6400 or E4310 it works perfectly. However, Dell has renewed those models, and is now using E6410 and E4310. If I use the same task sequence for the new models, the image will deploy just fine, the computer will reboot, and then just start windows. The computer is not joined on the domain, nor is any of the software packages installed that should be installed. Some drivers are missing, but none that should be crucial for this task. (WLAN (and we are using cable), freefallsensor and fingerprint reader). The same thing happens with newer Fujitsu machines like the Lifebook S710.

As already recommended, I would look at your driver packages. In particular, I would take a look at your NIC driver as joining a domain and installing packages from a ConfigMgr DP requires a valid network connection.

I would advise you to update your driver packages anyway to reflect the changes with the new Dell models. Secondly review your smsts.log file and look for any errors there.