kevinorritt Absent Member.
Absent Member.
5311 views

zac reg -g

I'm after some inspiration from the forum! I have a reasonable number of machines on my ZCM deployment that have the same guids (never did get to the bottom of why it happened), I was thinking I could try and put a bundle together that would deploy a script to those devices to generate a new guid on the workstation the re-register. I was thinking that the new -g switch in zac reg might help?

Has anyone done this, or got any suggestions on how I can achieve it?
Labels (2)
0 Likes
7 Replies
bronislav1 Absent Member.
Absent Member.

Re: zac reg -g

kevinorritt;1890286 wrote:

Has anyone done this, or got any suggestions on how I can achieve it?


I have same issue in some pc's. I was apply zenworks-registartion.war path and completely unregister and then register problem workstations with zac reg -g. It solve but, may be not need to apply zenworks-registartion.war path.

Anton Ilin
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: zac reg -g

I would definitely recommend that patch.
It helps prevent duplicate guids and device registration issues.

A brief overview is that the zenworks-registration.war file was updated to
resolve dupe guid issues, but the fix caused registrtion issues in some
cases.
The file was then updated to correct the cases where the dupe fix causes
registration issues.

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"bronislav" <bronislav@no-mx.forums.novell.com> wrote in message
news:bronislav.41ssmn@no-mx.forums.novell.com...
>
> kevinorritt;1890286 Wrote:
>>
>> Has anyone done this, or got any suggestions on how I can achieve it?

>
> I have same issue in some pc's. I was apply zenworks-registartion.war
> path and completely unregister and then register problem workstations
> with zac reg -g. It solve but, may be not need to apply
> zenworks-registartion.war path.
>
>
> --
> Anton Ilin
> ------------------------------------------------------------------------
> bronislav's Profile: http://forums.novell.com/member.php?userid=25388
> View this thread: http://forums.novell.com/showthread.php?t=392972
>



0 Likes
kevinorritt Absent Member.
Absent Member.

Re: zac reg -g

Thanks guys, I will apply the zenworks-registration.war fix.

Once I've done that, if I run the following command (on an affected device) as a script though ZCC, should the targeted device re-register with a new guid? If it does, what will happen to the other device that was sharing its original guid, would it continue to use the original or would it lose association with the server?

zac reg -g -k guidfix -u username -p password [url]https://servername[/url]

What do you think, could it really be that straight forward.......?
0 Likes
bronislav1 Absent Member.
Absent Member.

Re: zac reg -g

kevinorritt;1890817 wrote:
Thanks guys, I will apply the zenworks-registration.war fix.

Once I've done that, if I run the following command (on an affected device) as a script though ZCC, should the targeted device re-register with a new guid? If it does, what will happen to the other device that was sharing its original guid, would it continue to use the original or would it lose association with the server?

zac reg -g -k guidfix -u username -p password https://servername[/URL]

What do you think, could it really be that straight forward.......?


"zac reg" only register new device.
If you want to reregister devices with the same guid, you need first to unregister this both devices and than register it with zac reg -g.

Anton Ilin
0 Likes
gerwil1478
New Member.

Re: zac reg -g

Agree - reregister both devices. I found the one 'left behind' had issues later on so reregister all duplicates.
Cheers
0 Likes
kevinorritt Absent Member.
Absent Member.

Re: zac reg -g

Probably a bit simple, but do you think if I created a bundle to put this .bat file in the 'all users' startup folder it would unregister devices, create a new guid and re-register them for me after a few reboots?

@ECHO OFF
IF EXIST "C:\zen\zen1.set" GOTO REGISTER
MD C:\ZEN
zac unr
ECHO DONE>> C:\zen1.set
GOTO COMPLETE
:REGISTER
IF EXIST "C:\zen\zen2.set" GOTO REMOVE
zac reg -g -k key -u username -p password https://servername
ECHO DONE>> C:\zen\zen2.set
GOTO COMPLETE
:REMOVE
DEL "C:\Documents and Settings\All Users\Start Menu\Programs\Startup\zen.bat"
ECHO DONE>> C:\zen3.set
:COMPLETE
0 Likes
toddk_cityofnor Absent Member.
Absent Member.

Re: zac reg -g

I have had this same issue with a number of devices in my environment.

Using the zac reg -g works great in registering the device with a new guid, no reboot needed.

As for the "other" device with the dupguid it could be lost in the bit bucket somewhere. I have found that if two machines with the same guid show up then the last one to refresh/talk to the zen server wins. So I guess once you have fixed the guid on one machine it is possible that the other will be ok. In my case I have always just run the zac reg -g on both devices that had the dup guid.

Ken

kevinorritt;1890817 wrote:
Thanks guys, I will apply the zenworks-registration.war fix.

Once I've done that, if I run the following command (on an affected device) as a script though ZCC, should the targeted device re-register with a new guid? If it does, what will happen to the other device that was sharing its original guid, would it continue to use the original or would it lose association with the server?

zac reg -g -k guidfix -u username -p password https://servername[/URL]

What do you think, could it really be that straight forward.......?
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.