roboticsguy1988

This was it. I cannot believe I overlooked this! I have had this issue before with imaging computers. Thank you all for your time and patience.

Alright the hard drive has 0 bad sectors. I cleaned the hard drive and even wiped the hard drive yet I still have a 0x80004005 error with Static Media and a 0x80070057 with Dynamic Media. Attached are the log files.DynamicMedia.txt StaticMedia.txt

I will try this tomorrow morning after HDAT2 scan is done. I have heard many times of cleaning the USB drives for OSD deployment but never have heard of cleaning the hard drive. Excellent suggestion though.

Initial Dell diagnostics show no problems. Running HDAT2 as a more thorough hard drive test.

It is a used (old) PC. The hard drive should be healthy but as a double check I have started diagnostics. I will post the results here when complete.

Gatt, Thanks for your response. As a test to eliminate that as the issue I went into (Administration > Site Configuration > Sites > selected my site > Properties > Client Computer Communication) and unchecked "Clients check the certificate revocation list (CRL) for site systems". After that I made a new USB Flash Drive and tried imaging but I still receive the 0x80070057 error message. So this at least is not the root cause unless there is some place else I need to tell it not to check for CRL (as a test). All, As another test I decided to make the USB Flash Drive site-based instead of dynamic. This gives me a 0x80004005 error instead of the original error. Attached is the SMSTS.log file from this test (This test also had CRL checking off as mentioned above). smsts2.txt

I have had this error in the past and it is usually related to boundaries. However, this time it is only this one computer, I can image other computers just fine. To eliminate other causes I have used the same network port, same USB Flash Drive, and added the computer to SCCM the same way I add other computers, as well as added it to the same imaging device collection. I don't believe it is a network drive issue as I get a proper IP address and can ping the SCCM server. I have attached the smsts.log file for your review (rename .txt extension to .log) Thanks you in advance for taking the time to help with this issue. smsts.txt