Select Page

Firefox and ZENworks

There’s a nice post from Ben Goodger (lead Firefox developer) on enterprise deployment of the browser. Most of the comments are Windows specific – but it’s good stuff.

One of the things I’ll try and find time to do is take this great data and make it ZENworks relevent. If someone has more time feel free to post it to Cool Solutions!

I’ll also look at how this data can be used with ZENworks 7 Linux Management; deployment of the browser and then locking it down.

ZLM 6.6.1 and Oracle

I posted a while ago on getting ZLM 6.6.1 to work with Oracle. Just some additional clarification in the docs.

Oracle database support is limited to the following configuration:

* An Oracle 9i database running on any platform supported by the Oracle database.
* A TCP listener running on your Oracle 9i database, which can be contacted by your client using onames or tnsnames.
* ZENworks Linux Management installed on Red Hat Enterprise Linux 3 Advanced Server.
* The Oracle 9i client libraries installed on your ZENworks Linux Management server. The recommended Oracle client is Oracle 9i client, Release 2.

We recommend working with your Oracle database administrator for database installation, management, and other Oracle-related issues.

Oracle 10g support on SLES will be part of ZLM 7 SP1.

ZLM 7 mirror – zlmmirror – how to

Here are some examples of ZLM 7 ZLMmirror configurations – fresh from cvs.

There are several key changes to mirroring from ZENworks 6.x Linux Management or Red Carpet Enterprise:

– a single configuration file for all mirror services
– configuration file is now an XML document rather than a conf file

Examples will be given for mirroring from RCE/ZLM 6.x (such as update.novell.com), YaST Online Update, Red Hat Network and finally ZLM 7 upstream services.

(more…)

ZENworks Linux Management – Cache licenses

I’ve been asked about ZLM cache licenses.

These are enabled in two places – in the base server.key license file; also with activation licenses for the caches.

First step is to check your server.key enables cache support

The server.key must have a line:

< caches > some number < /caches >

If the server.key does not have this line you will need a new server.key. Get this from Novell.