cancel
Showing results for 
Search instead for 
Did you mean: 

Ports used by PMC push installation?

Highlighted
Supporter

Ports used by PMC push installation?

Hi, 

 

 

which ports I need to open to get push installation working on a remote server?

1 ACCEPTED SOLUTION

Accepted Solutions
Moderator

Re: Ports used by PMC push installation?

Hello @hyvokar 

 

Policy Manager Console uses TCP port 135 for remote procedure call (RPC) access and port 445 for network and file sharing access. The target computer and Policy Manager Console both use Policy Manager Server's host port to report the installation result.

 

Please have a look of smilar this thread to find check list for push installation to be working.

3 REPLIES 3
Moderator

Re: Ports used by PMC push installation?

Hello @hyvokar 

 

Policy Manager Console uses TCP port 135 for remote procedure call (RPC) access and port 445 for network and file sharing access. The target computer and Policy Manager Console both use Policy Manager Server's host port to report the installation result.

 

Please have a look of smilar this thread to find check list for push installation to be working.

Superuser

Re: Ports used by PMC push installation?

As in a domain setup those ports are usually open I think you are in a small environment?!
If so, you have no GPO to disable that and you need to go to each host anyway. Thus using an exported MSI-package is the faster option.

OTOH if you think about pushing an UPDATE to an already running F-Secure installation you better look into a policy based update. PUSH is only useful for first-time-rollout.
M.

Matthias
----------
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de

Superuser

Re: Ports used by PMC push installation?

Hello,

 

I think the FSCS version 14 .MSI-based distribution method is less practical then FSCS12/13 used to be, as keycode cannot be inserted. I think F-Secure should work on a method which creates a properly structured MSI file, without the need for end-user tweaking.

 

On the other hand, the Push-based method is difficult to authorize in the Windows 10 era: remote registry service must be running, admin$ network share must be available, classic sharing model must be enabled (these need a regedit), firewall ports must be open, user account password reqs must be met, etc.

 

Best regards: Tamas Feher, Hungary.