Absent Member.
Absent Member.
10016 views

ZCM 11.0 - Cumulative Agent Patch 1 - Known issues

Hey,

For those of you deploying this, please reply to this thread with issues you encounter and a few lines about your setup (eDir/AD usersource, Client OS and Server OS).

I ask this because I've tested the file prior to the release (and the earlier ZESM fixes), I've had negative results that impact the implementation of the fix.

The error I am getting after deploying this is a massive increase in the time the agent service takes to start up, up to 5 minutes extra on a relatively new computer (Dell Latitude E5410), making such things as login with new userprofile and the NWC increase dramatically.... When the service is started, it is however fixed as they say, regarding the Location Awareness engine that was my initial problem(The TID also lacks VMXNET 3 network controller from the affected)...

This is not an attack on Novell or anything, its just that I want more information from others, if its my setup or if its common, other issues etc. (I really want Novell to be more open though, so its easier to work with your products, and I hope they fix their RSS feeds!)


Best Regards,
Rune "TheFlyingCorpse" Darrud
Labels (2)
0 Likes
69 Replies
Absent Member.
Absent Member.

Chucks0,

did you copy in the update.xml file?

--

Shaun Pond


0 Likes
Absent Member.
Absent Member.

fancy! 😉
0 Likes
Absent Member.
Absent Member.

Theflyingcorpse,

that was one of the benefits of taking the cumulative approach. What I
expect to happen now is that "interim" FTFs, like the Patch Management
one I expect to release today, will just have the individual files, so
existing devices can be updated, and the MSIs will appear in the next
cumulative update. That makes it much quicker for me to put out the
FTFs, and for engineering to generate them

--

Shaun Pond


0 Likes
Absent Member.
Absent Member.

I finally got it to work after resetting file permissions on all of the files. Of course it doesn't fix the issue we are having (No agent login after ZCM 11 Agent update via System Update). The SR for this issue is 10683480211. Unfortunately, response has been very slow from Novell on this particular issue so progress has been very slow.

spond;2095418 wrote:
Chucks0,

did you copy in the update.xml file?

--

Shaun Pond
0 Likes
Micro Focus Expert
Micro Focus Expert

Did you do a file compare of all files, both CASA and ZCM Agent, between
an Upgraded and Cleanly installed agent?

Focusing on DLLs and EXEs, any differences?

On 4/12/2011 10:36 AM, chucks0 wrote:
>
> I finally got it to work after resetting file permissions on all of the
> files. Of course it doesn't fix the issue we are having (No agent login
> after ZCM 11 Agent update via System Update). The SR for this issue is
> 10683480211. Unfortunately, response has been very slow from Novell on
> this particular issue so progress has been very slow.
>
> spond;2095418 Wrote:
>> Chucks0,
>>
>> did you copy in the update.xml file?
>>
>> --
>>
>> Shaun Pond

>
>



--
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.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Absent Member.
Absent Member.

May I know Anyone facing slow performance / login after using cumulative Agent patch 1 ?
0 Likes
Absent Member.
Absent Member.

navyzone;2095885 wrote:
May I know Anyone facing slow performance / login after using cumulative Agent patch 1 ?


Yup! Use a proxy?

Anywho -> Try this to fix it:
On the affected machine:
- Create file %ZENWORKS_HOME%\bin\ZenworksWindowsService.exe.config
- Contents of file:
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>

- Reboot, check if its faster now.

The fix above skips checking the publishers "evidence", aka certificate which could be troublesome if you have network connectivity, but have a manual proxy change to get on the internet, like set the proxy server to proxy:8080 to get access.

This solved the low performance in my zone and the speed is now somewhat faster when starting the service, regardless if its patched or not. After patch its however a lot more stable and policies work after a hibernate for example 😉
0 Likes
Absent Member.
Absent Member.

Hi

Would you then recommend to wait for the sp1, if i'm going to choose between updating none or All of our clients? About 2500 clients...
Thanks

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
Absent Member.
Absent Member.

I noticed no speed difference using this fix. Running Cumulative Agent
Patch 1.

"theflyingcorpse" <theflyingcorpse@no-mx.forums.novell.com> wrote in message
news:theflyingcorpse.4s4ns2@no-mx.forums.novell.com...
>
> navyzone;2095885 Wrote:
>> May I know Anyone facing slow performance / login after using cumulative
>> Agent patch 1 ?

>
> Yup! Use a proxy?
>
> Anywho -> Try this to fix it:
> On the affected machine:
> - Create file %ZENWORKS_HOME%\bin\ZenworksWindowsService.exe.config
> - Contents of file:
>
> Code:
> --------------------
> <configuration>
> <runtime>
> <generatePublisherEvidence enabled="false"/>
> </runtime>
> </configuration>
> --------------------
>
> - Reboot, check if its faster now.
>
> The fix above skips checking the publishers "evidence", aka certificate
> which could be troublesome if you have network connectivity, but have a
> manual proxy change to get on the internet, like set the proxy server to
> proxy:8080 to get access.
>
> This solved the low performance in my zone and the speed is now
> somewhat faster when starting the service, regardless if its patched or
> not. After patch its however a lot more stable and policies work after a
> hibernate for example 😉
>
>
> --
> theflyingcorpse
> ------------------------------------------------------------------------
> theflyingcorpse's Profile:
> http://forums.novell.com/member.php?userid=31288
> View this thread: http://forums.novell.com/showthread.php?t=436516
>



0 Likes
Absent Member.
Absent Member.

I compared the files and didn't notice any differences. Running zenupdater manually on the client after a failed upgrade seems to fix it however I don't like the idea of having to do that 16,000 times.

craig_wilson;2095667 wrote:
Did you do a file compare of all files, both CASA and ZCM Agent, between
an Upgraded and Cleanly installed agent?

Focusing on DLLs and EXEs, any differences?

On 4/12/2011 10:36 AM, chucks0 wrote:
>
> I finally got it to work after resetting file permissions on all of the
> files. Of course it doesn't fix the issue we are having (No agent login
> after ZCM 11 Agent update via System Update). The SR for this issue is
> 10683480211. Unfortunately, response has been very slow from Novell on
> this particular issue so progress has been very slow.
>
> spond;2095418 Wrote:
>> Chucks0,
>>
>> did you copy in the update.xml file?
>>
>> --
>>
>> Shaun Pond

>
>



--
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.
0 Likes
Absent Member.
Absent Member.

If you are experiencing issues, I'd wager the resource cost of upgrading the machines versus the problems, if they are having any at the moment.

In my org, 860 pc's atm, 4000 more over the coming 2 months, will be deployed with the updated agent.
Those already setup with the old(840 at the moment), will get a special bundle unlike the official suggested way, that can be run at async times when it fits for the user. Spawn a separate cmd as system and do the update. There is no driverupdate in the CAP, which is why it works. 🙂
0 Likes
Micro Focus Expert
Micro Focus Expert

I'd recommend getting an SR opened so you can find what the difference
would be. the upgrade logs could be analyzed as well.

Most likely, there is one small issue causing major problems but once
the small issue is identified, a quick and simple targeted fix could
take place.

On 4/13/2011 1:06 PM, chucks0 wrote:
>
> I compared the files and didn't notice any differences. Running
> zenupdater manually on the client after a failed upgrade seems to fix it
> however I don't like the idea of having to do that 16,000 times.
>
> craig_wilson;2095667 Wrote:
>> Did you do a file compare of all files, both CASA and ZCM Agent,
>> between
>> an Upgraded and Cleanly installed agent?
>>
>> Focusing on DLLs and EXEs, any differences?
>>
>> On 4/12/2011 10:36 AM, chucks0 wrote:
>>>
>>> I finally got it to work after resetting file permissions on all of

>> the
>>> files. Of course it doesn't fix the issue we are having (No agent

>> login
>>> after ZCM 11 Agent update via System Update). The SR for this issue

>> is
>>> 10683480211. Unfortunately, response has been very slow from Novell

>> on
>>> this particular issue so progress has been very slow.
>>>
>>> spond;2095418 Wrote:
>>>> Chucks0,
>>>>
>>>> did you copy in the update.xml file?
>>>>
>>>> --
>>>>
>>>> Shaun Pond
>>>
>>>

>>
>>
>> --
>> 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.

>
>



--
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.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
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.