Content Available on Distribution Points

Hi,
I would like to create a report for the content (packages, Image files, driver package, applications) available on Distribution Points in our environment.
If i go to the properties of Distribution Point -> content, it shows all the data available on DP.
Is there a way to export this to excel or any other SCCM report which provides all the details of the content available on DP.
Thanks

Torsten, Let me explain
If you go to Administration -> Distribution Points -> Properties -> Content
I could see all the content available on this distribution point
Now when i run the report All
content on a specific distribution point. This report shows the names of all the package/application etc. names available on this distribution point.
But in this report it shows names of applications/software which are not available on this and are not showing under the Content section of the distribution point.

Similar Messages

Enable PreStaged content on a distribution point.

I would like to enable Prestaged content on two current distribution points that already have content on them. I am assuming after I enable them I will still be able to use the option to Automatically download content to the distribution without presaging
it? (When a distribution point is not configured for prestaged content the content is automatically set to download when the package is assigned to a distribution point?)
Also if I have some packages that are set to Manually copy content do a distribution point (I don't know why this was set since our distribution points were not enabled for prestaged content yet) will they still work?
Is there a way to query for packages that have the distribution settings set to Manually copy?

So essentially if "Enable this distribution point for prestaged content."
is not selected on a distribution point, the content behavior for all packages is "Automatically download content when packages are assigned to distribution
points"?
If "Enable this distribution point for prestaged content."
is selected on a distribution point, and the distribution settings for a package is set to "Download only content changes to the distribution point". Does
the first time the package get deployed it need to be prestaged or will it fully copy the content the first time and then just update the changes?
My distribution points are not really network resource constrained but I would like to be able update images and software update packages with just updated content. I won't necessarily ever need to prestage content.

Difference between "Distribute Content" and "Update Distribution Points"

Hi,
Can someone clarify this for me, I need to redistribute a package to all my distributions points. Should select distribute content and then select the DP's or should I just use the option "Update Distribution Points" to redistribute? TIA

Yes. Once content has been distributed you can not "Distribute Content" again to the same DP. However, you do have another option, go to the properties of the DP, "Content" tab, find the package in question and conduct a re-distribute.
This approach does not increase the versioning of the content whereas "Update Distribution Points" does.
P.S. If you have not read it yet, here is a great
article about content monitoring and validation.
-Tony

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

How long until Deleted Content from Distribution Point frees disk space?

Hopefully this is an easy question for you guys with more experience with the product.
Yesterday, I created a new software distribution group for Office 2013 SP1, both 32 and 64bit. I didn't really understand at the time that it was going to download nearly 8GB into my /sources folder...which is where I save my package contents. I
would have not expected this download to exceed approx 2GB.
Since I indicated that it should also be distributed to my Distribution point, which is the same server, it also increased the disk usage in the /sccmcontentlib folder, as well as increasing the amount of space used in my SQLDatabase which is on the same
drive. It was never deployed to anything.
Since I'm not yet ready to deploy this update to clients, but have a few others things to do instead, I wanted to delete the content from the distribution point to free up some disk space.
I went into Software Library, Deployment Packages, went to properties of my Office2012_SP1 deployment, went to Content Locations, picked my single distribution point from the list, and chose Remove.
However, no disk space was cleared on my drive. I've still got 6GB free on my 120GB volume, so I'm not out of space.
Is this something where a scheduled job will come through and process this removal and free up the disk space? Or is there a way to kick of the process manually?

It was never setup as an application.
It was a Windows Update, which was added to a software update group. Then, I went to the software update group and right clicked and chose Download. I created a new deployment package, and then distributed the content to one of my distribution
point.
By doing that, I understood that it would create the D:\sources\WindowsUpdates\Office2013_SP1 folder and put the deployment files there. And I also see that because that content was set to a distribution point, it copied it there into the ContentLib.
So, I wanted to remove the data from ContentLib, so I went to the Deployment Package, went to Content locations and removed my Distribution Point.
So, are you saying that in order to remove the ContentLib, that I have to remove the entire Deployment Package?
I thought by removing the Content Location it would remove it from the DP, and if I later wanted to add it back ,I could go back to the Deployment Package, go into Properties and add a DP back to the content location.

Distribution manager failed to connect to the distribution point

After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
I see the following error.
source: SMS Server
Component: SMS_DISTRIBUTION_MANAGER
message id 2391
Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
The firewall is not enabled.
wbemtest is able to connect to the remote server that has the distribution point role installed.
The network access account is working.
How do I fix this?

but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
I have the same issue as described above.
The IT guys from LukOIL

OSD: prestaged image does not distribute to remote distribution point

Hi,
We have an SCCM 2012 with 2 distribution points: a virtual (the sccm server) and a physical (a pure distribution point). Once and a while we have issues with deploying packages to the physical dp but clearing it and redistirbuting solves the issue.
Now we have a big OS image (15 GB) which does not want to deploy to the physical distribution point at all.
The status stays "in progress" since this morning 11 AM (+/- 8 hours ago). Other packages distribute also slowly but fine.
Distmgr.log shows only logs from end of March this year and then stopped logging anything so I don't have a clue what is going wrong.
Please advise.
J.
Jan Hoedt

Hi,
Please go to the properties of the OS image, make sure "Manually copy this content to the distribution point" on the "Distribution Settings" tab is checked.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point

We currently in the process of the doing a site server refresh at all our remote sites. Each remote site currently has a physical 2012 SP1 DP, and will be replaced with a new DP at each location, and will eventually decommission the current one.
What's the best way to introduce a new DP and remove the old one?
Thanks
Bern

You can use this method if distributing through the WAN is not an option.
http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx
If you don't care, just add it to SCCM and replicate your content. Modify your boundary once done.
I hope you have a DP Group, if so, just make it member of the group and all your content will be copied. If not, you'll have to go through all your content and add it manually or script the process using PowerShell.
To remove your existing it's simply a matter of removing the "Distribution Point" role on your Server using the SCCM Console. (Administration / Site Configuration /Site Server, select your distribution point, right click Remove)
Benoit Lecours | Blog: System Center Dudes

2012 -- 2012 Migration: How to Reassign Distribution Points that Reside on Source Secondary Site Servers to the Target Site

Source hierarchy AAA is at 2012 R2 CU3 and contains a primary site and 14 secondary sites (A01 through A14). The 14 secondary site servers hold the following roles:
Site system
Management Point
State migration point
Site server
Site database server
Component server
Distribution Point
Target hierarchy BBB is also at 2012 R2 CU3 and contains only a primary site. The goal is to "downgrade" the severs at source secondary sites A01 through A14 to distribution points.
AAA was added as a source site. Data gathering was done. A migration job was created an run, and distribution points from the source hierarchy were shared to allow a phased migration of the clients.
We have reach the point where we are ready to reassign distribution points in sites A01 through A14 from AAA to BBB, but none of the shared distribution points are eligible for reassignment. We surmise that since the DP role is not the only role on
these servers (as you can see from the bullet list above), they are ineligible for reassignment. We are unable to remove most of the roles. In fact, the only 2 roles that can be removed are the DP role itself, and the State Migration
Point. If we delete the secondary site, it removes ALL roles...not leaving any behind...including the one we need...DP.
My question is 2-part:
Is our assumption correct? Must a DP role be the only one on the server for a DP to be eligible for reassignment?
Is there any way we can reassign these DPs instead of deleting everything and building them from scratch?
These secondary site servers are in branch offices and host a lot of distributed packages. It would be very inconvenient to have to rebuild the DPs from scratch and redistribute all those packages over the WAN.

Full Disclosure: I have never used this tool myself. I intend to, however the opportunity or time to do so has not yet arisen.
You could use the techniques outlined in CloneDP (https://gallery.technet.microsoft.com/scriptcenter/CloneDP-for-SCCM-2012-SP1-825ce5b1) to create prestage media on each DP and rebuild. That at least would prevent redistributing over the WAN
Ken provides a nice writeup too: http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx

Restrict clients from a distribution Point

Is there any way to restrict distribution points to clients from a particular limiting collection or at least change the priority of a distribution point used?

Our organization has several entities that provide support desktop. Central IT provides core services support such as networking, directory services and email services to the entire organization. Central IT also provides Desktop support to a large
portion of our organization. We offer the entities of our organization that have their own desktop support use of our tools such as SCCM. It is configured with collection limiting to limit access to each entities OU so that the admins can administer
the machines in their ou and that's it. We also allow them to use the content, i.e. Applications, programs, task sequences etc that we (Centeral IT) create. In some cases the admins distribute our content to their Distribution points. I am
noticing that this causes some of our deployments to use their distribution points for content and not ours. We don't have a very clear cut IP configuration to break out each entities with their own boundary group. I just want our clients to use
our distribution points because with they use other distribution points, we are noticing slowness in deployments such as OSD.

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 :)

Secondary Site Distribution Points content flow

We are implementing an environment that contains over 750 locations with distribution points. With the limitation of 250 DPs per site, we are going to have to put DPs under secondary sites.
In preparation for this configuration we would like to have a better understanding of how the content will flow to the lower level DPs (under secondary sites). We are aware that content
being sent to a dp on a secondary site server is compressed at the primary, sent to the secondary and uncompressed. Here are our questions:
1. Will the content for lower level DPs, under the secondary Site, receive its content directly from the primary site DP, or the Secondary Site DP?
2. Will the content for the lower level DPs be compressed, sent and uncompressed (from the primary or secondary)?
This information will help determine the network configuration we use to limit our WAN traffic.
I appreciate any insight into these questions you can provide.
Thanks.

Sorry, but can someone explain #1 more detail?
I have Secondary Site with multiple DPs.
If I distribute the content to only 1 DP at Secondary site (not pull DPs), will the content distribute to the Secondary Site server first, then to the DP? Does the content also available at the SS Server?
Does the data flow like: Primary Site -> Secondary Site -> DP ?

Is there a way to avoid having a content library on a site server when the Distribution Point role is not installed on that server (disk cost issue)?

Hello,
I don't think it is possible, but my goal is to start a discussion about content libraries and maybe suggest something for a future release or version of Configuration Manager.
Actually, based on Configuration Manager Technet documentation, Configuration Manager creates a content library on each site server and on each distribution point.
Often, when designing the architecture, people will offload the distribution point role from the site server to an external server (and add the role to other servers too for redundancy). They could also do the same for the Management Point role, but this
is not related to content library. The idea is to save the site server from having to deal with clients for software distribution (applications, software updates, OS, etc.), this is especially true for organizations having a large number of clients and/or
primary site servers involved in a hierarchy. Doing so will allow more resources on the site server to deal with the database and also replication in the case of a hierarchy.
When doing that, you still have to maintain a content library on the site server and the thing is this library will usually become huge, especially for organizations having more than 1000 applications (add also OS images to this). Will the content library
on the site server become as huge as the one for a distribution point having a copy of all content? I guess the answer is yes.
I know that Pull distribution points will help offloading the task from the site server to distribute content to distribution points, but, correct me if I'm wrong, you still have to maintain a content library on the site server when using them, and they
will not make the content library smaller on the site server. Also, I don't like the fact that you lose the rate limits feature with Pull DPs, but this is another story.
Storage cost is high and in this scenario, it hurts to have to pay this cost for a content library not used by the clients, but only to distribute content to DPs.
Correct me if I'm wrong, but the key component here is Distribution Manager on the site server; this is the one which has to maintain a content library to do its job.
It would be nice if we could have a way to elect a specific distribution point (not on the site server) as the Distribution Manager for a site, that main DP would hold a copy of all content by default, but would be used to distribute content to other DPs
and avoid the content library on the site server. Said differently, the Distribution Manager component would become a site system role that could be transferred outside the site server.
Tnx for comments, answers or suggestions.
Patrick

There is no way to avoid that the contentlib will be placed on the site server.
I don‘t agree that storage cost is high. It might be true for fast storage, but that‘s not needed for it.
Torsten Meringer | http://www.mssccmfaq.de

"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

Failed to get the Availability State on server Distriubtionpoint1 for role SMS Distribution Point

Distriubtionpoint1-- Server share distribution point
Distriubtionpoint1-- Acting as site system role (DP)
Distriubtionpoint1--attached under the primary PR0 (Primary server0)
Primary server0-- reporting to CS0 (central site 0)
Distriubtionpoint1-- Windows 2008 sp1 r2 standard
Infrastructure details:-
=============
Distriubtionpoint1 located in different domain with one way trust.
1) Check ping status with FQDN from both domain and it is success.
2) Check port 135, 445, 80,443 through telnet from both domain and success.
3) Primary Server0 account is member of the local admin group on Distriubtionpoint1.
4) Check the PR0-SCCM-DP$ folder NTFS & Share permission
Share permission
a) everyone & local admin group has full control
Security permission
a) System has full permission
b) user has read & exec
4) Local admin full
Sitestat.log error message:
---->: Failed to get the Availability State on server
Distriubtionpoint1 for role SMS Distribution Point. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4/22/2014 9:00:15 PM 952 (0x03B8)
---->: Now polling via NAL for SiteObject "["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\" SMS_SITE_SYSTEM_STATUS_SUMMARIZER
4/22/2014 9:00:15 PM 952 (0x03B8)
for ["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\, no connection account is available SMS_SITE_SYSTEM_STATUS_SUMMARIZER
4/22/2014 9:00:15 PM 952 (0x03B8)
---->: The NAL path ["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\ is currently not accessible. SMS_SITE_SYSTEM_STATUS_SUMMARIZER
4/22/2014 9:00:18 PM 952 (0x03B8)
Info>: Unable to get available space for the Site Object ["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\ SMS_SITE_SYSTEM_STATUS_SUMMARIZER
4/22/2014 9:00:18 PM 952 (0x03B8)
STATMSG: ID=4701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_SYSTEM_STATUS_SUMMARIZER" SYS=Distriubtionpoint1 SITE=PR0 PID=4112 TID=952 GMTDATE=Wed Apr 23 01:00:18.002
2014 ISTR0="\\Distriubtionpoint1\PR0-SCCM-DP$" ISTR1="\\Distriubtionpoint1\PR0-SCCM-DP$" ISTR2="2014 04 4 17 04 31 31 000" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4/22/2014 9:00:18 PM 952 (0x03B8)
for ["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\, no connection account is available SMS_SITE_SYSTEM_STATUS_SUMMARIZER
4/22/2014 9:00:18 PM 952 (0x03B8)
---->: GetOperationsManagementData failed to connect to ["Display=\\Distriubtionpoint1\PR0-SCCM-DP$\"]MSWNET:["SMS_SITE=PR0"]\\Distriubtionpoint1\PR0-SCCM-DP$\; error
= 5. SMS_SITE_SYSTEM_STATUS_SUMMARIZER 4/22/2014 9:00:20 PM 952 (0x03B8)

I have tried to access the server share DP from the primary server by using my user
credential. Yes I can able to access the share.
But when I use the system credential to access the share received an error message as shown in below screenshot
Hence i have provided the share and ntfs permission administrators, system, everyone,
primary server account with full control on both tab. but still i am receiving error message.
:\temp>whoami
US\prasath
c:\temp>dir \\PrimaryServer1\SCCM-DP$
Volume in drive \\PrimaryServer1\SCCM-DP$ is Data
Volume Serial Number is 22F0-661B
Directory of \\PrimaryServer1\SCCM-DP$03/17/2014
03:33 PM <DIR> .03/17/2014 03:33 PM <DIR> .
04/01/2014 08:04 AM <DIR> SMSPKG
0 File(s) 0 bytes
3 Dir(s) 514,625,064,960 bytes free
===========================================
C:\Windows\system32>whoami
nt authority\system
C:\Windows\system32>dir
\\PrimaryServer1\SCCM-DP$
Access is denied.

Content Available on Distribution Points

Similar Messages

Maybe you are looking for