none
Client fails to request user state store - no local SMP found RRS feed

  • Question

  • Have a 2012 client, and we are attempting a very basic task sequence that requests the state store, does a a capture, and releases the state store. This is intended for an in-place migration, so no computer association has been created.

    However, we are getting odd failures.

    Client1 resides at IP a.b.c.d, and that subnet is listed in the 'USMT test boundary' boundary group, as well as the range a.b.c.1-a.b.c.254. The Boundary group is associated with a Desktop based DP, as well as our dedicated SMP server.

    When the request state store runs, it fails and this is what we find is smsts.log

    Command line: "osdsmpclient.exe" /capture OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Client joined to the XYZ domain. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Client is a member of the Columbus site. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    DhcpGetOriginalSubnetMask entry point not supported. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Begin checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Finished checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Adapter {4CCABA30-E631-45C2-A9A6-55EA390F718A} is DHCP enabled. Checking quarantine status. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Loading client certificates. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Default CSP Type is 24 OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Setting the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype). OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Requesting a list of available state migration points from the management point. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Initializing HTTP transport. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    cannot create a certificate context from the given encoded string OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Set authenticator in transport OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    Sending request to MP MP.domain.com. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
    signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Received 46974 byte response. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Retrieving SMP list.. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    SMP Location Info = <SMPLocationInfo><Sites><Site><SMPSite SiteCode="sitecode" MasterSiteCode="sitecode" SiteLocality="REMOTE"><LocationRecords><LocationRecord><ADSite Name="Columbus"/><IPSubnets><IPSubnet Address="F.G.H.0 -->not the IP subnet of the client"/><IPSubnet Address=""/></IPSubnets><ServerName>http://SMPServer.domain.com</ServerName></LocationRecord></LocationRecords></SMPSite></Site></Sites></SMPLocationInfo> OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    DHCP entry points already initialized. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Begin checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Finished checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Adapter {4CCABA30-E631-45C2-A9A6-55EA390F718A} is DHCP enabled. Checking quarantine status. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Number of local SMP's = 0 OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Retrieving SMP list succeeded OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Looking for UsersList OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    User List is empty in MigrationInfo from MP. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Successfully processed response from MP. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Contacting available state migration points to service capture request OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    No state migration points are available to service request. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    ExecuteCaptureRequestSMP failed (0x80004005). OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    OSDSMPClient finished: 0x00004005 OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
    Process completed with exit code 16389 TSManager 4/12/2013 10:12:20 AM 4848 (0x12F0)

    What is even more counfounding is that if I add a new boundary group with just this subnet, and associate it only with our SMP, the task sequence will fail to run, stating 'The software could not be found on any servers at this time', when I know the boundary is listed in both boundary groups. Removing this second boundary group reverts the issue back to the error about not finding a SMP.

    Thoughts?


    Will

    Friday, April 12, 2013 2:27 PM

All replies

  • Does the smpmgr.log on the SMP show that it is healthy?  Also, It looks like your MP is returning an SMP server for the client to use however the client looks like it is possibly being denied due to the 0x80004005 error.

    My Personal Blog: http://madluka.wordpress.com

    Friday, April 12, 2013 3:43 PM
  • The SMPMSI indicates a successful installation, and SMPMgr has a 200 OK every 5 minutes.

    If I read the log correctly, its returning the SMP as remote, even though the client is in the boundary associated with the subnet. Lower you'll notice "Number of local SMP's = 0" . I even attempted to allow machines outside boundary to use as fallback, and it still would not use it.

    I installed the SMP role on one of our DP's, and everything works for that server. We can't do this long term (for reasons I can't discuss here) but it at least serves as a workaround.

    I also just realized you cannot specify different boundary groups for a DP and SMP role on the same site server. It would be nice if the wizard warned you of that. I'm starting to wonder if there is some sort of bug with a site server that is only a SMP and not a DP.

    The real test I guess will be to go back and add the DP role to the non-functioning SMP and see if it suddenly starts working.


    Will

    Friday, April 12, 2013 4:59 PM
  • Hi to all,

    I have exactly the same problem, SCCM (current branch) Ver.1610.

    I pointed out my attention of this log portion:SMP Location Info = <SMPLocationInfo><Sites><Site><SMPSite SiteCode="SCM" MasterSiteCode="XXX" SiteLocality="REMOTE"><LocationRecords><LocationRecord><ADSite Name="YYYY"/><IPSubnets><IPSubnet Address="A.B.C.D"/><IPSubnet Address=""/></IPSubnets><ServerName>http://mysmpserver.mydomain.local</ServerName>

    </LocationRecord></LocationRecords></SMPSite></Site></Sites></SMPLocationInfo>

    I'm absolutely sure about the Boundary Group configuration (I associate DP and SMP, and it works great for software distribution, but it never works for SMP).

    IPSubnet Address="A.B.C.D"/ --> like Will wrote, is not the client subnet, is the SMP subnet. Is it right?

    SiteLocality="REMOTE" --> Why? It's inside boundary e Boundary Group ...

    There is something that I can check / try?

    Any further help (or suggestion) will be higly appreciated, thanks in advance.

    Friday, March 17, 2017 5:28 PM
  • Hi to all,

    in my specific environment, after a support call from MSFT, we founded that there is an issue with Boundary Group Fallback Relationship and SMP’s. When we added a Fallback relationship we may get the error "No state migration points are available to service request"

    One known workaround for the moment is to remove the fallback relationship from the Boundary Group.


    Wednesday, July 26, 2017 12:18 PM
  • I have the exact same problem and just fell onto this thread.

    My testing showed that if I add the MP server in the Boundary Group (MP server has nothing to do with the local DP and SMP, it's REMOTE), then the detection works properly.

    I will try your method.

    I am on SCCM 1710.

    --

    Alex

    • Proposed as answer by YW IT Thursday, July 26, 2018 5:52 AM
    Friday, February 23, 2018 3:21 PM
  • Folks the exact same issue in my separate thread here. https://social.technet.microsoft.com/Forums/en-US/96c4557a-96c6-453d-9f31-d57a55e30f87/1710-state-migration-point-smp-detected-as-remote?forum=ConfigMgrCBOSD I have tested on 1710 but not on 1802 yet. Alex
    Thursday, July 26, 2018 3:49 PM
  • Experienced same issue on CB 1806.  Removed Fallback and SMP selection works fine.
    Monday, June 10, 2019 3:49 PM
  • Hi.

    Just found this on a customer site.

    Issues still exists on CM 1902 with Hotfix KB4500571 applied.

    Wednesday, August 14, 2019 12:19 PM
  • Just ran across this in a customer environment (1906 with Hotfix Rollup KB4517869) and can confirm its still an issue. 

    Per Fabio's post removing the fallback relationship from the Boundary Group does workaround the issue but kind of defeats the purpose of the fallback relationship config.


    • Edited by SeNaT0R Sunday, November 10, 2019 4:58 AM
    Sunday, November 10, 2019 4:56 AM
  • Hi to all,

    yes, thanks SeNaT0R, I'm aware about that; I'm still waiting for a definitive solution (maybe 1910 …).

    Monday, November 18, 2019 4:11 PM