Jump to content


sd1204

Established Members
  • Posts

    2
  • Joined

  • Last visited

sd1204's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. The CRS site was created when SCCM 2012 was installed. The site code for 2007 is different. May I ask why you think it is trying to assign to a 2007 site?
  2. I am in the process of doing a side by side migration from SCCM 2007 to SCCM 2012. I have a test system that was previously a SCCM 2007 client and has been upgraded to a SCCM 2012 client using the install client. CCMsetup runs and says completed successfully but it is unable to be assigned to the site either automatically or manually. The site is a standalone primary site. Below shows the error in the LocationServices log file on the client: MYSERVER - is the management point CRS - is the site name <![LOG[Won't send a client assignment fallback status point message because the last assignment error matches this one.]LOG]!><time="07:55:18.489+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="fspclientdeployassign.cpp:197"> <![LOG[Won't send client assignment fallback status point message because last assignment message was sent too recently.]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="fspclientdeployassign.cpp:180"> <![LOG[Processing pending site assignment.]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:3219"> <![LOG[Assigning to site 'CRS']LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:3225"> <![LOG[LSIsSiteCompatible : Verifying Site Compatibility for <CRS>]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:5061"> <![LOG[Attempting to retrieve lookup MP(s) from AD]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:2110"> <![LOG[Lookup Management Points from AD:]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsutils.h:205"> <![LOG[Name: 'TEST.1234.567.COM' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsutils.h:211"> <![LOG[Name: 'MYSERVER.TEST.333.DDD.COM' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsutils.h:211"> <![LOG[Retrieved lookup MP(s) from AD]LOG]!><time="08:00:18.459+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:2136"> <![LOG[LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'CRS']LOG]!><time="08:00:18.490+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:4960"> <![LOG[LSIsSiteVersionCompatible : Site Version '4.00.6487.0000' is not compatible.]LOG]!><time="08:00:18.490+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:5023"> <![LOG[LSIsSiteCompatible : Site <CRS> Version '4.00.6487.0000' is not compatible.]LOG]!><time="08:00:18.490+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="lsad.cpp:5126"> <![LOG[LSVerifySiteAssignment : Client cannot be assigned to site <CRS>.]LOG]!><time="08:00:18.490+300" date="06-11-2013" component="LocationServices" context="" type="3" thread="3792" file="lsad.cpp:5160"> <![LOG[Won't send a client assignment fallback status point message because the last assignment error matches this one.]LOG]!><time="08:00:18.490+300" date="06-11-2013" component="LocationServices" context="" type="1" thread="3792" file="fspclientdeployassign.cpp
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.