We recently finalized and posted our latest build of SOLO Server: 184.108.40.206. Although there are many small changes, improvements and fixes in this release as outlined in the full release notes, there are two main enhancements of interest in this release.
In a previous blog post, we outlined in Phase 3 our plans to remove the customer password from the SOLO Server administration interface to improve the overall security of the system and the customer data contained within. After talking to customers and giving careful thought to this design, we determined that it was necessary to provide an easy way for SOLO Server administrators and customer service representatives to view the password required for software activation without exposing the ability to see the customer’s password that was used for the shopping cart and customer license portal.
In this release of SOLO Server:
We understand that some changes like this create confusion. However, we feel confident that these changes were necessary and the introduction of the Activation Password feature has additional benefits, such as:
Additional updates to the Activation Password were completed in the next release of SOLO Server. View the SOLO Server 220.127.116.11 Released blog post for more information.
When a customer successfully activates with a license, each installation can be assigned a unique Installation ID, and there are multiple ways that an Installation can be deactivated or banned. When the customer chooses to deactivate an Installation through the Customer License Portal or inside of the software application, they have always been allowed to re-activate the software on the same computer. However, when an administrator deactivated an Installation from the activation history in the SOLO Server administrative interface, a warning message appeared that you were banning or blocking this computer from activating with this license in the future on the same computer. Early feedback from customers showed that they wanted to be able to prohibit the same computer from activating again. The thought process was the fact that deactivating an Installation would increment the Activations Left parameter for that License ID, allowing a different computer to activate. The administrator always had the ability to reactivate a deactivated/banned Installation through the administrator interface.
In this latest release of SOLO Server, however, administrators are given the option to either ban or simply deactivate the Installation ID when using the SOLO Server author interface. Clicking the Red X in the activation history for an Installation ID will display a message similar to:
“Do you want to deactivate or ban InstallationID “93832-ABCDE-82YFM-123454-UP5D3-Z”? Banning an installation will permanently prevent future activation on the computer.”
[Deactivate] [Ban] [Cancel]
Clicking Deactivate will allow the same computer to activate under the same License ID. Clicking Ban will prohibit this computer from activating under this same License ID.
Feel free to contact us with any questions you have.
Mike Wozniak is one of the co-founders of SoftwareKey.com and responsible for marketing, content and product strategy. When he isn't plotting new ways to help customers solve licensing and business automation challenges, he likes to travel and entertain guests who come to visit the Orlando area. He also writes most of the licensing tips here.
SOLO Server 18.104.22.168 Released with a New GDPR Module and Other Enhancements
September 10, 2018 Updates to the Instant SOLO Server Terms of Service
SOLO Server 22.214.171.124 Released with Enhancements to Custom License Parameters and Multi-Tenant Catalog Features
Instant Protection PLUS 3 Version 126.96.36.199 Released
Protection PLUS 5 SDK Major Updates for Android Users
Protection PLUS 5 SDK version 188.8.131.52 released