locked
Clients pick up wrong Site version and therefore cannot be assigned.... RRS feed

  • Question

  • Hi All,

    I have been struggling with this issue for some time now....

    Current Environment is as follows: 3 DC's, only Win 7 Computers, One Primary SCCM2012 SP1. 

    I installed the Config Manager correctly and it is working fine. It even finds computers via AD scanning. All the clients have the new Agent installed via push. This I confirmed via client logs CCMSetup log. When opening the config manager in Control panel however, only the version 5.000.... shows. There is no Client connection and neither Certificates issued. Strange thing is that only 3 PC are connected automatically.

    When I researched the Client location logs, I stumbled upon something interesting, here it is:

    ___________________________________________________________________________________________________________

    Won't send a client assignment fallback status point message because the last assignment error matches this one. LocationServices 2013/06/12 08:49:43 AM 3588 (0x0E04)
    Won't send client assignment fallback status point message because last assignment message was sent too recently. LocationServices 2013/06/12 08:57:20 AM 3588 (0x0E04)
    Processing pending site assignment. LocationServices 2013/06/12 08:57:20 AM 3588 (0x0E04)
    Assigning to site 'PPD' LocationServices 2013/06/12 08:57:20 AM 3588 (0x0E04)
    LSIsSiteCompatible : Verifying Site Compatibility for <PPD> LocationServices 2013/06/12 08:57:20 AM 3588 (0x0E04)
    Attempting to retrieve lookup MP(s) from AD LocationServices 2013/06/12 08:57:20 AM 3588 (0x0E04)
    The MP name retrieved is 'PPD-SCCM01.SAM.COM' with version '6487' and capabilities '<Capabilities SchemaVersion="1.0">
    </Capabilities>' LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    MP 'PPD-SCCM01.SAM.COM' is compatible LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    The MP name retrieved is 'PPD-VS-SCCM1.PPD.SAM.COM' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    MP 'PPD-VS-SCCM1.PPD.SAM.COM' is compatible LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Current AD forest name is SAM.COM, domain name is PPD.SAM.COM LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Lookup Management Points from AD: LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Name: 'PPD-VS-SCCM1.PPD.SAM.COM' HTTPS: 'N' ForestTrust: 'N' LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Name: 'PPD-SCCM01.SAM.COM' HTTPS: 'N' ForestTrust: 'N' LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Retrieved lookup MP(s) from AD LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'PPD' LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    LSIsSiteVersionCompatible : Site Version '4.00.6487.0000' is not compatible. LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    LSIsSiteCompatible : Site <PPD> Version '4.00.6487.0000' is not compatible. LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    LSVerifySiteAssignment : Client cannot be assigned to site <PPD>. LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)
    Won't send a client assignment fallback status point message because the last assignment error matches this one. LocationServices 2013/06/12 08:57:22 AM 3588 (0x0E04)


    _______________________________________________________________________________________________________

    What I realized is that the PC's are picking up the site version from a different server(namely in the top-level domain:PPD-SCCM01.SAM.COM) instead of getting the Site version from  PPD-VS-SCCM1.PPD.SAM.COM.

    Server: PPD-SCCM01.SAM.COM does not exist anymore for a long time now. 

    The Only SCCM Server Publishing anything in AD in both domains (child and top-level) is PPD-VS-SCCM1.PPD.SAM.COM. All 3 items ManagementPoint, RoamingBoundaryRange and SMS_site are published.

    Question: Is there any other place within AD (perhpas registry that I can alter, so as not to pick up PPD-SCCM01.SAM.COM? Any suggestions?

    THanks a lot

    Holger

    

    Wednesday, June 12, 2013 8:19 AM

Answers