According to the Zenworks Command line utilities reference https://www.novell.com/documentation...a/bb15p2z.html
There exists an option to register a device with a new GUID by doing the following...

register (reg) [-g] [-k <key>] [-u <username> -p <password] <ZENworks Server addressort>
Registers the device in a Management Zone.

You can use the following options:

g - Lets you create a new device object with a new GUID and password for the device if you have multiple devices with the same GUID. When you register a device by using this switch, all the associations (policies and bundles) assigned to the original device object are removed. You cannot use this option to create a new GUID for a Primary Server or a Satellite device. The local user must have Local Administrator rights to use this option.

I would like to know if it is possible to have such a command line option for the agent installation. So built into the agent installer, a command line option to force the agent to register with a new GUID.

We are having CONTINUOUS problems with the above scenario. When we move devices from one computer lab to another and re-image the device, Zenworks keps trying to assign the same GUID to the device and this mixes up our Dynamic Workstation groups, which then affect the applicable policies to each device.

I would like to know if there is an option to tell the installer to stop remembering the GUID and simply register the device with a new guid on agent installation.
This way we can build that into the post imaging scripts which install the zenworks agent.