Select Page

ZENworks for Toasters

This goes back a long, long way.

Summer 2000 I was talking to an audience of customers and resellers in South Africa about how the directory, identity-driven management and ZENworks specifically could manage anything. The concepts of management by exception and the extensibility of the Novell Directory Services (as it was then known) were ideal for this.

We were joking around concepts of management – and we came on ZENworks for Toasters.

Some Java fun in ConsoleOne – and we had a cool demo plugin for our internal Systems Engineers.




ZENworks Configuration Management – imaging, PXE and DHCP

ZENworks imaging can use the Preboot eXecution Environment – PXE – to start it’s imaging engine.

When the imaging server components (TFTP server, Imaging engine, Proxy DHCP) are running on the same server as the DHCP server there are certain configuration changes that need to be made.

Read the ZCM10 documentation for more.

Three steps to happiness – I’ll document this for Windows; SLES is broadly similar.

– set the Proxy DHCP to run correctly
– set Proxy DHCP to start automatically
– add DHCP option tag 60 to the DHCP scope


ZENworks Configuration Management – building a custom agent deployment package

A long title for a short post.

The default agent deployment packages created during Primary Server installation are hard coded to the Fully Qualified DNS Name and the static IP address of your server. All well and good for a single server; but what about:

  • DNS round robin
  • servers behind static NAT
  • etc

Here’s how to build a custom agent deployment package with either no server details (add them via registration at deployment time) or with a single DNS name.