Page 1 of 1

HowTo install EssentialPIM Pro Business on Win 2016 server

Posted: Wed Feb 19, 2020 5:30 pm
by Castaldini
Hi, i would like to test EssentialPIM Pro Business for a customer for a probable selling . It has a virtualized Win Server 2016 in a Hyper-V host, but i've not found any :oops: HowTo or similar procedure . It should be enough if someone could suggest some helpfull link or some topic , maybe i coudl redefine my search.Thanks a lot
Claudio

Re: HowTo install EssentialPIM Pro Business on Win 2016 server

Posted: Fri Feb 21, 2020 10:18 pm
by Max
Hello,

installing EPIM Business on virtualized Win Server should not be much different from installing EPIM on Windows.
Just install normally and follow this guide to connect to it: https://www.essentialpim.com/help/conne ... verhhh.htm
You may also need to set up some port forwarding:

Code: Select all

Following ports need to be open to allow EssentialPIM clients to communicate to the server:
- on Server machine for fbserver.exe:
      - incoming: 3050 and 3051
      - outgoing : whole range (fbserver uses random range of ports to communicate events)
- on Client machine for EssentialPIM.exe:
      - incoming: whole range
      - outgoing: 3050 and 3051

Re: HowTo install EssentialPIM Pro Business on Win 2016 server

Posted: Tue Mar 10, 2020 3:50 pm
by Castaldini
Dear Maxim, i wish to thank you for your helpfull answer. In the weeks to come i'll install and test . Please forgive my delay in answering but, i'm italian and the situation is far to be "normal" at moment, not as dramatic as it seems, but far to be normal. Regarding ports to open: you mean both UDP & TCP i suppose ? Thanks,
Claudio

Re: HowTo install EssentialPIM Pro Business on Win 2016 server

Posted: Tue Mar 10, 2020 10:23 pm
by Max
Yes, both UDP and TCP protocols.

Re: HowTo install EssentialPIM Pro Business on Win 2016 server

Posted: Tue Oct 06, 2020 10:52 am
by DierkO
Now it works in my network too.

Suggestion: Please add this little information to your network setup guide:

- on Server machine for fbserver.exe:
- incoming: 3050 and 3051 (TCP and UDP)
- outgoing : whole range (fbserver uses random range of ports to communicate events)

I defined two separate rules (one for TCP and one for UDP) - and then it rocks :-)