Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
mnorthSACS Absent Member.
Absent Member.
2590 views

machine GUID getting appended to alias part 2

We tried creating an image with the ZEN agent installed. We ran "zac fsg -d" that would clean out unique identifiers for the agent(on the image), allowing us to deploy an image with the agent ready to go (except no GUID assigned). we kept seeing the appended GUID on the hostname, so we deleted the hosts from ZCC, and tried re registering. This did not work so we used "zac unr" then "zac unr -f" to locally unregister the host. We then used "zac reg -g (server address)". At this point the host name was GUID free when viewing the agent properties from the local machine, but did not appear in ZCC. We didn't touch it for 2 weeks, and now only 7 hosts show up in ZCC. There is one GUID that follows the last host to be "accessed" in ZCC. also there is a duplicate hostname for every alias witht he GUID appended that does NOT have the GUID appended (ex. PC01-f18b345f6sht54, and PC01). It seems the serial may be causing this, but I am at a loss now. Help!!!!
Labels (2)
0 Likes
3 Replies
marklar23 Absent Member.
Absent Member.

Re: machine GUID getting appended to alias part 2

I think that I ran into the same problems when I first tried deploying ZCM in my environment and started using imaging. I had a great response to a thread but I can't remember which one but did copy and paste the instructions out of it. I had all of my workstations come in under the same GUID and was unable to use patch management or use ZEN to deliver apps until I fixed them. Give this a try...

On the computer that is the image source:
Install OS, agent, apps, updates, etc etc etc
From the command line run the following commands
1. zac unr (unregisters workstation from zenworks)
2. zac cc (Clears Zen Cache)
3. zac fsg –d (Clears Zen GUID info.)

Delete the following files from C:\Program Files\Novell\Zenworks\Conf
1. Devicedata (Also delete devicedata.sav if exists)
2. Deviceguid (Also delete deviceguid.sav if exists)

Run C:\Program Files\Novell\Zenworks\bin\preboot\ziswin.exe
1. Click Edit and clear Image-safe Data
2. Save changes and Close ziswin. Click No if prompted to save again when closing.

Run your sysprep and let the system shut down and restart into ZEN imaging maintenance mode.
Once booted and at the new command line type the following commands
1. zisedit -c (clears ZEN Cache again in case it grabbed anything new)
2. img (opens the zen imaging window and lets you take or multicast your images)

Once your systems have restarted and you check the properties of the ZEN agent it should say "unmanaged" at the command prompt type in
zac reg -g [serverURL] to make the workstation register and regenerate a new GUID when it connects to the server.

I've gone as far as creating a bat file for connecting and disconnecting workstations from the ZEN server because I found it to be easier than trying to remember the commands every time and having to type in credentials for registering. For example here are what I used

ZenDisconnect.bat- zac unr
ZenConnect.bat- zac reg -g -U [ZenAdminUsername] -P [PasswordforNameUsed] [url]http://[zenURLorIPAddress][/url]

Hope this helps.
0 Likes
Kelvarr Absent Member.
Absent Member.

Re: machine GUID getting appended to alias part 2

If you don't want to mess with having to do a zac reg -g [serverURL] command, the following CoolTool has information on getting the ZEN Adaptive Agent in an Image:

ZCM Imaging - Installing the ZEN Adaptive Agent in the image | Novell User Communities

This is what I use, and I have no problems with newly imaged machines.
0 Likes
mnorthSACS Absent Member.
Absent Member.

Re: machine GUID getting appended to alias part 2

We took your suggestion to prep the image and modified it to "re-register" a lab of workstations that were having an identity crisis.

marklar23;2164743 wrote:

On the computer that was already imaged and unsucessfully registered with a GUID that would append itself to the most recently registered machine:
From the command line run the following commands
1. zac unr -f (unregisters workstation from zenworks)
*Had to run this command as many as 4 times, until machine sucessfuly unregistered with the zone AND locally).
2. zac cc (Clears Zen Cache)
3. zac fsg –d (Clears Zen GUID info.)

Delete the following files from C:\Program Files\Novell\Zenworks\Conf
1. Devicedata (Also delete devicedata.sav if exists)
2. Deviceguid (Also delete deviceguid.sav if exists)
* the .sav files were the only ones in the folder.

Browse to C:\Program Files\Novell\Zenworks\bin
1. delete the conninfo folder (to confirm the correct serial number was recognized as opposed to the S/N from the image source.)
*This file re-creates itself when you register the machine.

Run C:\Program Files\Novell\Zenworks\bin\preboot\ziswin.exe
1. Click Edit and Modify Image-safe Data
2. Remove the values in Object Name and Object ID fields.
2. Save changes and Close ziswin. Click No if prompted to set Just Imaged flag.

Restart the machine.

Once your systems have restarted and you check the properties of the ZEN agent it should say "unmanaged" at the command prompt type in
zac reg -g [serverURL] to make the workstation register and regenerate a new GUID when it connects to the server.


Thank you so much for sharing your knowledge. Now we are going to try getting it on an image (the right way) and test it out.
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.