{"id":1099,"date":"2026-04-03T16:31:36","date_gmt":"2026-04-03T08:31:36","guid":{"rendered":"https:\/\/www.nsecsoft.com\/en\/?p=1099"},"modified":"2026-04-03T16:31:36","modified_gmt":"2026-04-03T08:31:36","slug":"smart-snap","status":"publish","type":"post","link":"https:\/\/www.nsecsoft.com\/en\/course\/smart-snap.html","title":{"rendered":"How to Enable Scheduled Screenshots on Employee Endpoints"},"content":{"rendered":"

<\/p>\n

Smart Screenshot<\/strong> is suitable for periodic evidence collection of endpoint desktop activity, helping administrators continuously understand screen changes for key roles during designated time periods and within designated business applications. Compared with continuous screen recording, scheduled screenshots usually consume less storage and are better suited to long-term trace retention, spot checks at key moments, and behavioral traceability.<\/p>\n

Before officially issuing the strategy, it is recommended to clarify the screenshot goal first. If you want to continuously track the usage of a certain type of business system, you can limit the scope of screenshots to specified programs through Process Information<\/strong>; if you only want to retain screen evidence during working hours, you should plan the Screenshot Interval<\/strong>, Scheduled Screenshot<\/strong> and Ignore Conditions<\/strong> in advance to avoid the accumulation of invalid data caused by excessive collection.<\/p>\n

Policy configuration steps<\/strong><\/h4>\n

1. Switch to the Data Security<\/strong> tab in the Ping32 Management Console and click Policy<\/strong> \u2192 Screen Security<\/strong> (as shown below).<\/p>\n

2. Enable the Smart Screenshot<\/strong> slider, and then click Parameter Settings<\/strong> (as shown below).<\/p>\n

\"\"<\/p>\n

3. Click the \u201c+\u201d<\/strong> button to configure parameters. The key parameters are explained as follows:<\/p>\n

Process Information<\/strong>: The client will only trigger screenshots when running the specified process.<\/p>\n

Trigger conditions<\/strong>:<\/p>\n

    \n
  • Always<\/strong>: Always take screenshots<\/li>\n
  • Only in foreground<\/strong>: Take a screenshot only when the specified process is in the foreground<\/li>\n<\/ul>\n

    Ignore conditions<\/strong>: You can choose to lock the screen or stop taking screenshots when the mouse is idle for a specified time to save disk space.<\/p>\n

    Screenshot Interval<\/strong>: How many seconds to capture a picture.<\/p>\n

    Scheduled screenshot<\/strong>: Take a screenshot at a specified time point. This parameter is independent of the Screenshot Interval.<\/p>\n

      \n
    • Example: If you set the “Screenshot Interval” to 3 seconds, and also set “Screenshot at 11:00”, then a picture will be captured at 11:00, even if the time is not at the 3-second interval.<\/li>\n<\/ul>\n

      Save Location<\/strong>: It is strongly recommended to select Server<\/strong>.<\/p>\n

        \n
      • Screenshots and other data are stored in the object storage directory: \\Ping32\\Server\\DataDB\\s3\\ping32\\smartsnap<\/code><\/li>\n<\/ul>\n

        Smart Analysis<\/strong>: Used to Unified Search and retrieve text information in Smart Screenshots, requiring a separate OCR engine deployment.<\/p>\n

        4. After the screenshot policy is set, confirm that the policy application endpoint is correct, and then click Apply<\/strong> to officially deliver the Smart Screenshot<\/strong> policy to the target endpoint.<\/p>\n

        Parameter configuration ideas<\/strong><\/h4>\n

        In actual use, the combination of screenshot interval<\/strong> and scheduled screenshot<\/strong> determines the collection granularity. If the administrator needs to continuously observe the operation process, the screenshot interval<\/strong> can be shortened appropriately; if more attention is paid to certain fixed time points, such as shift handover, settlement, batch export and other time nodes, scheduled screenshots<\/strong> can be used to supplement this to ensure that screenshots are retained at critical moments.<\/p>\n

        Ignore condition<\/strong> Mainly used to reduce the proportion of invalid screenshots. For endpoints that are online for a long time but are not continuously operated, it is recommended to control the lock screen, mouse idle time and other conditions to reduce the impact on server storage and retrieval efficiency. If you plan to subsequently retrieve screenshot text through Unified Search<\/strong>, you should also plan the OCR environment simultaneously and enable intelligent analysis<\/strong> in the strategy.<\/p>\n

        Effect verification and implementation suggestions<\/strong><\/h4>\n

        After the policy takes effect, it is recommended to open the controlled business program on the test endpoint, wait for a complete collection cycle, and then go to Data Security<\/strong> \u2192 Screen Record<\/strong> to check whether the Smart Screenshot record of the corresponding endpoint has been generated. If the screenshot is not generated as expected, you should first check the following items: whether the process matches, whether the endpoint meets the trigger conditions, whether it is filtered by ignored conditions, and whether the policy has been correctly applied to the target endpoint.<\/p>\n

          \n
        • If the enterprise wants to view records stably even offline, it is recommended to set the save location<\/strong> to server<\/strong>.<\/li>\n
        • If you need to retrieve the text information in the screenshot by keyword later, you need to complete the deployment of the OCR server in advance and enable Intelligent Analysis<\/strong> in the screenshot policy.<\/li>\n
        • If the screenshot object is a high-frequency operation position, it is recommended to test run it on a small scale first, and then adjust the collection interval based on the number of screenshots and the retrieval effect.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

          Smart Screenshot is suitable for periodic evidence coll […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[69],"class_list":["post-1099","post","type-post","status-publish","format-standard","hentry","category-course","tag-kb-type-guide"],"_links":{"self":[{"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/posts\/1099","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/comments?post=1099"}],"version-history":[{"count":1,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/posts\/1099\/revisions"}],"predecessor-version":[{"id":1101,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/posts\/1099\/revisions\/1101"}],"wp:attachment":[{"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/media?parent=1099"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/categories?post=1099"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nsecsoft.com\/en\/wp-json\/wp\/v2\/tags?post=1099"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}