This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 47%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBD%3C/text%3E%3C/svg%3E)
We are having issues with the deployment of apps installations during a Build and Capture TS in my SCCM CB 2006 environment. Packages are installing correctly. Otherwise, during the OS reinstallation TSs (when the computer is domain joined) the same applications installing correctly.
It began when we configured Cloud Management Gateway on SCCM primary site.
In TS monitoring status, TS fails with error 0x87d00269
In smsts.log file appears these errors:
socket 'connect' failed; 8007274d
Failed to connect to Management Point :80
connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274d (..\libsmsmessaging.cpp,897)
socket 'connect' failed; 8007274d
Failed to connect to Management Point :443
Failed to run the last action: Install Applications. Result -2016411031. Execution of task sequence failed.
Task sequence execution failed with error code 80004005
Lately we have configured Cloud Management Gateway and it works fine. While the computers are not Azure AD joined, we had to configure HTTPS on Mangement Point. PKI client certificates are used. Before that HTTP was configured on MP. On DPs are still configured HTTP.
We checked during client installation SMSMP property is used correctly.
Are you changing the startup mode for the ConfigMgr client agent service in the task sequence?
Have you reviewed clientlocation.log and locationservices.log to see if the client is detecting itself on the Internet or intranet?
In the smsts.log, what MP does it say it's attempting to communicate with?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 47%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBV%3C/text%3E%3C/svg%3E)
Hello - We are also facing same error what he mentioned above. Tried with his resolution but no luck. Currently running with CB 2010 and client 20H2.
Any suggestion please
Thank you for your quick response. Few days ago we finally solved it!!! Since we had alredy configured SMSMP property in Setup Windows and ConfigMgr, we had to add also DNSSUFFIX and CCMHTTPSSTATE=31 properties. After we configured those parameters, applications have installed with no errors in Build and Capture task sequences. It works perfectly in our enviroment.
If you are already setting SMSMP, then DNSSUFFIX has zero value. Also, directly setting CCMHTTPSTATE is unsupported. Is there a reason you haven't answered any of my above questions?
'Sorry, we haven't answered.
Generaly, we didn't change startup mode. But than we also tried to change startup mode, and the same error occured.
We checked these log files. Same errors repeat on and on.
LocationServices.log
ClientLocation.log
We know that CCMHTTPSSTATE is not officialy supported, but it solved our problem. Btw, if we leave out DNSSUFFIX, we get the same error again. At least, that is what we have expirienced in our enviroment during testing.
We checked during client installation SMSMP property is used correctly.
Can you expand on exactly what this means?
Hi Jason,
I saw on couple of forums that solution for this problem is to set FQDN of MP for SMSMP property. I just wanted to point out that we have already done that.
For example:
https://www.prajwaldesai.com/sccm-task-sequence-fails-with-error-0x87d00269/
Today we used CCMHTTPSPORT=443 instead of CCMHTTPSSTATE=31 and task sequence ran with no errors. But we had to configure DNSSUFFIX, and of course SMSMP properties.
But what exactly are you setting and where?
In build and capture task sequence, we configured those properties in task Setup Windows and Configuration Manager:
But with what values?
Also, as noted, SMSMP and DNSSUFFIX have the same purpose so if setting DNSSUFFIX addresses an issue, that means what you have configured for SMSMP is likely incorrect.
We thought SMSMP property was mandatory. We tested with only DNSSUFFIX configured and there were no errors. Obviously the other two are not necessary.
Jason, thank you very much for clarification.
That depends. It's one of multiple ways for the client agent to locate a "bootstrap" MP which is also the exact purpose of DNSSUFFIX. Thus, having both, while not harmful, is redundant. Also, most folks don't have their MP info published to DNS so using DNSSUFFIX, while benign, is also useless.