Skip to main content
Question

Nvivo for Mac

  • June 12, 2014
  • 29 replies
  • 262 views

Show first post

29 replies

mark_mahabir
Forum|alt.badge.img+16
  • Jamf Heroes
  • January 19, 2018

Does anyone have any advice for disabling auto-updates?


Forum|alt.badge.img+6
  • Contributor
  • January 10, 2019

@Look this still seems to work for NVivo 12 but the app name is slightly different:

Make a snapshot installer that includes a valid

/Applications/NVivo 12.app/Contents/MacOS/Activation.xml

You can download a sample one from Nvivo:
http://techcenter.qsrinternational.com/desktop/nm12/nm12_mass_deployment.htm

Follow it with a script that does the following

/Applications/NVivo 12.app/Contents/MacOS/NVivo 12 -initialize MY_NVIVO_SERIAL_NUMBER -activate /Applications/NVivo 12.app/Contents/MacOS/Activation.xml

Forum|alt.badge.img+6
  • Contributor
  • February 14, 2022

Anyone having much luck with packaging the latest version of NVivo? Using the method mentioned above (with the updated file path) does not seem to work. Keep getting prompted to Activate on first launch..... ughh


Forum|alt.badge.img
  • New Contributor
  • February 23, 2022

Anyone having much luck with packaging the latest version of NVivo? Using the method mentioned above (with the updated file path) does not seem to work. Keep getting prompted to Activate on first launch..... ughh


I was finding that the activation call would "succeed" even with an invalid xml path, which would lead to the behaviour that you are experiencing (the application would present the activation window on first launch with the key already populated). If I called the command again manually, it would say my key was already initialized. However, my -activate path was initially not properly escaping spaces (ex 'NVivo\\ 12.app'), so the activation.xml was not being passed properly (but no error was presented either). Once I corrected the xml path, everything behaved properly.