Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, June 29, 2012 4:20 AM
how to reset status for distribution point in console? monitoring > distribution point configuration status > status type
All replies (21)
Friday, June 29, 2012 7:38 AM ✅Answered
That cannot be reset if I am not mistaken; it will be updated/changed dynamically according to status of each DP.
Torsten Meringer | http://www.mssccmfaq.de
Friday, June 29, 2012 9:44 AM
My question associated with problem http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/a447fee2-25b2-45df-a0c2-d3a1478da557#a447fee2-25b2-45df-a0c2-d3a1478da557
DPs have old error about not transfer package "client upgrade".
now it package is prestaged (manual deploy) but config status for DP not update. (now client package must be "in progress" )
and DPs still in error
Saturday, June 30, 2012 3:03 PM
How did you manuall deploy the pacakge? How would CM12 know that you have manually deploy the package?
IMO the best option would be to fix what every issue is holding up CM12 from deploying the pacakge.
Monday, July 2, 2012 9:23 AM
I create Prestaged content file for ConfigMgr client (packages created during site setup)
And use ExtractContent Tool for each DP.
But in this question i ask for
how to reset status for distribution point
Monday, July 2, 2012 5:58 PM
Hey snesov,
As Torsten mentions, the status cannot be reset.
Thanks,
Moiz
Tuesday, July 3, 2012 8:38 AM
Then it is BUG.
In my case pakage transfer settings is "manual" and DP show error for transfer this pkg and not change to "in progress"
Monday, December 16, 2013 9:04 PM | 2 votes
I'm going to have to bring this up again -
On my DPs, I had a package fail to transfer right after we initially installed SCCM (due to configuration issue). This was back in May. Since then, there have been no errors, yet status is still error on all DPs.
Remember, mark posts that are helpful, or if it has answered your question, mark as answer.
Friday, January 3, 2014 5:42 PM | 1 vote
I am guessing the package ID is one of the ABC00002 or ABC00003 (where ABC is your site code). You can't see the upgrade package which I believe is ABC00003 package. You need to use a Powershell script to refresh the package on your DPs.
This will work for any package or application you just need to change the Site Code and Package ID. Run from Powershell Console under an account which has rights to do the refresh on your CAS or Primary that has the DPs in the error state.
$SiteCode = "<Your 3 Letter Site Code Here>"
$PackageID = "<Your 8 Character Package ID Here>"
$distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
foreach ($dp in $distpoints)
{
$dp.RefreshNow = $true
$dp.Put()
}
It works for hidden packages as well which is probably the one holding up your error state. That is almost always the ***00003 package. It was a bug back around SP1 release time.
Wednesday, February 26, 2014 9:17 AM
There is a similar thread which I believe is the same problem seen by the original poster. I've seen this also. So essentially this seems to be around the validation of content on the DP.
You should check your smsdpmon.log on your DP, find what content is showing as at fault. If your content does actually exist then run a validation on it and/or re-distribute. If your content doesn't actually exist (like mine) you should remove the reference from WMI on the DP as in Dave Gangwer's post above and then run a validation on the DP. You can either wait for your validation schedule to kick in if you set one or you can run it manually from the DP from task scheduler.
Thursday, March 20, 2014 8:45 PM
I am trying to figure out how to get this to status to update the DP is working and I can publish contect etc... But for some reason it still has an old error on it... How can I get this back to green?
Friday, March 21, 2014 3:08 PM
I decided to write up how this all works so take a look here http://wmug.co.uk/wmug/b/peter_egerton/archive/2014/03/19/configuration-manager-dp-configuration-status-and-content-validation.aspx
It could be that you need to run a validation on your DP to clear the error.
Wednesday, September 24, 2014 5:40 PM
How do you run a validation on the DP ?
Wednesday, September 24, 2014 5:54 PM
it can be scheduled in the properties of a DP.
Torsten Meringer | http://www.mssccmfaq.de
Thursday, September 25, 2014 1:07 PM
I'd also recommend scheduling it through your DP properties. Alternatively for a one off you can simply run C:\Program Files\Microsoft Configuration Manager\bin\x64\smsdpmon.exe on your DP.
Don't forget to use whatever drive letter is relevant to you.
Friday, January 16, 2015 4:14 PM
So I was having content validation issues back in October 2014 (due to a long standing upgrade issue) and that issue was resolved but the DPs are still yellow. The Details tab content has been green since then. The Content Validation is scheduled for Saturday every week since that time in October and content validation has succeeded. I have ran smsdpmon.exe but I run it from <Drive>\SMS_DP$\sms\bin\smsdpmon.exe as the recommended path by Peter does exist on my DPs for obvious reasons. My DPs continue to stay yellow. I have monitored the <drive>\SMS_DP$\sms\logs\smsdpmon.log (and smsdpprov.log for good measure) and see no issues. I have well over 100 DPs and this is just one of those issues that nags at me. Its hard to explain to the admins what is going on here when they see all the yellow. "Ignore all that" doesn't go over very well :-)
Monday, January 19, 2015 2:16 PM
Did you read that blog article I linked? I was in exactly the same position but got to the bottom of it in the end and wrote it up.
Wednesday, December 23, 2015 3:15 PM
Hi,
I have another question.
Did somebody know hom to enable smsdpmon.log logging.
I can't find this log on one of my DP.
Best Regards
Tuesday, September 27, 2016 3:08 PM
So I was having content validation issues back in October 2014 (due to a long standing upgrade issue) and that issue was resolved but the DPs are still yellow. The Details tab content has been green since then. The Content Validation is scheduled for Saturday every week since that time in October and content validation has succeeded. I have ran smsdpmon.exe but I run it from <Drive>\SMS_DP$\sms\bin\smsdpmon.exe as the recommended path by Peter does exist on my DPs for obvious reasons. My DPs continue to stay yellow. I have monitored the <drive>\SMS_DP$\sms\logs\smsdpmon.log (and smsdpprov.log for good measure) and see no issues. I have well over 100 DPs and this is just one of those issues that nags at me. Its hard to explain to the admins what is going on here when they see all the yellow. "Ignore all that" doesn't go over very well :-)
Hello,
I have the same Issue. My Error is from Year 2014. The DP Content Validation are ok.
MfG Hei_G
Tuesday, September 27, 2016 3:25 PM
Apologies as my German isn't good so I can't make out the error message. Have you checked for any orphaned content on the DP? Also have you checked the vSMS_DPStatusInfo view in SQL for counts of content?
Peter Egerton - @PeterEgerton
Tuesday, October 4, 2016 8:31 AM
Hello Peter,
Sorry for the late response, I was on vacation. The problem seems fixed now after I've cleaned up the content according to your instructions.
MfG Hei_G
Wednesday, October 5, 2016 9:07 AM
Good to hear :)
Peter Egerton - @PeterEgerton