I had this same problem. Major screw up on F-Secure to be using these ports. I paid for Premium Support and they wouldn't even help me figure out what the problem was. They told me to change the ports for Policy Manager and then none of course none of my clients or servers could connect then. They were not helpful with this either. I finally figured out it was the World Wide Web Publishing Service, even though I couldn't tell by netstat that it was using or listening on port 80. I disabled that service and I was able to get back into the Policy Manager. In order to change the ports and keep my clients connected, I changed the port back to 80 and tried to distribute a policy telling the clients to use 85. That did not work. The policies would not update. So I've had to leave the WWW Publishing service turned off and leave the ports on 80, 8081, and 8080. Otherwise I would have had to reinstall to all clients, or manually change the port on all clients. Unbelievable. Policy Manager is turning out to be pretty buggy.
... View more
I've been using a trial key to demo Policy Manager and a bunch of clients. Now that we've bought a license, how can I push out the license to the clients? I'm not seeing a place in the policy settings for this. Also, is there a way I can export a package that already includes my new license? Or does this happen automatically once the license is in place in Policy Manager? thanks for the help!
... View more