Set Up Virtual Appliance - VM Workstation Pro

The PrinterLogic Virtual Appliance is the latest generation of PrinterLogic's private cloud platform. Typical use cases include:

  • It’s a streamlined, self-contained solution for new customers who want the benefits of PrinterLogic’s serverless printing infrastructure but need tighter control over their print environment.
  • For PrinterLogic Web Stack customers, the Virtual Appliance is a path forward to get the latest features PrinterLogic has to offer. Switching over is a track change but provides the newest functionality and ongoing support.

The PrinterLogic Virtual Appliance gets distributed as a fully integrated, standards-based private cloud solution. As a result, it helps customers maximize their investments in virtual infrastructures designed to reduce unnecessary hardware, software, and ongoing maintenance costs.

The PrinterLogic Client deployment, by default, checks for the use of SSL certificates for security considerations. Using SSL Certificates to encrypt data between the Virtual Appliance and other connected systems is highly recommended to ensure the confidentiality and integrity of your communications. Not using SSL Certificates will require additional configuration that may require assistance from PrinterLogic support engineers.

Minimum System Requirements

Depending on the configured features and user count, the minimum requirements for the Virtual Appliance may increase. Use the recommendations below when creating your Virtual Appliance, but continue to monitor the CPU and RAM utilization and allocate additional resources as needed.

  • Four 3.5-4.0 GHz processors. Add two 3.5 GHz processors for each additional 15,000 users.
  • 16GB RAM for up to 15,000 users.
    • Add 2 CPUs / 8GB RAM for each additional 15,000 users.
    • Add a minimum of 2 CPUs and 4GB RAM if using the Internal Service Client.
    • Add 2 CPUs and 4GB RAM per 500 CPA/Simple Badge Release installations.
  • 150GB free hard disk space for the host disk.
  • There should be 50GB of free hard disk space on the persistent storage disk (add 4GB for every 100 printers).
  • There is a requirement for NTLMv2 to connect to the appliance-storage shared folder of the PrinterLogic Virtual Appliance.

If you are migrating from a Web Stack instance please refer to the steps on Web Stack Migration to Virtual Appliance. Only continue if you are setting up a new installation of the Virtual Appliance.

Prerequisites

  1. Download the Virtual Appliance ova file.
  2. DNS configured properly.
    1. Identify a FQDN to use for the PrinterLogic Virtual Appliance (i.e., printerlogic.mycompany.com).
    2. Create an A record in DNS (i.e., printerlogic.mycompany.com) that points to the IP address of the Virtual Appliance.
    3. Create a CNAME record in DNS (i.e., *.printerlogic.mycompany.com) that points to the A record above (i.e., printerlogic.mycompany.com)
  3. SSL certificates created and available.
    1. The SubjectAlternativeName extension must list the two DNS entries above (i.e., printerlogic.mycompany.com and *.printerlogic.mycompany.com). In depth information can be found in the Virtual Appliance SSL Certificates document.
  4. Open ports for DB access from your machine:
    1. TCP 3306 - MySQL
    2. TCP 80 - HTTP
    3. TCP 443 - HTTPS
    4. TCP 8000 - Configuration API
    5. TCP 8080 - Configuration UI
    6. TCP 445 - SMB
  5. (Optional) If you are using advanced features requiring a Service Client, you must ensure the Service Client gets appropriately configured. See Set up a service client for more information.

Configure the Virtual Machine

Virtual Appliance should be able to work on any supported version of VM Workstation Pro, but it has been successfully tested on versions 12 and 15.

  1. Open VMWare Workstation Pro.

  2. Click Open a Virtual Machine.

    Open a Virtual Machine button as seen in the VMware Workstation Pro interface.

  3. Navigate to the .ova file you downloaded.

    File explorer view after navigating to the OVA file to upload.

  4. Click Open.

  5. Click Edit virtual machine settings.

    An arrow pointing to the Edit virtual machine settings option in the upper left of the VMware interface.

  6. Click Network Adapter.

    VM settings pop-up with the Hardware tab selected, and the Network Adapter option highlighted.

  7. Select Bridged: Connected directly to the physical network (if it is not already selected).

    An arrow pointing to the Bridged: Connected directly to the physical network option in the Network Adapter tab in the VM settings.

  8. Click Add.

    VM settings pop-up with an arrow pointing to the Add button in the lower middle.

  9. Select Hard Disk and click Next.

    Add Harware wizard pop-up with the Hard Disk option and selected and the Next button highlighted.

  10. Keep SCSI selected and click Next.

    Add Harware wizard with the SCSI option selected.

  11. Keep Create a new virtual disk selected and click Next.

    Add hardware wizard with the Create a new virtual disk setting checked.

  12. Adjust the disk size to the minimum recommended setting of 50 GB and click Next.

    PrinterLogic recommends 50GB free persistent hard disk space (add 4GB for every 100 printers).

    Add harware wizard on the Specify Disk Capacity step where the maximum disk size is edited.

  13. Click Finish.

    Add hardware wizard final step with the path to the disk file and Finish button.

  14. Click OK.

  15. Click Power on this virtual machine.

    VMware VM main interface with the new VM selected, and the Power on this machine option highlighted in the upper left.

  16. When the virtual machine loads, you will see the following message.

    Web console view of the IP address to continue setup, and the network settings login credentials for the VM.

  17. The IP address will be specific to your PrinterLogic Virtual Appliance. You will want to note it for a following step.

  18. Copy down the displayed login and password displayed to be able to access the network settings. This will be needed if you choose to configure static IP settings..

    Web console image with the IP address and network settings credentials highlighted.

    If you will be using a fully qualified domain name for accessing your Virtual Appliance, you should configure it in DNS and assign it the IP address shown on this console. You would also need to have the license file that PrinterLogic provides to contain the same FQDN for the licensed URL. When you are done with configuration from the above URL, the system will redirect you to the FQDN/URL you have in your license. If you are just testing and don’t need to manage more than 5 printers, you can continue to access the server via IP.

Configure Virtual Appliance Network Settings

The Virtual Appliance starts as a DHCP client. It’s possible to leave it that way and configure the TCP/IP settings via DHCP Reservation. Otherwise, use the steps below to configure a static IP and to optionally change the private IP range that the Virtual Appliance uses by default so that it doesn’t conflict with existing subnets in the environment.

  1. In the hypervisor where the Virtual Appliance runs, open the web console to access the Virtual Appliance Linux terminal interface.
  2. Login with the credentials supplied in the terminal banner for the network user.

    VA web console showing basic settings with the network settings credentials highlighted.

  3. Enter "Y" to change the network settings.
  4. Enter "Y" to change the network mode.

  5. Enter the TCP/IP settings.

    The image below is just an example. Ensure you use the settings specific to your network.

    VA web console, after logging in with network settings credentials, with the adjustable network settings all displayed and highlighted.

  6. If the existing address pool does not conflict with any subnets in the environment, enter “N”. Otherwise, enter “Y” to set a different address range.

    VA web console, Would you like to change the unassigned address pool for your network setting highlighted.

    If needing to adjust IP addresses, be sure to read and understand the network range options you are presented with. Any range used must have a netmask < 20.

    VA web console, with the network range IP requirements highlighted.

  7. If needing to adjust the IP address ranges, configure the address range.

    The image below is just an example. Ensure you use the settings specific to your network.

    VA web console, example highlighted of the unassigned CIDR range.

  8. Press any key to exit.

Launch the Virtual Appliance Wizard

The following steps are ONLY for setting up a new Virtual Appliance. If you are migrating from Web Stack to the Virtual Appliance, continue the migration by selecting Client Cut-over: Step 9 or DNS Cut-over Step 9.

The steps below are for creating new Virtual Appliance instances. If you are upgrading from an older host build, reference Host Upgrade.

  1. Open your preferred, supported browser window, and paste the IP address into the Address Bar, including port 8080. Example: 192.168.10.20:8080.

  2. When the PrinterLogic Virtual Appliance wizard appears, click Let's Do This.

    "Lets do this" button on the Welcome to PrinterLogic VA initialization wizard browser page.

  3. Select the Storage Type drop-down and select VM-Attached Virtual Disk.

    VM-Attached Virtual Disk option in the Storage Type drop-down, selected in the VA wizard.

  4. Click Format Attached Storage.

  5. When the attached disk is ready, click Continue.

    Orange Continue button highlighted in the upper right of the VA wizard Configure Storage window.

  6. If creating a new Virtual Appliance instance, click on Start New Instance.

    VA Wizard showing two button options, Start a New Instance, or Upgrade my Current Instance.

  7. When the General Settings appear add the domain name, then upload your license file, SSL certificate, and SSL key. When finished, click Continue.

    Ensure you document and save the Shared Storage Password so you can access the Data Drive later as needed. You can find more information on accessing the shared storage at the end of this document.

    General settings tab in the wizard showing the domain name, shared storage password, and upload location for the license file, SSL certificate, and SSL Key.

  8. When the Setup Database settings appear, make adjustments on the database type and then click Continue.

    If you want the MySQL database to reside on the VM's data drive, then leave the default settings for Database Type.

    Database type drop-down with two database options. One for using the internal VA database, or an external MySQL8+ database.

  9. Click Finish Setup.

    VA Setup wizard window with an arrow pointing to the Finish Setup button in the lower middle.

    Please do not refresh the page during the installation procedure.

  10. A new "Thank You" browser window will open when the installation is complete. This window can be closed as needed.

  11. The PrinterLogic Virtual Appliance login window appears, where you can Set up Login Credentials

    PrinterLogic root user account set up fields seen when first visiting the VA Admin Console.

  12. Once you are logged in, you will need to accept the License Agreement.

  13. You are now ready to work with your PrinterLogic Virtual Appliance.

    PrinterLogic Admin console shown after first logging in. Tree view to the left, object tabs in the center, and menu drop-downs in the upper right.

Accessing Data Files

If you need to add or update a license file or certificate or access the log files, you will need to map a network drive to the Virtual Appliance folder share. This can be done by using a non-elevated command prompt using a command similar to:

net use V: \\<hostname>\appliance-storage <password> /user:Admin /p:yes.

If the password contains special characters you will need to place "quotes" around the password.

Make sure you use a non-elevated command prompt to map the drive. If you have Windows UAC enabled on your workstation, drives mapped from an elevated command prompt are not visible in Windows Explorer by default. You can find additional information in Microsoft documentation.