GoodNotes for Business for MacBook

Jonasthieny
New Contributor II

Hey. 
Im trying to upgrade GoodNotes for Institutions into GoodNotes for Business. 
There is only an instruction how to install a license key for iPad/iPhone (https://support.goodnotes.com/hc/en-us/articles/7568710302607-Installing-Goodnotes-for-Business-Ente...). 
Does someone know how I can install a license on MacBook via JamfPro? 


1 ACCEPTED SOLUTION

justin_beek
New Contributor III

yes. 

https://ibb.co/0nW8NLS

 

Our plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.goodnotesapp.x.managed</key>
    <dict>
      <key>LicenseKey</key>
      <string>XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-V3</string>
    </dict>
  </dict>
</plist>

 

View solution in original post

7 REPLIES 7

justin_beek
New Contributor III

Same issue.

I am guessing setup App and use Composer?

erwin_c
New Contributor II

Were you able to deploy the licenses? I follow the instructions based on the Goodnotes support link above but the app doesn't recognize that a license has been deployed. Scope is set correctly and installed based on the log. The same license key is valid works without problems for our organizations iPads. Not sure what I'm missing. 

justin_beek
New Contributor III

yes. 

https://ibb.co/0nW8NLS

 

Our plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.goodnotesapp.x.managed</key>
    <dict>
      <key>LicenseKey</key>
      <string>XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-V3</string>
    </dict>
  </dict>
</plist>

 

It worked. Appreciate it! 

erwin_c
New Contributor II

I've done the same thing but in Goodnotes on the Mac it still gives me these errors. In JAMF, it says that the profile has been pushed through. Any ideas? 

Screenshot 2024-09-26 at 20.33.30.pngScreenshot 2024-09-26 at 20.34.46.png 

erwin_c
New Contributor II

FIXED: There was an extra colon in our application domain field. The solution above works well.