Print / forms Command | Explanation | Required Value |
---|
ntp | This is the operator indicating the use of NTP.exe |
- required value: : | This is the first command flag. -d indicates that an output destination will be defined following the flag |
. required value: -: | This is the full share location of the printer. |
It should always start with \\ and include the Hostname then another \ and finally the ShareName Note: If the printer is installed locally on the App server, you will not need \\Hostname\, only the name of the printer. |
- required value hostname (the server name) \sharename (share name of the printer)Hostname\ShareName or PrinterName | -@ |
: This | This command flag indicates that the output will use an options file to define the output format |
. required value: : This command flag indicates that the output will use an options file to define the output format. required value: ls | This is where the output format is defined. Available formats are included in the %musys%\pdefs folder on the Munis application server. Basic outputs include: |
, pm, nrA printer definition set up with a server name of "Server1", a share name of "printer1", and printing in landscape mode would look like: Click “Accept” to save new printer definition
A unique printer definition will need to be setup for each output type needed. As such, it is not uncommon for up to three unique printer definitions to exist for each printer added to Munis. This ensures end users can print in whatever format works best for the situation. When naming printers, it is helpful to define a standardized naming schema, such as: {UserInitials}_Local_{OutputType} For example, consider the following scenario: User: John Smith Workstation Hostname: JSOffice Printer ShareName: LocalPrint Recommended Printer Definition: Printer Name | Print/Forms Command | Output Result |
---|
js_local_pm | ntp -d \\ |
Server1printer1 lsHave a user test this printer by selecting this printer within Munis |