No but I can see using it in the future. The problem I see here in the DP Group Status is ghost DP's assigned to packages through old versions of a DP Group. I spent the last several days getting most of my DP Configuration Statuses green. That was either ghost package entries in the DP servers WMI or orphaned .ini files in pkglib. But I think some ini files or folders in DataLib were causing issues too.
Fixing all of that was in steps. 1. First a handful was fixed running this, https://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69 using this command line from my CAS, CMD /C C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy ByPass -File C:\<blah>\Remove-WMIInvalidContent.ps1 -SiteServer <CAS_FQDN> -Sitecode ABC. 2. Then I used Content Library Explorer from the Configuration Manager Toolkit to look at each problem DP. If a package showed up grayed out, I removed all folders and 'ini' files with its package ID from SMSSIG$, SCCMContentLib\PkgLib and SCCMContentLib\DataLib. Then I opened the console and set a package validation for 5 minutes in the future. After the validation was done, I had to use the new R2 right click menu in Monitoring\Distribution Status\Content Status to redistribute whatever packages came up by right clicking the server entry in the Error tab. I did use this script to set all validations again when I was done, http://mikw77.blogspot.com/2014/06/powershell-script-to-enable-content.html . I had to edit it since I have a CAS and 2 Primaries. This script works using a Primaries WMI. I could have run it from each Primary but I ran it from the CAS and edited as so.. a. Commented out: #$SiteCode = $PSD[0].name b. Commented out: #$SCCMserver = $PSD[0].root c. Copy and pasted everything below that once for each Primary and in each individual section replace $SiteCode and $SCCMserver with the info for a specific Primary. I edited on the 1st line starting with: $AllDPs = Get-WmiObject -computer . Also put the site again on the line that starts with: Set-CMDistributionPoint -SiteCode d. When I was done, I set EnableValidateContent to false for now. No more validations for while. They always cause extra work. Dave On Tue, Feb 17, 2015 at 2:24 PM, Ryan <[email protected]> wrote: > Did you happen to try the script I wrote to redistribute all content with > errors? > > http://ephingadmin.com/cm2012-redistribute-content-with-errors/ > > > > On Tue, Feb 17, 2015 at 12:21 PM, David Jones <[email protected]> > wrote: > >> No I definitely don't want to edit the database without MS helping but I >> just found a way to get it fixed. It will be labor intensive but doable. >> >> Look in Database views for v_DPGroupMembers. Find a server, DPNALPath, >> that is in your DP group and determine the DP GroupID from that. If the >> server is in more than one DP Group then you will have to count the >> instances of the GroupID to find the one with the right number of servers >> for the DP Group you are interested in. All of my DP's are in 2 Groups, All >> DP's and DP's of the agency that the server is located in. So one will have >> far more instances of GroupID than the other. >> >> Take that GroupID and find the view v_DPGroupContentDetails. Right click >> the view and choose Select Top 1000 Rows. After the last line of query at >> the top add: where GroupID = '{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}' . >> Use single quotes and keep the {} brackets. >> >> In the result I am finding something like this: >> >> There are 19 servers in this DP group. Note that some packages show 20 or >> 21 servers and have a stuck status of In Progress or Error. I am going to >> each package, removing the DP Group, waiting a few minutes and then putting >> it back. So far so good. And I am doing NO editing of the database. This >> will take a few days. >> >> [image: Inline image 2] >> >> Dave >> >> >> >> On Tue, Feb 17, 2015 at 12:45 PM, elsalvoz <[email protected]> wrote: >> >>> +1 >>> >>> True/false on status all the time. Don't trust them as your environment >>> health view for distribution. >>> >>> Cesar >>> On Feb 17, 2015 8:52 AM, "Nash Pherson" <[email protected]> wrote: >>> >>>> I think the best thing to do in these scenarios is open a support >>>> case with Microsoft. There are a bunch of bugs in those health status views >>>> which require going into the database to clean up records. (And the more >>>> of us that call and open tickets, the more likely it is that they will fix >>>> the bugs.) >>>> >>>> >>>> >>>> >>>> >>>> Nash >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *From:* [email protected] [mailto: >>>> [email protected]] *On Behalf Of *David Jones >>>> *Sent:* Tuesday, February 17, 2015 8:48 AM >>>> *To:* [email protected] >>>> *Subject:* [mssms] "Distribution Point Group Status" in SCCM 2012 R2 >>>> CU4 Console >>>> >>>> >>>> >>>> I have spent the past week getting all of the 'Distribution Point >>>> Configuration Status' statuses green. Mostly it was ghost packages left >>>> over from when SCCM 2012 was upgraded from sp1 to R2. But now they are all >>>> Green. They were all real issues at each DP that had to be cleaned from >>>> both the WMI and file structure. Luckily there are scripts online and >>>> the Content Library Explorer that helped find which ones were the culprits. >>>> >>>> >>>> >>>> However, the "Distribution Point Group Status" is another story. Many >>>> show either Error or In Progress. When you open the 'View Status', nothing >>>> is under In Progress, Error, or Unknown. So I have nothing to go by to help >>>> me figure out what is hanging these group statuses from showing Success. >>>> >>>> >>>> >>>> Has anyone dealt with this before? >>>> >>>> >>>> >>>> Dave >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >> > >
