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.

Similar Messages

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

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.

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.

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

Prestaging Content on Pull DP temporarily

Hi,
I've read below in the MS documentation that a Pull DP configured for Prestaged Content does not Pull from a source DP:
The allow prestaged content configuration for a distribution point overrides the pull-distribution point
configuration. A pull-distribution point that is configured for prestaged content waits for the content. It does not pull content from source distribution point, and, like a standard distribution point that has the prestage content configuration, does not
receive content from the site server.
My question is: Once I have prestaged my content onto the Pull DP can I remove the checkbox that enables the Pull DP for Prestaged Content and have the Pull DP revert back to pulling packages from its designated source DPs?
In other words, once a Pull DP is selected for Prestaged Content, and the prestaged content has been distributed, can the Pull DP's configuration be reversed by unchecking the Allow Prestaged Content checkbox? Does this allow the Pull DP to return to normal
Pull DP activities by pulling packages over the network from its Source DPs?
Thanks!
Grant

Thank you Torsten. One quick follow-on question:
I've read this in the docs as well:
When the distribution point is configured as a pull-distribution point, do not enable the distribution
point for prestaged content. The
prestage content configuration for a distribution point overrides the pull-distribution point configuration. A pull-distribution point that is configured
for prestaged content does not pull content from source distribution point and does not receive content from the site server.
Just wanted to be sure that this also means that if we deploy a large number of Pull DPs, and then check the box to allow Prestaged content, then import our content, then uncheck the box enabling Prestaged Content that the Pull DPs will go back to acting
normally and pulling from their Source DPs.
Thanks again,
Grant

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

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

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

Problems with Distribution Points, "in Progress", etc

I have two SCCM 2012 R2 networks. They have similar problems with DPs. Each network has two servers and each server has a DP. Server01 is site server and primary DP on each network.
1) On Server01 on both networks in "DP Configuration Status" the icon is the upward green arrow (which I think in "In Progress") and in the details tab a weekly forced reboot package says "starting to process content" on NetworkA
and "processing content for site server" for NetworkB and for status they both say "In Progress". Is this because it a weekly recurring package?
2) On Server02 for NetworkB I have two "failed to distribute content" messages and neither has details available. On message is a week 5 days old. Pkgxfrmgr.log only has errors about "pulldpqueryresult failed to execute wmi query...".
3) On Server02 for NetworkA I have two "failed to update package" messages about updating Server02. The only errors in pkgxfrmgr.log are "pulldpquery failed".
4) On NetworkA I mistakenly had checked "enable prestaged content" and later turned it off. Now I have a bunch of hung "In Progress" messages about Server02 needing content manually prestaged. How can I kill these messages?
Help much appreciated.
Ben JohnsonWY

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?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

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.

Problem with option: enable this distribution point for prestaged content

Hi, for past few days I have been focused on application deployment with SCCM 2012 R2 (I am learning SCCM 2012 R2 reading books, watching video trainings . . .). Having followed allong book Mastering System Center 2012 R2 Configuration Manager I also did
deployment of Microsoft Office 2013, Adobe Reader 11, Foxit Reader 4.2 and Notepad ++ to test collection containing one Windows 7 computer. In one of examples prestaged content file is created for Foxit Reader application. In order to do so, if I am
right, option Enable this distribution point for prestaged content
has to be checked on distribution point and I did that.
Problem is that I noticed deployment of any application to test collection failed every time - system waits for prestaged content file if this option is selected. Then I have to delete deployment of given application, application itself, deselect option
Enable this distribution point for prestaged content and create app, distribute it to DP and deploy to test collection - then everything works well.
To make things worse, having deselect option Enable this distribution point for prestaged content (I did it yesterday and I checked that several times) this morning I checked again and this option is selected again. What might be the cause
of this behaviour? I expected this option to be deselected - this is weird to say at least.

When you enable the option "Enable this distribution
point for prestaged content" on a DP, it causes newly created applications/packages to default to "Manually copy the content in this package to the distribution point"... This would then cause the deployments on the clients to remain
at 'waiting for content' - unless if you manually prestage the content, as this option requires it.
If you enable the option "Enable this distribution
point for prestaged content" on the DP, but want to automatically have CM distribute the content, then configure the app/package to do so,
before distributing the content: Distribution Settings tab > Prestaged distribution point settings > Automatically download content when packages are assign to distribution points.

"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

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

Enable PreStaged content on a distribution point.

Similar Messages

Maybe you are looking for