Unable to image / re-image a once known workstation

[socc1]

So I am trying to re-image my test workstation again and it's not getting the bundle (No work to do). PXE booting and TFTP is all working just fine. Also if I try to image a workstation fresh out of the box that also works just fine. Now I have deleted the workstation object by finding it in the ZENworks console under devices, workstations and this did not help. I have wiped the hard drive partitions, run zisedit -r and zisedit -c with no luck. Current version of zcm 11.3.1, single ZENworks server on Windows 2008 R2.

At this point I am guessing ZENworks still knows about this workstation and will not send down the bundle. Help! Please! 😄

[Anonymous_User]

Socc,
> So I am trying to re-image my test workstation again and it's not
> getting the bundle (No work to do).

How is this set up? Image manually assigned to WS or rule-based
imaging?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

[socc1]

This would be hardware rule based. I deleted the workstation out of ZENworks. I also have remove all of the rule sets and just tried one at a time for this system that will not image. No luck. 😞

[socc1]

I have now pulled the original hard drive and put a new one in the workstation I can't seem to re-image. This did not help. It still says No Work To Do. What log files should I be checking on the ZENworks server for detailed issues?

[Anonymous_User]

Socc,

check the preboot logs, see what the device is "seeing"...

--

Shaun Pond (now working for ENGL)
newly reminted as a Knowledge Professional

[nop19832]

socc wrote:

>
> So I am trying to re-image my test workstation again and it's not
> getting the bundle (No work to do). PXE booting and TFTP is all
> working just fine. Also if I try to image a workstation fresh out of
> the box that also works just fine. Now I have deleted the
> workstation object by finding it in the ZENworks console under
> devices, workstations and this did not help. I have wiped the hard
> drive partitions, run zisedit -r and zisedit -c with no luck.
> Current version of zcm 11.3.1, single ZENworks server on Windows 2008
> R2.
>
> At this point I am guessing ZENworks still knows about this
> workstation and will not send down the bundle. Help! Please! 😄

Hi

How do you deploy this imaging bundle to unknown devices? What are the
rule-set?

--
Niels
I have always liked... Cowabunga!

If you find this post helpful, please show your appreciation by clicking
on the star below.
A member must be logged in before s/he can assign reputation points.

[socc1]

I have three hardware rule sets for testing. Two for BIOS asset tag numbers and one rule for System Manufacturer. I was even able to push a bundle image to a VMware workstation via PXE boot.

[hschoene]

maybe there is a second ws-object for this ws with a different name ?
next you can try to restore this ws with hardware-rules and the "force"-switch in the rule("Force Download (even if this image matches the most recently installed)") or try to replace the nic.

[socc1]

Changed the hard drive and changed the NIC with no luck. Also I checked the box for (Force Download) for the matching hardware rule.

[Anonymous_User]

Socc,
> Changed the hard drive and changed the NIC with no luck. Also I checked
> the box for (Force Download) for the matching hardware rule.

Have a look at the logs as Craig suggests. They tend to be quite
revealing.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

[socc1]

Are you talking about the following log files? If so they seem to be no help as of right now. This could be do to I don't know what I am looking for at this time.

novell-pbserv.log
novell-proxydhcp.log
novell-tftp.log
novell-zmgprebootpolicy.log

[Anonymous_User]

Socc,
> Are you talking about the following log files?

Yes. novell-pbserv.log and for starters as that is the process that
determines whether there is work to do. You need to yank up the logging
level though.

%ZENWORKS_HOME%\conf\preboot\novell-pbserv.conf
%ZENWORKS_HOME%\conf\preboot\novell-zmgprebootpolicy.conf

Do that, restart the zenserver processes and retry the operation

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

[socc1]

OK, I will turn up the logging and try again within the next day or two and post back.

[Anonymous_User]

Socc,
> OK, I will turn up the logging and try again within the next day or two
> and post back.

FWIW, the definitive guide to troubleshooting is the material from ATT311
(iirc) from Brainshare a few years back. Let me see if I can get
specifics. Only have a printed copy I got there (judging from it being in
Letter format and not A4)

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

[socc1]

OK, I configured the logging to level 3 for those two .conf files. Restarted the services , pxe booted the workstation to the ZENworks Img maintenance option and pressed F9. No work to do. So now looking at the log files I really don't' see much of a difference.

In the novell-pbserv.log file I see a line that show the following:

[(RNT) Error String:] [] [] [] [Imaging]

So far I can't find anything that jumps out at me. There is also another line that shows [ (LC) open*** connection, server address, 0.0.0.0 [] [] [] [Imaging]. Don't know if that is OK?

Thank you.