# Standalone MinIO Deployment

Canonical: https://www.nsecsoft.com/en/course/minio-install.html

Language: en-US

Updated: 2026-04-02T01:42:47Z

This article describes the operation process of deploying MinIO on a stand\-alone server and configuring the Ping32 server to connect to the MinIO service\. It is suitable for scenarios where you want to separate object storage from the Ping32 server and deploy it separately to improve storage scalability and operation and maintenance flexibility\. Prepare the \[…\]

This article describes the operation process of deploying MinIO on a

**stand-alone server**

and configuring the Ping32 server to connect to the MinIO service. It is suitable for scenarios where you want to separate object storage from the Ping32 server and deploy it separately to improve storage scalability and operation and maintenance flexibility.

#### **Prepare the environment**

-   Prepare an independent server for deploying MinIO.
-   Make sure that the MinIO server and the Ping32 server are in the same network environment and that the two networks are interconnected (the IP is reachable and the port is accessible).

#### **Required documents**

-   **MinIO file** (obtained from the installation directory of the installed Ping32 server)
-   **service.json file** (configuration file for Ping32 server to connect to MinIO)

#### **Create directory and prepare files**

-   Create a new `Server` folder in the disk partition with larger space on the independent server.
-   Copy the MinIO file to the `Server` folder (the MinIO folder is obtained from the installation path where the customer has installed the Ping32 server).
-   Create a new `DataDB` folder under the `Server` folder.

#### **Modify the MinIO service configuration file**

-   Enter the MinIO file directory and find the `MinIO-Service.xml` file.
-   Modify `<arguments>` parameters
    -   Modify **storage path** (pointing to the data directory, such as `DataDB`)
    -   Modify **service listening port** (the port number is subject to the delivery parameters)
-   Configuration label description:
    -   `<env name="MINIO_ROOT_USER">`: MinIO user name
    -   `<env name="MINIO_ROOT_PASSWORD">`: MinIO password

The above username and password are the MinIO login account and password. Use the default values and do not need to change them. The account number and password need to be filled in the

`service.json`

file of the Ping32 server, which is used for the Ping32 server to connect to the independent MinIO server.

#### **Install MinIO service**

-   Open CMD with administrator rights.
-   Use `cd` to enter the MinIO file directory.
-   Execute the following command to install the MinIO service:
    
    ```bat
    .\MinIO-service.exe install
    ```
    

#### Start the MinIO service

-   After the installation is complete, execute the following command to query the service status:
    
    ```bat
    sc query nsecfs
    ```
    
-   If the prompt status is STOPPED, execute the following command to start the service:
    
    ```bat
    net start nsecfs
    ```
    

#### **Configure Ping32 server connection MinIO**

-   Return to the Ping32 server, open the Ping32 installation directory, and enter the path: `Server\config`
-   Copy the `service.json` file to the above directory.
-   Open the `service.json` file and modify the content: only keep MinIO related configuration information, and delete the rest.
-   Parameter filling instructions:
    -   `host`: fill in the MinIO server IP address
    -   `user`: MinIO connection user name (see step 4)
    -   `password`: MinIO connection password (see step 4)
    -   `port`:

#### **Restart the Ping32 server**

After the configuration is completed, restart the Ping32 server to make the configuration take effect.

#### **Verification**

Upload a software to the Ping32 software store. If you can see the software file in the independently deployed MinIO, it means the deployment is normal.