Unfortunately Moving from Nprinting 16 17 is quite complex because a queue of hay has many features not 17 yet. That is my Recomendación if you have many reports ES 16 is better stay in that version.
It does not have the button available On Demand and neither can be embedded in the body of your HTML report.
All reports you have in the 16 must re- design in 17
Let me clarify , I'm not speaking ill of the product. I give my appreciation according to the experience I have had with the tool.
Actually it has a long way to adjust yet.
Thanks, Karen. My question was more from the server and application end of moving from one to the other.
I understand NP16 and 17 should not be installed on the same system so I was wondering how people were doing it and if there were any instructions on upgrading?
"All reports you have in the 16 must re- design in 17"
This is not true. There is a project import tool from NP16 that allows you bring in report templates to 17.x. That process is outlined here: http://help.qlik.com/en-US/nprinting/17.1/Content/ReportsDevelopment/Import-reports.htm
Note that in order for the import to work, you must be using the same QVW connection as used in version 16 with the same object IDs.
As of now, templates are the only entity that can be migrated from v16 to v17.
If you uninstall version 16, that will not delete the NSQ files, so if you ever need to re-install, your work will still be saved.