Jump to content

Recommended Posts

Posted

Good Afternoon,

 

I have just setup a brand new instance of SCCM Current Branch and built my task sequence and deployed applications.

 

I have then setup and changed all communications to HTTPS and now my task sequence is failing. I suspect this is because the computer I'm trying to run the task sequence on does not have a valid certificate on.

 

Has anyone had this before?

Posted (edited)
You may need to update your boot images if the TS is running from WinPE. If from normal Windows you need certificate enrolment setup via group policy. Edited by free780
Posted

So I have got GPO set and enrolling clients which is working fine. The task sequence will be running on PCs that won't have ever been domain joined. I have imported the certificate into SCCM console and set everything to HTTPS then updated the distribution points with the boot images.

 

How should I be adding the certificates to the boot images?

Posted
Yeah that's what I thought and done. My first step in the task sequence is to restart in Windows PE then go through and apply operating system. But it is failing on the first step with 0x80070002. Only since changing everything to HTTPS.
Posted

Have you setup your network access account etc? 70002's are normally that the account being used can't access the share/files, and when HTTP is enabled it's normally also allowing anonymous connections so if you disabled that it requires direct accounts to connect.

 

Steve

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...