DON'T install any Zenworks component on an OES2SP3 DSfW server!!!!

Question

Although not mentioned anywhere, this will kill kerberos authentication
for the DSfW server, because Zenworks sets the LD_LIBRARY_PATH to paths
including Kerberos libraries not compatible with DSfW (Xad) Kerberos.
Since ZCM 11.1 this is more crucial than before as every start of the
agent sets the path newly. Before SP1, this was only done during bootup
of the server, so you could unset that path before loading the XAD
things.
As this is known to NTS for almost 4 months it would be nice if that
information gets to the developers of ZCM and OES, to avoid
incompatibilities between those products.
W. Prindl

Answer 1

Given the current information level, I think, not starting or
deploying the ZCM agent is the only viable solution for now.
W. Prindl
craig wilson wrote:
>Actually in 11.1, other scripts are setting it too, so updating those
>files will not help. Not sure if others should be touched, so
>careful if u do.
>
>On 9/5/2011 1:41 PM, craig wilson wrote:
>>https://bugzilla.novell.com/show_bug.cgi?id=692548 seems to be the
>>ZCM defect.
>>
>>The one you referenced was the root issue native in the incompatible
>>server software that was not directly ZCM Related. (We did update
>>paths which could cause an issue as you stated.)
>>
>>It seems you can control the ZCM agent behavior to some extent, but
>>not sure if a complete fix will be there until the compatibility
>>issues on the server side are resolved between the various
>>components.
>>
>>"So as a workaround /etc/profile.d/novell-zenworks.sh and
>>/etc/profile.d/novell-zenworks.csh can be modified to remove the
>>setting of LD_LIBRARY_PATH."
>>
>>
>>
>>
>>On 9/5/2011 12:59 PM, W_ Prindl wrote:
>>>My SR nr was 10693389312 and there was created a defect # 692556.
>>>
>>>The initial encounter during upgrade to OES2SP3 was really
>>>catastrophic. Now after the update of ZCM from 11 to 11.1 I was
>>>already aware of the possible issues and could easily disable the
>>>startup of the agent after Kerberos errored out.
>>>
>>>Another strange issue I had during the upgrade to ZCM 11.1 was,
>>>that the update started to deploy itself to all managed devices
>>>despite I had set it to only delpoy itself to defined staging
>>>areas - but that could be a problem of the Web-interface not
>>>taking the correct inputs, because I had several FF hangs during
>>>that phase.
>>>
>>
>>