PHDWIN WEEK 2025

September 8-12

Happy Holidays! We’re grateful for your support and wish you a joyful season.

Welcome to the PHDwin Download Website
Support is online M-F from 9:00 am - 5:00 pm (CDT).

Request a License

Concurrent-Users & Network Installation

With a concurrent-user/Network License, you can install PHDwin on multiple computers. However, the number of users who can access PHDwin at the same time is limited to the number of concurrent licenses purchased. To set up the concurrent-user/network license, follow the steps below:

Step 1 – Download and Install the PHDwin License Server Application (License Manager)

  1. Download the latest version of the PHDwin License Server install from https://www.phdwindownload.com/phdwin-license-server/.
  2. This will be a zipped file – PHDwinLicSvr.zip.
  3. Unzip the file to get to the installation file – PHDwinLicSvr.msi.
  4. Make sure you are logged in with “Administrative” privileges – the install should only be executed under an administrative login.
  5. Close all other programs.
  6. Double-click on the PHDWinLicSvr.msi file to execute it – this will start the Installation Wizard.
  7. Read the first screen and comply with all recommendations and click Next. (If you must fix any issues, you can hit Cancel and just restart the installation wizard again when finished).
    • Note: If you do not see a “Welcome” screen but see options to “Modify, Repair or Remove” PHDwin License Server, it has already been installed. The program runs as an NT Service so you may not notice it is installed or running. If you are trying to update to a new version, it can only be installed after uninstalling the previous version.
  8. You must accept the license agreement to continue. After an authorized user has read the agreement, choose “I accept the license agreement” and click Next to continue.
  9. Next choose the installation location. The default location is C:\Program Files(x86)\PHDwin License Server–it is highly recommended that you do not change this location. Click Next to finish the installation.

Step 2 – Requesting a PHDwin Unlock Code License for Concurrent-User / Network Deployment

To use PHDwin in a Concurrent-User/Network License Server, you will need to request a license by completing the following steps:

  1. Double-click the PHDwin License Server icon and click on the Registration button.
  2. Fill out the registration form completely – every field must be filled in to complete the request. Ensure that the System ID field has been populated before sending your request.

     

    • If the System ID field is not populated, click on the Delete button to regenerate an ID.
  3. Email your license request to the PHDwin license team by either:
    • Clicking the Request button, which will automatically generate an email with the necessary information pre-populated. All you need to do is send the email.
    • Manually emailing the information in the registration form to license@phdwin.com. You can take a screenshot of the completed registration form by pressing Ctrl + PrintScreen or typing in the information, including your name, company name, address, phone, email, and system ID. Ensure that the subject line of your email is “Network License Server Request for PHDwin Version 3”.
  4. After the licensing team receives your email, they will process it and send you two emails with a separate license file attached to each email.
  5. Follow the instructions below to save the license files.
PHD License Server Registration Window
PHD License Server Registration window

Step 3 – Save your Unlock Code Files

After receiving two emails with unlock code files attached, you will need to save them as follows:

  1. Open the email from license@phdwin.com that contains the unlock code files.
  2. Save both unlock code files to the License Server installation folder. The default location is C:\Program Files(x86)\PHDWin License Server. Note: The files should be named PHDWin License Server.lic and PHDwin.lic. Please make sure to check the file names, as some email programs may append underscores to attachment names.

Step 4 – Starting the License Server​

Once you have received the unlock codes and saved them to the PHDwin License Server installation directory, you need to start the license server application by selecting Start. If the unlock codes are valid, the status of the License Server should say “Accepting License Requests”.If it says it is unable to open the main license file, try re-saving the files or contacting support. The first thing to check will be to make sure that no characters have been added to the name of the license files such as an underscore to the beginning of the file name. This is a common issue with text attachments being sent via Outlook. The file names are: PHDWin License Server.lic and PHDWin US.lic.

The License Manager also has several features that can be helpful to users. The application indicates:

Status & Licenses: how many unlock codes are available on the license.

Current Network Users: how many network users are currently logged in (and which users they are).

Checkedout Licenses: how many unlock codes have been checked out

Step 5 – Set Up Each User's Machine to Connect to the License Server​

  1. Once the PHDwin program is installed on each user’s computer, go to the default location where the PHDwin unlock code file (previously known as license file) is saved: C:/Program Files/TRC Consultants/PHDwin 3.1/Config. Delete the PHDwin.lic file if it exists.
  2. Open the PHDwin splash screen and click on the Registration button.
  3. Click on the Network License button and type the name of the server next to “Host”.
  4. Click “Apply” to save the changes and go back to the Registration window.
  5. Click “Close” in the Registration window.
  6. Restart PHDwin. When running PHDwin, the computer will then look to the server to see if there is an unlock code available to open the program.

**.MSI does not include SQL Server Express or any of the PHDwin V3 dependencies.**

  1. V3 .exe (Executable File): A V3 .exe file is an executable file that contains all the necessary installation files and instructions within a single executable file. When you run a V3 .exe file, it launches a setup wizard that guides you through the installation process. This type of file is commonly used for standalone installations, where the installation process and required files are contained within the .exe file itself.
  2. V3 .msi (Microsoft Installer): A V3 .msi file is a Windows Installer Package file. It is specifically designed for use with the Windows Installer technology, which provides a standardized and consistent way to install, configure, and remove software applications on Windows operating systems. An .msi file contains a package that includes all the necessary files, resources, and instructions for the installation process.

Compared to a .exe file, an .msi file provides additional capabilities, such as the ability to customize the installation process, perform administrative installations, and support features like repair and uninstallation through the Windows Installer service. In summary, the key difference between V3 .exe and V3 .msi lies in the installation method and the capabilities provided by the respective file formats. A .exe file is a standalone executable that guides you through the installation, while an .msi file is designed for use with the Windows Installer technology, allowing for more advanced installation and management options.

System administrators can use the V3 .msi file to perform silent installations, which means the installation process runs without any user interaction or prompts. This is useful when deploying software to a large number of computers simultaneously, as it allows for automated and unattended installations.

Additionally, the .msi format supports customization options, allowing administrators to modify the installation behavior, set default configuration settings, and apply specific policies during the installation process. It also provides features like repair and uninstallation, making it easier to maintain and manage software installations across multiple machines.

Overall, the V3 .msi file is intended for use by IT professionals who are responsible for software deployment and management in enterprise environments or large-scale deployments.

System administrators can use the V3 .msi file to perform silent installations, which means the installation process runs without any user interaction or prompts. This is useful when deploying software to a large number of computers simultaneously, as it allows for automated and unattended installations.

Additionally, the .msi format supports customization options, allowing administrators to modify the installation behavior, set default configuration settings, and apply specific policies during the installation process. It also provides features like repair and uninstallation, making it easier to maintain and manage software installations across multiple machines.

Overall, the V3 .msi file is intended for use by IT professionals who are responsible for software deployment and management in enterprise environments or large-scale deployments.

The PHDwin License Server is a component of the PHDwin software that manages the licensing and usage of PHDwin within an organization. It acts as a central server where licenses are stored and distributed to users who want to run PHDwin.

The license server ensures that only authorized users can access and use PHDwin by validating the license information. When a user wants to run PHDwin, they connect to the license server to request a license. If the license server confirms that a license is available, it grants permission to the user, allowing them to use PHDwin.

The license server also provides information about the number of available licenses, the number of users currently logged in, and any licenses that have been checked out or reserved. This helps organizations keep track of their license usage and ensure compliance with the terms of their licensing agreement.

Overall, the PHDwin License Server helps organizations manage and control the licensing of PHDwin software, ensuring that it is used by authorized users and in accordance with the licensing terms.

In the context of the PHDwin License Server, licenses refer to unlock codes that are associated with a specific software license owned by an organization. These unlock codes are essentially unique codes or keys that enable the organization to use PHDwin software.

When an organization purchases a license for PHDwin, they receive unlock codes that correspond to the specific license agreement they have. These unlock codes are then stored in the PHDwin License Server. Each unlock code is linked to a single license, allowing the organization to activate and use the software on the specified number of machines or for the agreed-upon number of concurrent users.

The PHDwin License Server acts as a repository for these unlock codes. When a user wants to use PHDwin, they connect to the license server and request a license. The license server checks the availability of licenses and, if a license is available, grants permission to the user to access and use the software.

In this way, the unlock codes, which are essentially licenses, are managed by the PHDwin License Server to control and regulate the usage of PHDwin within the organization. The license server keeps track of the number of available licenses, the number of users currently logged in, and any licenses that have been checked out or reserved, ensuring that the organization complies with the terms and conditions of their license agreement.

So, in summary, licenses in the context of the PHDwin License Server are represented by unlock codes that are associated with a specific license owned by an organization, and the license server manages the distribution and usage of these licenses.