CLEANACCESS Archives

August 2006

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Rajesh Nair (rajnair)" <[log in to unmask]>
Reply To:
Perfigo SecureSmart and CleanMachines Discussion List <[log in to unmask]>
Date:
Tue, 29 Aug 2006 22:39:41 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (116 lines)
Matt,

I am assuming that you downloaded the CCAAgentUpgrade.tar.gz file from CCO and uploaded it via the CAM UI?

Yes, we are aware of the issue and we will fix it shortly. 

-Rajesh. 

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List [mailto:[log in to unmask]] On Behalf Of Matt Moore
Sent: Tuesday, August 29, 2006 7:00 PM
To: [log in to unmask]
Subject: Re: PROBLEM FOUND WITH 4.0.3 UPGRADE[Scanned]

I experienced the same problem that others had with the 404 error when a user with 4.0.1.0 agent is trying to upgrade to 4.0.2.0 agent.  

The resolution for me was to download the 4.0.2.0 upgrade separately and upload it to the server manually. 

Matt Moore
Systems Administrator
Dakota Wesleyan University
605-995-2187     

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List [mailto:[log in to unmask]] On Behalf Of Prem Ananthakrishnan (prananth)
Sent: Tuesday, August 29, 2006 5:50 PM
To: [log in to unmask]
Subject: Re: PROBLEM FOUND WITH 4.0.3 UPGRADE[Scanned]

If you upgrade to 4.0.3, you will have to make sure that all the end users are upgraded to 4.0.2.0 on their agent.
If you have Mandatory upgrade on the agent, that will take care of that.

If you don't want to upgrade to 4.0.3, or if you don't want to push the 4.0.2.0 agents to all the end clients, then Wait for he 4.0.2.2 patch that will be out later today

Thanks
Prem

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List [mailto:[log in to unmask]] On Behalf Of Matt Moore
Sent: Tuesday, August 29, 2006 3:37 PM
To: [log in to unmask]
Subject: Re: PROBLEM FOUND WITH 4.0.3 UPGRADE[Scanned]

We are running 4.0.2 on CAS and CAM and had 4.0.1 agent until early this morning.  It appears that everyone that has upgraded are not going through any checks.  There are no reports being generated.  

I have disallowed any further upgrades but do not know a way of forcing users to uninstall and reinstall the 4.0.1 agent.  

It looks like our only option is to upgrade the CAS and CAM to 4.0.3.  Is that correct?

Matt Moore
Systems Administrator
Dakota Wesleyan University
605-995-2187     

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List [mailto:[log in to unmask]] On Behalf Of Ryan Dorman
Sent: Tuesday, August 29, 2006 3:22 PM
To: [log in to unmask]
Subject: Re: PROBLEM FOUND WITH 4.0.3 UPGRADE[Scanned]

There was another use who emailed me off-list about having the same problem... Is

 > Justin Nelson
> Network Analyst
> Augustana College

Out there?  Could you provide Rajesh with more info?  Maybe something about our setups is different?
--
Ryan Dorman, CCNP
Network Engineering Specialist
Millersville University
717.871.5883




On 8/29/06 4:02 PM, "Rajesh Nair (rajnair)" <[log in to unmask]> wrote:

> Ryan,
>  
> I just tried it again on a test setup... Downloaded the 
> CCAAgentUpgrade file and uploaded it via the CAM UI and the CCAA 
> directory and the Update.exe files did get created and a test client was able to upgrade to the 4.0.2.0 agent.
>  
> -Rajesh.
> 
> 
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Ryan Dorman
> Sent: Tuesday, August 29, 2006 12:38 PM
> To: [log in to unmask]
> Subject: Re: PROBLEM FOUND WITH 4.0.3 UPGRADE
> 
> Rajesh-
> 
> A Timeline:
> 
> 1. We  are on 4.0.2 and the 4.0.2.0 agent was pushed out.  Clients 
> were beign forced to upgrade due to our policies.  They upgraded and 
> logged in with  no checks an null OS.
> 
> 2.  I upgraded to 4.0.3 and checked the łupgrade agent˛ check box
> 
> 3.  Users with the 4.0.1.0 agent now got a 404 error on trying to 
> access the Update.exe file
> 
> 4.  I manually sent the tar.gz file of the agent with the GUI
> 
> 5.  Users still got the 404 on trying to access the Update.exe file
> 
> 6.  I checked packet captures to see what they werenąt getting and 
> noticed the archive hadnąt been unpacked.
> 
> All of this happened within the space of about an hour so maybe 
> something else was happening simultaneously.  But thatąs what I saw.

ATOM RSS1 RSS2