LDAPS and HTTPS in eDirectory allow SSLv3 for secure communication, and SSLv3 has been found to have protocol vulnerability as per CVE-2014-3566. After applying the Appliance patches, ensure that you disable SSLv3 to prevent POODLE security vulnerability.
To disable SSLv3 through LDAP, add number 128 to the ldapBindRestrictions attribute on the LDAP server object.
When syncing users from an external LDAP source, the processor utilization increases if you try to import 10,000 users.
The reason for this behavior is that the User Sync is scheduled to run every 8 minutes, by default. Therefore, each time the User Sync is started, which is every 8 minutes, the processor utilization increases to around 50%, and remains in that state for up to 5 minutes. The utilization might further increase if you import over 10,000 users.
To workaround this issue, you can change the sync interval by editing the crontab file.
Launch the crontab file located at /etc/crontab.
Browse to the line where the sync interval is set to 8 minutes.
# run iprint migrate every 8 minutes
*/8 * * * * root /usr/bin/python /opt/novell/iprintmobile/python/migrate/migrateUsers.pyc >> /var/log/ipmigrate.log 2>&1
Change the time to the desired time interval.
For information on scheduling time intervals for cron jobs, see the article about Cron on Wikipedia.
When using iPrint Appliance 1.0, you may not be able to create a backup if you have a Driver Store in excess of 6 GB. This is caused due to lack of disk space in the virtual machine.
To workaround this issue, you must add an additional hard disk to your virtual machine, then backup iPrint Appliance 1.0. If your Drive Store is 10 GB in size, then you must add an additional 20 GB of hard disk space. The hard disk space must be twice the size of the resdir folder.
Power off the iPrint Appliance 1.0 VM.
In the vSphere client, right-click the iPrint Appliance 1.0, then click Edit Settings.
Click Add.
Select Hard Disk, then click Next.
Select Create a new virtual disk., then click Next.
Specify the Disk Size, then click Next.
Click Next on the Advanced Options screen.
Click Finish.
Power on the iPrint Appliance 1.0 VM.
Create a partition using the fdisk command.
Run the command fdisk /dev/<disk name>.
When prompted for a command, specify n, then tap the Enter key.
For partition, specify p, then choose the default option.
When prompted for a command, specify w.
Create a file system using the command mkfs.ext3 /dev/<disk name>.
Stop the jetty service.
Mount the /tmp folder to the newly added hard disk using the command mount /dev/<disk name> /tmp/.
Start the jetty service.
After completing the procedure mentioned above, try backing up iPrint Appliance 1.0.
When upgrading iPrint Appliance 1.0 to a higher version, the license file does not get automatically exported to the newer version. This issue is caused because the license file is not automatically backed up on the iPrint Appliance 1.0.
To work around this issue:
You must manually copy the license file located at /opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/ on iPrint Appliance 1.0 to your system.
Launch the Managment Console of iPrint Appliance 1.1.
Go to iPrint Appliance Configuration > License, then upload the backed up license file.
When upgrading iPrint appliance using the iPrint Appliance Management Console, the progress bar continues processing. This issue is caused by the automatic update feature of the web browser.
To work around this issue, close all open browser sessions, relaunch the browser, then wait for the browser update to complete before upgrading iPrint Appliance.