Highlighted
sgrespan Absent Member.
Absent Member.
668 views

Hardware rules for imaging not working

Hello,

since 've installed Zenworks 2017 i'm struggling against hardware rules for imaging. I'm trying to make them work for new devices but I always obtain this message:

Contacting Zenworks Preboot Policy Server...Done
PXE-M0F - Exiting PXE Rom

The message is the same with different computers (HP) and criteria (Serial number or Mac Address). The same machines have always been recognised by preboot services in my old Zenworks 11.4. I've no problem if I press CTRL+ALT, enter the PXE menu and start Zenworks Imaging Manteinance.
I guess i've forgot something in preboot configuration but i can't figure what, this is what i've dome in ZCC:

1) in Bundles -> Images i created a Zenworks Image bundle ("HP_Image")
2) in Configuration -> Device Management -> Preboot Services i created an hardware rule associated with the bundle and added the serial number of my PC.

Is there something i can do to understand what is missing?

Thanks

Stefano
Labels (1)
0 Likes
8 Replies
Micro Focus Expert
Micro Focus Expert

Re: Hardware rules for imaging not working

Which Version of ZCM 2017 are you running?
There were some issues with HW Imaging Rules in early Versions of ZCM 2017.
I don't recall the exact versions, since it has been fixed for quite a while.
0 Likes
sgrespan Absent Member.
Absent Member.

Re: Hardware rules for imaging not working

It's 17.4, i think it's the last update.
I've even opened the novell-zmgprebootpolicy.log and seen that "work assigned: 0" but i can't understand the source of the problem (my rul is now based on BIOS serial number)

[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [30501] [] [zmgtool] [] [Received an OPCODE_OPEN_SERVICE packet from 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [30501] [] [zmgtool] [] [ Setting protocol version for 10.62.x.x to 2] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [30501] [] [zmgtool] [] [The selected port is 46810] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [30501] [] [zmgtool] [] [ Sent an OPCODE_OPEN_SERVICE ACK packet to 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Thread started for 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Received an OPCODE_REQ_CUSTOM_DATA_SIGNATURE packet from 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:14.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Sent an OPCODE_REQ_CUSTOM_DATA_SIGNATURE ACK packet to 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Received an OPCODE_REQ_PXE_MENU packet from 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [MACAddress=aa:bb:cc:dd:ee:ff] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [FirmWareType:BIOS64] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [menu:MACAddress=aa:bb:cc:dd:ee:ff] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Connecting to Preboot Server at 10.62.x.y] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [The PXE menu state is HOTKEY_ONLY] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [The PXE menu file is pxemenu.txt] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Menu policy: Hotkey
Menu name: pxemenu.txt
New custom data: 0
Referred: 0] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:15.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Sent an OPCODE_REQ_PXE_MENU ACK packet to 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Received an OPCODE_REQ_CFG_NAME packet from 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [FirmWareType:BIOS64] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Connecting to Preboot Server at 10.62.x.y] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Work assigned: 0
CFG name:
New custom data: 0
Kernel parms:
Referred: 0 for 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Sent an OPCODE_REQ_CFG_NAME ACK packet to 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Received an OPCODE_CLOSE_SERVICE packet from 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [ Sent an OPCODE_CLOSE_SERVICE ACK packet to 10.62.x.x] [] [] [] [Imaging]
[DEBUG] [05/14/2019 17:33:18.000] [30501] [zmgtool] [45385] [] [zmgtool] [] [Thread ended time for 10.62.x.x] [] [] [] [Imaging]
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Hardware rules for imaging not working

Thanks.....Let me ask about....
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Hardware rules for imaging not working

And just to confirm, these are completely "New" hardware devices that have never part of your current zone.
Imaging Rules will not apply if there is a device object in the Zone with matching hardware values.
0 Likes
sgrespan Absent Member.
Absent Member.

Re: Hardware rules for imaging not working

They're not completely new in the zone. I imagined it manually and they have been parted of it until some days ago. Now i deleted them because i want to implement the auto-imaging with preboot services
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Hardware rules for imaging not working

That may be part of the confusion........
Any Device that is part of the Zone, needs to be assigned the work through it's device object.

If a Device is already a device in The Current Zone or another Zone, then it will not automatically image based on the rules.
The Device's status about membership in the current or other Zone is Based on the ZENworks Information Data it sends to the imaging server.

I'm not 100% sure of what behavior to expect, because the expected process to image a device that exists in your zone is to assign imaging work to that device, not delete the object.
Clearing the ZENworks Information Safe Data on the Device now that is has been deleted from the Zone may do that so they will image.

#1 - Create Hardware Based Rules to automatically image new devices. If there is a Universal Image, this may be something quite simple so that everything matches.
Or you may have differnet images based upon Make, Model, etc....then you set the rules to check for that.
Checking for "Serial Number" would be quite unusual.

#2 - One the Device is IN the zone, then you simply assign an Imaging Bundle to that device and next time it boots, it detects the assigned work and applies it.
No need to Look up the Devices Serial Number, Create an Imaging Rule for that Number, etc....





sgrespan;2499832 wrote:
They're not completely new in the zone. I imagined it manually and they have been parted of it until some days ago. Now i deleted them because i want to implement the auto-imaging with preboot services
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Hardware rules for imaging not working

And FYI...I just confirmed with a co-worker that Yes, Clearing ZISD would be needed since the device used to be in the zone...but you need to look at your process because Deleting Devices to image them is not how it should be done.
0 Likes
sgrespan Absent Member.
Absent Member.

Re: Hardware rules for imaging not working

Thanks Craig, I've just tested your solution and it works: simpler an better 🙂
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.