Distribution Point Group Status Pie Chart Incorrect

In my SCCM 2012 R2 environment, I have only one Distribution Point Group, which contains all 20 of my DPs.
All packages have been distributed successfully to this DP group (verified via the Content Status node and checking each package, as well as the Distribution Point Configuration Status showing all 20 DPs with the green check-mark.
However, when I look under the Distribution Point Group Status, I see my DP group ("All DPs"), showing 20 members, but an Overall Distribution Status of "Error". The pie chart for that group shows package status as Success: 106
/ In Progress: 0 / Failed: 163. The pie chart for "Distribution Point Group Status" for the "All DPs" group shows the colors appropriate to these (incorrect) numbers. If I click the "View Status" link next to the pie
chart, the different tabs (Success, In Progress, Error, Unknown) show:
Successfully distributed content: 20 (269 Content Items) (last status time: today)
Successfully processed content on distribution point: 19 (263 Content Items) (last status time: yesterday)
Nothing in the In Progress, Error, or Unknown tabs.
So my question... Why is my Distribution Point Group Status showing the group with 163 Failures, but all Distribution Points showing 100% success on all packages? Is there a bug that causes the Distribution Point Group Status to not update?
I've restarted the server a couple of times, and still no change.

Hello all together!
I've the same issue in my SCCM R2 environment.
Has everybody an idea, how to correct this issue?
Thanks for your reply.
Regards Luke

Similar Messages

Distribution Point Configuration Status - SMS Client - Restart might required

SCCM 2012 was updates to SCCM 2012 R2. After that Management Console display for one of servers in Monitoring section - Distribution Point Configuration Status: SMS Client - Restart might required - In Progress. This DP was restartred but status "In
Progress" stay.
Distribution point works fine but status is confuses me.
How delete this status? Where can I delete dp status from SQL server?

Check the database to find any DP with the InsStr2 value is 3010. Here are the steps for your reference. > Make sure you have good backup of the site DB> Run the following select statement to find the Distribution Points in this state:
select * from dbo.DistributionStatus where InsStr2 = '3010'
> Once identified then Delete a record an affected DP with:
delete from dbo.DistributionStatus where ID = <DPID of affected DP identified by above command>

Redistributing Application to Distribution Point Group

Hey Guys -
Just a quick question for you about something I've never been 100% sure about and wanted to clear up...
Let's say I have an "Application" in which I've added files to the source folder which is required by the script the application runs. After adding the file, I need to update it's distribution on all 3 of my distribution points (which all
happen to be in a DP Group.) Which of the following methods will accomplish this or is the preferred method?
1. Select Application in console, choose "Deployment Types" tab, right click on type I want to update and choose "Update Content"
2. Open Application's Properties, choose "Content Locations" tab, select the Distribution Group (which contains all 3 DPs) and click "Redistribute"
3. Open Application's Properties, choose "Content Locations" tab, select each of the 3 distribution points and choose to "Redistribute" to each one of them
Below is what my Content Locations looks like when distributed to all 3 DPs. As is was distributed to the group containing all 3, it lists the group and the 3 DPs for a total of 4 objects. Which of the above methods (or a different one) is the
best way to go?
Thanks!
Ben K.

Option #1
http://eskonr.com/2013/09/sccm-configmgr-2012-how-do-i-refresh-the-application-after-change-in-source-files-or-source-location/
Benoit Lecours | Blog: System Center Dudes

Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

Hi,
Some of our DP's have a warning (Shown with a yellow exclamation mark) that never goes away. I have run a script on the DP's that could check for inconsistency in WMI, but it found nothing. Everything seems to work fine, but it is annoying that everything
is not green when it should be!
The warning is:
Failed to retrieve package list on the distribution point. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.

Hi Peter,
Yes I have tried to validate all content to no avail. ;(
No help to find in smsdpmon.log, I really think it is a bug...
Here is a small part of it:
]LOG]!><time="03:50:29.934-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
<![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:29.943-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Start to evaluate package 'C010003E' version 0 ...]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:586">
<![LOG[Report status message 0x4000094C to MP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.996-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Start to evaluate package share for package 'C010003E' version 0 ...]LOG]!><time="03:50:32.510-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:629">
<![LOG[Package C010003E is verified successfully]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:649">
<![LOG[Report state message 0x40000950 to MP]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:889">
<![LOG[Report Body: <ReportBody><StateMessage MessageTime="20141129025032.000000+000" SerialNumber="0"><Topic ID="C010003E" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>C010003E</Param><Param>["Display=\\dk01dc1sscm01.local.avk.dk\"]MSWNET:["SMS_SITE=C01"]\\dk01dc1sscm01.local.avk.dk\</Param></UserParameters></StateMessage></ReportBody>
]LOG]!><time="03:50:32.520-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
<![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:32.528-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Report status message 0x40000959 to MP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Report status message 0x40000952 to MP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[DP monitoring finishes evaluation.]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:500">

Distribution Point migration status in CM12 console

Hi,
We are using sccm 2012 r2 cu2. we are in middle of migration.
We have in sccm 2007 under secondary site server name assd1 it contain MP and DP role.
Under ASSd1 server i was created one of the distribution point server and copied all the package to the new server assd2.
I created this new distribution point last week.
Today I gathered data from sccm 2007 to sccm2012.
Previously I did the same almost 5 servers and after sccm2012 administration-->under site hierarchy--> shared distribution point it shows. after that i will migrate to sccm2012 DP
but this server not showing. but when i saw migctrl.log i can see the log
The DP assd2.xxx.org is eligible for upgrade
but not showing under administration-->under site hierarchy--> shared distribution

Issue got resolved..

Last Status Update in Distribution Point Configuration Status after 2012 R2 Upgrade not updating

I am having the oddest problem, and I was wondering if anyone had some pointers or knows how I can get this working. After I upgraded from
2012 SP1 CU3 to 2012 R2, the status update date on the DP config status will not update at all, even though under each DP it is updating? I can still push content to them, but instead of getting a % of transfer that is complete I get the generic 'Detail will
be available after the server finishes processing the messages'. I have tried to remove and re add the DP role to the DP's and am met with the same problem. I am assuming it's something is SQL but where to begin to look I have no idea.

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?
BTW I find that most of these type of things take ~ 24 hours to update.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Distribution point shows 0 items.

SCCM 2012 SP1 with 6 DPs.
We had 6 distribution points. The Primary Site server D drive got full while installing new DP. We reboot the server and now Administration->Distribution Points show 0 items.
Distribution point shows 0 items.
Distribution Point group shows ALLDPGroup however members show 0 items.
Content Status shows 0 items
Distribution Point Group Status 0 items
Distribution Point Configuration Status 0 items
MP could not complete a task when processing Relay.
Check the logs for clues. Possible cause: Out of disk space.
Solution: Increase the disk space, remove unprocessable files.

If you can get into the Console do you have maintenance task set-up to clean up and delete old records? if so do that.
Why should that help in that case?
@Parvinder_Randev: were you able to free up some disk space? Have you already examined the site and component status? Are there other errors? Site systems should not vanish just because of the disk being full.
Torsten Meringer | http://www.mssccmfaq.de

System Status- Site Status- Distribution Points Missing

Quick question,
I seem to be missing some DP's from Site Status, if a DP is installed and running, I'm presuming that it should appear in the Monitoring\system Status\Site Status workspace....only I have some DP's that don't appear, what would cause this?
many thanks

They should show-up there eventually. Did you check the Distribution Point Configuration Status
node to see if the distribution points are up-and-running already?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Problem with Pie Chart Size

I am using the CL_GUI_CHART_ENGINE to show pie charts in a dashboard format. One of my charts has just started to randomly decide to display the pie slices incorrectly.
this is the XML for the data
<Chartdata>
<Categories>
    <Category>Fax</Category>
    <Category>Phone call</Category>
    <Category>Phone Support</Category>
    <Category>Emergency service</Category>
    <Category>Web</Category>
    <Category>Email</Category>
    <Category>EDI</Category>
</Categories>
<Series label="Series" customizing="Series">
    <Point label="$26,815.03">
      <Value type="y">26,815.03</Value>
    </Point>
    <Point label="$17,045.12">
      <Value type="y">17,045.12</Value>
    </Point>
    <Point>
      <Value type="y">0.00</Value>
    </Point>
    <Point>
      <Value type="y">0.00</Value>
    </Point>
    <Point label="$33,914.70">
      <Value type="y">33,914.70</Value>
    </Point>
    <Point label="$23,731.63">
      <Value type="y">23,731.63</Value>
    </Point>
    <Point label="$973.08">
      <Value type="y">973.08</Value>
    </Point>
</Series>
</Chartdata>
The problem is, the last point on the pie chart is showing like it is about 85% of the pie. I admit, this is my first attempt at this, but why would it be OK, then suddenly NOT OK. Any ideas on what i may have coded incorrectly? what does the type indicator in the Value tag represent? i have looked at the documentation available for the chart engine, and it is pretty weak on specifics.
by the way, the label on the very large part of the pie is $973.08, which is considerably less than the values in the other "slices". The data is correct, as far as having the correct values. it is just suddenly displaying it incorrectly, putting the wrong size slice with the categories.
Edited by: David Knittle on Nov 22, 2010 1:32 PM

could it be because the chart is interpreting the values as text values instead of numbers? and 9 would then be much larger than ther other values? I'd try values without comma....tell it it's a numeric value like 12345.67.

Monitoring and troubleshooting in-place distribution point upgrades

I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi

Sync distribution points?

Hi,
Is there an easy way to sync distribution points?
Now we have some packages which were only distributed to DP1, we'd need to select those and distribute it to DP2. I can select them in content status but not select them to distribute to other DP.
J.
Jan Hoedt

You'll need to create a new distribution point group and add your DP's as members (you can do that at creation time of the group or later on once you have distributed the content to the group).
Afterwards in the distribute content wizard click the Add button and select distribution point group (instead of distribution point). A list with all DP groups will be displayed, just pick the one that contains the DP's to which you want the content
to be distributed.

SCCM 2012r2 - Remove "invisible" packages/applications from Distribution Point

Hello alltogether,
I've encountered the following issue:
Our distribution points are displaying applications/packages as "In Progress - Waiting for Prestage content".
These packages doesn't exist anymore. Neither as prestage file nor in the config manager itself. We never tried to apply this package by using a prestage file because such a file never existed.
Even if I open the "content" tab of one distribution point, I can't find these packages in there.
The exact status of this package is the following:
Message: Distribution Content
Message Detail: Distribution Manager instructed Package Transfer manager to send Package "x" to distribution point "y".
Status Type: In Progress
I want to remove these "ghost" packages from the Distribution Status overview. Anyone has a clue how to accomplish this?
Thanks in advance!
Best Regards
Feyh

Hello,
thanks for your answer!
Unfortunately no, there is no information about these files.
Yesterday we installed a new one, extracted all of our prestage files on it and watched the status. The Packages weren't listed in the "Distribution Point Configuration Status".
After some time we added the new DP to our general DP-group where all of our packages/applications are assigned to. Now the "non-existing" packages are added with the "in Progress" status.
I had a look into "Distribution Point groups -> Our group -> properties -> content" but these packages aren't displayed in the list. Some of the packages are now in the "waiting for prestage content" state, others are staying with the "Detail will
be available after the server finishes proccessing ...".
We managed to remove one of the packages by deleting it from the database.
The following statement removed it from the Distribution status overview. However, we still are able to find the package in the database.
select * from SMSPackageswhere PkgID = 'P100003B'
DELETE from SMSPackages
where PkgID = 'P100003B'
Apparently the delete-statement affected 72 rows. But we are having no clue which. As long as we are not sure we killed anything important we are not going to do this with the other packages because it's the productive system. We can't reproduce this in our
test system...

Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
point and failed to connect to remote distribution point"
Errors on the package transfer log file.
CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
Failed to connect to the DP WMI namespace on the remote DP

Thanks Sandys for your suggestions.
i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
server is unavailable" from both ends.
error:0x800706ba - The RPC server is unavailable

Recovery Distribution Point

Hi All
I am busy with creating a recovery plan for our SCCM 2012 related servers
I have a question according to the recovery of a Distribution Point
Is it possible to do a full server recovery in case of a mayor issue (failed) of a server with the role distribution point (and is it supported).
If it is not supported (or possible) what is the best way of removing de failed distribution point from the SCCM environment
Step 1 : Remove failed Distribution Point from Boundary Group
Step 2 : Remove failed Distribution Point from Distribution Point Group
Step 3: How to remove the entries of the failed Distribution Point from the SCCM Console (SCCM environment) , I think the failed Distribution Point cannot be removed from the Console (Remove Rol Distribution Point will not work anymore I think).
I hope someone can help me with completing the steps
Regards,
Johan

A full server backup and restore of a DP site system would be OK, but you would need to ensure that you either have content validation enabled or you re-distribute any changed content to that restored DP.
You can simply delete a failed (server down) distribution point site system, rather than trying to remove the distribution point role. You would need to re-provision that site system and re-send all of the content.
My Personal Blog: http://madluka.wordpress.com

New Site Server with Distribution Point & Software Update Point Roles not pulling SUGs

I just set up a new server & installed the DP & SUP roles on it. I am getting the following in the log this is just a small sample as its kind of repetative:
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Retry 10 times SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate all packages ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate package 'FPP00002' version 0 ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x4000094C to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate package FPP00002, Error code 0x80070002 SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x40000952 to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
DP monitoring finishes evaluation. SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate some packages after 10 retry SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
The Console shows for the DP that it's waiting for content and I don't see where I can create a Prestage Package
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

D:\SMS_DP$\sms\logs\smsdpmon.log
This is the 2nd server in our SCCM 2012 Sp1 Hierarchy. It is set up with the following Site System Roles:
Component Server
Distribution Point
Site System
Software Update Point
It is Prestaged Enabled. My intent is that the client systems @ the location where this DP is located will use it to pull their Microsoft Updates from as well as content for any Applications we push to them rather than going over the WAN to the Primary
Site Server.
IN Distribution Point Configuration Status. the console shows "Failed to update package" & "Packaget Transfer Manager failed to update the package "yxz00040". Version 3 on Distribution Point server.my.domain.com review pkgxfermgr.log for more information
about this failure."
It also goes on toe list 2 possible causes and solutions
Site servers does not have sufficient rights to the source directory.
(Site server account is a member of local Administrators on Primary)
Not enough disk space available
(I have over 1TB of available space and primary site server has only 150GB available for entire content repository, both applications and sofware updates.)
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

Distribution Point Group Status Pie Chart Incorrect

Similar Messages

Maybe you are looking for