Novell Cool Solutions

ZENworks Configuration Management – imaging, PXE and DHCP



By:

January 22, 2008 3:52 pm

Reads:16,655

Comments:0

Score:Unrated

Print/PDF

This is a re-post of an earlier article posted on Novell Cool Blogs.

ZENworks imaging can use the Preboot eXecution Environment – PXE – to start its 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

Setting Proxy DHCP to co-exist with the local DHCP server

Edit %ZENWORKS_HOME%\conf\preboot\novell-proxydhcp.conf

Change the line: LocalDHCPFlag to

LocalDHCPFlag = 1

SNAG-0007

Setting Proxy DHCP service to start automatically.

From the Services Control Panel:

SNAG-0001

SNAG-0002

Click on Start:

SNAG-0003

From the command line:

sc config "novell proxy dhcp service" start= auto
[SC] ChangeServiceConfig SUCCESS

net start "novell proxy dhcp service"
The Novell Proxy DHCP Service is starting.
The Novell Proxy DHCP Service started successfully.

Adding DHCP option tag 60

From the command line:

netsh
dhcp server
add optiondef 60 ClassID STRING 0 PXEClient

Next add the new option to the scope; either per scope or globally for the server:

SNAG-0004

SNAG-0005

Now you should be set. Test PXE booting from a client machine – and you should be happy.

As a bonus – on multi-NIC or multi-homed machines – you do need to specify the listening IP address in the configuration files for the Preboot services.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

ZENworks Configuration Management – imaging, PXE and DHCP

coolguys

By:

November 8, 2007 5:08 pm

Reads:11,127

Comments:2

Score:Unrated

Print/PDF

By Martin Buckley

ZENworks imaging can use the Preboot eXecution Environment – PXE – to start its 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

(more…)

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

2

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

2 Comments

  1. Off topic—

    Martin, I love your posts and anxiously look forward to them. Would you consider doing a post on the current version of ZCM and what environments you can and can’t deploy it in? Also, could you post something (on your blog or this one) about the 10.1 update and how it deploys (or doesn’t) through system update?

  2. By:Dave Lee

    You will love imaging using PXE… Until… You find that it the imaging part of ZCM and Zen7 has poor hardware support that Novell is SLOW to update… Its a pain to have to add your own drivers… I think this comment from Novell customer in the imaging forums that sparked a massive thread says it all

    “Novell has managed to make updating of drivers in Zen Imaging so
    complicated and frustrating that it is quickly becoming a worthless
    product.”

    Even with a new version of Zen its still rubbish

Comment

RSS