Filtered Index

Over the past couple of months, I have been involved with migrating remote NetWare servers to Open Enterprise Server 2 (OES2) Linux. During this time, there are some lessons that have been learned that hopefully this article will be able to help you, the reader, perform your own migrations more smoothly and avoid some of the pitfalls we encountered.

If you're not familiar with iPrint, it is one of the nicest end-user technologies I think Novell develops. On Linux I find the technology even more appealing.... no rebooting, no restarting applications to use printers, nothing strange like that. With that said iPrint wasn't developed originally for a 64-bit platform, and wasn't developed for Linux first. That it works so well just makes me that much more pleased.

Frequent-contributor Mike Faris has rewritten one of his most popular articles, so you don't have to know about previous software packages to follow his steps. He has plans to write additional migration articles as well, which you will find here. This is what makes Cool Solutions so cool. Smart people, sharing. Thanks Mike!

We were running out of file cache memory on our 6-node NetWare cluster, and we didn't have any money for new 64-bit servers and OES 2. Xen virtualization of NetWare allowed us to move certain services off of our larger cluster onto a pair of smaller clusters, on just two
servers. This allowed us to spread the file-serving load across all 6 nodes of the old cluster, and ease our memory problems. This is how we did it.

This article is about the migration of a OES cluster from one storage area network (SAN) to a new SAN.

Canon iPrint "Job Accounting" and "Get Device Status" Problem Solved

When using iPrint to print to a range of Canon corporate printers the "Job Accounting" and "Get Device Status" features do not work. The following solution will allow the features to work correctly.