2nd update server

I am running version 11 of policy manager on my main site, i have a 2nd site with over 100 machines on a slow connection.

is it possible to setup a second update server on that site so it downloads just the updates and distributes them to that site.

if so where would i get the info to set this up please

Find more posts tagged with

Comments

JohannesL

Hi, AndyB!

Did any of the solutions above answer your question?

If it didnt solve the issue could you explain further about the problem/question?

If it solved the problem, It would be great if you could select which answer/solution that did solve the issue by "select it as solution" so that we know and so that if someone that have this problem/question can easly see the solution.

Chu

Yes! Its possible!

Its works fine, we have a lot of customers using PMS as PMP. They using PMS as PMP over Windows Server 2012, because the PMP dont support Windows Server 2012.

All you need is install Policy Manager Server in another server and in the Policy Manager Server (main), put in the:

Settings -> Automatic Update -> Use HTTP proxy as User-defined

Settings -> Automatic Update -> HTTP proxy address

Put the HTTP://IP of the another Policy Manager Server (where act as Policy Manager Proxy)

Distribute the policy.

The hosts where have this configuration, will get the vaccines from this new Policy Manager Server acting as Policy Manager Proxy.

Vad

Hello AndyB,

I can propose one more solution for you:

Setting up a secondary AUS instance

One way to reduce the load on PMS is to use a separate AUS installation to serve anti-virus database updates for the clients. Unfortunately, current version of PM does not support such configuration as such, but one can use a simple workaround to achieve similar effect.

To make use of a separate AUS instance, follow this instruction:

Set up a separate instance of PMS the usual way. Don't worry about the PMS configuration - only AUS will be used in this installation.
Using the AUA user interface, make sure AUS can download and install latest database updates:

3. From PMC connected to the primary PMS, change the policy settings 'Use HTTP Proxy' }} and {{'HTTP Proxy address' to make use of the new AUS instance:

This setting can be applied to individual hosts as well as to the entire domain structure.

Having new policies distributed, the hosts to which new settings were applied will connect to the secondary AUS, treating it as an HTTP proxy.

Best regards,

Vad

Costas-Inter

Also don't forget to the 'neighborcast' feature for those machines on the remote session.

See

http://download.f-secure.com/webclub/pm11_adminguide_eng.pdf

page 82

Costas

Ben

Hello AndyB,

You could implement a Policy Manager Proxy.

You'll find information ann documentation about the product on this page.