Ideally we would like to deploy our os images via pxe booting. However, we have many computers that unfortunately don't have unique smbios numbers. We have found one solution that suggests editing a stored procedure to allow them to pxe boot. This actually works brilliantly. However, the os deployment still fails when it comes time to run a task sequence. It still sees the computer as a computer already in the site and simply says that there are no tasks to run. Are there other workarounds like the stored procedure edit? We have read about bannedguids but there is virtually zero information on them and we haven't got them to work. Can we simply make SCCM ignore the smbios? We have unique MAC addresses, can we use those instead? Do we have to create bootable media for all of these devices? If so, how will they then be seen in the site? Will this prevent the smbios nightmare? Any suggestions or ideas would be greatly appreciated.

refer: http://blogs.technet.com/b/configurationmgr/archive/2010/04/12/osd-task-sequence-fails-with-there-are-no-task-sequences-available-for-this-computer-if-multiple-machines-have-the-same-smbios-guid.aspx basically, the values stored in SMBIOS really need to be corrected, and that's something the OEM tools/vendor can do. if your hardware is a well known brand, or you have a good contract/relationship with your hardware reseller/integrator, they will help you with this. there may be some reluctance or difficulty with them providing you with the utilities to DIY the fix (I've faced that, but a quick call to our account manager fixed that :)Don

Thanks Don, I have already read that particular post. I don't seem to be able to get a utility from Asus to update the GUID. If there is any other workaround, please let me know. At this point it doesn't even seem possible to get the systems into SCCM at all. We could image them by bootable media but it doesn't appear that they will live happily together in SCCM once imaged. Frustrated.