none
Software installs and task sequence not working after port change. RRS feed

  • Question

  • Hi Everyone, I was dealing with an issue where client push was not getting to the clients and in the process I set up the HTTP and HTTPS ports to have a fallback port. (we only use HTTP) I switched the fallback ports to default to test and that seems to have broken everything. I am getting this error when installing any software: "The software change returned error code 0x87D00607(-2016410105)."

    CAS log shows:
    Failed to send Location Request Message ContentAccess
    Failed to create Location Request Message body ContentAccess
    GetLocationSyncEx3 failed with error 0x87d00231 ContentAccess

    I changed the port back right after I saw that it wasn't going to work. Since then I have made sure the boundaries are set correctly, the DP is in the correct boundary group, I tried redistributing the software, I uninstalled the client but when I went to reinstall it fails to reach the MP. Clients are pingable and I can reach them over the correct ports with Test-Netconnection. I tried googling but have yet to find a solution that works. Any tips would be awesome.

    SMST Log: 

    reply has no message header marker	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    DoRequest (sReply, true), HRESULT=80004005 (..\libsmsmessaging.cpp,6774)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    Failed to get client identity (80004005)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (tsmbootstraputil.cpp,1610)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    failed to request for client	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    SyncTimeWithMP() failed. 80004005.	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    Failed to get time information from MP: http://SCCM.ABC.local.	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    MpCnt > 0, HRESULT=80004005 (tsmbootstraputil.cpp,2189)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    QueryMPLocator: no valid MP locations are received	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    TSMBootstrapUtil::QueryMPLocator ( true, sSMSTSLocationMPs.c_str(), sMediaPfx.c_str(), sMediaGuid.c_str(), sAuthenticator.c_str(), sEnterpriseCert.c_str(), sServerCerts.c_str(), nHttpPort, nHttpsPort, bUseCRL, m_bWinPE, httpS, http, accessibleMpCnt), HRESULT=80004005 (tsmediawizardcontrol.cpp,1007)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    Failed to query MP locator	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    Exiting TSMediaWizardControl::GetPolicy.	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (tsmediawelcomepage.cpp,304)	TSMBootstrap	9/20/2019 10:05:22 AM	1580 (0x062C)
    Setting wizard error: An error occurred while retrieving policy for this computer  (0x80004005). For more information, contact your system administrator or helpdesk operator.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    WelcomePage::OnWizardNext()	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Skipping Confirmation Page.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Skipping Task Sequence Selection Page.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Skipping Variables Selection Page.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Skipping Resolve Progress Page.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Activating Finish Page.	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Loading bitmap	TSMBootstrap	9/20/2019 10:05:22 AM	1420 (0x058C)
    Executing command line: X:\windows\system32\cmd.exe /k	TSBootShell	9/20/2019 10:07:12 AM	636 (0x027C)
    The command completed successfully.	TSBootShell	9/20/2019 10:07:12 AM	636 (0x027C)
    Successfully launched command shell.	TSBootShell	9/20/2019 10:07:12 AM	636 (0x027C)
    

    Friday, September 20, 2019 7:57 PM

Answers

  • I figured out the issue today. The ports in IIS were not bound to the correct cert. I was able to use Support Center (in the Tools folder on the install directory) and check that the MP cert was not being issued. Took a look in IIS and found that the ports were not bound correctly to the right cret. Bound them accordingly, restarted the service, and it worked.
    • Marked as answer by EWarden Tuesday, September 24, 2019 12:38 AM
    Tuesday, September 24, 2019 12:38 AM

All replies

  • Check the Client to server port TCP port 80 is working? and ensure the network access account is configured.

    Kannan.CS | kannancs@hotmail.com

    Friday, September 20, 2019 8:04 PM
  • Thanks for the reply. Clients can reach the server over port 80 no problem. Network Access account is configured properly as far as I can tell. 
    Friday, September 20, 2019 9:31 PM
  • I figured out the issue today. The ports in IIS were not bound to the correct cert. I was able to use Support Center (in the Tools folder on the install directory) and check that the MP cert was not being issued. Took a look in IIS and found that the ports were not bound correctly to the right cret. Bound them accordingly, restarted the service, and it worked.
    • Marked as answer by EWarden Tuesday, September 24, 2019 12:38 AM
    Tuesday, September 24, 2019 12:38 AM