After SCCM 2012 R2 CU4 update Client won't report status message back

We had SCCM 2012 R2 CU3, just updated it to CU4 (all site servers and clients) last week.
Right after the clients received the CU4 update (no reboot), I saw these started popping up the event log:
The ConfigMgr Client encountered a certificate for Management Point SCCM that could not be verified.
I checked online and it has to do with trusted root key mismatch, but there was no site change. The only thing we did was upgrading from CU3 to CU4.
Right now the symptom is that all these clients do not report status messages back to the MP so we have no idea how our deployments would go.

i am having what i think is a similar issue. i upgraded to CU4 and the only clients to report back in are my SCCM site server and my only DP server. no clients have reported in since. i checked a few clients and they did get the CU4 client update
and installed it but they are not reporting back
I have pretty much the same situation.
A successfully upgrade to SCCM 2012 r2 cu4 on the primary site.
Deployed the cu4 to a few computers which was successfully. Later I also deployed the cu4 to the primary site server and it turned out to be the only computer reporting back with the proper client version.
There is no errors or warnings in the event logs which could explain this strange issue. As far as I can tell the clients is operational but they are just not reporting back with the proper client version. A quick look at the sccm client
logs has also not revealed the root cause.
Any ideas would be appreciated a lot.
Per Dahl Christiansen

Similar Messages

Prestage content no longer working after SCCM 2012 R2 CU1 update

I run SCCM 2012 R2 CU1 on a Windows 2008 R2 server.
I upgraded to CU1 in June, and today is the first time I've attempted to pre-stage a package since then. After pre-staging my package and getting the content out to the target DP, I went to properties of the DP, checked the box "Enable this
distribution point for prestage content", then hit Ok.
Next I went to distribute the content to the DP, however after going thru the wizard, nothing changes. There is no pending status, waiting on prestage content, that I had seen in the past when doing this task. I can go in and run the wizard
again, and the target DP shows up in the list, like I'd never initiated the push before.
Normal (non-prestaged) distributions work fine.
In troubleshooting this, I also noticed that I looking at the site status of the target DP, there are no status message entries for since I upgraded to CU1 (for that matter, none of my DP's have any entries since CU1). I did see a similar issue like
this in the forums
http://social.technet.microsoft.com/Forums/en-US/9491c2b1-37e6-46e3-9bb0-c5d673490d8a/component-status-not-updating-since-upgrade-from-sccm2012-sp1-cu3-to-sccm2012-r2?forum=configmanagergeneral but I don't have a backed up stat.mgr\retry inbox, it's empty.
I think this is related to why I can no longer prestage content, but I can't seem to find a reason for it. The fixes for R2 CU2 don't mention my issue here either
Anyone else seeing this?
Tony

Hi,
Please check SmsAdminUI.log and Smsprov.log after you distribute the content to the DP.
Best Regards,
Joyce
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.

After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

Hi,
So you have tried to reinstall IIS conponents and DP?
Have you checked the distmgr.log? Anything helpful?
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SMS Provider Locations Do Not Match - Problem installing SCCM 2012 R2 CU4

I have an SCCM 2012R2 CU1 site that has been upgraded from SCCM 2012 non-SP1, so I have gone from 2012 to 2012SP1 through CU5 and then to R2 and then to CU1.
Over the course of the life of this site, which has more than 10k clients and 10 Site Systems, we have installed roles, removed roles, moved roles and removed Site Systems.
I have also installed and removed SMS providers . . . which is where my issues begin.
The site properties in the console list 6 SMS Providers and even lists an SMS provider on a server that was retired and is no longer a Site System. When I query WMI using the following VBS script it only returns the *ACTUAL* SMS Provider locations,
2 of the 6 listed in the GUI.
On Error Resume Next
Const ForReading = 1, ForWriting = 2, ForAppending = 8
strComputer = "."
Set oFS = CreateObject("Scripting.FileSystemObject")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\sms")
If Err.Number <> 0 Then
WScript.Echo "Cannot connect to WMI"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set oLog = oFS.OpenTextFile("C:\Temp\SMS_ProvList.log",ForAppending, True)
If Err.Number <> 0 Then
WScript.Echo "Could not create output file"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_ProviderLocation",,48)
count = 0
For Each objItem in colItems
count = count + 1
oLog.WriteLine "-----------------------------------"
oLog.WriteLine Now()
oLog.WriteLine "Provider instance " & count & " : " & objItem.Machine
oLog.WriteLine "NamespacePath : " & objItem.NamespacePath
oLog.WriteLine ""
Next
I have a test environment which has also gone through some growth over its lifetime and has had the same changes to SMS Providers made. When I first attempted to install SCCM 2012 R2 CU4 in this test environment the installer continually failed the
prerequisite checker when querying the CU level of the SMS Providers. The only way that I could get past that issue was by running a site maintenance task via the CM installer and installing an SMS Provider at the location that had previously been an
SMS Provider but I had uninstalled that role.
I do not want to have to do that in my production environment, and would not even be able to do so if I wanted as I have retired one of the servers listed and cannot re-provision that machine.
Any CM12 gurus out there with suggestions? This strikes me as a standard MS problem when having multiple development teams working on a product/update and not having a standard location to check for configuration information (This is exactly the problem
when configuring DNS suffixes via GPO and not manually setting the GUI to match).
Thanks!
Josh Gerner
Cornell University.

The issue I have is that I cannot find the WMI class that holds the SMS Providers that are returned by the GUI.
I actually engaged MS Premier for a SCCM 2012 RAAS about 2 years ago and that was when the discrepancy first reared it's head. The support person that I worked with couldn't give me a way of cleaning those entries at that point which is when I started
logging the locations to be sure that my maintenance task was really installing or removing the SMS Providers.
Josh Gerner

Cannot install SCCM 2012 SP1 CU4

Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?

The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file? .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

[SCCM 2012 R2] How SCCM 2012 handles Software Update Revisions?

Hi All,
There are a lot of questions regarding how SCCM 2012 handles Software Update Revisions.
Does anyone know what happened if:
Windows update publish some update with revision #1
Same update downloaded and deployed via SCCM 2012
Windows update publish same update with revision #2 or any newer revision
What is happening with SCCM and already deployed and downloaded revision? How should I know what revision is really on my distribution points?
Thank you in advance.
Regards,

In WSUS Revision History is very simple:
Where I can find revision history in SCCM??? (please do not mention dates):
Possible scenario in SCCM:
Windows update publish revision #1 for one update
SCCM Download and Deploy same update and revision #1
Windows update change revision to #2
What SCCM does after this scenario?
Auto update Distribution Points with new revision of already deployed and downloaded update?
Clearly state in SCCM Console that there is new revision of already deployed and downloaded update and waiting for admin to act?
Just update the revision in SCCM Console and leave old revision od Distribution Points?????

SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?

Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

Machines not Joining Domain SCCM 2012 R2 CU4

SCCM 2012 R2 CU4
Recent change CU1-4
This was all working until recently. The SMSTS log shows no failures. The Netsetup.log has no entries. The Panther\setupact.log shows a few odd things " [msoobe.exe] Failed to open event to start up services [0x80070002]" but then appears
to proceed fine.
The account used for Domain join is not locked out. I have no log telling me why it is not working. I have refreshed the drivers on the DP just incase the NIC driver got corrupt, though it appears to be fine in device manager and works.
I am just lost as I don't have any log that shows me any real failures and since SCCM passes the Domain Join off to the OS I don't know where else to look.

Is this a duplicate of
https://social.technet.microsoft.com/Forums/en-US/9122cebc-11b9-4f81-a5d7-3a14667f874c/smts-not-correct-showing-code-0-for-programs-while-none-get-installed-no-domain-join?forum=configmanagerosd#d5670eeb-55de-493c-abf1-eec9397d7081 ?
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 SP1 CU4 ccmsetup runs with SMS Agent Host on the "Service" mmc after upgrading the client to CU4.

Dear Brothers,
I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:
Scenario:
1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.
2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.
Issue:
After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host"
at the Service MMC. Which I believed this is very unusual behavior.
The Client however it seems properly installed and working please see below details:
Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.
1. How can I resolved this issue?
2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?
3. Or this is a normal behavior for the scenario?
Advance thanks for your future replies, my brothers in technology.

Dear Brother,
2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed
the issue .
CCMsetup.log
==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
Ccmsetup command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628
(0x15FC)
MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
2. Checks the desktop client version and gets the installation direcotry.
3. Stops remote control and other desktop components.
4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
Action: InstallFiles.
ErrorMessages:
Internal Error 2902. ixfAssemblyCopy
7/1/2014 7:15:33 PM 5628 (0x15FC)
A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)
Regards,

SCCM 2012 R2 CU2 Update - Need to update console or clients as well?

Hi,
I am going to be installing the following update onto out SCCM 2012 server:
http://support.microsoft.com/kb/2970177/en-us
I am not 100% sure but is there a need to update all installed consoles and/or all sccm clients after the CU2 installation?

Site server, console and clients needs to be updated.
Full installation guide : http://www.systemcenterdudes.com/sccm-2012-r2-cu2-installation-guide/

Windows Updates constantly failing and reverting after SCCM 2012 R2 pushes out updates

Hi folks,
I wonder could anyone help me with a strange problem I am having!
We use SCCM 2012 R2 and I am trying to roll out updates to a Windows 2008 R2 Standard 64 bit server.
When I deploy the updates to the server they get to the server and install but during the reboot it says Windows Modules Installer for a while then shows the failure configuring Windows Updates, reverting changes screen.
I’ve tried the suggestions of disabling 'Windows Management Instrumentation' and 'Windows Modules Installer' and renaming the repository folder but still no joy.
If I use Windows Update to install the updates the updates do go on but then when I add it to the collection in SCCM to push out the patches it sees the server as if the updates aren’t installed and begins doing the installs.
After the patches installs using SCCM and when the server is rebooted it goes back into the loop of saying Windows Modules Installer and reverts the updates and strips out the patches again.
I was hoping that when the Windows Updates were installed via Windows Update and once I put the server into the collection to push out the updates to the server it would have shown that the updates are already installed on the server and show that server
as being compliant in SCCM but unfortunately that isn’t happening.
It sights a couple of errors in the Setup event logs on the offending server: -
For multiple patches - Package KBXXXXXXX failed to be changed to the Installed state. Status: 0x80070643
For multiple patches - Initiating changes for package KBXXXXXXX. Current state is Invalid Resolved. Target state is Installed. Client id: WindowsUpdateAgent.
After doing some research,
0x80070643 refers to a .Net Framework issue so I’ve ran a .Net Repair tool but that didn’t work either so I’m running out of ideas so any help would be greatly appreciated on how I can get this sever updated using SCCM and showing as compliant.
Thanks,
Bonemister

Hi Torsten,
Thanks for your reply!
I was afraid you were going to say that as it just doesn't make sense that when I install the update using Windows Update via the Ire-nternet and when the install and re-scan no updates are required. It is only when I ask SCCM to check for patches
that it sees updates are missing and installed the updates before the OS reverts when.
Is there a way in SCCM to remove the record of what patches have been installed onto a particular server? I tried deleted the server out of SCCM then applying the Windows Updates via the web then added the server back into SCCM and see did it pick
up the newly installed updates on the server.
The thing is I don't think that WindowsUpdate.log will show any failures as Windows update is showing as no more updates required. It is just when SCCM installs that patches that the problem happens so that is what is leading me to think it is an SCCM
problem.
My main goal is to get the updates into the server and for it so show as complient!
I'll check back through the even logs again. Are they any SCCM logs that show patches failing to install and why?
Thanks again,
Bonemister

DQS Client doesn't upgrade after SQL 2012 SP1 CU4

One of my clients just has the DQS client tool installed and not DQS Server. After realizing he was trying to connect to DQS servers on a higher version he went and ran the CU4 update to get his DQS client in compliance. After running the service
pack, his SSMS was properly upgraded but the older DQS client is still there. Has anyone run into this issue? I tried to have him upgrade the dlls but the dqsinstaller.exe isn't on his machine since he didn't install DQS server. Is there
a special step that is required to upgrade the client?
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

This issue can be closed. My client did the following: 1)Uninstalled the SQL 2012 SP1 service
pack 2)Ran windows update service that had issues in the queue 3)Re-Ran SQL 2012 SP1 CU4 with success.
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

SCCM 2012 R2 CU4, how can we make sure clients without any CU upgrade will continue to communicate?

Hi,
We're about to upgrade the SCCM 2012 R2 server from CU1 to CU4. However no clients were ever upgraded (don't even have CU1). Is there any way(matrix or other) we can assure ourselves clients will keep on communicating (f.e. for SCCM R2 CU4, clients need at
least to be at CU1)?
Please advise.
J.
Jan Hoedt

Go through each one and see for yourself. Note that they are cumulative so you only need to deploy the latest. CU4 contains all the others. The issues that are fixed are listed.
CU4
https://support.microsoft.com/en-us/kb/3026739?wa=wsignin1.0
CU3
https://support.microsoft.com/en-us/kb/2994331
CU2
https://support.microsoft.com/en-us/kb/2970177
CU1
https://support.microsoft.com/en-us/kb/2938441
It's always better to use the latest version where possible.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 agent Deployed on clients SCEP in not update and shown inactive on cosole

Dear there are no of system in this state. SCCM client installed but SCEP is also installed but not getting update.
durranifaisal

OK, a couple of things for you. First off, if a client had not sent in Heartbeat DDR, then the console would not reflect "Yes" in the "Client" column. Yours does, so you have had at least one Heartbeat DDR received and processed by the client. If you want
to see when it was, you can view the Properties for that client, and in the Properties dialog, look at the AgentTime attribute. Very likely (always has been in my experience) it will be the very last time listed (you likely will have three or four 'agents'
that have discovered this client, and thus reported time.
The "Client Activity" column can be updated when you Refresh Client Status (on the Client Status node in the Monitoring workspace). It will happen automatically, but you can force it with this action.
Lastly, none of this has anything to do with the fact that the Endpoint Protection menu option is unavailable. I don't even have it enabled in my test site (the current snapshot that I'm testing on), and the menu item still appears. My guess there is that
you are logged on with a user that does not have rights to that action. So more likely a security issue rather than clients not reporting properly.
Wally Mead

SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"

Hi Team; I’m having 2 issues with SCCM 2012 R2:
Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
distmgr.log file.
~Package BDC00002 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~SourceVersion (1) of package BDC00002. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~Package BDC00003 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002"
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
~SourceVersion (1) of package BDC00003. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
AVAL0="BDC00003" $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
the status is packages deployment compliance stuck at 0%
Infrastructure:
3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
server is configured for each group respectively.
A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
is that I can't deploy the packages to production PCs in the Office subnet!
Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
I tried configuring IP Subnet Boundaries, still no luck!!
Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
<![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
thread="4884" file="lsad.cpp:770">
And here are the last 4 lines in the ClientLocation.log
<![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
<![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
<![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
While on the PC that the application was installed on I see the folowing in the LocationService.log:
<![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
Is there something wrong with the Distribution point on the Secondary Site server?
Please help…
Thanks..

Update:
I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
However; the second issue is still unsolved...
Please help..

After SCCM 2012 R2 CU4 update Client won't report status message back

Similar Messages

Maybe you are looking for