Can't find what you're looking for? Access our previous PDF-based library.
6 min read
️ Updated Dec 11, 20251. Introduction
Welcome to the Virtual Appliance Deployment Guide of Lepide Data Security Platform. Lepide Data Security Platform now offers new deployment options in addition to the traditional on-premises deployment. This Virtual Appliance deployment will get you up and running in less than 15 minutes.
Virtual Appliance: Lepide Data Security Platform can now be deployed as a virtual appliance using VMware AND Hyper-V. Virtual Appliance is essentially a VM image file with pre-installed Lepide Data Security Platform.
2. Virtual Deployment
The section below explains how to import the virtual appliance into VMware AND Hyper-V with installed Lepide Data Security Platform. The following configuration options are available:
Generalized Windows Server 2019 Datacenter
180-day evaluation version
Microsoft SQL Server 2019 Express with native Reporting Services installed.
2.1. Requirements to Deploy the Virtual Appliance
This section basically covers the software and hardware requirements where Lepide Data Security Platform is going to be deployed. The requirements are as below:
Software Requirements
Hardware Requirements
NOTE: The requirements below are sufficient only for evaluation purposes only. Refer to the Lepide Data Security Platform Installation and Configuration guide to Install Lepide Data Security Platform in production environments.
2.1.1. Software Requirements
The minimum software requirements are:
VMware – VMware ESXi 5.1, 5.5, 6.0, 6.5
VMware – Workstation 11 and 12
2.1.2. Hardware Requirements
When deploying Lepide Data Security Platform Virtual Appliance, a pre-configured virtual machine is created. Presented below is the default hardware configuration of the VM where Lepide Data Security Platform Virtual Appliance is going to be deployed:
Processor: 8 cores
RAM: 32 GB
Hark Disk: 1 TB for Virtual Appliance Setup
Total Video Memory: 16 MB
Network Adapter: vmxnet3
Other: Check and upgrade VMware tools during power cycle
2.2 Standard Resource Recommendations for a Virtual Appliance
By Use Case
Although the information below may vary, here are our recommendations based upon what we understand from our previous experience deploying Lepide DSP on a virtual appliance based on required modules/components:
2.2.1 Use Case 1
Modules: Auditing, Permission Scanning & Anomaly Detection
Change Frequency = 50K changes per day, Permission Scan Data set = Max 50K Files and Folders
Components: AD & File Servers
Total Machines Required: 1
Lepide + SQL Server Specs: 1 Machine
CPU: 8 Cores
RAM: 32 GB
Disk: 1 TB
2.2.2 Use Case 2
Modules: Auditing, Permission Scanning & Anomaly Detection
Change Frequency = 50K changes per day, Permission Scan Data set = Max 50K Files and Folders
Components: AD, File Servers & M365
Total Machines Required: 1
Lepide + SQL Server Specs: 1 Machine
CPU: 8 Cores
RAM: 48 GB
Disk: 1 TB
2.2.3 Use Case 3
Modules: Auditing, Permission Scanning, Anomaly Detection, Data Discovery & Classification
Change Frequency = 50K changes per day, Permission Scan Data set = Max 50K Files and Folders
DDC Data set = Max 100 GB
Components: AD, File Servers
Total Machines Required: 2
Lepide + SQL Server Specs: 1 Machine
CPU: 12 Cores
RAM: 48 GB
Disk: 1 TB
Data Discovery & Classification Agent Server: 1 Machine
CPU: 6 Cores
RAM: 16 GB
Disk: 200 GB
2.2.4 Use Case 4
Modules: Auditing, Permission Scanning, Anomaly Detection, Data Discovery & Classification
Change Frequency = 50K changes per day, Permission Scan Data set = Max 50K Files and Folders
DDC Data set = Max 100 GB
Components: AD, File Servers & M365
Total Machines Required: 2
Lepide + SQL Server Specs: 1 Machine
CPU: 16 Cores
RAM: 64 GB
Disk: 1 TB
Data Discovery & Classification Agent Server: 1 Machine
CPU: 6 Cores
RAM: 20 GB
Disk: 200 GB
OS Version: Any windows OS above Windows Server 2016 (Latest edition preferred)
OS Edition: Any version above SQL Server 2016
.NET Framework: 6.0 and above (Inbuilt in latest OS Versions)
Disclaimer - The recommendations above are to be used as guidelines only, exact requirements will vary from case to case .
3. Importing the Virtual Machine from Image to VMware
To import the Virtual Machine from image to VMware, please follow the steps below:
Go to File and click on Open
2. On the next screen, select LepideApplicance.ova from the location you have downloaded it.
On the next screen, please select a name for the VM and click Import.
Once you import the machine it will be visible in the VMware console with the provided name and will be ready to use.
4. Importing the Virtual Machine from Image to Hyper-V
Please follow the instructions below to import the virtual appliance into Hyper-V server:
On your Hyper-V server, unzip the Lepide virtual appliance package to the specified location.
Navigate to Start, All Apps, Hyper-V Manager.
In the Hyper- V Manager, navigate to Actions, Import virtual machine and follow the Wizard instructions:
Locate Folder - Browse for the folder that contains extracted Lepide virtual appliance
Select Virtual Machine - Select Lepide Virtual Appliance
Choose Import Type - Choose the import type that best suits your needs
Choose Network Type - Select a virtual switch
Summary - Review your virtual machine settings. Click Finish to exit the wizard
NOTE: If your Hyper-V server runs Windows Server 2012, instead of importing a virtual machine, select New virtual machine. Proceed with the wizard: set the startup memory to 4096 MB, specify your network switch and select the Use an existing virtual hard disk option.
The newly created virtual machine named Lepide Virtual Appliance will appear in the list of virtual machines. Right-click and select Start.
5. Configuring the Virtual Appliance
Follow the steps below to configure the Virtual Appliance with Lepide Data Security Platform:
Once you connect to the virtual appliance, you will see that Windows Server 2019 installation is almost complete. On the Settings page, specify a password for the built-in administrator account. Then re-enter your password. Click Finish.
On the next page, check the box to accept the agreement and click Proceed.
If you wish to configure the appliance then click on Yes, Configure the Virtual Appliance, otherwise select No, exit and reboot to do it later.
Provide a Computer name, NetBIOS Name, Time Zone and SQL Server Password for the VM and click Next.
Now configure the network adapter according to the required settings or select No if you plan to do it later.
Once the network settings are done, the next step is to join the machine to a domain if you wish to, or you can leave it in the workgroup as per your requirements.
The SQL server is automatically configured. The sysadmin server role on SQL server instance is granted automatically to the BUILTIN\administrators group. The user will need to set up the SQL settings in the solution to create the database.
Reboot the virtual machine and you will be able to launch Lepide Data Security Platform from Start menu or by double clicking the Lepide Data Security Platform shortcut on the desktop.
NOTE: SQL Server
Windows Authentication and SA Authentication is already enabled.
Password for SQL Authentication is same as you have set in Figure 7 for the SA Account.
Server Manager
Group Policy Management is given pre-installed
6. Configure Service Credentials
The last step is to configure the solution Service Credentials
From the Lepide Data Security Platform home screen, click the Settings icon.
Right click on Component Management and choose Configure Service Credentials.
The Service Credentials dialog box is displayed:
The Solution needs a domain admin account, this could also be a service account
Add the service account credentials and click OK
4. Select Default SQL Server Settings from the options on the left hand side
Enter the SQL server (either LepideDSP\SQLEXPRESS or the hostname of the machine with SQL installed) together with the credentials set in initial setup
Click Test Connection, then click Apply
As an additional check also ensure the dedicated account has Full Control of the Lepide install folder:
