Hi I've checked the release notes for 4.1.6, and I see that this problem still hasn't been resolved. Does anyone know when (if at all) Cisco plan to address it? It seems to me that 10 months is quite long enough to wait for a fix. How do Cisco think this looks to the prospective Cisco purchasers thgat are using it? Max Caines IT Services, University of Wolverhampton Wolverhampton, West Midlands WV1 1SB Tel: 01902 322245 Fax: 01902 322777
_____ From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Michael Forster Sent: 16 December 2007 16:23 To: [email protected] Subject: Re: [CLEANACCESS] Avast V4.7 & CCA 4.1.2.1 We were having the same problem and opened a ticket with Cisco. This is their response: This is a new defect in the agent code. It will be fixed in the next 4.1.3 agent version. I'll update you later if there is any workaround at this moment and let you know the release date for 4.1.3 agent. Thanks & Regards, ------------------------------ Vaishali Deshpande SJ TAC - AAA/VPN Cisco Systems, Inc. [EMAIL PROTECTED] 408-525-2307 ___________________________________ michael forster network engineer [EMAIL PROTECTED] | 757.226.4043 regent university From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Stewart Sent: Thursday, December 13, 2007 9:22 AM To: [email protected] Subject: Re: Avast V4.7 & CCA 4.1.2.1 We have seen several cases of this... Dennis Xu wrote: Has anyone experienced problem with Avast V4.7 and CCA 4.1.2.1? It seems the agent does not recognize this product. TAC says several customers have already reported this problem, but they still do not have a solution or bug created. frustrating.. Dennis Xu Network Analyst(CCS) University of Guelph 5198244120 x 56217 -- Jeff Stewart Network Engineer Network Computing & Support Western Kentucky University
smime.p7s
Description: S/MIME cryptographic signature
