PENDING SCCM 1610 Distribution Point Certificates

[Rich Huws]

I have recently upgraded my site from 1606 to 1610 and the main site (server A) has upgraded and everything works fine. I have then tried to add a second distribution point (server B) This server con communicated fine with the MP and gets all the content but the clients cannot connect to this DP, I just get Waiting for content. Have confirmed that all the content has been distributed to both DP's.

As I am using HTTPS, I assume the problem may lie here, but am not sure where to start looking.

Does Server B require it's own DP certificate to deploy to all clients, or does the DP Client certificate created initially with Server A also work with Server B.

 

[Prajwal Desai]

Can you confirm if you have implemented these two things -
https://prajwaldesai.com/deploying-the-client-certificate-for-windows-computers/
https://prajwaldesai.com/deploying-the-client-certificate-for-distribution-points/

 

[policeman51]

I have recently upgraded my site from 1606 to 1610 and the main site (server A) has upgraded and everything works fine. I have then tried to add a second distribution point (server B) This server con communicated fine with the MP and gets all the content but the clients cannot connect to this DP, I just get Waiting for content. Have confirmed that all the content has been distributed to both DP's.

As I am using HTTPS, I assume the problem may lie here, but am not sure where to start looking.

Does Server B require it's own DP certificate to deploy to all clients, or does the DP Client certificate created initially with Server A also work with Server B.

Did you ever get an answer to this question? I have the same question and I have been looking everywhere online, but I can't find the answer.