Nils Lang Posted May 2, 2016 Posted May 2, 2016 PVsyst cannot run in licensed mode on system that does not provide any hard disk identifier. We have already observed such issues on WMware virtual machines that have only SCSI hard drives. Adding one virtual IDE or SATA hard drive on such machines will allow PVsyst to run in licensed mode.
Nils Lang Posted November 3, 2016 Author Posted November 3, 2016 How to verify that your computer provide a hard disk identifier:Before you activate your license, you can verify with PVsyst weather your computer provides a hard disk identifier by doing the following: 1. Run PVsyst and open the license menu 2. Open the synchronize dialog and check content of external synchronization step 2 box. The string following 'HARDDISK=' should contain a hard disk identifier. Please refer to your virtual PC software documentation on how to configure it in order to provide a hard disk identifier.
Nils Lang Posted September 3, 2020 Author Posted September 3, 2020 PVsyst cannot run in licensed mode on system that provide a hard disk identifier that change on each reboot. We have already observed such issues on WMware virtual machines that have only SCSI hard drives. Adding a virtual IDE or SATA hard drives on such machines will add a hard disk identifier that does not change on each reboot. This will allow PVsyst to run in licensed mode. Please do the following actions to solve this issue: 1. Add a new virtual hard disk of type IDE on your virtual machine 2. Verify that you have now a stable hard disk identifier: https://forum.pvsyst.com/topic/1005-license-activation-error-on-a-virtual-machine/?do=findComment&comment=3001 3. If your license is already activated, ask PVsyst Support to deactivate it 4. Activate your license.
Sylvain Pepoli Posted February 12, 2021 Posted February 12, 2021 Use PVsyst on a Microsoft Azure Virtual Machine WARNING : this will describe how to use PVsyst on an Azure Virtual Machine, which is different from Azure Virtual Desktop. Azure Virtual Dekstop is not suitable for PVsyst as it is running on a specific Windows version which is actually a Server version. To be able to use PVsyst on Azure VM you need to make sure that you attach a secondary hard drive to the VM because the OS harddisk ID will always change when rebooting the machine. So basically you can create a basic HDD (not even an SSD) of 32GB (minimum available size now) and attach it to the VM prior to activating PVsyst. If you already activated PVsyst on the machine, you need to contact our support in order to reset your license : https://www.pvsyst.com/contact/
Recommended Posts