SCCM Distribtuion Point on 2019 Server Fails to Install

asked 2020-09-29T14:02:59.547+00:00
David Jenkins 941 Reputation points

I'm trying to install a Distribution Point on a 2019 Server. I keep getting this error although I have placed the site server in the Admin group. We're on version 1910.

Distribution Manager failed to install distribution point ...
Possible cause: Distribution Manager does not have sufficient rights to the computer.
Solution: Verify that the site server computer account is an administrator on the distribution point computer.

I've removed the install and tried again. It never gets there. I can get the to admin shares just fine.

Is there anything about 2019 server that doesn't work with SCCM?

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
23,696 questions
No comments
{count} votes

Accepted answer
  1. answered 2020-09-30T03:03:36.613+00:00
    Amandayou-MSFT 10,941 Reputation points

    Hi @David Jenkins ,

    We could check if there is something wrong with the WAN optimizer, the issue could be resolved once we removed it.

    If this way could not work, we could check them in following steps:
    a. We could check if the SCCMADMIN account is used and it does have the access as a domain admin as well the local administrator group local DP
    b. IIS installation has been checked during the DP configuration. Is it supposed to install and configure IIS?
    c. Could antivirus and firewall be closed on the DP?

    Here is the similar post we could refer to:
    Distribution Point creation failed. possible cause : distribution manager does not have the sufficient access right to the computer

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

1 additional answer

Sort by: Most helpful
  1. answered 2020-09-29T15:22:16.38+00:00
    Jason Sandys 30,881 Reputation points Microsoft Employee

    Have you reviewed distmgr.log on the primary site server?

    Have you validated that the computer account for the primary site server is a local admin on the target system?