Here's a little warning. I just applied July 2013 Scheduled Maintenance for
OES11SP1 to a 3 node cluster. Then I noticed the iprint cluster resource
went comatose when migrated to a patched server as idsd failed to start
saying it wasn't configured.

Upon investigation I found that the Scheduled maintenance included iPrint
patches. I thought that iPrint had its own update package and previously
this would just fail unless the cluster resource was loaded on the node in
question, as the iprint clients normally get updated and the iprint ini.
This time I didn't have iPrint mounted until I got wise.

What the patch did on my broken nodes was fairly straightforward to fix once
I spotted it (assuming I found everything). The 3 symbolic links that get
created as part of the iprint_nss_relocate script had got mangled:
/etc/opt/novell/iprint/conf was pointing to
/media/nss/IPRINT/var/opt/novell/iprint instead of
/var/opt/novell was pointing to /media/nss/IPRINT/var/opt/novell/log/iprint
instead of /media/nss/IPRINT/var/opt/novell/iprint
/var/opt/novell/log/iprint was pointing to 633 instead of
/media/nss/IPRINT/var/opt/novell/log/iprint , as if a chmod argument had
been applied instead of a filename.

Hopefully this will aid anyone about to patch, or anyone else who got caught
by this. As this is likely to hit cluster only, i posted here instead on
the iprint forum