hey
are you plannin to add an option to install multiple policies in paralel ?
like on R77.30 that you could choose multiple FW (for the same policy) but here i am talking about the ability to choose multiple policies.
hey
are you plannin to add an option to install multiple policies in paralel ?
like on R77.30 that you could choose multiple FW (for the same policy) but here i am talking about the ability to choose multiple policies.
Also in R80.10 you are able to select which out of your GWs will get the selected policy installed. If this unsupported feature is important, you could change to MDM and use different CMAs.
Hi,
You can make different policy package same as R77.30 and also you can select the gateways to which this policy can be applied. You can set Policy targets.
That is true - but you can not install a second policy before the first install has ended...
+1 to this recommendation. We do regular policy pushes every week where the same policies get installed and it would be nice to be able to push them in parallel to save time.
Hi,
Indeed this is a limitation. One workaround is if you are a Multi-Domain user, you can log into your MDS domain, right-click a domain and choose "install policy". Here you can select multiple gateways are linked to different policies, and press OK. It will execute their policy installations right after another. You will not need to wait for one job to complete in order to launch the next one.
Another workaround would be utilizing the install-policy API command and create a custom policy installer scheduler which waits for one policy installation to complete and then runs the next policy installation.
Hi,
Indeed this is a limitation. One workaround is if you are a Multi-Domain user, you can log into your MDS domain, right-click a domain and choose "install policy". Here you can select multiple gateways are linked to different policies, and press OK. It will execute their policy installations right after another. You will not need to wait for one job to complete in order to launch the next one.
Another workaround would be utilizing the install-policy API command and create a custom policy installer scheduler which waits for one policy installation to complete and then runs the next policy installation.