Activate Ping32
First, this is an activation tutorial for Ping32, let's go!
First, this is an activation tutorial for Ping32, let's go!
Before using Ping32, let's first familiarize ourselves with the operation flow of the Ping32 Policy Manager and create a simple policy. Taking the website auditing policy as an example, the operation steps are as follows: 1. Access Ping32 DashboardFirst, open the Ping32 Dashboard, click the “Internet Usage” menu, and then select the “Policies” button. 2.
Before deploying the Ping32 endpoint agent, be sure to confirm the following items. Improper configuration may cause the endpoint agent installation to fail, or the endpoint agent may be installed but unable to stably connect to the server, resulting in problems such as multiple endpoints going offline simultaneously. Generate endpoint agent installer 1. Enter the
This article explains how to uninstall the Ping32 endpoint agent, authorization recycling, and data retention considerations. Depending on the operation and maintenance goals, you can choose: Uninstall/remove endpoint from server side Uninstall locally from endpoint agent Recommendation: If audit traceability, compliance retention or evidence collection requirements are involved, please carefully select operations such as "clean
This article provides server-side and endpoint agent-side checking methods to confirm whether the Ping32 endpoint agent has been successfully installed, whether the service is running normally, and whether it has established a connection with the server and is online. Server side confirmation method (recommended to check first) After the endpoint agent is installed normally and
After the endpoint agent is installed for the first time, it runs in background silent mode by default (no pop-ups, no interruptions, no tray icons) to ensure that users' daily use is not affected. When enabling capabilities that require interaction or status prompts with the user, the endpoint agent will automatically display a tray icon
Endpoint Agent connection parameters are important configuration information for establishing communication between the endpoint agent and the server. The connection parameters can be set to the server internal/external network IP, private domain name or public domain name. In actual applications, appropriate connection parameters should be selected based on deployment and access requirements to ensure normal
Server-side push endpoint agent upgrade Note: Endpoint Agent upgrade requires the corresponding version of the update.cab file, which needs to be provided by contacting the vendor. Upload the upgrade package 1. Open the Ping32 Management Console 2. Click More -> Endpoint Update 3. Click Add -> Next -> Select the update.cab file 4. Click Next
Ping32 supports modifying the endpoint name through Management Console modification or endpoint agent user independent modification to meet the needs of different scenarios for unified operation and maintenance management and personalized endpoint identification. Ping32 Management Console modification: The administrator can modify the endpoint name directly in the Management Console Endpoint Agent self-modification: The endpoint user
During daily operation, maintenance and troubleshooting, administrators often need to confirm which policies are currently in effect on a certain endpoint, whether the policies have been successfully delivered, and the specific functions corresponding to the policy numbers. This article provides two commonly used viewing methods: server Management Console viewing and endpoint agent local viewing to
As explained before: When some functions are enabled, the endpoint agent may display icons in the system tray area. For relevant instructions, please refer to: [Which functions are turned on and the endpoint agent tray will be displayed] In order to meet the management requirements of "minimum visibility of the endpoint agent interface / completely
Ping32 includes multiple functional modules, and each module has its own policy model and delivery logic. This article uses Web Browsing Audit as an example to explain how policies are created, assigned, and applied in Ping32. Before you start creating policies, it is helpful to understand the following core concepts. Policy concepts Endpoint policy Path:
Activation process for new installation or expired license Login 1. After the server and Management Console are correctly installed, double-click the "Ping32 Endpoint Security Management System" icon on the desktop to run the Management Console. 2. Click the Settings button in the upper right corner of the login interface to configure the server IP (no
Ping32 is designed based on C/S architecture and mainly includes endpoint agent, server program and Management Console modules. The Management Console is used to help IT administrators deliver control policies to endpoints, view audit data, etc. In order to meet multi-administrator collaborative management scenarios (such as security approval, group control, etc.), an independent Management Console
Server environment configuration requirements The server configuration needs to be adjusted according to the number of management endpoints and enabled functional modules. Please refer to Ping32 Configuration Calculator: Recommended configuration for test environment: CPU: 8 cores Memory: 16 GB (minimum 8 GB of available memory) Hard drive: 1 TB Formal deployment recommendations: The system partition