Scheduled reporting requirements when using Policy Manager for Linux - F-Secure Community
<main> <article class="userContent"> <p> </p>Scheduled reporting requirements when using Policy Manager for Linux <p>The new version of Web Reporting introduced in Policy Manager 15.00 requires a running Chromium instance for scheduled reports to work. </p> <p>Windows systems can handle the Chromium instance automatically, but Linux systems require some additional actions from the administrator. </p> <p><strong>Note:</strong> The delivery of scheduled reports does not work with Red Hat Enterprise Linux 6, SuSE Linux Enterprise Server 11, and SuSE Linux Enterprise Desktop 11 distributions. </p> <p>To configure your Linux system to support scheduled reporting: </p> <ol><li> Check the following list of Linux distributions and install the required dependencies if necessary. Run the command that applies to your Linux distribution: <ul><li>Ubuntu Server or Debian: <p><code class="code codeInline" spellcheck="false" tabindex="0">sudo apt install libgtk-3-0 libxss1 libpangocairo-1.0 libasound2 libgbm1 libcups2 libxi6 libxdamage1 libxcursor1 libcomposite1 libxcb-dri3-0 libxcb1 libx11-xcb1 libatk-bridge2.0-0 libatk1.0-0 libxrandr2 libnss3</code> </p> <strong>Note:</strong> Do not forget to run <code class="code codeInline" spellcheck="false" tabindex="0">sudo apt-get install -f</code> to fix dependencies that your previous installations missed. </li> <li>CentOS minimal installations: <p><code class="code codeInline" spellcheck="false" tabindex="0">sudo yum install libX11 libXcomposite libXcursor libXdamage libXext libXi libXtst atk at-spi2-atk cups-libs libXScrnSaver libXrandr libgbm pango gtk3</code> </p> </li> <li>SLES without X: <p><code class="code codeInline" spellcheck="false" tabindex="0">sudo zypper install mozilla-nss libXss1</code> </p> </li> </ul></li> <li> Run the following command to check that rendering to PDF is working: <p><code class="code codeInline" spellcheck="false" tabindex="0"> ./chrome --headless --disable-gpu --no-sandbox --print-to-pdf https://google.com</code> </p> </li> <li> Run the following command to check that the DevTools port information is printed: <p><code class="code codeInline" spellcheck="false" tabindex="0"> ./chrome --headless --disable-gpu --no-sandbox --remote-debugging-port=0 --ignore-certificate-errors </code> </p> </li> </ol> </article> </main>