Distribution point waiting for content

Hi all,
I have a problem with my secondary site distribution point where the applications don't seem to be replicating. I installed the role weeks ago and the applications are still sat on waiting for content. There are a lot of questions regarding this error but
they appear to relate to clients and not the DP itself. I have been over the config here
http://myitforum.com/cs2/blogs/cnackers/archive/2010/09/20/configuration-manager-configuring-server-2008-r2-for-site-systems.aspx and completed that, but it's been 24 hours since then and the DP is still sat on waiting for content. Any help would
be much appreciated.

The most effective way to troubleshoot the issue is to check the log files distmgr.log, PkgXferMgr.log and MSDPPRov.log at the remote distribution point.
Juke Chou
TechNet Community Support

Similar Messages

"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

Client machines waiting for content

Hi - I have deployed a couple of applications that never seem to deploy to clients
This does not happen with every application so I don't think its a problem with connectivity / communications anywhere.
My clients are pointing to the correct management points and site.
Application content has been successfully distributed to my distribution points
My Distribution Settings tab on the package is set to "Distribute the content for this package to refereed DP's" and to "Automatically download content when packages are assigned to DP's"
My Content Locations tab on the package has the correct distribution point
Distribution types content tab has the correct content location and deployment options is set to "Download content from DP's and run locally"
Distribution types Programs tab has the correct installation / uninstall parameters
Distribution types Detection Method is set
Distribution types user experience set to install for system and installation probably hidden. I have tried with different logon requirements and still get no where
Deployments Properties content shows the right DP
Deployment Properties Deployment Settings action Install and Purpose Required. Also checked is allow clients on a metered internet connection
Deployment scheduling based on client local time
Deployments User Experience set to display in software center and show all notifications
Commit changes at deadline or during maintenance window is set
Alerts is set to create a deployment alert when the threshold is higher than 0
Content is distributed and deployed to a valid machine collection with valid machines pointing to the right site
Monitoring > Deployments shows waiting for content
I can manually install the apps OK.

Please check the client log files for more information. For example log files like
execmgr.log, LocationServices.log and CAS.log.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

10035 Waiting for Content Error?

Hey guys was hoping for some help. Running SCCM 2012 R2 on SQL 2008 R2 CU6. I've been running SCCM since SMS 2003 so I'm not a total noob with it. It started with running 2012 (no SP1), it just broke out of nowhere. and stopped working.
I needed to fire off some Flash/Java updates so I loaded up my .bat files and deployed to my test environment. Every single client was stuck in Not Applicable/10035/Waiting For Content and would not move. I did my research and noticed several
hotfixes, SP1 for SCCM 2012, R2, SQL updates so I just decided to build up a new VM with the above new configuration and to my surprise the same error is still present to my test environment. Every single client, endpoint AV, everything connected with
the new server as I set configuration. Everything worked, clients all updated automatically to R2 CCM Version, no more critical component status, everything is butter except deploying applications. I have been running my .bat scripts for years
that I roll out to our clients to update flash. I know it's probably not the "correct" way of doing it but it's worked flawless for along time now. I can't really figure this out as logs are not showing any errors? I see the hotfixes
for my issue, but they don't apply to SCCM R2, just regular and SP1. Thanks for the help guys.

CAS.log are filled with this.
<![LOG[No matching DP Location found]LOG]!><time="17:04:22.833+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="7952" file="locationcontentrequest.cpp:618">
<![LOG[Location update from LS for content 57000006.1 and location request {73460019-3DCC-4049-8C82-5D16CA39C083}]LOG]!><time="18:04:22.904+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="4788" file="locationcontentrequest.cpp:597">
<![LOG[No matching DP Location found]LOG]!><time="18:04:22.904+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="4788" file="locationcontentrequest.cpp:618">
<![LOG[Location update from LS for content 57000006.1 and location request {73460019-3DCC-4049-8C82-5D16CA39C083}]LOG]!><time="19:04:23.069+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="3584" file="locationcontentrequest.cpp:597">
<![LOG[No matching DP Location found]LOG]!><time="19:04:23.069+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="3584" file="locationcontentrequest.cpp:618">
<![LOG[Failed to get DP locations from LS for content 57000006.1 and location request {73460019-3DCC-4049-8C82-5D16CA39C083}]LOG]!><time="20:04:23.227+300" date="01-24-2014" component="ContentAccess" context="" type="2" thread="5260" file="locationcontentrequest.cpp:690">
<![LOG[Releasing content request {73460019-3DCC-4049-8C82-5D16CA39C083}]LOG]!><time="20:04:23.281+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="8532" file="contentaccessservice.cpp:1861">
<![LOG[Canceling LS Job {00000000-0000-0000-0000-000000000000} for content 57000006.1]LOG]!><time="20:04:23.281+300" date="01-24-2014" component="ContentAccess" context="" type="1" thread="8532" file="locationcontentrequest.cpp:547">
<![LOG[CancelLocationRequestfailed]LOG]!><time="20:04:23.284+300" date="01-24-2014" component="ContentAccess" context="" type="3" thread="8532" file="locationcontentrequest.cpp:566">
<![LOG[Requesting content 57000006.1, size(KB) 821, under context System with priority Low]LOG]!><time="14:03:54.195+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="contentaccessservice.cpp:934">
<![LOG[Created and Sent Location Request '{10139BD8-BD60-497C-985D-54C84394B4E7}' for package 57000006]LOG]!><time="14:03:54.246+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="ccmpkglocation.cpp:84">
<![LOG[LS job {10139BD8-BD60-497C-985D-54C84394B4E7} submitted to get DP locations for content 57000006.1]LOG]!><time="14:03:54.246+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="locationcontentrequest.cpp:512">
<![LOG[Successfully created location request {A3D1AEF4-BA27-4FA2-84D7-BA86B6CC7EE2} for content 57000006.1]LOG]!><time="14:03:54.250+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="locationcontentrequest.cpp:530">
<![LOG[Location update from LS for content 57000006.1 and location request {A3D1AEF4-BA27-4FA2-84D7-BA86B6CC7EE2}]LOG]!><time="14:03:54.348+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="locationcontentrequest.cpp:597">
<![LOG[No matching DP Location found]LOG]!><time="14:03:54.348+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="8764" file="locationcontentrequest.cpp:618">
<![LOG[Location update from LS for content 57000006.1 and location request {A3D1AEF4-BA27-4FA2-84D7-BA86B6CC7EE2}]LOG]!><time="14:04:41.397+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="4412" file="locationcontentrequest.cpp:597">
<![LOG[No matching DP Location found]LOG]!><time="14:04:41.397+300" date="01-28-2014" component="ContentAccess" context="" type="1" thread="4412" file="locationcontentrequest.cpp:618">
Searching "No matching DP Location Found" is related to Boundaries? Nothing has changed in my boundaries and I do not configure by boundaries by anything advanced like Subnets, IPRanges, ect. It's just a simple active directory boundary?

Waiting for content

Hello,
Security updates are deployed by deployment management. I see machiens which are under "Downloading Updates" are still in the same state for more number of days.
I have restarted the smsagent service and observed that it is still under same "waiting for content" state in SCCM Client Center->Running Executions -> SMS/SCCM Jobs.
Please let me know how this can be resolved.
Regards,
Boopathi S

I would check DP are ok and updated on the site where machine looking for a content and its IIS logs for any error ?
Since its for patching did you checked your CBS store that its not corrupted etc.. the path is \\xxxx\c$\Windows\Logs\CBS\CBS.LOG and you can see the error if its corrupted and it may get resolved by a system restore to a previous working state. i
haven't tried this restore as my machines are not having that option as its customized while doing build image.
I would just test on one machine with the above steps and will see how it goes and decide future course of action for it.
Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

Deployment Status In Progress - Waiting for Content?

Hi,
I have an application (language pack) I am trying to deploy to some clients and only about 78 out of 200 have a status of success. The number hasn't improved in the last few days. What would be the best way to get the rest installed? Can I delete the deployment
and deploy again? If I do this, will it uninstall it on the successful clients? Or is there a way to re-deploy? It just seems to be not improving at all and would like to get it pushed out asap. Thank you very much

Have you added an IPv6 boundary for the Direct Access clients and added to a boundary group for content location?
See how to do that here:
http://www.gerryhampsoncm.blogspot.ie/2014/10/configmgr-2012-sccm-2012-all-boundary.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Distribution point and failed content

Hi I have SCCM 2012 R2 and 5 Pull DPs now when I distribute Packages to these Pull DPs some times i can see some package didn't distributed and giving me failed content but when I redistribute it i can see the SCCM Start to redistribute the package from
the failed point which is will resume the distribution and to be honest this very coll specifically for big packages but on some packages starting from 0,
to be honest I'm Confused when the SCCM will resume and when will not.
Thanks,
Ahmed Ali

Hi,
There might be many files in a package. I think when one file transfers failed, it starts from the failed file.
I suggest you use BITSAdmin to monitor BITS jobs in the transfer queue.
http://msdn.microsoft.com/en-us/library/aa362813(v=vs.85).aspx
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.

Wait for content thumbnails to refresh listener. How?

Hi
On Bridge CS6 I have some action (any action...) to run over a group of image thumbnails but, when I select a folder with images, Bridge build in first place the cache for the contents of that folder opened for the first time.
I want to make a condition to run my action IF the refresh is finished.
>> f refhesh is over >> run my action
>> and if not over wait until is really over
(I have also to think if the user selects another folder before my first action is over on the previous folder: may be could warn to wait...?? or queue it to run it next...)

I have realized that this event 'loaded' is called:
Once: when a folder is browsed for the first time getting new thumbnails (children). It is called after the built of all thumbnails, but before (and if) generating full previews;
Twice: when a folder was browsed before and is select again. In this case, the event is called at the moment that the folder is clicked and again a second time, after the built of all thumbnails, but before (and if) generating full previews;
This was a bit trouble to solve, but my aim was to call only once a function with this to behaviors every time I select or reselect a folder.
I have used setEnv to personalise a bollean variable with the name of the folder (in my case it never repeats). The function runs only once with each folder.

How to wait for content rendering in a Div

How can i check the status of a div content, whether the content is completely rendered or not?
sekhar

I have already tried WaitForControlReady Method. The thing is the content inside div is dynamic. We can't compare it using any of InnerText , HelpText or DisplayText property.
This Div tag consists of spans and child div's. The Content of these child elements consists MathJax content(For displaying mathematical eqtns/graphs etc..).
sekhar

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.

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

Determine Distribution Point For PC Naming

I'm trying to automate the PC Naming process during Windows 7 Deployment with MDT 2010 and SCCM 2012.
I need to add a 3-character site code to the PC name, but I'm not sure how to get it. Ideally, I would like to identify the distribution point used for OSD, and then based on that distribution point, create a custom MDT variable that is the site code,
and later add that custom variable to a string that will be the name.
For example, if a computer was imaged using DP01.mycomapny.local as a distribution point, then MDT customsettings.ini would set the custom variable
SiteCode = HOU and later in the CustomSettings.ini I would have
OSDComputerName = %SiteCode%-%SerialNumber%
My problem is that I don't know how to determine the distribution point from inside customsettings.ini. Any help would be greatly appreciated.

You can use TS Variable "OSDComputerName" for defining new computer name and "_SMSTSSiteCode" for determining Site Code. What are you want to use as SerialNumber?
Vladimir Zelenov | http://systemcenter4all.wordpress.com
Bob - thanks for your reply. I know that OSDComputerName is that variable I want to set. I also know that
SerialNumber is another builtin MDT variable that will pull the machine's serial from the BIOS. I can't use
_SMSTSSiteCode because I need the distribution point name, not the SCCM site code. When I mentioned that I need to add a 3-character site code to the value for OSDComputerName, I didn't mean the SCCM site. The site code I need to
use is an in-house site code for geographic areas. Our SCCM infrastructure has 1 parent site that services multiple geogrpahic areas within a small region, with each geographic area having its own unique company site code. Also, each company site
has a distribution point, not a secondary site server. So, I need to be able to identify the distrubtion point that is handling the OS deployment, not the SCCM site.

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 untrusted domain - Not acknowledging Network Access Account (FYI)

Hello!
Scenario
Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
errors indicate that this software can'tbe downloaded.
In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
Problem
The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
were reinstalled. A fresh install didn't detect the NAA.
Solution
After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
domains aren't approved automatically (by default).
In this case something as simple as an Approving the client fixed these issues.
The DataTransferService.log highlights the issue:
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="1" thread="3136" file="dtsjob.cpp:3501">
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
<![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="3" thread="3136" file="dtsjob.cpp:3513">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.h:166">
<![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
{38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download. Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="2" thread="3136" file="dtsjob.cpp:3652">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.cpp:3205">
<![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
thread="3136" file="netaccessaccount.cpp:288">
<![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
type="1" thread="3136" file="netaccessaccount.cpp:858">
<![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
(0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
The IIS server logs u_ex150219.log captures the request:
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 2 5 1509 2
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 4
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 3
2 x Domains: DomainA and DomainX
- Single domain forests
- No trusts between domains/forests
DomainA\PRIMARYSERVER
- Primary Site Server, MP, DP, IIS, all roles
DomainX\DP1
- Distribution Point, IIS, etc
- CCM client installed

Based on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
Jason | http://blog.configmgrftw.com | @jasonsandys

Is the distribution point role required on an SCCM 2012 site server?

I am wondering if the distribution point role is required on an SCCM 2012 site server.
We have an installation of SCCM 2012 SP1 with a site server, and two remote DPs.
I would like to remove the DP role from the site server, and stand up another server (2012) at the same location, making it a DP and also have it hold the WSUS content.
I was successful in creating the DP on the new server. I distributed all of our packages to the new server.
I then removed the packages from the DP on the site server, and removed the DP role from the site server.
After making these changes, we lost the ability to deploy packages, either from the new DP server, or from the previously existing DPs that were at other locations.
Deployment status in the SCCM console showed that clients were “waiting for content”.
I found that adding the DP role back to the site server, and distributing packages to it corrected the problem.
Deployment resumed after doing that. Is it necessary to have packages on a DP on the site server?
We want to virtualize the server, and would like to make it as small as possible to facility restores.

Hi,
Have you checked the log file distmgr.log? Maybe it can give us some clues.
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.

Distribution point waiting for content

Similar Messages

Maybe you are looking for