Is your client installation package on the required dsitribution points? Jeff
On Fri, Apr 25, 2014 at 3:09 PM, Mark Evers <[email protected]>wrote: > Running into a small issue with one of our Distribution Sites, I have > deployed a DP only using https, along with their corresponding Boundary > Group, SCCM is reporting that it deployed successfully. However, When I > enabled the Client Push installation, as opposed to going the local DP, the > clients are coming back to the Primary site DP, and this is causing network > issues. Right now I have eliminated the situation by disabling the network > port on the computer, I'll enable over the weekend, when the network is not > needed. However I still need to figure out why the computers did not go to > the local DP. > > Going through the log on the client this is what I am seeing: I replaced > my Server names and domain names. > > Discovered 2 local DP locations. ccmsetup 4/25/2014 9:59:10 AM 2864 > (0x0B30) > PROPFIND 'https://DPServer.Domain/NOCERT_SMS_DP_SMSPKG$/CAS00003' ccmsetup > 4/25/2014 > 9:59:10 AM 2864 (0x0B30) > Failed to send HTTPS request. (Error at WinHttpSendRequest: 12029) > ccmsetup 4/25/2014 9:59:11 AM 2864 (0x0B30) > Failed to check url https://DPServer.Domain/NOCERT_SMS_DP_SMSPKG$/CAS00003. > Error 0x80072efd ccmsetup 4/25/2014 9:59:11 AM 2864 (0x0B30) > PROPFIND 'https://DPServer.Domain/SMS_DP_SMSPKG$/CAS00003' ccmsetup 4/25/2014 > 9:59:11 AM 2864 (0x0B30) > Failed to send HTTPS request. (Error at WinHttpSendRequest: 12029) > ccmsetup 4/25/2014 9:59:12 AM 2864 (0x0B30) > Failed to check url https://DPServer.Domain/SMS_DP_SMSPKG$/CAS00003. > Error 0x80072efd ccmsetup 4/25/2014 9:59:12 AM 2864 (0x0B30) > Enumerated all 2 local DP locations but none of them is good. Fallback to > MP. ccmsetup 4/25/2014 9:59:12 AM 2864 (0x0B30) > GET 'HTTPS://PrimarySvr.Domain/CCM_Client/ccmsetup.cab' ccmsetup 4/25/2014 > 9:59:12 AM 2864 (0x0B30) > > I thought it my be an issue with the certificate, so I a deleted it on the > server, re-enrolled, exported it using to export the private key, and > selected .PFX, I did not select any sub options for certification path, > deleting the private key, or export all extended properties. Applied a > password and copied, and inserted it into the properties for the DP, with > the same password. But that didn't alleviate the issue, as I assume since > the clients were already pulling from the Primary site, there was no way to > re-direct them. But I don't know if that will fix the issue, is there any > way I can test to verify this? > > Or am I going down the wrong rabbit hole? > > Mark E > > > > > > > > >
