I definitely remember that "Malformed or incomplete XML" error from my
PullDP experiment.
Good news, then...


On Fri, Sep 20, 2013 at 11:40 AM, Schwan, Phil <
[email protected]> wrote:

>  Not sure what specifically you’re seeing, but possibly addressed by
> newly available CU3?****
>
> ** **
>
> http://support.microsoft.com/kb/2882125/en-us****
>
> ** **
>
> *Software Distribution*
>
> This cumulative update fixes the following issues:****
>
> **·         ***A pull-distribution point may crash when it tries to
> download packages. The PullDP.log stops recording any activity when this
> issue occurs.*
>
> **·         ***Packages migrated from Configuration Manager 2007 to 2012
> Configuration Manager may not download to pull-distribution points unless
> the Update Distribution Points wizard is used. *Error messages that
> resemble the following are logged in the PullDP.log file:****
>
> CPullDPPkgJob::LoadJobFromXML() could not load any content jobs from XML!
> CPullDPPkgJob::LoadJobFromXML() could not fully load job! Malformed or
> incomplete XML. Job has failed.****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Todd Hemsell
> *Sent:* Friday, September 20, 2013 1:24 PM
>
> *To:* [email protected]
> *Subject:* Re: [mssms] PullDP****
>
>  ** **
>
> they stay installed for about an hour, then commit suicide. You remember
> when WSUS used to uninstall itself? yea, it is like that.****
>
> ** **
>
> On Fri, Sep 20, 2013 at 11:29 AM, Trevor Sullivan <[email protected]>
> wrote:****
>
>  I’m working on a project right now where I’m recommending them in the
> design. It’s a small-medium size environment with about 12 distribution
> points and only one Primary Site. There don’t seem to be any limitations
> with using Pull DPs for PXE booting, UEFI PXE booting, or anything like
> that. From what I can tell, it appears that the main benefit of using the
> Pull DP is to take the load off of the PkgXferManager component on the
> Primary Site. It’s essentially a client that’s pulling content from the
> “source DP” using BITS. In fact, based on the TechNet documentation, it is
> using the CCMFramework component of the ConfigMgr client.****
>
>  ****
>
> To manage the transfer of content, pull-distribution points use the
> CCMFramework component of the Configuration Manager client software. This
> framework is installed by the Pulldp.msi when you configure the
> distribution point to be a pull-distribution point and does not require
> that the Configuration Manager client be installed. After the
> pull-distribution point installs, the CCMExec service on the distribution
> point computer must be operational for the pull-distribution point to
> function. When the pull-distribution point transfers content, it transfers
> content by using Background Intelligent Transfer Service (BITS) and logs
> its operation in the datatransferservice.log and the pulldp.log on the
> distribution point computer.****
>
>  ****
>
> *Planning for Content Management in Configuration Manager* -
> http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_PlanPullDps
> ****
>
>  ****
>
> Cheers,****
>
> Trevor Sullivan****
>
>  ****
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Todd Hemsell
> *Sent:* Friday, September 20, 2013 10:16 AM
> *To:* [email protected]
> *Subject:* [mssms] PullDP****
>
>  ****
>
> Is anyone using PullDP's?****
>
>  ****
>
> What are your experiences?****
>
>  ****
>
> ** **
>
>  ** **
>
> ** **
>  ------------------------------
>
>
> PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it
> are privileged and confidential and intended solely for the use of the
> individual or entity to whom they are addressed. If you have received this
> email in error please notify the sender. If you are not the named addressee
> you should not disseminate, distribute or copy this e-mail or any of its
> attachments.****
>
>  ****
>
>



Reply via email to