NPrinting Designer requires you to manually run each task, pretty similar as what you can do with QlikView Desktop vs. QlikView Server.
Moreover, NPrinting Designer needs a session exclusivity, meaning that you need a computer running NPrinting in the foreground, and only one task at a time.
While this could be enough for you, this is not its intended purpose, again, as with QlikView Desktop you can run scripts, but when you need a serious deployment, you use QlikView Server.
Very few to add to what Miguel wrote.
NPrinting Server consists in a Windows service running in session 0 that you can use to have your schedule run automatically according to the settings you choee in the .nsq files.
The service runs in the background so you will be able to use NPrinting Designer at the same time.
Moreover NPrinting Server is required to use NPrinting On-Demand.
There are a lot of limitations to the scheduling on the client side - the client must be up and running at the time the schedule kicks off, cannot have a screen saver running or the machine being locked.
The scheduling feature on the client is a great way to test your job and schedule but should not really be used for production - that is what the server is used for
All of the answers above are correct.
The NP designer is a limited way to schedule and distribute NPrinting reports.
It can only deliver reports from a SINGLE nsq
It must remain 'logged on'
It must NOT have screen savers or slept timers
It can NOT be used to design reports when being used as a scheduler
Allows you to automate and monitor the distribution reports from Multiple NSQs
Runs as a background service and does NOT require the NPrinting designer
NP Server can be lock while the NP service runs in the background
Primary system for distribution of NPrinting reports throughout the business enterprise