Client push not working after ports open

Question

Client push is enabled on primary server

– source to wsus server – opened 80/443/8530/8531

– source to primary server – opened 10123/80/443

-Primary server to source – opened 135/445

-Source to primary server – opened dynamic ports (49152 to 65535)

Finally I am not able to do client push to azure VM

Any other ports needs to be opened ???

solved 0
ram kumar 8 months 2020-08-19T06:45:23+05:30 9 Answers 71 views Beginner 0

Answers ( 9 )

    0
    2020-08-22T17:48:54+05:30

    No response hence closing the thread

    0
    2020-08-19T16:40:58+05:30

    If only 445 opened from client – client can access admin$.
    Am I right ?

    0
    2020-08-19T16:38:51+05:30

    It’s mentioned “between” in the guide
    Is that mean bidirectional open

    0
    2020-08-19T16:37:31+05:30

    Is 445 bidirectional or unidirectional

    0
    2020-08-19T15:24:25+05:30

    – Admin$ share should present
    – Admin$ access on windows 10

    Can you guide how to enable this both.

    0
    2020-08-19T15:01:40+05:30

    How to enable access for admin$ on client machine ?

    Do we need to enable separate port ?

    Admin$ not working from client machine I hope because of this I have client push issue

  1. Hello – I don’t think so… the following are the ports required.

    SMB between the site server and the client computer. — 445
    RPC endpoint mapper between the site server and the client computer. 135 135
    RPC dynamic ports between the site server and the client computer. — 49152-65535
    Hypertext Transfer Protocol (HTTP) from the client computer to a management point when the connection is over HTTP. — 80/443

    But what is the error your are getting … they are many other prerequisites needed for client push that I explained in https://www.anoopcnair.com/install-configmgr-client-using-client-push-installation-method-sccm/

    Have you already checked?

    Best answer

Leave an answer

Sorry, you do not have a permission to answer to this question .