I know this thread is old, but have run into a similar situation.
With my MDT 2010 setup, I had a SQL Express database setup to dynamically determine the make and model. Based on the make and model, my task sequence would inject specific drivers as well as specific applications. This worked really well until I noticed differences in the make and model information in the bios. I have HP EliteBook 8540p laptops. These machines were the same bios revision shipped on the same order from HP, but had differences in the model in the bios. Some of them were 'HP EliteBook 8540p' and some of them were 'HP EliteBook 8540p (VD446AV)'. Caused some of them to get the correct driver and applications, while others didn't.
I ended up abandoning the 'single task sequence for all models' approach. I now just have a separate task sequence for each model we use, which ended up being about a dozen. A little more work when updating applications, but easier in the long run than dealing with multiple models in the bios.