System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager Software Distribution > Problems distributing a package with a "." as the first character of a folder name to an XP BDP
Ask a questionAsk a question
 

AnswerProblems distributing a package with a "." as the first character of a folder name to an XP BDP

  • Thursday, November 05, 2009 10:54 AMBill Bradley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We have had instances in the past with issues distributing packages (from source to distribution points) that have non-alphanumeric characters in folder or file names.  Often, they will distribute fine to other site servers, and server-class distribution points (all servers being Server 2008), but not to XP BDP's.  We have gone through a laborious process to add multiple exclusions into McAfee VSE 8.5 w/SP8, have edited the IIS files to prevent blocking certain extensions, and, are aware and have applied the SCCM (I think, maybe a Windows) hotfix for files with a "&" in the name.  Besides the "&" and "." (as a first character, at least), we had a problem with a "-" as a middle character in a folder name.

    Is there just a plain issue with non-alphanumeric characters, and, is it not fully an SCCM problem, but is a Windows, Windows XP, or IIS, BITS, or, another component problem?  And if so, is there a hotfix, or succession of hotfixes or reghacks or settings file changes, to get completely rid of this issue with using BDP's?

    In many cases, we are at the mercy of the vendor as to the naming of files and folders, and can't always readily change the name.

    Thanks.

Answers

  • Thursday, November 05, 2009 2:44 PMJason SandysMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Also remember that BDPs aquire their content (by default) using BITS which is driven by IIS. IIS 7 has many security restrictions out the box that could prevent BITS from distributing certains types of files or files with certain names. This is controlled by the requestFiltering section of the applicationHost.config. The cofiguring a site system for Windows 2008 article (http://technet.microsoft.com/en-us/library/cc431377.aspx) discusses how to correct this issue.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

All Replies

  • Thursday, November 05, 2009 10:59 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I just tested creating a folder named ".test" using Win7. It's possible using "md .test", but not using windows explorer. It's definitely not a ConfigMgr issue in my eyes.
  • Thursday, November 05, 2009 11:31 AMBill Bradley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for the quick reply.  Don't know that all of this IS SCCM, for sure, but something in the mechanism used to pass the package source files down is blocking them--or, at least having an issue with them.

    Can you create it on Server 2008?  This package does distribute (replicate?  not sure of the exact term) to distribution points and site servers, but, not to ANY BDP, including a few Server 2008 ones.
  • Thursday, November 05, 2009 2:44 PMJason SandysMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Also remember that BDPs aquire their content (by default) using BITS which is driven by IIS. IIS 7 has many security restrictions out the box that could prevent BITS from distributing certains types of files or files with certain names. This is controlled by the requestFiltering section of the applicationHost.config. The cofiguring a site system for Windows 2008 article (http://technet.microsoft.com/en-us/library/cc431377.aspx) discusses how to correct this issue.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
  • Thursday, November 05, 2009 6:09 PMBill Bradley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks, Jason.  We were VERY aware of this, as, we had some packages with files with the .bin extension, and, they were being blocked.  We also found other extensions being blocked (.config), and, had to remove them.  I've seen posts on this forum where all or a lot of the blocked extensions are being removed.

    It's...amazing...how many strange extensions are being used in deployment these days...<G>

    Thanks, again!