Hi, I have an SCCM 2007 R3 SP2 environment. All of my DP's are BITS Enabled. I have a Branch DP located behind a firewall to manage some SCCM clients. Internal SCCM Site Server + SUP + Bit's DP all on one server ---- Firewall (with TCP 80 and 8530 open to int sccm server) ---- branch DP When I updated packages on the DP's above, the package works just fine. however, if I update the same package, the package is updated on the Bits enabled DP but never gets updated on the Branch DP. I'm starting to suspect that maybe port 445 is needed to be opened between the BDP and the DP? Any thoughts?

Branch DP is almost lika a ordinary client, it needs to download the machine policy before it knows to download the package. Have your branch dp downloaded the machine policys?

Yes, I believe that they have. In fact you can force a lookup on the Branch DP... by clicking "branch dp maintenance task.. I have six seperate environments where this is setup... and they all act the same: initial package installs fine on DP... but an update to the package never is made available on the branch dp.

Is the segment that the BDP is on NATed also?Jason | http://blog.configmgrftw.com

no, none nat

again.. generally the original package update completes fine to the Branch DP. It's the next time the package gets updated where the problem is noticed. Here are some example errors, that I see on the site system status for the Branch DP:

Message Id = 10053 ID=10025 for the above errors.

Here is an example of the BranchDP.log error: Checking provisioning status for package = EY000825, version = 2. Download failed for content CTM job {8F951D99-3B44-4000-AE6D-C7ABC8581FD0}, error 0x80004004 CPDPJob::DownloadError PeerDPAgent 8/1/2012 10:05:41 AM 912 (0x0390) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of PDPDownloadFailEvent { ClientID = "GUID:477C2191-CA01-4FF3-84CF-39C0B760B099"; DateTime = "20120801140541.331000+000"; MachineName = "SCCMBranchDPserver"; PackageID = "EY000087"; ProcessID = 2376; SiteCode = "XXX"; SourceVersion = 60; ThreadID = 912; };

I found that RDC was not enabled on my Branch DP's... I have enabled this now... waiting to see if anything changes in my error states.