7013074: iPrint Appliance local rendered jobs are canceled, aborted, or improperly rendered.

The iPrint Appliance version 1.1 introduced the ability to assign specific Linux printer drivers to individual printer agents. The same ability exists in the 2.x and 3.x versions of the iPrint Appliance.

The steps in the Resolution section of this TID shows how to use the Linux printer drivers (PPDs) which ship with the iPrint Appliance. PPDs obtained from other sources (such as http://www.openprinting.org/printers) can also be uploaded to the Driver Store. However, the iPrint Appliance does not support all of the filters used by the various PPDs obtained from external sources. When the PPD references a filter which the Appliance does not support, print jobs submitted via mobile devices will be canceled or aborted.

One common filter which may be of use to install is the hplip filter.

Note: The printer drivers in the /usr/share/cups/model/manufacturer-PPDs/hplip directory do not use the hplip filter. View the PPD content (a PPD is a text file) and search for the word ‘filter’. If hpcups or hplip is listed as a filter, you must install hplip to the iPrint appliance for that PPD to be a valid option.

To install the hplip filter:

mkdir /tmp/hplip

wget -P /tmp/hplip ftp://ftp.novell.com/outgoing/hplip-ForAppliance.tar.gz

tar xvzf /tmp/hplip/hplip-ForAppliance.tar.gz

rpm -Uvh /tmp/hplip/*.rpm

Note: If the hplip-ForAppliance.tar.gz file does not exist on the Novell FTP outgoing site, email patchfeedback@novell.com with the subject of “Need hplip for the iPrint Appliance”. An email will be sent in reply notifying you when that file has be re-added.

When choosing a ppd to assign to a printer, a generic ppd is often a good choice. Some examples of generic printer drivers are:

/usr/share/cups/model/Postscript-level2.ppd.gz

/usr/share/cups/model/Postscript.ppd.gz

/usr/share/cups/model/deskjet.ppd.gz

/usr/share/cups/model/laserjet.ppd.gz

Other strategies include testing a PostScript vs PCL driver. Often a printer driver for a specific printer model will work for a different model and even different manufacturer printer. The key is use a printer driver which matches the printer language which is supported by the printer type (PostScript or PCL).

If an remote renderer is configured (also known as a Windows renderer), none of the above configuration applies. All print jobs, regardless of the format, will be rendered by the remote, Windows renderer as long as it is active.

Related:

Mobile printing with iPrint

qmangus

The use of mobile devices has greatly improved productivity in the workplace. Users can more easily access systems, quickly communicate and collaborate, and even create and share documents and files on their mobile devices (Micro Focus Filr is a great solution for this). In fact, a recent survey by Samsung and Frost & Sullivan found …

+read more

The post Mobile printing with iPrint appeared first on Cool Solutions. qmangus

Related:

  • No Related Posts

7023341: iPrint Appliance Directory Servers Configuration: An error has occurred

This document (7023341) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus iPrint Appliance 3.x

Situation

When clicking the Synchronize Now button within the iPrint Appliance Directory Servers -> Directory Servers Configuration page, the following error is returned

Last manual synchronization [DATE]

  • Status: Failed
  • Server:
  • Error: An error has occurred. See the server logs for more information.

Resolution

Run the Re-Index Everything tool with the Search Index tool.
  1. Take a snapshot of the Appliance.
  2. Delete the kablink cache
  • rm /vastorage/search/lucene/kablink/*
  • Stop the firewall
    • rcSuSEfirewall2 stop
  • Find the Filr admin password
    • Paste the following command into a terminal session:
      • base64 -di /etc/opt/novell/iprintmobile/conf/credstore.conf
    • Look for the line which shows <entry key=”filr.password”>
    • Copy the password which shows for that entry.
  • Launch the Filr console from the browser.
    • https://<appliance host address>:8444
    • Type ‘admin’ for the user name
    • Type the password found from step 3 for the password
    • Choose “Cancel” when prompted to change the password
  • At the top right corner, click the “admin” link and choose “Administration Console”
  • Click “Search Index” within the left navigation list (under the “Management” section”)
  • Check the box for “Re-Index Everything” and click OK.
    • This might take quite some time so let it continue until it is completed.
  • Start the firewall.
    • rcSuSEfirewall2 start
  • Verify the problem is resolved.
  • Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    7023349: Chromebook iPrint printer install loops, never installs

    This document (7023349) is provided subject to the disclaimer at the end of this document.

    Environment

    Micro Focus iPrint

    Situation

    When attempting to install an iPrint printer to a Chromebook, the install loops from 0 to 100% and never installs.

    Resolution

    Micro Focus is investigating a solution to this problem. Until that time, the following two options exist:

    1. Use the PSMHostAddress to access the iPrint Portal page.
    • Find the PSMHostaddress by running the following command a terminal session to the iPrint server:
      • cat /etc/opt/novell/iprint/conf/ipsmd.conf | grep PSMHostAddress
    • When accessing the iPrint Portal page, use the address PMSHostAddress value.
      • For example, if the address following PSMHostAddress is iprint03.mycompany.com, then use this address to bring up the iPrint Portal:
        • https://iprint03.mycompany.com/print
  • Recreate the certificate with a SAN to match the PSMHostAddress
  • Cause

    The iPrint code cannot handle a scenario where the address bound to the Print Manager does not match the address used to access the iPrint Portal page (https://<iPrintDNSName>/print).

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    7008708: History of iPrint Client fixes

    Fixes introduced in the 6.15 iPrint Client

    Available through the OES and iPrint Appliance Update channel and through the iPrint Appliance 2.1 Patch 7 download.

    • User printers installed using WSACL rules and shortname could not be removed (Bug 1089861)
    • iPrint Lite: Unsupported files information icon updated (Bug 1081341)
    • iPrint Lite is allowing to print unsupported files through windows context menu open with option. (Bug 1069221)
    • iPrint_lite: Clicking on iprint-lite icon on windows task bar does not minimize it. (Bug 1070780)
    • iPrint_lite: Hitting Enter key after entering server-ip does not click on “Find” button. (Bug 1070925)
    • iPrint Authentications fail with Novell Client installed (userPrincipalName) (Bug 1080884)
    • No error message when user prints to an SSL printer that he has no rights (Bug 1077610)
    • Printer driver download without iPrint provider using CLI. (Bug 116453)
    • iPrint client allowing to print the document even if the copies field is null. (Bug 1070716)

    Fixes introduced in the 6.12 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Refresh iCM feature introduced (Bug 1057892)
    • Context menu printing crashes Windows Explorer with files with no extension (Bug 1063863)

    Fixes introduced in the 6.11 iPrint Client

    Available through the OES and iPrint Appliance Update channel

    • Minor cosmetic fixes.

    Fixes introduced in the 6.10 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through iPrint Appliance 2.1 Patch 5

    • TID 7020136: OES Client nwtray crashes when you login through icon repetitively

    Fixes introduced in the 6.09 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Hot Patch 4
    • iPrint Appliance 2.1 Hot Patch 4
    • Error messages flooding NPSMMON.LOG (Bug 1021421)
    • Print dialog within MS Office or Adobe Reader in perpetual error state or spins indefinitely. (Bug 1029529)
    • User Printer installation crashes print spooler if location or description is set. (Bug 1028999)

    Fixes introduced in the 6.08 iPrint Client

    Available through the OES and iPrint Appliance Update channel or through these iPrint Appliance patches:

    • iPrint Appliance 2.0 Patch 4
    • iPrint Appliance 2.1 Patch 2
    • TID 7017101 – 0x00000002 error installing iPrint printers with the EFI Fiery driver (Bug 1019023)
    • TID 7017417 – Direct Printers looses parts of the printed document if bDirectPrintSpoolJobEnabled is enabled (Bug 1021882)
    • TID 7021962 – Hide Document Names for iPrint printer’s Windows Printer Queue
    • Printer driver DLLs are being over-written during iPrint printer installation. (Bug 990474)
    • iprntcmd based printer install and deletion enhanced for new User Printer implementation (Bug 103440)
    • iCM settings only read on log on. Provided message-box in case iCM not enabled. – Added few strings to the string table for User Printer. (Bug 104441)

    Fixes introduced in the 6.07 iPrint Client

    Available through the OES Update channel

    • Mac driver upload via iManager results in inproper driver name. (Bug 984480)
    • iCM fails to launch when logging in with OES Client. (Bug 1011189)
    • error 0x00000002 installing PS EFI Fiery driver (Bug 1019023)
    • Spooler crashes with Auto driver/profile update on Win 10 x86 (Bug 1020818)

    Related:

    7023334: Apache won’t load and “Document failed to print” after upgrade to OES 2018

    This document (7023334) is provided subject to the disclaimer at the end of this document.

    Environment

    Open Enterprise Server 2018
    iPrint Client 6.15

    Situation

    After upgrading to OES 2018, sending a print job thru the Windows iPrint Client returns the error:

    Document failed to print
    iPrint Client properties, iPrint document status shows “Creation failed” error

    ipsmd (Print Manager) and idsd (Driver Store) are running fine.

    Apache is not loaded. When loading Apache, the following is returned:

    [DATE + TIME] server start_apache2[6338]: httpd-prefork: Syntax error on line 204 of /etc/apache2/httpd.conf: Syntax error on line 119 of /etc/apache2/default-server.conf: Syntax error on line 5 of /etc/apache2/conf.d/oes_httpd.conf: Syntax error on line 9 of /etc/opt/novell/httpd/conf.d/iprint_g.conf: Cannot load /opt/novell/iprint/httpd/lib64/mod_ipp.so into server: /usr/lib64/libcurl.so.4: undefined symbol: libssh2_agent_disconnect

    [DATE + TIME] server systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE

    Resolution

    Remove the incorrect link
    Follow these steps to find the incorrect link and link the correct library:
    1. Run the following command on both a working and non-working OES 2018 server:

    ldd -r /usr/lib64/libcurl.so.4

    The following will be returned on a working server:

    linux-vdso.so.1 (0x00007ffe50bac000)

    libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007fa924d73000)

    libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007fa924b47000)

    libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007fa9248dc000)

    libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007fa924483000)

    libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fa92423b000)

    liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007fa92402c000)

    libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007fa923de0000)

    libz.so.1 => /lib64/libz.so.1 (0x00007fa923bca000)

    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa9239ad000)

    libc.so.6 => /lib64/libc.so.6 (0x00007fa923608000)

    libdl.so.2 => /lib64/libdl.so.2 (0x00007fa923404000)

    libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fa923134000)

    libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fa922f04000)

    libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fa922d00000)

    libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fa922af3000)

    libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa9228dc000)

    libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007fa9226bf000)

    /lib64/ld-linux-x86-64.so.2 (0x00007fa925217000)

    libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fa9224bb000)

    libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fa922295000)

    libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fa922026000)

    The following will is an example of what was returned from one non-working server:

    linux-vdso.so.1 (0x00007ffec170d000)

    libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007f62ea6e4000)

    libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f62eac5f000)

    libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007f62ea479000)

    libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007f62ea020000)

    libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f62e9dd8000)

    liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007f62e9bc9000)

    libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007f62e997d000)

    libz.so.1 => /lib64/libz.so.1 (0x00007f62e9767000)

    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f62e954a000)

    libc.so.6 => /lib64/libc.so.6 (0x00007f62e91a5000)

    libdl.so.2 => /lib64/libdl.so.2 (0x00007f62e8fa1000)

    libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007f62e8c01000)

    libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f62e8931000)
    libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f62e8701000)

    libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f62e84fd000)

    libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f62e82f0000)

    libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f62e80d9000)

    libsasl2.so.3 => /usr/lib64/libsasl2.so.3 (0x00007f62e7ebc000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f62eab88000)

    libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f62e7cb8000)

    libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f62e7a92000)

    libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f62e7823000)

    undefined symbol: libssh2_agent_disconnect (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_init (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_free (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_free (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_readfile (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_get_identity (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_check (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_session_hostkey (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_userauth (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_session_block_directions (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_writefile (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_init (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_connect (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_knownhost_add (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_scp_send64 (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_sftp_seek64 (/usr/lib64/libcurl.so.4)

    undefined symbol: libssh2_agent_list_identities (/usr/lib64/libcurl.so.4)

    2. Compare the working and non-working output to the ldd command. In the above scenario, the 3rd line shows a library linked to an incorrect file:

    libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f62eac5f000)

    3. Do a listing on the incorrect module:

    l /lib64/libssh2.so.1

    In this scenario, the following is returned:
    lrwxrwxrwx 1 root root 49 Nov 21 2012 /lib64/libssh2.so.1 -> /usr/openv/pdde/pdopensource/lib/libssh2.so.1.0.0*
    4. Execute an RPM query on the incorrect package:
    rpm -qf /lib64/libssh2.so.1
    In this scenario, the following is returned:
    file /lib64/libssh2.so.1 is not owned by any package

    5. Delete the link:

    rm /lib64/libssh2.so.1

    6. Refresh the library links:

    lddconfig

    7. Start Apache
    rcapache2 start

    Cause

    There was a wrong library link.

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    7023317: iPrint on OES2018 Cluster fails to load – failed at step EXEC spawning /opt/novell/iprint/bin/precheck

    This document (7023317) is provided subject to the disclaimer at the end of this document.

    Environment

    iPrint for Linux Open Enterprise Server
    Open Enterprise Server 2018 (OES 2018) Linux
    Cluster

    Situation

    After fully patching an OES2018 server (note: fully patched as of 30 August 2018, which is Update 3, released 27 June 2018) with iPrint configured to run in a cluster, the iPrint services will not load. The following error is found in the system log:
    failed at step EXEC spawning /opt/novell/iprint/bin/precheck

    Resolution

    Download ftp://ftp.novell.com/outgoing/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm
    Install this RPM on each node. The node must have the Cluster Volume hosting iPrint loaded at the time of the install.
    If the server can access external sites, the following string of commands can be pasted into a terminal session to download and install the RPM.
    wget -P /tmp ftp://ftp.novell.com/outgoing/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm;rpm -Uvh /tmp/novell-iprint-server-6.18.0_1074650-1.1.x86_64.rpm

    Cause

    A defect in the iPrint server code.

    Additional Information

    This issue is scheduled to be fix in the next update. This article will be modified once the fix has been released.

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    7022285: Unable to load Certificate from Keystore – iPrint Appliance 3.1

    This document (7022285) is provided subject to the disclaimer at the end of this document.

    Environment

    Micro Focus iPrint Appliance 3.1

    Situation

    After upgrading from iPrint Appliance 3.0 to 3.1, with 3rd party certificates applied, clicking the “Certificates” link within the iPrint Management Console (https://<ip or dns>:9443/iprintconfig/certificates) results in the following message:

    Unable to load Certificate from Keystore

    Also, when attempting to update the CSR generated from the Management Console in the Certificate Authority page, an error is returned:

    The following error was encountered:

    The CSR has an invalid signature.

    Resolution

    Update the iPrint Appliance server to version 3.1.2 to obtain an updated certman.sh file which has been enhanced with a new target of utils with these two options:

    c : generate a private key and CSR using openSSL command and verifies the same

    u : update certificate alias name in keystore file to hostname

    Then, follow these steps:

    1. Make a backup of the server’s /opt/novell/iprintmobile/bin/certman.sh file.
    2. Copy the updated certman.sh file to the server’s /opt/novell/iprint/iprintmobile/bin directory.
    3. Copy/paste the following string of commands into a terminal session.
    • chmod +x /opt/novell/iprintmobile/bin/certman.sh
  • Copy/paste the following command into a terminal session:
    • /usr/bin/keytool -list -keystore /vastorage/conf/certs/keystore -storepass changeit -v | grep “Alias name:”
      • If only one alias name is returned, then execute the following command:
  • sh /opt/novell/iprintmobile/bin/certman.sh -t utils -u
    • The above command will update the alias name of the certificate file in the keystore as hostname and restart all the required services.
      • Note: There will be disruption of printing services during this activity because some of the print services will be restarted
    • After restart of the services you can view the Certificates page from iPrint Appliance Management Console. You are done now and no need to follow the next steps.
  • When you see more alias names listed in the output of the command executed in step 1, first identify the valid certificate. You can view the validity of the certificates by executing the following command:
    • /usr/bin/keytool -list -keystore /vastorage/conf/certs/keystore -storepass changeit -v
  • Now delete the rest of the certificates from the keystore file using the alias name listed in output of step 1 using the following command:
    • /usr/bin/keytool -delete -keystore /vastorage/conf/certs/keystore -storepass changeit -v -alias <alias_name>
  • Once you are left with required certificate in keystore, execute the command in step 5 and view the Certificates page from the iPrint Appliance Management Console.
  • The above steps 5-8 needs to be executed when you see the error “Unable to load Certificate from Keystore” in Certificates page of iPrint appliance Management Console.

    When there is an error during uploading the certificate signing request (CSR) generated from Certificates page of iPrint Appliance Management console, following the next steps:

    1. Copy/paste the following command into a terminal session:
    • sh /opt/novell/iprintmobile/bin/certman.sh -t utils -c
      • A private key file along with certificate signing request will be created in /vastorage/conf/certs folder with hostname as filename. For example if hostname of the server is iprint-server1.mf.com, then the files will be created as iprint-server1.mf.com.key and iprint-server1.mf.com.csr.
        • The output of the command will also mentions the same:
          • Generated private key at /vastorage/conf/certs/iprint-server1.mf.com.key
            • The .key file name will be different from what is listed above. iprint-server1.mf.com is simply an example.
          • Generated CSR at /vastorage/conf/certs/iprint-server1.mf.com.key.csr
            • The .csr file name will be different from what is listed above. iprint-server1.mf.com.key.csr is simply an example.
      • The above command will also verify the generated CSR and output will be listed on the command console.
        • Copy the output between lines:
          • —–BEGIN CERTIFICATE REQUEST—–
          • MIICbTCCAVUCAQAwKDEmMCQGA1UEAxMdd2dwLWR0MjQwLmxhYnMuYmxyLm5vdmVs
          • YwLnFG0nozfIdStriCcZnzqFsb1/jdAT9HgaQizBcpocGfFZirMImn57w21sND6C
          • —–END CERTIFICATE REQUEST—–
    1. Copy/paste the above certificate data, including the header and footer, and submit that to your certificate authority to get the response.
    2. Once you get the files from your certificate authority, upload all certificates along with private key in the MC Certificates page.

    Cause

    Multiple certificates were uploaded the keystore.

    Additional Information

    The error “The CSR has an invalid signature” will come for multiple reasons like:

    • Using of RSA-2048 public key with RSA-4096 private key
    • RSA signature length 512 bytes is not accepted on some sites
    • Using of special characters in CN name
    • Junk characters were added while copying the certificate
    • Multiple certificates have been applied to the keystore

    This TID addresses the “Multiple certificates have been applied to the keystore” cause.

    To verify the validity of a CSR, run this command:

    • Syntax:
      • openssl req -in </path/to/CSRfile> -verify
    • Example:
      • openssl req -in /tmp/MyCSRfile.csr -verify

    Disclaimer

    This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

    Related:

    Invite for Beta participation- Micro Focus iPrint 3.2

    iPrint team has been working hard for quite some time on the next release. There are a bunch of features and lots of bug fixes that are shaping up for this. We would absolutely love to hear your feedback on them, and therefore are opening up the beta for iPrint 3.2. Find the registration link here. Program …

    +read more

    The post Invite for Beta participation- Micro Focus iPrint 3.2 appeared first on Cool Solutions. Punyashloka Mall

    Related:

    • No Related Posts

    Packaging Cupsfilter on a Mac Device

    Installation of the printer fails on Mac if the cupsfilters specified in the PPD file is not installed. Some vendors do not distribute the drivers in .pkg or .dmg format. Hence, associating the package to the PPD file is not possible. Micro Focus iPrint server has an option to associate a package containing cupsfilters to …

    +read more

    The post Packaging Cupsfilter on a Mac Device appeared first on Cool Solutions. wpreetham

    Related: