Okay, so I was attempting to import a computer to bare metal image using SCCM and I got a weird error. The computer imports into the collection successfully but when a bare metal image is kicked off the computer is unable to find the task sequence. This happens on RARE occaisions but I have been able to identify which records will have the issue. When importing a computer manually or from the a file the GUID shows up in all upper case and the Unkown Computer Flag is set to <null>, this record will find the task sequence and image successfully. On the occassions where the computer is unable to find the task sequence the GUID show up in all lower case and the Unkown Computer Flag is set to 1. I believe that when this happens SCCM doesn't realize that this computer exists or is actually known to it. When I delete the record and re-enter it from scratch this most times fixes the issue, however there are cases where it doesn't. I found information about an MS Hotfix: http://blogs.technet.com/b/configurationmgr/archive/2010/04/05/new-hotfix-kb980270-the-computer-associations-are-not-created-by-the-import-wizard-in-sccm-2007.aspx however it doesn't seem to speak to importing a computer and having it show up as unkown. I was hoping for some feedback or some answers or some tips to try and resolve the issue. We are using Configuration Manager SP2 R2. Thanks, CourtneyCourtney Marr

The computer wouldn't happen to be a Dell gx270 or something. These had duplicate GUIDs on the machines and this is a known error. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

No sir, This happens from older machines HP 6930's to HP 8440's even their desktops...sadly not just one model:( Thanks, CourtCourtney Marr

No sir, This happens from older machines HP 6930's to HP 8440's even their desktops...sadly not just one model:( Thanks, CourtCourtney Marr

Pull apart the TAsk Sequence log and see if the MAC is not the same as the machine. Then do a report and see if that machine is found in SCCM. Also compare the SMSGuid and see if they match. If that is the case then you have the same fate as the GX270 and there were several work arounds. Let me know what you find...http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Pull apart the TAsk Sequence log and see if the MAC is not the same as the machine. Then do a report and see if that machine is found in SCCM. Also compare the SMSGuid and see if they match. If that is the case then you have the same fate as the GX270 and there were several work arounds. Let me know what you find...http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Matthew, I promise this will make you raise your eyebrows. I noticed these same sort of symptoms on computers that are entered correctly and not reporting to be unkown. I checked the SMSTS.log file as you advised to find those machines reporting their IDs as completely different than the record they are entered as. For exmaple: A record entered in as: COMPUTER1.domain.com GUID:XXXXXXXXXXXXXXXXXXXXX in SMSTS.log shows an identy of: COMPUTER5123.domain.com GUID:CCCCCCCCCCCCCCCCCCC Also, COMPUTER5123.domain.com is a current record in SCCM, with the guid that's being used in the log. This is for a baremetal build, with no client, however it seems to be assuming the ID of another computer already in SCCM. Thanks, CourtCourtney Marr

Matthew, I promise this will make you raise your eyebrows. I noticed these same sort of symptoms on computers that are entered correctly and not reporting to be unkown. I checked the SMSTS.log file as you advised to find those machines reporting their IDs as completely different than the record they are entered as. For exmaple: A record entered in as: COMPUTER1.domain.com GUID:XXXXXXXXXXXXXXXXXXXXX in SMSTS.log shows an identy of: COMPUTER5123.domain.com GUID:CCCCCCCCCCCCCCCCCCC Also, COMPUTER5123.domain.com is a current record in SCCM, with the guid that's being used in the log. This is for a baremetal build, with no client, however it seems to be assuming the ID of another computer already in SCCM. Thanks, CourtCourtney Marr

So you face the same fate as the Dell GX270's the GUID is in use by another machine and SCCM knows that. One way to go is to delete the machine out and do the reassoication for imaging and see if it gets in. When you do the association you type in the MAC address correct? you can try to enter both the GUID and the MAC. Otherwise you can contact the vendor and they are suppose to give you a tool to change it. Most of the time we just kept trying, adding, removing and then it would catch the new machine and not the one currently in SCCM. you can go a lookup of SMSGUID and GX270 and see what others did to get around the problem you also now have.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

So you face the same fate as the Dell GX270's the GUID is in use by another machine and SCCM knows that. One way to go is to delete the machine out and do the reassoication for imaging and see if it gets in. When you do the association you type in the MAC address correct? you can try to enter both the GUID and the MAC. Otherwise you can contact the vendor and they are suppose to give you a tool to change it. Most of the time we just kept trying, adding, removing and then it would catch the new machine and not the one currently in SCCM. you can go a lookup of SMSGUID and GX270 and see what others did to get around the problem you also now have.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com