[SOLVED] package problem: tis-generate-new-uuid

[t.heroult]

Good morning
I have a handful of machines which, after OS deployment, end up with the same UUID.
So I tried tis-generate-new-uuid but I got an error:

Code: Select all

Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4235, in install_wapt
    exitstatus = setup.install()
  File "C:\Windows\TEMP\waptx54g8mwl\setup.py", line 9, in install
TypeError: list indices must be integers or slices, not str

Any idea what's wrong?
Thanks in advance !

[jpele]

Hello,
I'm currently reworking this package; quite a few things in it seem to be outdated.

Regards,
Jimmy

[jpele]

The package tis-wapt-generate-random-uuid-if-needed was created to replace tis-generate-new-uuid, can you test it?

[t.heroult]

Good morning
There are several points to raise.
Regarding the package, I tested it by adding the system UUID of a PC (Windows 10 Pro) to the package, the result is:

Code: Select all

UUID BIOS: 6f078c2d-a7db-47b9-b5d0-f8041457b00c
UUID WAPT: WINDOWSIT.monentreprise.local
New UUID WAPT: rnd-d66b48ce-0605-4aef-88fa-9313f19c7a04
waptservice will restart in 2mins.

Well, even after rebooting, the WAPT UUID hasn't changed (nor any other for that matter) and is still WINDOWSIT.mycompany.local, so it doesn't seem to have had any effect

In any case, there is clearly a misunderstanding, because it is not the wapt UUID, but the system UUID that is duplicated on the deployed machines.
They do have different WAPT UUIDs and therefore are not confused in WAPT.
What I was looking to do was change the Windows UUID, not the WAPT UUID (in this case, it didn't work either anyway).

[jpele]

Hello,
it is not possible to change the machine's UUID; this is a manufacturer error.
Regards,
Jimmy

[t.heroult]

Yes, I looked into it a bit and that's what I understood.
Thank you