I miss-stated versions here. The CA Server/Manager are on 4.1.3.1. My server is pushing "setup version" 4.1.3.1, and "Patch Version" of 4.1.7.0. (I also have the "Allow 4.1.0.x Agents to login" option ON). Some of the users have not been online (this is for VPN - virtual gateway mode) for quite some time, and have the 4.0.x clients. They are able to connect to the clean access server to download and install the new version, but AFTER the new version is installed, they cant authenticated/remediate with the clean access servers.
From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Osborne, Bruce W. (NS) Sent: Tuesday, October 14, 2008 1:49 PM To: [email protected] Subject: Re: strange happenings after client upgrade I doubt 4.1.7 agent is supported on 4.0.3 CAM/CAS. In 4.1.x you need to explicitly allow 4.0.x agents if you want them. So there must have been come major agent changes. Bruce Osborne Liberty University From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Don Click Sent: Tuesday, October 14, 2008 2:02 PM To: [email protected] Subject: [CLEANACCESS] strange happenings after client upgrade I have a few clients that are upgrading from 4.0.3 to 4.1.7 agent. They were able to get to the Clean Access Manager page to be told about the new upgrade, but after the upgrade, the agent fails to attempt to talk with the manager again. My question is actually 2 - 1. Has anyone seen this before, and how do I get around it? 2. Should I have the clean access agent pointing to the MANAGER, or the SERVER? 3. Don Click Telecommunications Manager Department of Information Services Denton County (940) 349-3020 - Office (940) 349-5186 - Fax
