Does anyone have any additional ideas on this one?
Thanks in advance. ________________________________ From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Joey Mavity Sent: Thursday, January 31, 2008 12:27 PM To: [email protected] Subject: Re: [CLEANACCESS] File Distribution and "next" Michael, When I quit out of Clean Access or cancel and re-login, it passes the check so the requirement never fails. But yes, it does pass the check. On a side note, I tried uploading a jpeg and made a check for that picture. If I fail the picture test, it downloads and I can click "next" just fine. It seems that the agent is treating non-executables differently than it treats 'regular' files in this situation. HTH, --Joey ________________________________ From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Stanclift, Michael Sent: Thursday, January 31, 2008 12:06 PM To: [email protected] Subject: Re: [CLEANACCESS] File Distribution and "next" When you cancel out of the agent and relogin, I assume it detects it then? Another annoyance I've noticed with the file distribution rule is that is likes to default to the Windows System directory instead of something easy like My Documents or the Desktop. Anyone know a way to change that? Michael Stanclift Network Analyst Rockhurst University Conway Hall, Office 415 1100 Rockhurst Road Kansas City, Missouri 64110 (816) 501-4231 From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Joey Mavity Sent: Thursday, January 31, 2008 12:15 PM To: [email protected] Subject: File Distribution and "next" Hey everyone, I've spent the last several days trying to figure out the "File Check" rule. The goal is trivial: I have a rule for any vendor / any installation and another rule for any vendor / any update. Then I made a new file distribution requirement which prompts the user to download our SAVCE download. This is the first place I noticed a problem: Clean Access Agent doesn't prompt you if you name the same as a file already in the directory. So if someone clicks on a file inside the target directory (which users are wont to do), then realizes their mistake and clicks "save", that file is gone. OOPS! Second, after running the installer (an .msi), when I try to click "Next", the agent continues to prompt me to install the file. It never indicates that it's re-checking the requirements. What's going on there? Thanks, --Joey Azusa Pacific University
