Distribution Point re-deployment best practice?

We've been having some issue with a distribution point due to the client being "magically" uninstalled. I removed the Distribution Point site system role and a day later (machine is in Europe with a rather slow connection) the Component server role has been removed as well.  Client reinstalled cleanly and she's reporting beautifully now.

My question is now that both of those roles have been removed and the client install a success, would there be any reason to delete the site system altogether and subsequently re-adding it, for cleanup or whatever reason - this was just a distribution point, nothing more.  Or should we be OK to simply re-add the Distribution Point role and move on?

Any insight would be much appreciated,

Shane

June 5th, 2014 11:01am

I've never seen any issue with getting client installed on a DP server. I would surely readd the DP role. You need to further troubleshoot with the help of client log file like ccmsetup.log. This will provide you some information about why the client got uninstalled.
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2014 11:12am

The use of the word "Magically" was sarcasm, we know when/why the client was uninstalled... simple mistake.

My main question was more from a best practice perspective.  With the Distro Point role removed and subsequently the Component server role, would there be any reason to completely remove the Site system from the list of Servers and Site System Roles listing?  I can easily re-add the Distro point role, just want to see if anyone has had any experience with this.

June 5th, 2014 11:27am

The ConfigMgr client has nothing to do with the DP role itself. They are totally unrelated.
Did I get that right? The client was uninstalled and therefore you removed to DP role?
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2014 11:50am

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?

June 5th, 2014 12:33pm

Once the secondary site was removed from the site server at Site A, the DP at Site B started having issues.

"Site"? In terms of what? Geographical site? AD site? ConfigMgr site? Was the DP a site system for that secondary site?
Again: the client and ConfigMgr roles are unrelated.

Free Windows Admin Tool Kit Click here and download it now
June 5th, 2014 12:42pm

Site = Physical location as well as AD Site.  Each of our "Sites" have a local DP.  This was the case with SCCM 2007 as well.

I understand the client and ConfigMgr roles are unrelated.  It just seems odd the client will install on any machine in our environment with the exception of Servers that have been added as site systems and the DP role implemented.  I am still questioning some things about the initial setup of 2012 as I was rather new to the environment build.  I have looked at the all of our distribution points and about half are missing the client and ALL show the errors mentioned earlier. 

June 5th, 2014 12:47pm

http://social.technet.microsoft.com/Forums/en-US/3329a401-77fd-4990-bc19-a75c7d7f5602/installing-the-sccm-2012-client-onto-a-pulldp?forum=configmanagerdeployment<o:p></o:p>

An example of the same issue we are experiencing.  Ours, while not a PullDP, is showing the same error with the client install.  Unfortunately, removal of the NO_SMS_ON_DRIVE.SMS and being an R2 environment, we are still experiencing the problem.<o:p></o:p>

Free Windows Admin Tool Kit Click here and download it now
June 5th, 2014 4:21pm

Yes, I know this is an old post, Im cleaning up old post, did you get this fixed, if so what was the solution?

March 22nd, 2015 9:46pm

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

Free Windows Admin Tool Kit Click here and download it now
July 25th, 2015 9:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics