 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Tue, 29 Aug 2006 17:36:40 -0500 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
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.
|
|
|
