Jump to content

Recommended Posts

Posted

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

Posted

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

Posted

I have had all sorts of weird errors with SCCM OSD, most been fixed by cleaning the disk.

 

PXE boot

Press F8

Type Disk Part

Type Select Disk 0

Type Clean

Close the command window and try again.

 

Sounds odd but it has fixed the same issue as this in the past.

  • Thanks 1
Posted
I have had all sorts of weird errors with SCCM OSD, most been fixed by cleaning the disk.

 

PXE boot

Press F8

Type Disk Part

Type Select Disk 0

Type Clean

Close the command window and try again.

 

Sounds odd but it has fixed the same issue as this in the past.

 

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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...