The DHCP option 100 "Middle Tier server" is configured and
added on the scope under "Other DHCP Options".
The values set for option 100 are two operable IP-addresses, reflecting
two running Middle Tier servers

When a client gets it's DHCP-address, the registry values for
the Middle Tier server is corrupted.
The registry keys hosting the values are (reference TID 10092121 for

HKLM\Software\Novell\ZENworks\<dword> MiddleTierDHCPOptionNumber
(we use decimal value 100 as Option number)

HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress
(we use and in the DHCP-scope)

But the Middle Tier login fails after DHCP delivery.
Looking at the registry on the client, the string values for the
MiddleTierAddressis corrupted. Instead of showing the two correct
IP-addresses, it shows just messed up characters like squares,
bars and other cryptical signs at the end of the enrty.

Without a DHCP delivery, things works ok, if the ZfD Agent is configured
with the Middle Tier DNS name.

The registry key holding the DHCP-distributed Middle Tier address is:
HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress

After DHCP-distribution, in the Middle Tier login dialog, the squares
appears like bold vertical bars. Middle Tier login then fails.

Also found a related TID # 10089967.