Use a single GUID per machine in a TDPDOM WIN86 environment

Problem title
GUID flapping (repeated ANR1639I messages)

Environment:
Product or Service: Data Protection for Domino Windows 7.1.W
Component ID: 5698DPDAP

VMware vSphere 5.5 U3
Windows 2008 R2 x64 Standard Edition
Lotus Domino 8.5.2 FP4 x32
TSM server 6.3.5
TSM BA client 7.1.2.3
TDP for LD 7.1.0.2 X86_X64
MS Active Directory


Problem description
After investigating the problem with L2 it was apparent that the GUID flip is done because the scheduler service, running in 64-bit mode, and the TDP, running in 32-bit mode, are using the same node name.

In this particular environment it seems that the GUID is not bound to the node name, but to the bit-mode on this system.
L2 support said this behavior is working as designed.
However, in this case I would say there is a mismatch between design and documentation, because the TSM documentation describes the GUID as being a means to uniquely identify a machine regardless of how many TSM nodes may connect to the TSM server from it.
From a couple of places on the internet, including the Changing the client GUID on Windows tehcnote (http://www-01.ibm.com/support/docview.wss?uid=swg21616058) that contains the regedit stuff performed in the PMR:

Globally Unique Identifier (GUID)
An algorithmically determined number that uniquely identifies an entity within a system.

Globally Unique ID
The GUID identifies the host computer on which the node is located.

The GUIDs are intended to help uniquely identify a particular machine (for reporting purposes), regardless of how many different node names are used on the machine, or which network adapter on the machine is used to connect to the Tivoli Storage Manager server.


Given the above, the TDPDOM WIN86 implementation is out of line regarding the above nature and purpose of the GUID and should be ammended to use a single GUID together with the "normal" baclient, just like the TDPDOM 64-bit does.

Thank you,
Best regards,
Petre Huica