Packages with .ASPX and .ASMX files cannot be distributed to Configuration Manager 2007 Branch Distribution Points

Article ID: 2516319 - View products that this article applies to.
Expand all | Collapse all

Symptoms

When pushing a software distribution package with .ASPX or .ASMX files to a Branch Distribution Point (BDP), the transfer fails.  Transfers via SMB to the same BDPs work fine.  You may also see BITS jobs failing with transient errors.

Cause

This occurs because .ASPX and .ASMX files are dynamic content and BITS will not download dynamic content.  This is by design.  Since a BDP will only use BITS to get the package from the Distribution Point it fails.

ref: http://msdn.microsoft.com/en-us/library/aa362846(v=VS.85).aspx

Resolution

Other than not including ASPX or ASMX files in your packages, as a workaround you can pre-stage the content on the BDP manually.

1. If one does not already exist, create an SMSPKG<driveletter>$ directory and share on the branch distribution point.

2. Using a standard distribution point as the original source for the package, copy the packages into the SMSPKG<driveletter>$ directory.

3. On the central site where your packages exist, select your package and chose properties. On the Distribution Settings tab make sure that the Administrator manually copies this package to branch distribution points to checked.

4. Next use the package wizard to add a DP to the package. In this case you will be selecting the Branch DP.

5. Give it a few minutes to allow the new policy to flow down from the central site to the Branch DP Clients parent site.

6. Force the client to request new Machine Policy or allow it to request Machine policy on its own. Once policy is received it will take 2 minutes before the policy is applied to this client.

7. On the branch distribution point computer, double-click Configuration Manager in Control Panel.

8. On the Actions tab, select Branch Distribution Point Maintenance Task and then click Initiate Action

*Note: When creating an SMSPKG<driveletter>$ directory and share, the <driveletter> is the relevant drive on the branch distribution point. For example, SMSPKGC$ would be the directory and share created on drive C of the branch distribution point.

More Information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2516319 - Last Review: March 8, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft System Center Configuration Manager 2007
  • Microsoft System Center Configuration Manager 2007 R2
  • Microsoft System Center Configuration Manager 2007 R3
  • Microsoft System Center Configuration Manager 2007 Service Pack 1
  • Microsoft System Center Configuration Manager 2007 Service Pack 2
Keywords: 
KB2516319

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com