And since it failed it rolled back. I blamed a few coworkers for sabotaging me before we learned the cause. I bite my tongue these days
Sent from my iPhone On Sep 20, 2013, at 1:31 PM, Kim Oppalfens <[email protected]> wrote: > Cm07, backup of cm site triggered msi repair on wsus installs. The msi was > badly written so that a repair usually failed. > > Sent from my Windows Phone > From: Trevor Sullivan > Sent: 20/09/2013 19:41 > To: [email protected] > Subject: RE: [mssms] PullDP > > I don’t remember that. How long ago did that happen? My memory is somewhat > volatile. > > Cheers, > Trevor Sullivan > > From: [email protected] [mailto:[email protected]] > On Behalf Of Todd Hemsell > Sent: Friday, September 20, 2013 12: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? > > > > > >
