Tuesday, July 1, 2014

Installing remote distribution point failed with 0x80041001

Last week I installed multiple remote distribution points on Windows Server 2008 R2 systems. The installation went to be fine, but no files were replicated on disk. This because of multiple distribution errors, which can be found in the distmgr.log:
-CSendFileAction::AddFile failed; 0x80041001
-CSendFileAction::SendFiles failed; 0x80041001
 
 
I did choose "Install and configure IIS if required by Configuration Manager" during installation, but IIS was installed already on servers. I did install BITS on servers also, because this seems to be needed (installation can be failing otherwise). Strange thing, because BITS is no prerequisite at all? What I did NOT however is installing RDC as a prerequisite. Therefore files couldn't be replicated after all.

Note: With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS.
 
Note: The Remote Differential Compression (RDC) feature is a set of application programming interfaces (APIs) that applications can use to determine if a set of files have changed, and if so, to detect which portions of the files contain the changes. RDC detects insertions, removals, and rearrangements of data in files, which enables an application to replicate only the changed portions of a file. This is useful when replicating files over a limited-bandwidth network such as a wide area network (WAN) connection.
 
Let's have a look for all prerequisites also, for a distribution point you need: 
  • Application Development (IIS)
    • ISAPI Extensions
  • Security (IIS)
    • Windows Authentication
  • IIS 6 Management Compatibility (IIS)
    • IIS 6 Metabase Compatibility
    • IIS 6 WMI Compatibility
  • BITS (feature)
  • RDC (feature)

Source: Supported Configurations for Configuration Manager

No comments:

Post a Comment