To answer the specific question, Yes, the distribution point in question had the CCM Client removed inadvertently, and then the DP role removed. It was originally
a member of a set of distribution points in Europe which were pointed at a secondary site when created. We removed the secondary site and the management point along with it due to our environment - less than 5,000 systems world wide. Once the secondary
site was removed from the site server at Site A, the DP at Site B started having issues. This is where the client being removed came into play. I asked to have the DP removed and re-added. A co-worker was under the impression the client would
need to be reinstalled as well since the secondary site was removed. I then tried to reinstall the client with no luck. SO I removed the DP and was able to install the client without a hitch.
Well, after looking further, it appears several of our sites housing Distro points do not have the client installed in the Site System server but
do show up as functional distribution points. Each server has entries in the install logs - ccmsetup.log and client.msi.log - indicating errors during install. I just tried to install the client on a distribution point I distributed content to
last week and successfully deployed a package to several machines in that location. It is failing to install the client locally as well.
Error from the ccmsetup.log:
<![LOG[MSI: Setup was unable to compile the file UpdatesAgent.mof
The error code is 80041002]LOG]!><time="07:50:01.552+240" date="06-05-2014" component="ccmsetup" context="" type="3" thread="4292" file="msiutil.cpp:300">
<![LOG[MSI: Action 7:50:01: Rollback. Rolling back action:]LOG]!><time="07:50:01.649+240" date="06-05-2014" component="ccmsetup" context="" type="0" thread="4292"
file="msiutil.cpp:314">
<![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterWmiMofFile.
ErrorMessages:
Setup was unable to compile the file UpdatesAgent.mof
The error code is 80041002
]LOG]!><time="07:50:05.717+240" date="06-05-2014" component="ccmsetup" context="" type="3" thread="4292" file="msiutil.cpp:872">
<![LOG[Next retry in 120 minute(s)...]LOG]!><time="07:50:05.765+240" date="06-05-2014" component="ccmsetup" context="" type="0" thread="4292" file="ccmsetup.cpp:8498">
Error from the client.msi.log:
MSI (s) (5C:B0) [07:50:05:701]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (5C:B0) [07:50:05:701]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
Not much information on these errors has panned out. Have spoken with a colleague who had similar issues in a lab environment and his only recourse was to remove the role, install the client, the re-add the role. This is where my "Best Practice"
question came into play: If all roles are removed, is there any reason to delete the site system and re-add it prior to re-adding the DP role?