web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

How to ensure that my model can't be deployed on other machines

(5) ShareShare
ReportReport
Posted on by 493
I built a vertical and I'm selling it for clients... how to make sure that the vertical works only on the client's machine and doesn't work no any other machine?
Categories:
I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    238,086 Most Valuable Professional on at
    You can use licensing to control who is allowed to use your solution. See Independent software vendor (ISV) licensing for more details.
  • AbdullahAhmed_ Profile Picture
    493 on at
    Thank you martin, it worked on the dev environment but when I go to the UAT the configuration key isn't visible...
     
    The documentation says to put the LicenseFile.txt in ImportISVLicense in AOSService bin and create All in One deployable package... but it's not working in the UAT! 
  • Martin Dráb Profile Picture
    238,086 Most Valuable Professional on at
    Before we can identify what you've done wrong, we must know what you've done. Please tell us more about your implementation, deployment and configuration, and the problem you're observing.
  • AbdullahAhmed_ Profile Picture
    493 on at
    Here are the steps I've followed:
     
    1- Create a certificate in .cer and .pfx format.
    2- Import .cer file in the model and create a license code and configuration key linked to it.
    3- Create a LicenseFile.txt with customer name and serial number.
    4- Import the license into the environment using:
    C:\AOSService\PackagesLocalDirectory\Bin\Microsoft.Dynamics.AX.Deployment.Setup.exe 
    --setupmode importlicensefile --metadatadir C:\AOSService\PackagesLocalDirectory 
    --bindir C:\AOSService\PackagesLocalDirectory --sqlserver . --sqldatabase axdb 
    --sqluser axdbadmin --sqlpwd ******** --licensefilename c:\Certificates\licenseFile.txt
     5- Sync database from visual studio.
     
    then in the license configuration form I found the configuration key enabled and the model is visible.
     
    Now for the UAT part..
    1- I go to "C:\AOSService\PackagesLocalDirectory\bin\CustomDeployablePackage\ImportISVLicense.zip\AosService\Scripts\License" and put LicenseFile.txt there
    2- Create All in One package.
    3- Upload to UAT.
     
    The configuration key isn't visible in  license configuration form in UAT environment!
     
  • Martin Dráb Profile Picture
    238,086 Most Valuable Professional on at
    A possible explanation is that your changes haven't been deployed at all.
     
    I see you're creating a deployable package manually (which is potentially dangerous). Make sure you've included all the necessary packages. make sure that the deployment succeeded. You may want to explicitly verify that your changes have been deployed, e.g. by updating the model number and checking it in UAT.
     
    I'm assuming you're using a self-signed certificate. Please confirm.
     
    Please show us how you created the license.
  • AbdullahAhmed_ Profile Picture
    493 on at
    Yes, I create All in One package manually and I'm sure the deployment has succeeded.
     
    I'm using a self-signed certificate as in the documentation Independent software vendor (ISV) licensing 
     
    these are the files for licensing and It works completely fine on the Dev environment. 
     
  • Verified answer
    AbdullahAhmed_ Profile Picture
    493 on at
    I figured out what I was doing wrong.. I'm using a self-signed certificate I've created on my machine not using a certificate bought from a certification Authority like globalsign.com 
  • Verified answer
    André Arnaud de Calavon Profile Picture
    301,411 Super User 2025 Season 2 on at
    Hi AbdullahAhmed,
     
    Martin asked you about self-signed certificates. These can only be used in development environments for testing purposes. For UAT/Sandbox and production environments, you must acquire a certificate from a Certificate Authority. A self-signed certificate will not be trusted and your module will then not be visible.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 679 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 429 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 264 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans