Vinay is awesome. On Tue, Feb 17, 2015 at 9:04 PM, CESAR.ABREG0 <[email protected]> wrote:
> Vinay is also the one that submitted a couple of bug during a case last > year regarding status messages not displaying the correct state or not > changing. > > Cesar A. > Meaning is NOT in words, but inside people! Dr. Myles Munroe. > > On Feb 17, 2015, at 5:58 PM, Todd Hemsell <[email protected]> wrote: > > DP still has in WMI > > no, it looks at the ini files in the content repository. I have a case on > it if you want to look it up. Vinay sorted it out. > > On Sat, Feb 7, 2015 at 11:24 AM, Russ Rimmerman < > [email protected]> wrote: > >> Confirm the package ID mentioned is still an app/package that actually >> exists and not one that has been deleted but the DP still has in WMI. Also >> check to see if there’s a corresponding <packageID>.INI file for it in >> SCCMContentLib/PkgLib on the DP. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *George Salmaniw >> *Sent:* Thursday, January 29, 2015 3:59 PM >> *To:* [email protected] >> *Subject:* Re: [mssms] SCCM 2012R2 Content distribution warnings >> mismatch between Content Status and Distribution Point Configuration Status >> >> >> >> smsdpmon.log displays the following for the package in question: >> >> Report status message 0x4000094C to MP >> SMS_Distribution_Point_Monitoring 1/24/2015 5:18:38 PM 7084 (0x1BAC) >> Status message has been successfully sent to MP from remote DP >> SMS_Distribution_Point_Monitoring 1/24/2015 5:18:38 PM 7084 (0x1BAC) >> >> So I see the error and will investigate, however there has been no >> updates to the log file since 1/24/2015 ... could this monitoring be on a >> weekly schedule? >> >> G >> >> >> >> On Thu, Jan 29, 2015 at 2:08 PM, Sean Pomeroy <[email protected]> >> wrote: >> >> What are the errors in the smsdpmon.log on the DP? >> >> On Thu Jan 29 2015 at 2:05:16 PM George Salmaniw < >> [email protected]> wrote: >> >> Further information just came to light. Noticed that the two DPs that >> are reporting failures, and therefore bringing this distribution content >> mismatch to light, are the only DPs to have Content Validation enabled. >> How significant is these error messages? >> >> >> >> G >> >> >> >> On Thu, Jan 29, 2015 at 1:54 PM, George Salmaniw < >> [email protected]> wrote: >> >> Using SCCM 2012R2 CU3 and am seeing the following behaviour when >> monitor content distribution on a specific distribution point: >> >> >> >> Under Monitoring / Distribution Status / Content Status / <Application> >> status shows Content was distributed to distribution point >> >> >> >> Under Monitoring / Distribution Status / Distribution Point Configuration >> Status / Distribution Point Name / Details the same Application [same >> Package ID] shows error with message Failed to validate package on >> distribution point … >> >> >> >> The only difference I am noticing is on the timestamps for each. Under >> Content Status its last update was January 28, 2015. Under Distribution >> Point Configuration Status its last update for the particular package was >> January 24, 2015. >> >> >> >> Is the reason for the content mismatch warnings due to the Distribution >> Point Configuration Status not being updated to the current status? Is >> there a way of manually updating Distribution Point Configuration Status >> for a particular DP? >> >> >> >> Assistance is appreciated, >> >> >> >> G >> >> >> >> >> >> >> >> >> >> >> >> >> >> > > >
