SCCM client upgrade

Hi,
What are the previous versions of SCCM 2007 client will upgrade by SCCM 2012 R2 client? I mean, if my environment having different versions of SCCM 2007 client installed on the machines and I want to install now SCCM 2012 R2 client by using client push method
to these machines, will it upgrade or not?
Thank you,
RR

To upgrade SCCM Client automatic, In the Configuration Manager 2012 Console, browse to the Administration workspace, click on Site Configuration, Sites and select your Configuration Manager Site. Next you need to select Hierarchy Settings and browse to the
Client Installation Settings tab and select the option “Upgrade client automatically when new client updates are available”.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Similar Messages

Trying to deploy SCCM Client upgrade...

A few days ago I upgraded our SCCM 2007 R2 Site Server with SP2. I did this in preparation for Windows 7 support and deployment. Anyhow, I decided to release the client upgrade via software distribution using the same package that I include with my image deployment (data source is \\server\sms_001\client )
Yesterday, I created an advertisement to distribute the SCCM client upgrade to my entire network but today System Center Console is reporting that out of 1148, 996 have not yet started, 0 succeeded, and 149 have failed. We're a school so most of our computers are off. The issue is that of the computers that are on 149 have failed with 0 reporting a success....or so they say.
I checked a few of my clients and the ccmsetup.log indicates that installation has in fact succeeded. However, what the "status of a specific advertisement" report is telling me is that the client failed with the "last status message name" column indicating "Program Failed (unexpected restart)". It shows the same thing for all clients that have reported a failure.
The software package program function is configured to run the following and I'm not using any client options: "CCMSETUP.EXE /noservice SMSSITECODE=AUTO"
Any ideas why the client appears to have been upgraded but reporting a failure?
Below is the execmgr.log:
Policy arrived for parent package 00100006 program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010949.649000+000";
MachineName = "ADMIN-OFF-TSEC";
ProcessID = 1976;
SiteCode = "001";
ThreadID = 3784;
execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Requesting content from CAS for package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Successfully created a content request handle {36479D3C-24C9-4844-BED1-2AB2B0BDD0F1} for the package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Program Advanced Client Silent Upgrade change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from NotExist to AdvancedDownload execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Mandatory execution requested for program Advanced Client Silent Upgrade and advertisement 00120025 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Creating mandatory request for advert 00120025, program Advanced Client Silent Upgrade, package 00100006 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010950.555000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
PackageVersion = "4";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1348;
execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Successfully raised SoftDistWaitingContentEvent event for program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingDependency to WaitingContent execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Content is available for program Advanced Client Silent Upgrade. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingContent to NotifyExecution execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Notify user mandatory program Advanced Client Silent Upgrade is about to run execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Manager timer has been fired. execmgr 12/22/2009 8:15:25 PM 1736 (0x06C8)
Executing program CCMSETUP.EXE /noservice SMSSITECODE=AUTO in Admin context execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from Running to NotifyExecution execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Checking content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System for use execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Executing program as a script execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Command line = "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO, Working Directory = C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Created Process for the passed command line execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\ccmsetup.exe\" /noservice SMSSITECODE=AUTO";
DateTime = "20091223011525.457000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 3500;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\";
execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raised Program Started Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Request in running or report status found for program Advanced Client Silent Upgrade package 00100006 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Service stopped while program Advanced Client Silent Upgrade is running execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
OpenProcess failed for process 1396, error 80070057 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Looking for MIF file to get program status execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramUnexpectedRebootEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223011911.783000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 3636;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1700;
execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raised Program Unexpected Reboot Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)

This KB article covers the upgrade of the client via hotfixes:
http://support.microsoft.com/kb/2477182
An important thing to note is that the Program needs the following set:
After Running: Program Restarts Computer; this is needed to ensure that any status MIF files are collected after a restart of the client service (ccmexec.exe). No actual restart of the computer should occur.
This enables the SCCM client to detect that it re-started and to process the MIF files for status messages.
Installing the following updates one at a time normally is sucessful:
KB2761938
KB2516517
KB2815223
Other updates such as KB2276865 fail with the Unexpected Reboot Event error (possibly because the MIF is not written correctly) but it has been superseeded by KB2815223 wich is OK.

SCCM Clients, Upgrade RTM to R2

Hi
I know that there is no support for upgrading SCCM 2012 RTM to SCCM 2012 R2. So, i need to apply SP1 first and perform than an upgrade to R2
Can my Clients, which are still at RTM (7711), still communicating with my Site, which will be at Version R2 (7958)?
Can i upgrade my Clients directly from RTM (7711) to R2 (7958)?
Thanks in advance :-)

Hi,
I concur with Jason, I found a relevant thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/6f718d93-20a0-4b92-914f-8bae719ce3ad/sccm-2012-rtm-to-sccm-2012-r2?forum=configmanagerdeployment
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Client upgrade package deployment error (yet successfull)

Hello,
I've been deploying my-self created package of a upgrade installation file I have found in the installation directory of SCCM 2012.
I have run a test deployment on a test collection on my two colleagues and the deployment showed 100% compilance with no error and installation went great.
So, I thought that it's ok to deploy it on more populated collection (Office computers only) and see what happens.
What actually happened is that after one day later there was 0% compilance on that deployment and every installation seem to have failed with ID 10021 stating "Program failed (unexpected restart)" so I assumed the installation failed and the upgrade
wasn't installed. Yet, I have checked some of the workstations and the client version number and it matched the R2 version. (which we are using)
Can anyone explain this to me?
The file used for the test upgrade and the pilot upgrade is located here:
...\ConfigMgr\ClientUpgrade\ccmsetup.exe (1,577 KB)
it does the trick when launched manualy and on a small collection, but on the large one, it "fails" the way I have described above.
I don't get it...
The IT guys from LukOIL

the answer from the below thread will answer your question
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0e8749a3-9c2d-4a7d-ae16-80474912bd8f/trying-to-deploy-sccm-client-upgrade?forum=configmgrswdist
Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin
Now I understand!
Thank you all for your time!
The IT guys from LukOIL

Problems with SCCM client instalaltion after upgrade to R2 version

Hi,
Few days ago, I have upgraded SCCM 2012 Sp1+CU3 to SCCM 2012 R2. I see now manyy issies in component manager with SMS_EXECUTIVE and SMS_MP_CONTROL_MANAGER. Reaon of this is automatically process of installation SCCM client in latest version. This same
issue apppear when I trying install SCCM manually. In both cases I have got in ccmsetup.log this:
CcmCreateEmbeddedClientState. Creates the client state file, which is needed for write filter handing.
CcmCreateEmbeddedClientStateRollback. Rolls back the action of creating the client state file.
RegisterExtensionInfo. Registering extension servers
WriteRegistryValues. Writing system registry values
Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. Verify that you have sufficient access to that key, or contact your support personnel.
Rollback. Rolling back action:
Computer where I want install SCCM client, my adm account, Primary site server or NT SERVICE\TrustedInstaller has full right to this registry key but log file record is always this same.
AV and Firewall turned off.
What next?

Hi Torsten,
I have checked client.msi.log and there is this same:
Note: 1: 1401 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls 3: 5
Product: Configuration Manager Client -- Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. System error . Verify that you have sufficient access to that key, or
contact your support personnel.
Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls. System error . Verify that you have sufficient access to that key, or contact your support personnel.
User policy value 'DisableRollback' is 0
Machine policy value 'DisableRollback' is 0
InstallFinalize. Return value 3.

SCCM 2007 to SCCM 2012 CLIENT upgrade

Hi,
We have some Windows XP machines with a SCCM 2007 client, connected to a SCCM 2007 server. Meanwhile some client are already migrated to Windows 7 but still connected to SCCM 2007 (and their packages/collections).
Now we would like to:
-migrate the Windows 7 machines to SCCM 2012 and keep their packages (so no re-run of advertisements) run
-migrate the Windows XP machines by migrating the SCCM 2007 clients then advertise a task sequence (Windows 7) to it
Questions:
-should we push the sccm client from 2007 or from 2012 server to keep the membership of collections?
-if we have to push from 2007, please advise howto: use ccmsetup.exe, the msi (is this the way to go: http://blog.metasplo.it/2012/10/how-to-upgrade-sccm-2007-clients-to.html)?
Please advise.
J.
Jan Hoedt

It doesn't seem to be published on the site.
I'll paste it here. Could you advise?
I would like to test with a cmd, so I made an install.cmd which contains.
@echo on
Cscript ConfigMgrStartup.vbs /ConfigMgrStartup.xml
pause
Then I edited the configmgrstartup.xml:
*Commmented lab1 since I'm not sure what to put there, why put a machine name and why the forward slash?
I'd expect domain\administrator.
*Commented out hotfixes since we don't need it
Launched the cmd but nothing happens, no loggings either.
!-- <Option Name="LocalAdmin" >lab1/dadmin</Option> -->
   <Option Name="SiteCode" >LTF</Option>
   <Option Name="CacheSize">8120</Option>
   <Option Name="AgentVersion">5.00.7804.1000</Option>
   <Option Name="MinimumInterval">0</Option>
   <Option Name="ClientLocation">\\oursccmserver\SMS_PRD\Client</Option>
   <Option Name="MaxLogFile">2048</Option>
   <Option Name="ErrorLocation">\\dfs\ErrorLogs\Clientinstall</Option>
   
   <Option Name="Delay" >5</Option>
   <InstallProperty Name="FSP">oursccmserver.fqdn</InstallProperty>
   <InstallProperty Name="SMSMP">oursccmserver.fqdn</InstallProperty>
   <CCMSetupParameter Name="BITSPriority">HIGH</CCMSetupParameter>
   <CCMSetupParameter Name="noservice" />
   <ServiceCheck Name="BITS" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="winmgmt" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="wuauserv" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="lanmanserver" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="RpcSs" State="Running" StartMode="Auto" Enforce="True" />
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="EnableDCOM" Expected="Y" Enforce="True" Type="REG_SZ"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="EnableRemoteConnect" Expected="Y" Enforce="False" Type="REG_SZ"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="LegacyAuthenticationLevel" Expected="2" Enforce="False" Type="REG_DWORD"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="LegacyImpersonationLevel" Expected="2" Enforce="False" Type="REG_DWORD"/>
</Startup>
Jan Hoedt

SCCM 2012R2 Automatic Client Upgrade - mandatory / forced restart?

We've upgraded our SCCM environment from 2012 sp1 to 2012R2.
If I check the box under site settings (Hierarchy settings) for "Upgrade client automatically when new client updates are available." What is the installation / restart behavior? Will it only occur during a maintenance window if one
exists and will it force a restart?
# When I wrote this script only God and I knew what I was doing. # Now, only God Knows!

Automatic upgrade is a great feature, but not much in this World is perfect.
Clients in slow or unreliable boundaries, are not upgraded automatically.
Here is a brief overview over what happens when you enable this feature:
http://www.ronnipedersen.com/2014/08/sccm-2012-how-does-automatic-client-upgrade-work/
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Collection query for specific SCCM client version - Parameters?

Good morning,
I need to upgrade my older clients as I recently upgraded SCCM to SP2. I can't seem to find the parameters in query builder to populate a collection with a specific SCCM client version. Can anyone help me out or point me in the right direction? I can't find anything using "The Google". You'd think lots of people would want this that there'd be a default query in SCCM already. Thanks.

Here is a query of all clients running sp1 version:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version = "4.0.6221.1000"
JonL

SP1 Client Upgrade Issue

Hello, i am having an issue trying to upgrade out SCCM Clients from RTM to SP1 versions. I have upgraded the server already sucessfully. I setup a software distribution package with the new client source files, however, when i deploy to clients i get a error message on 98% of them (a handful of clients worked sucessfully): Status Mesasage 10021: Program failed (unexpected restart). My command line is just the default from the definition file (except added a FSP): CCMSETUP.EXE /noservice SMSSITECODE=AUTO FSP:<myserverhere>. I can't figure out what is causing the client upgrade to fail, anyone have any ideas?
Thanks!

That topic was already covered in the forums. See these threads for detailed explanations:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3424297&SiteID=17
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2965261&SiteID=17

SCCM Client R2 CU3 in OSD

Our base image was created using SCCM build and capture. I created the base image using sccm client 2012 SP1 ( 5.00.7804.1300). Now, we recently upgraded to SCCM 2012 R2 CU3 and we would like to update our deployment production task sequence with
the config manager client package so that the machine will pick up the new client version after the build. Upon testing, I always encounter an incomplete build. After the installation of the sccm client, the ts stops and will show the login window. The ccmsetup.log
indicates a successful installation of the client as it exits with a return code of 0. I have a gut feeling that the sccm client was upgraded and was not able to save the task sequence which caused the task sequence to stop. Any idea on why the build
stops after the installation of the client and how to resolve the issue?

You can follow this post to configure CU3 in OSD.
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
Nick Pilon | Blog : System Center Dudes

Trouble with SCCM Client Push

I am having issues with pushing the SCCM client. I am able to push the client just fine as it installs OK but it will not assign the site code. When I try to manually enter the site code I get the "Failed to Update Site Assignment" error. However,
when I log off of my domain admin account and log on as the local administrator I can manually enter the site code and it accepts it. My domain account is added as a local administrator..
The old Network Admin who setup most of SCCM in not with us anymore so I am in charge of figuring out where he left off at and getting everything working. From what I can put together we have extended AD and the System Management folder is populated. I have
ran a query in AD to ensure we do not have any over lapping boundaries. As far as I know we installed SCCM 2012 fresh and did not upgrade from 2007. I have checked our GPO and have not found any that are trying to push the site code.
I have copy and pasted a couple logs below that may help troubleshoot. I have googled for days now how to fix the issues I see in the logs but haven't found anything. Please Help!!
LocationServices.log:
<![LOG[The MP name retrieved is 'E091SCCM.campbell.ketsds.net' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="14:34:36.365+300"
date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsadcache.cpp:334">
<![LOG[MP 'E091SCCM.campbell.ketsds.net' is compatible]LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsadcache.cpp:339">
<![LOG[Lookup Management Points from AD:]LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:205">
<![LOG[Name: 'EDKDECCMP1.KETS.KETSDS.NET' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.365+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:211">
<![LOG[Name: 'E091SCCM.campbell.ketsds.net' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.366+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsutils.h:211">
<![LOG[Retrieved lookup MP(s) from AD]LOG]!><time="14:34:36.366+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2136">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.376+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.376+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[Site and assignment site code match. Verifying site.]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:4001">
<![LOG[LSIsSiteCompatible : Verifying Site Compatibility for <PRI>]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5061">
<![LOG[Attempting to retrieve lookup MP(s) from AD]LOG]!><time="14:34:36.383+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2110">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[Lookup Management Points from AD:]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:205">
<![LOG[Name: 'EDKDECCMP1.KETS.KETSDS.NET' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsutils.h:211">
<![LOG[Name: 'E091SCCM.campbell.ketsds.net' HTTPS: 'N' ForestTrust: 'N']LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsutils.h:211">
<![LOG[Retrieved lookup MP(s) from AD]LOG]!><time="14:34:36.385+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:2136">
<![LOG[Current AD forest name is ketsds.net, domain name is campbell.ketsds.net]LOG]!><time="14:34:36.391+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:818">
<![LOG[Domain joined client is in Intranet]LOG]!><time="14:34:36.391+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080" file="lsad.cpp:896">
<![LOG[LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'PRI']LOG]!><time="14:34:36.398+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:4960">
<![LOG[LSIsSiteVersionCompatible : Site Version '4.00.6487.0000' is not compatible.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5023">
<![LOG[LSIsSiteCompatible : Site <PRI> Version '4.00.6487.0000' is not compatible.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1" thread="8080"
file="lsad.cpp:5126">
<![LOG[LSVerifySiteAssignment : Client cannot be assigned to site <PRI>.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="3" thread="8080"
file="lsad.cpp:5160">
<![LOG[A Fallback Status Point has not been specified. Message with STATEID='607' will not be sent.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="LocationServices" context="" type="1"
thread="8080" file="fspclientdeployassign.cpp:55">
ClientLocation.log
<![LOG[Getting Assigned Site]LOG]!><time="14:13:39.330+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:13:41.940+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:13:42.417+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="7616" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:13:47.468+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="7616" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:13:47.531+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="7616" file="smsclientclass.cpp:562">
<![LOG[Getting Assigned Site]LOG]!><time="14:14:34.803+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="3332" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:14:37.517+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="2520" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:14:45.167+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="2520" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:14:45.424+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="2520" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:15:35.577+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="6888" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:15:35.627+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="6888" file="smsclientclass.cpp:562">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:25:36.861+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8276" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:25:36.930+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="8276" file="smsclientclass.cpp:562">
<![LOG[Getting Assigned Site]LOG]!><time="14:33:00.123+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="6592" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:34:31.483+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8800" file="smsclientclass.cpp:989">
<![LOG[Getting Assigned Site]LOG]!><time="14:34:33.521+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8080" file="smsclientclass.cpp:989">
<![LOG[Assigning client to site 'PRI']LOG]!><time="14:34:36.145+300" date="01-15-2014" component="ClientLocation" context="" type="1" thread="8080" file="smsclientclass.cpp:501">
<![LOG[Unable to verify sitecode 'PRI'. Cannot continue site assignment.]LOG]!><time="14:34:36.399+300" date="01-15-2014" component="ClientLocation" context="" type="3" thread="8080" file="smsclientclass.cpp:562">

Is this 2012 R2?
When I upgraded from SP1 to R2 I had a very similar message. This thread helped me out:
http://www.windows-noob.com/forums/index.php?/topic/7217-client-version-50078041000-is-not-compatible-with-the-site-111-version-50077110000/
Specifically this bit:
DerGali, on 23 Jan 2013 - 08:41 AM, said:
I had the same Problem with the client version thing. I had to do following Steps to fix it:
1. If you made an Extension in the Active Directory for your SCCM Installation just open ADSIedit go To CN System=>CN System Management remove the Object CN=SMS-MP..... (don't worry it will be recreated by
the sccm server hourly. if not check rights on the object (the sccm computer object need to have rights to write into the System Management Object)
2. Just wait until next morning! The Server should updated all Version Numbers by itself!
MCP, MCDST, MCTS x 6, MCITP x 3
Please don't forget to mark this post as an answer if it is the solution to your problem!
If you like trance music, please subscribe to my podcast
Trancendance Podcast
View my MCP Certifications
Follow me on Twitter

Config Manager 2012 client upgrade (via package with batch commands)

Hello all,
I would like to kindly ask for your help with my question regarding a SCCM 2012 R2 client upgrade (from RTM to R2)
Recently, we have upgraded from RTM version of SCCM2012 to R2 (with the PXE hotfix applied)
During the process, I have choose not to upgrade clients when the SP1 was applied and go straight for the R2, which is not a problem I believe.
My question is regarding the pre-created packages, that are showing up in the console. I believe, that they are the easiest way to upgrade clients via packages in SCCM. (we can't push the installation due network policy)
This hotfix is stored here: \\"FQDN_site_server"\SMS_TSP\hotfix\KB2905002\Client\x64 (in case of x64 version, x86 is the same but x86 in the end)
The executed file from this path is this with this command following:
msiexec.exe /p configmgr2012ac-r2-kb2905002-x64.msp /L*v %TEMP%\configmgr2012ac-r2-kb2905002-x64.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
Anyway, when we install the clients when we deploy it for the first on a machine, that has no client or we reinstall it, we do it with help of this batch command:
set curdir=%~dp0
%curdir%ccmsetup.exe SMSSITECODE=TSP /NoCRLCheck /UsePKIcert /forceinstall SMSMP=HTTPS://CML.LTSPRAGUE.CZ CCMHOSTNAME=CML.LTSPRAGUE.CZ
I just need to know, if I can use the prepared package from the console in our case and if it will keep the settings when the package is deployed.
I belive I have found a similar questin here on the forums:
http://social.technet.microsoft.com/Forums/en-US/c9b40687-1843-44c7-b61b-fd26d53ab90b/cumulative-update-3-and-agent-upgrade?forum=configmanagerdeployment
The second answer might the answer I'm looking for, but can you explain that to me like I'm five years old? :)
Please, let me know.
The IT guys from LukOIL

I'm not sure, because of my short time at the company, but there are historical security reasons for setting the push installation off.
Second reason are strict firewall rules used here. SCCM Agent may contact site server through HTTPS - that is a one way communication, so push installation isn't possible.
Don't mix "client push" and "automatic client update". See
http://blogs.technet.com/b/configmgr_geek_speak/archive/2013/09/09/using-configuration-manager-automatic-client-upgrade-to-upgrade-to-the-latest-system-center-endpoint-protection-client.aspx for further details. (And yes, the article talks about SCEP, but
it also tells details about the entire process)
Torsten Meringer | http://www.mssccmfaq.de
Thank you for the article and your, but I find it easier to deploy packages right now.
I have found out, that there is a folder named "ClientUpgrade" in ConfigMgr installation folder.
I used this and made a package out of it. Deployment went fine as well as the installation of the upgrade for the client, but there is a problem now, that I don't see any software in the "Software Center" in "Available Software" - and there should be, since
I have may SW pointed to me and the list was populated before I have done the upgrade to the new version.
This may be a simple problem, but I really don't know what's wrong.
The IT guys from LukOIL

Clarification of "Automatic Client Upgrade" in Hierarchy Settings

Hello all, I am looking for clarification of "Automatic Client Upgrade" in Hierarchy Settings. I am SCCM 2012 R2 CU1. It says the latest version is "5.00.7958.1000" My CU1 version is actually "5.00.7958.1203".
From reading various other users forum questions regarding this issue I have learned that this upgrade will only work for "Major versions". That should be why I don't see the same versions. My question relates possibly more generally.
I am in the process of building and configuring the SCCM 2012 R2 CU1 (site code: IT1) environment. I have a running production SCCM 2007 R3 (site code: IT0) environment, with a different side code. I am not ready for these older SCCM 2007
R3 clients to be upgraded to SCCM 2012 R2 CU1 as I am still testing and finalizing things.
If I enable the "Automatic Client Upgrade" in Hierarchy Settings for 2012 R2 CU1, could someone better explain which clients this affects?
Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2?
Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1? (from what I have read, NO)
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2?
No
Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
Since we cannot have two sites with the same name in a hierarchy I assume these are two different hierarchies. The setting is for a hierarchy wide and works by creating a scheduled task for client to get the package via policies. Though I have not tried
this but logically it should not.
Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
On the same hierarchy,Yes!
Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
On the same hierarchy,Yes.
Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1? (from what I have read, NO)
You are correct. CUs are not a major release and a separate client package is created and you need to manually target them to the clients to get it upgraded.
Umair Khan | http://blogs.technet.com/umairkhan

Client Upgrade on Primary Site Server

This should be an easy question but I really want confirmation.
When you perform a Cumulative Update does the Update upgrade the client also on your primary site server? If so do when you create a device collection for x86/x64 clients do you exclude the site server from getting push?

Hi,
No the SCCM Client stays at version 5.00.7958.1000 on the primary site.
If you wanted you could upgrade the SCCM client on the primary manually by running.
C:\Program Files\Microsoft Configuration Manager\hotfix\KB2970177\Client\x64\configmgr2012ac-r2-kb2970177-x64.msp and then exclude it from the below collection or let it go out automatically.
This is from an older version but the principle is still the same.
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
You can go straight from R2 to CU2. You do not need to install CU1 first.

SCCM SP1 Upgrade - Updates compliance issues

After my upgrade to SP1 I noticed that the compliance level of my update lists had dropped considerably.
I am noticing there are 200-230 clients in an “unknown” compliance state.
I am worried that something is wrong with the software updates compliance policy or worse something wrong on over 200 of my clients.
I have applied all the hotfixes that were suggested before upgrading to SP1.
WSUS is up to date with newest hotfixes as well. The majority of my clients health checks are fine.
Not all of my clients are updated to the latest SCCM client 7804 but I wouldn’t think this would cause an issue with update compliance.
I triple checked my client settings on my primary server. Clients are set to check every hour.
Nothing was changed for this before the SP1 upgrade.
Am I missing something else? Is there a specific log to check for this?
It’s strange to me that before the upgrade I had high compliance rates and now they are very low. Its been 3 weeks since the SP1 upgrade and I would think by now comliance levels would increase so patience isnt an issue here.
Any help would be appreciated.
Ryan Ventimiglio

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Generally time will solve this problem.. give it a few days to clean itself up. If that doesn’t work then pick a few clients and review their SU logs to see why they are showing as unknown.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM client upgrade

Similar Messages

Maybe you are looking for