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

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>

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">

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

No status messages for any components after 2012 SP1 upgrade

Hi, after a recent upgrade to 2012 SP1 two of my sites no longer show any status messages in monitoring. All the services seem fine, I can distribute and deploy packages to clients, run queries etc.
All other sites are now fine, the difference is the working sites are on 2008 R2 or 2012 and the trouble sites are on 2008 Storage Server SP1. So obviously close at hand to assume the Site Server OS is somehow the culprit.
SP2 is installed on all sites for SQL Server 2008 R2, servers have been restarted.

There we go!
So sender.log had these:
There is no existing connection, Win32 error = 7054
and
Error during connection to \\primaryserver.domain.local\SMS_SITE (7054).
As mentioned already, I already verified the secondary site computer accounts were in the SMS_SiteToSiteConnection_XX1
on the primary site server. But I added my main SCCM service account there as well and under Administration\Hierarchy Configuration\File Replication I changed the File Replication Account from the computer account to the service account and the status messages
are now transfered and appearing in the Status Message Viewer.
I don't really care why the computer account wouldn't work, I'm just going to leave it like this, the 2008 Storage Servers
are due to be replaced or upgraded this year anyway.
Thanks Juke and everyone else!

Distribution point, a TFTP error message

Hello,
I have a problem when I tried to migrate
a computer via PXE Network in an Annex or
there is a distribution point, a TFTP
error message appears as follows:
PXE-E32: TFTP
open timeout.
TFTP.
knowing that this problem does not arise
at the main site.
please help me and thank you in advance.
cdt.
Rayo_Muchacho

As Torsten mentionned, review the requirements for PXE boot.
http://prajwaldesai.com/boot-images-distribution-point-configuration-osd-sccm-2012-r2/
http://gerryhampsoncm.blogspot.ca/2013/02/sccm-2012-sp1-step-by-step-guide-part_9487.html
Benoit Lecours | Blog: System Center Dudes

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

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

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..

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 Points not appearing when trying to distribute content

Hello,
When I try to distribute content for a OS task sequence to a distribution point to my 2 distribution points using distribute content wizard, my distribution points are never shown. When I click Add distribution points, the available distribution points are
empty. Just this morning I distributed the content for boot images, packages, applications, Operating system images, and operating system installers.
how can it work for these and not for Task sequence, if it is rights related. I tried to delete and recreate the task sequence, but still the DP don't show up in the list.
I understand that once the content is distributed to a DP, the DP won't show up in the list of DP when trying to distribute content. I don't see the task sequence listed on the DPs under content, but see the other boot images, etc.
•Site Status and Component Status are all green under Monitoring.
•The distribution Point configuration Status is a green Arrow.
12 successful, 0 in progress and 0 error
•Drive Settings for these DPs are set to 15,000 mb
•I have rebooted the DP, SQL and PS Server.
Thanks,
Mark

Hello,
When I try to distribute content for a OS task sequence to a distribution point
to my 2 distribution points using distribute content wizard, my distribution points are never shown. When I click Add distribution points, the available distribution points are empty.  Just this morning I distributed the content for boot images,
packages, applications, Operating system images, and operating system installers. how can it work for these and not for Task sequence, if it is rights related. I tried to delete and recreate the task sequence, but still the DP don't show up in the list.
I understand that once the content is distributed to a DP, the DP won't show up in the list of DP when trying to distribute content. I don't see the task sequence listed on the DPs under content, but see the other boot images, etc.
Site Status and Component Status are all green under Monitoring.
The distribution Point configuration Status is a green Arrow. 12 successful, 0 in progress and 0 error
Drive Settings for these DPs are set to 15,000 mb
I have rebooted the DP, SQL and PS Server.
Distmgr.log
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
Ignoring drive C:\. File C:\NO_SMS_ON_DRIVE.SMS exists.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
Share SMSPKGE$ exists on distribution point \\TXSCCMPSDR01.DR.LPL.COM\SMSPKGE$
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (TXSCCMPSDR01.DR.LPL.COM) is submitting SDK changes from site(1DR)
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
RDC:Successfully created package signature file from \\?\E:\SMSPKGSIG\1DR00010.5 to \\TXSCCMPSDR01.DR.LPL.COM\SMSSIG$\1DR00010.5.tar
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
Setting permissions on file MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\SMSSIG$\1DR00010.5.tar.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=10932 GMTDATE=Sat Dec 14 19:01:52.367 2013 ISTR0="1DR00010" ISTR1="["Display=\\TXSCCMPSDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMPSDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\"
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
Successfully created/updated the package server in the data source
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM       10932 (0x2AB4)
Performing cleanup prior to returning.   SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
DP thread with array index 0 ended.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
DP thread with thread handle 0000000000001920 and thread ID 10932 ended.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Created policy provider trigger for ID 1DR00010 SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Package 1DR00010 does not have a preferred sender.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Package 1DR00010 is new or has changed, replicating to all applicable sites.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=1DR00010, Version=5, Status=2301
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
StoredPkgVersion (5) of package 1DR00010. StoredPkgVersion in database is 5.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
SourceVersion (5) of package 1DR00010. SourceVersion in database is 5.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=6348 GMTDATE=Sat Dec 14 19:01:53.052 2013 ISTR0="FileZilla" ISTR1="1DR00010" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="1DR00010"
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
Exiting package processing thread.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Sleep 2402 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Sleep 2402 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Processing PullDP response 1DR - ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
    Package 1DR00010, Version 5(5), ActionState 32, PkgStatus 0, ActionData =
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
STATMSG: ID=9509 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=3872 GMTDATE=Sat Dec 14 19:02:56.793 2013 ISTR0="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
ISTR1="1DR00010" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
AID2=410 AVAL2="5"     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
Successfully processed PullDP response file E:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\72057594037927970.PUL
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM       3872 (0x0F20)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
Sleep 2339 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
Sleep 2334 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
Processing PullDP response 1DR - ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
    Package 1DR00010, Version 5(5), ActionState 1, PkgStatus 0, ActionData =
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
Successfully updated the package server status for ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\ for package 1DR00010, Status 3
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=3872 GMTDATE=Sat Dec 14 19:05:22.316 2013 ISTR0="1DR00010" ISTR1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
AID2=410 AVAL2="5"     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
Successfully processed PullDP response file E:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\72057594037927970.PUL
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM       3872 (0x0F20)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
Sleep 2193 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/16/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/16/2013 4:45:26 AM 3392 (0x0D40)
Sleep 3600 seconds...     SMS_DISTRIBUTION_MANAGER
12/16/2013 4:45:26 AM 3392 (0x0D40)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/16/2013 5:15:29 AM 3804 (0x0EDC)
Thanks,
Mark

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

Distribution Points content missmatch - WMI and content library

Hi,
We are using SCCM 2012 R2 with stand alone primary site.
After creating a new Distribution Point we distribute our task sequence content there.
This takes some time and after this the distributen point is shown as "Success" in "Distribution Point Configuration Status".
Content of the packages is shown as "Success", too.
We recognized this failure while trying to run our task sequence.
It breaks and tells us content is not available.
After a short check with the following script:
http://sccmroad.wordpress.com/2014/03/11/powershell-script-to-compare-dp-packages-with-wmi/all content is in WMI but NOT in content library.
We tried to redistribute etc. - everything without success.
After some try and error we found out that using prestaged content solves the problem.
This is a workaround but no solution to the problem. :(
Are there any ideas to how to find a solution?
Thank you for your help.
kind regards
mk-maddin

I opened a Microsoft case.
After a lot of searching through logs - not providing any error etc. we tested for packages.
Solution was to redistribute for packages (for applications we had to update the content).
A very hard task at this was the information which packages and distribution points are affected.
I wrote a little script to do this task:
http://gallery.technet.microsoft.com/SCCM-2012-WMI-ContentLib-80a53705
Thank you to Thorsten for help :)

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

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

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

Similar Messages

Maybe you are looking for