Suspend upload of packages to a distribution point
Imagine this situation:
I've created a new distribution point and added it to a distribution point group with a lot of content (packages) assigned to the group. I discover right after SCCM starts to upload packages to the new DP, that the network usage to that office reaches its
limit, and instead of using Rate limits, I would like to stop the package transfer for a while until the weekend comes. If I want to suspend the upload of packages to a distribution point for a day or two, will it be OK to remove the new DP from the DP group?
Freddy
You can certainly remove the DP from the group, but I doubt that that would stop the flow of content. It may also cause the content to be deployed, then removed, and then redeployed when you add it again.
Why not just temporarily change the rate limits or scheduling window and then change it back later?
Jason | http://blog.configmgrftw.com | @jasonsandys
Similar Messages
-
Unable to create package shares on distribution points
For any OSD packages in our environment (like images, driver packages, etc) I always check the option "Copy the content in this package to a package share on distribution points", so that we are able to run content directly from the DP's in a task
sequence instead of downloading it first to clients. But I've noticed now that for any new package I create, the package shares aren't being created thus my OSD tasks are failing due to missing content. When I check the copy content option for a new driver
package and monitor the distmgr.log, here is what I see:
Copying package DEV0007F to the package share location \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F on the server ["Display=\\hou-sccmdp03.network.local\"]MSWNET:["SMS_SITE=YYC"]\\hou-sccmdp03.network.local\ SMS_DISTRIBUTION_MANAGER
4/3/2013 11:02:35 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:35 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:40 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:45 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:50 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:55 AM 2156 (0x086C)
Failed to set security on \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F for package DEV0007F SMS_DISTRIBUTION_MANAGER 4/3/2013 11:03:00 AM 2156 (0x086C)
That same sequence of errors is repeated for every distribution point we have. I checked the sharing permissions on the SMSPGKE$ and SMSSIG$ folders on the DP and everything looks correct. I only started noticing this issue after our SP1 upgrade, but I can't
find anything from Microsoft saying this is a known bug or how to fix it. This is also affecting new distribution points that we created after the SP1 upgrade, so I don't believe going down the remove/reinstall of all the DP's route will work. Any suggestions?Copying package DEV0007F to the package share location \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F on the server ["Display=\\hou-sccmdp03.network.local\"]MSWNET:["SMS_SITE=YYC"]\\hou-sccmdp03.network.local\ SMS_DISTRIBUTION_MANAGER
4/3/2013 11:02:35 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:35 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:40 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:45 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:50 AM 2156 (0x086C)
SetObjectSecurity failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/3/2013 11:02:55 AM 2156 (0x086C)
Failed to set security on \\hou-sccmdp03.network.local\SMSPKGE$\DEV0007F for package DEV0007F SMS_DISTRIBUTION_MANAGER 4/3/2013 11:03:00 AM 2156 (0x086C)
I've seen similar errors after installing SP1:
Failed to set share security on share \\DP.domain.tld\SMSSIG$. Error = 5
Failed to set access security on share SMSSIG$ on server DP.domain.tld
DPConnection::Disconnect: Revert to self
Cannot find or create the signature share.
Solution for that case: Use the computer account instead of a site system installation account:
That might fix it.
Torsten Meringer | http://www.mssccmfaq.de -
SCCM 2012r2 - Remove "invisible" packages/applications from Distribution Point
Hello alltogether,
I've encountered the following issue:
Our distribution points are displaying applications/packages as "In Progress - Waiting for Prestage content".
These packages doesn't exist anymore. Neither as prestage file nor in the config manager itself. We never tried to apply this package by using a prestage file because such a file never existed.
Even if I open the "content" tab of one distribution point, I can't find these packages in there.
The exact status of this package is the following:
Message: Distribution Content
Message Detail: Distribution Manager instructed Package Transfer manager to send Package "x" to distribution point "y".
Status Type: In Progress
I want to remove these "ghost" packages from the Distribution Status overview. Anyone has a clue how to accomplish this?
Thanks in advance!
Best Regards
FeyhHello,
thanks for your answer!
Unfortunately no, there is no information about these files.
Yesterday we installed a new one, extracted all of our prestage files on it and watched the status. The Packages weren't listed in the "Distribution Point Configuration Status".
After some time we added the new DP to our general DP-group where all of our packages/applications are assigned to. Now the "non-existing" packages are added with the "in Progress" status.
I had a look into "Distribution Point groups -> Our group -> properties -> content" but these packages aren't displayed in the list. Some of the packages are now in the "waiting for prestage content" state, others are staying with the "Detail will
be available after the server finishes proccessing ...".
We managed to remove one of the packages by deleting it from the database.
The following statement removed it from the Distribution status overview. However, we still are able to find the package in the database.
select * from SMSPackageswhere PkgID = 'P100003B'
DELETE from SMSPackages
where PkgID = 'P100003B'
Apparently the delete-statement affected 72 rows. But we are having no clue which. As long as we are not sure we killed anything important we are not going to do this with the other packages because it's the productive system. We can't reproduce this in our
test system... -
Package deployment to Distribution points
We have SCCM 2012 SP1 with 5 primaries, 23 secondaries and 80 distribution points around the globe. How does SCCM distribute packages to the DPs? Past practice has us distributing to the primaries first, then the secondaries
and then finally the DPs. The question was raised that the DPs get their content from which server? A team member and I have been unable to locate the information in the Tech-net library, does anyone know the answer or can
we get a link to where we may be able to locate the info ourselves?
Thanks.
I am hoping someone else can fill in some gaps for you, but I will give it a shot. The primary site server grabs the content from the content source and sends it to the DPs. This is one reason to plan out your source folder structure carefully.
There was some recent discussion on this here:
https://social.technet.microsoft.com/Forums/en-US/afa0a018-889a-46dd-866c-ee688899ace6/what-is-the-best-practice-for-package-source-locations?forum=configmanagerapps#ad772921-6f85-44c5-8250-7ca1aff6dc11
Jeff -
Remove package from Distribution Point
I have been fighting with an OS deployment for the last day. The log was showing it was unable to find the package p0100001 which was my boot image. I eventually got it working as I failed to configure my boundary correctly. But it got me wondering...
In SCCM 2007, it was pretty straight forward on how to remove packages from distribution points. But I still can't figure out how to remove a package, specifically a boot image, from a DP. I can view the distribution in the monitoring section and see the
package successfully deployed, but what if I wanted to remove that boot image from the DP? How is this done. I'm sure it's staring me in the face, but I'm missing it. Thanks!I realize this is an old post, but I am dealing with the same issue regarding the removal of deployment package contents from Distribution Points. After removing a Distribution Point from the Contents Locations tab on one of my Deployment Packages,
how long does it take for the deployment package to be removed from the distribution point. I have removed a large deployment package from a distribution point, but am not seeing any increase in the available free space.
Any help would be appreciated.
Muskie
Muskie -
Distribution Point install failure
Hi all,
In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers.
About two days ago I have done an inplace upgrade on one server to 2012 R2.
The upgrade went mostly without a hitch except for the SCCM DP.
The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content.
So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy...
I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log.
~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)>
~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)>
Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)>
~Processing 18.INS $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)>
~DPID 18 - NAL Path ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ , ServerName = [SERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
22:20:59.263-600><thread=7708 (0x1E1C)>
Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)>
~Created policy provider trigger for ID 18 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)>
DPConnection::Connect: For [SERVER NAME HERE], logged-on as rondo\sccmpush~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)>
Found notification for package 'RDO00002' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)>
Found notification for package 'RDO00003' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)>
Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)>
~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)>
~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)>
~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)>
~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)>
~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)>
Failed to find a valid drive on the distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)>
~Starting package processing thread, thread ID = 0x88 (136) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)>
DPConnection::Disconnect: For [SERVER NAME HERE], reverted to SYSTEM context~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)>
user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([SITE SERVER NAME HERE]) is submitting SDK changes from site(RDO) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)>
~Starting package processing thread, thread ID = 0x2B78 (11128) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)>
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128
(0x2B78)>
~Retrying package RDO00003 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)>
No action specified for the package RDO00003. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)>
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136
(0x88)>
~Retrying package RDO00002 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)>
No action specified for the package RDO00002. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)>
Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)>
Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)>
Thread Handle = 00000000000035C0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)>
Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)>
Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)>
The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)>
Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)>
~Failed to install DP files on the remote DP. Error code = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)>
~Drive E: is not valid. Error = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)>
STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER
NAME HERE]\" ISTR1="[SERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[SERVER
NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)>
~Will try again after 20 mins ... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)>
Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)>
Thread Handle = 00000000000029C8 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)>
Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)>
DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)>
DP thread with thread handle 00000000000035C0 and thread ID 9852 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)>
The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)>
Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)>
DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)>
DP thread with thread handle 00000000000029C8 and thread ID 10028 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)>
~Package RDO00002 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)>
The package and/or program properties for package RDO00002 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)>
~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)>
~SourceVersion (3) of package RDO00002. SourceVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136
(0x88)>
~Failed to process package RDO00002 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)>
~Package RDO00003 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)>
The package and/or program properties for package RDO00003 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)>
~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)>
~SourceVersion (1) of package RDO00003. SourceVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
22:21:06.797-600><thread=11128 (0x2B78)>
~Failed to process package RDO00003 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)>
Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)>
~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)>
~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)>
~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)>
~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)>
~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)>
~Sleep 1826 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)>
Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)>
~Sleep 1821 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)>
Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)>
~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)>
~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)>
~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)>
So I have two questions,
How can I fix this and how do I prevent it from happening to the remainder?
Thank you all in advance.
Daniel.The server does not appear at all
You really need to give more information so we can help you.
What about the logs, are you getting the same errors after making all the changes? please upload the full log to SkyDrive or any other place.
Did you reboot this DP\DC?
Can you successfully ping from the primary to DP and back?
Do you have access from primary to C$ on that DP?
What account did you choose for installation?
Did you choose to install IIS?
If IIS was installed, try to remove it and let DP installation install it automatically.
Confirm that PowerShell 3.0 is installed.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
Hi Idan,
I will go through and reply to each of the suggestions you have made below;
1. The log that was attached was the full log. I cleared the log prior to setting up the DP and copied the contents into this forum after it has stopped.
2. Yes I had rebooted, Many times.
3. Yes I can successfully ping either way.
4. Yes I can access the C$ share on the DP from the Primary
5. I have tried both the PC account and a service account that is part of the domain admins group and also added to the local admins via a net command
6. Yes I did choose to install IIS and I had already tried uninstalling IIS and running the install again.
7. as above
8. Yes Powershell 3.0 is installed
PS C:\Users\admindg> $PSVersionTable
Name Value
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.34014
BuildVersion 6.3.9600.16394
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2
Thank you for all your suggestions and I hope that the information that I have provided is sufficient to draw a better picture of our environment.
Regards,
Daniel -
SCCM 2012 Distribution Point not working properly on a Windows 2012 Server
I have an SCCM SP1 site running on a Server 2008 R2 machine. I had a couple of distribution points, also running on 2008 machines. These served as DPs and PXE boot points. I had no problems with these.
I resently added a Server 2012 machine, and set it up as a DP, with a PXE boot point. The servers is part of a boundary group containing about 1500 clients. I distributed all of packages that are included in my main task sequence, and am able
to PXE boot, and image machines successfully.
However, I am having problems deploying other packages and Windows update packages from this DP. It seems like I am only able to deploy packages that have the "Copy the content in the package to a package share on distribution points" enabled.
If this is not enabled, the client will get the deployment policy, but will never download the package. The "In Progress" tab for the deployment status will just say "Waiting for content".
I have checked the rereqs for IIS on the Server 2012 DP, also checked the firewall. Everything that I see seems to be OK. Are there other things that I can check to determine why this DP isn't working right?Hello,
According to the following description, this behavior would be normal:
If you configured the option Run program from distribution point on the
Distribution Points page of the Deploy Software Wizard, do not clear the option
Copy the content in this package to a package share on distribution points, because this will make the package unavailable to run from distribution points.
http://technet.microsoft.com/en-in/library/gg682178.aspx -
SCCM 2012 R2 Distribution Point Installs but does not send packet.
I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got.
The computer account is in the Administrators group and Admin Domains;
Already checked the WMI with Wbemtest;
I uninstalled and installed the DP again;
Below is the log, changed the name to contoso by issues of customer privacy.
Sleep 928 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:00:07 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:12:13 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Thread Handle = 0000000000002330 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5264 (0x1490)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
DP thread with thread handle 0000000000002330 and thread ID 5264 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Failed to process package LAA00003 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:46 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
2528 (0x09E0)
Sleep 1824 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5736 (0x1668)
Thread Handle = 0000000000002A50 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with thread handle 0000000000002A50 and thread ID 5736 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Failed to process package LAA00004 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:42:18 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5112 (0x13F8)
Thread Handle = 0000000000001CF0 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5012 (0x1394)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
Failed to process package LAA00003 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
4576 (0x11E0)
Thread Handle = 00000000000025F8 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with thread handle 00000000000025F8 and thread ID 4576 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
5996 (0x176C)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30 5996 (0x176C)
Failed to process package LAA00004 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014
00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 5292 (0x14AC)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Processing status update for package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32
4008 (0x0FA8)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Sleep 1048 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Sleep 1043 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Processing status update for package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 1038 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleep 1033 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:28 5292 (0x14AC)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 5292 (0x14AC)
Found notification for package 'LAA00003' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Found notification for package 'LAA00004' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 2528 (0x09E0)
Starting package processing thread, thread ID = 0x388 (904) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34
2528 (0x09E0)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
Lucas Simoes MCTSNo (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 13/08/2014 23:57:10
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
13/08/2014 23:57:10 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0xBE8) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0x3B4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 3048 (0x0BE8)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 948 (0x03B4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45 3048 (0x0BE8)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
3048 (0x0BE8)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52 948 (0x03B4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
948 (0x03B4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:52 4004 (0x0FA4)
Created sending thread (Thread ID = 0x1680) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:52
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Created sending thread (Thread ID = 0x18A4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:16 5760 (0x1680)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:17 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43 6308 (0x18A4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
6308 (0x18A4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50 5760 (0x1680)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
5760 (0x1680)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0xF28) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0x11D0) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 3880 (0x0F28)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 4560 (0x11D0)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:16 3880 (0x0F28)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 3880 (0x0F28)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
3880 (0x0F28)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4560 (0x11D0)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 01:19:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 01:19:34 4004 (0x0FA4)
No (more) send requests found to process.
SMS_PACKAGE_TRANSFER_MANAG
Lucas Simoes Rezende MCP, MCTS , ITIL V3 -
Hi
1. Is there a way I can control the bandwith between 2 sites regarding the distirbution point syncronization
Requirement:
Pirmary Site --> Send packages to standard distribution point (server DP) "Link is 3 mb bandwith" and I want to limit 50kb the transfer.
Workstation afftectd in the remote location 100
2. What is you recommend for type of DP to be used (standard DP or secondary site with DP)
Please advise
RobertHi
You can go to Site Database --> Site Setting(of the primary Site) --> Go to addresses properties of the address you created there is a tab of rate limit you can punch in the rate at what you want the data transfer to be.
This can only be done for site to site communication.
In your case Primary site to secondary site.
Better you replicate package in out of office hours, rather then throtling the bandwidth to certain limit.
3MB bandwidth is not a too good bandwidth for 100 clients where package size is large. Monthly patching package will be minimum of 200 MB size for Security updates itself. I suggest you should go for secondary site with DP role created which will also help
in data transfer(rrporting data) collectively to primary site via Proxy management point role. Also for patching install WSUS console your secondary site Install SUP role then you need to configure it as Active SUP and configure it to sync from upstream
server that will be your Primary site to get the patch information.
Kindly mark this as Answere or helpfull as suitable to you so other can take advantage of similar situation
Based on the question, there are no secondary sites thus most of your answer does not apply to whats been asked and is thus not helpful.
Jason | http://blog.configmgrftw.com -
When I check "Access content directly from the distribution point" for the "Apply Operating System" task in my OSD Task Sequence, I get the failed error 0x80070002 at the step when running the sequence from WinPE.
If I uncheck it, I don't get that error or have any problems.
I've ensured that in the properties of my OS Image in the Data Access that "Copy the content in this package to a package share on distribution points" is checked, and that I Updated DPs.
Am I missing any other settings?
The reason I'm trying to do this is because the "Download" speed of the WIM is incredibly slow. I already installed a hotfix (KB2905002) that fixed this for my Dell systems, but it's not speeding it up for another computer model I'm imaging in
the same way. The Dell computers, after I installed the server hotfix, will downloading the .wim file at 1% per second. However the HP thin clients I'm imaging download at about 1% every 15 seconds, and I'm not sure if that's due to their hardware or what.Hi,
The error means file not found. So you need to check the smsts.log to see which DP it is accessing, then go to that DP to check the Shared Folder smspkg to make sure the file is there.
For the download performance issue, there are various reasons. You need to check your Switch bandiwidth and if the NIC driver is up to date. If downloading locally is slow, Accessing directly could be slow too.
Juke Chou
TechNet Community Support -
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. -
RBAC: grant rights to update distribution point
Hi,
I have created a specific group which has all rights to manage specific items within SCCM 2012 console.
Everything works fine BUT the distribution of packages to the distribution point, this is empty when distributing the packge.
Rights on Distribution point are: Read, Copy to Distribution Point.
Please advise.
J.
Jan Hoedt"Site: Read" is most likely missing.
Torsten Meringer | http://www.mssccmfaq.de -
Content is being distributed to the distribution point - stuck at "In Progress"
I have Windows Updates due to be installed on all international machines tonight at 12 AM, and our main distribution point gets the files just fine. Our international sccm server, however, is not.
I'm get the "In progress" on the Content View under Monitoring, but it has been sitting like that for over 8 hours. I know there are a ton of logs in the C:\Program Files\SMS_CCM\Logs location that are constantly updating.
Is there a log in there I can attach or show to help determine what's going on? There are so many logs. However, this is a very serious issue, and I don't know what's going on. It worked just fine, then last months worked, except for the fact that after
about a week, it would say that the content "Failed" on the second sccm distribution point. And now, this month's updates are stuck on "In Progress" on copying it over.
Please let me know what I can look into, as soon as possible.
Thank you!Alright, so this is what it's looking like:
PkgXferMgr.log has a ton of these:
======== Finished Processing Cycle ( 12/13/2014 6:20:56 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
Checking for sending capacity. Used 0 out of 15.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.696+420><thread=3632 (0xE30)>
COutbox::TakeNextToSend(pszSiteCode) $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
No (more) send requests found to process.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.698+420><thread=3632 (0xE30)>
======== Starting Processing Cycle ( 12/13/2014 7:20:56 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
======== Processing Jobs ======== $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
Job count is 0. $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.588+420><thread=3628 (0xE2C)>
======== Finished Processing Cycle ( 12/13/2014 7:21:06 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
Checking for sending capacity. Used 0 out of 15.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
COutbox::TakeNextToSend(pszSiteCode) $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
No (more) send requests found to process.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
======== Starting Processing Cycle ( 12/13/2014 8:21:06 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
======== Processing Jobs ======== $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
Job count is 0. $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.774+420><thread=3628 (0xE2C)>
======== Finished Processing Cycle ( 12/13/2014 8:21:16 AM Mountain Standard Time) ========~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
Sleeping for maximum 3600 seconds.~ $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
distmgr.log:
Start adding package to server ["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.455+420><thread=2464 (0x9A0)>
Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
Thread Handle = 00000000000010C0 $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=4932 (0x1344)>
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.484+420><thread=4932 (0x1344)>
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.485 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="US10008A" AID1=404 AVAL1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
$$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.485+420><thread=4932 (0x1344)>
~The contents for the package US10008A hasn't arrived from site US1 yet, will retry later. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932 (0x1344)>
STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.486 2014 ISTR0="US10008A" ISTR1="US1" ISTR2="JP1"
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A" $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932
(0x1344)>
DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
DP thread with thread handle 00000000000010C0 and thread ID 4932 ended. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
~Package US10008A does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.999+420><thread=2464 (0x9A0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=US10008A, Version=3, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.000+420><thread=2464 (0x9A0)>
~StoredPkgVersion (0) of package US10008A. StoredPkgVersion in database is 0. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
~SourceVersion (3) of package US10008A. SourceVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=2464 GMTDATE=Sat Dec 13 06:23:09.096 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="US10008A"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A" $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.096+420><thread=2464
(0x9A0)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.097+420><thread=2464 (0x9A0)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:12.865+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.394+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.395+420><thread=3348 (0xD14)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.409+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.410+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:53:17.953+420><thread=3992 (0xF98)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:00:08.191+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:14:38.368+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:23:23.041+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:53:28.130+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.375+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.376+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:14:38.544+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:23:33.227+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:53:38.332+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.577+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.579+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:14:38.734+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:23:43.428+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:53:48.526+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.783+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.785+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:14:38.926+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:23:53.624+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:53:58.722+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.985+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.986+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:14:39.116+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:24:03.820+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:54:09.080+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.393+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.394+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:14:39.521+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:24:14.228+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:54:19.325+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.612+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.613+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:14:39.713+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:24:24.423+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:54:29.521+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.817+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.819+420><thread=3348 (0xD14)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:14:39.905+420><thread=3988 (0xF94)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:24:34.623+420><thread=3992 (0xF98)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:54:39.721+420><thread=3992 (0xF98)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.021+420><thread=3348 (0xD14)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.023+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:35.600+420><thread=3992 (0xF98)>
Found package properties updated notification for package 'US10008A' $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.602+420><thread=3348 (0xD14)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.604+420><thread=3992 (0xF98)>
Found notification for package 'US10008A' $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.606+420><thread=3348 (0xD14)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.624+420><thread=3348 (0xD14)> -
SCCM 2012 SP1 Distribution points not updating
The package that holds my MS updates is not updating on my distribution points ever since I upgraded to SP1. If I remove the package from the distribution points and then add it back it will work fine. This is happening to me every I add updates to this
package. Below is part of the smsdpprov.log file from one of my distro points.
[C90][Thu 02/14/2013 11:03:51]:Content 'f16906f8-d1d4-44df-8cf7-35dd7428893a' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:55]:Content '1ebc4751-063f-46dd-a7ae-096cce3545dc' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:56]:Content 'b2903470-59e0-4d89-a1a5-808b58c9fd4e' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:58]:Content 'f058ee07-a66e-4bdf-8a53-7cc30affe333' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:00]:Content '03546ec3-2613-46ce-bf0c-a6064149f2c6' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:03]:Content '7492e432-b69c-478c-8c7b-7c2396302eb4' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:05]:Content '995a1a82-6d7c-4fb6-9e1b-8cfac070b787' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:06]:Content 'a0a2a75d-beab-49ca-96e5-e03afa98dc8f' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:08]:Content '21061204-1d54-4262-bc90-cf5922191940' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:11]:Content 'ce9e07ad-1467-4da5-bf03-8c7013743d34' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:14]:MoveFile failed for \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f.ENS00006.temp to \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f
[C90][Thu 02/14/2013 11:04:14]:FileRename failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:CContentDefinition::Finalize failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:Failed to finalize content '6178f7ae-a640-4e04-a851-abd13239a50f' for package 'ENS00006'. Error code: 0X80070005I've got the same issue. When I look at the smsdpprov.log on the distribution point, this is what I see.
[EB0][Thu 10/31/2013 08:39:08]:Content '0a3fe62c-58ce-47c7-b635-e23407515ecb' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:Content '809b4727-78b3-48bd-85ca-f2fdcf668297' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:MoveFile failed for
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93.ONB0007A.temp to
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93
[EB0][Thu 10/31/2013 08:39:08]:FileRename failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:CContentDefinition::Finalize failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:Failed to finalize content '5263454e-e3de-49e5-a077-48dba0eefe93' for package 'ONB0007A'. Error code: 0X800700B7
If I reboot the DP, then the package gets updated. I'd like to figure out how to make this not happen :) -
Failed to Update Distribution Point
I have an interesting issue with distribution point updating a deployment package. I have ADRs that run for AV definition updates. The rules run, add to an existing deployment package and update distribution points. This works great for
about a month at a time. After that, I have to delete the package and recreate it. I can try to update DPs, use Powershell to update, remove all DPs and add them again as if it were a new distribution, but none of those work. Does anyone
else experience this or have seen it in the past? The error I'm getting is the 80070003 in Package Transfer Manager. Note, this happens every 4-5 weeks and I've experienced it now for the 3rd time. Thanks in advance.
Best, Jacob I'm a PC.0x80070003 = "The system cannot find the path specified."
Make sure your deployment package where you download definitions is configured properly and accessible.
Is the source folder of the package on shared storage or saved locally on SCCM server?
What release of CM12 are you on?
I would also recommend looking at A/V exclusions for SCCM server:
http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx
http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012
Maybe you are looking for
-
How can I change the settings of an external hard drive?
I have a 250-GB external hard drive connected to my Mac mini, whose files and folders I can´t delete as it shows up as a read-only disk. According to the Mac help, I can use the files on a disk by clicking on the "Get Info" label and selecting "Ignor
-
Is there a way to totally disable Genius on iTunes 11?
I don't use Genius Mixes and I am not interested by its music, apps and movie suggestions ; and it takes too much processing power and time to gather information about my library and deliver the results. So really, on my Windows machine it is very mu
-
AV cable AVC-DC400 capabilities
I have the Powershot A1400 and i am wondering if the Canon compatible AVC-DC400 AV cable will allow me to live view my realtime movie recording on my TV in real time, or is it only capable of playing back already recorded files. The problem i have i
-
Can i copy an entire text conversation somehow to print?
I wouldl like to be able to copy an entire text conversation dating back to the past year; is there some way to do this?
-
Oracle version 9.2.0.1. I've got a "before" update trigger that fires whenever I change an existing value in the table but it doesn't fire when I delete a value or add a value that had previously been empty. It feels like I'm missing something that's