Mine went almost the same way, with a few extra messages (upgrading a 
test CAS 3140 from 4.7.1). I rebooted at the end - didn't seem right not 
to! I plan to upgrade my production system on Sunday (was planning to go 
to 4.7.1, but instead I'll jump right to 4.7.2).

[root@test-cas1 cca_upgrade-4.7.2]# ./UPGRADE.sh

Switching the perfigo service to maintenance mode...
BaseAgent process stopped!
type=1700 audit(1265728633.862:5): dev=eth1 prom=0 old_prom=256 
auid=4294967295 ses=4294967295
type=1700 audit(1265728633.962:6): dev=eth0 prom=0 old_prom=256 
auid=4294967295 ses=4294967295
click: stopping router thread pid 1830
poll f91e08e0: 4345438/14504 freed, 8/14444 allocated
click module exiting
click: starting router thread pid 31004 (f74e3bc0)
In Maintenance Mode...
Going to upgrade the server rpm
Backing up Clean Access Server
Finished upgrading the system to 4.7.2

[root@test-cas1 cca_upgrade-4.7.2]# cd /perfigo/common/bin
[root@test-cas1 bin]# ./showstate.sh | grep INCORRECT


-Mike


On 09/02/2010 3:00 PM, Speight, Howard wrote:
> I just upgraded from 4.7.1 to 4.7.2 in our test lab, looked a bit strange, although appears to have been successful?
>
> [root@cas3 ~]# cd /store
> [root@cas3 store]# cd cca_upgrade-4.7.2
> [root@cas3 cca_upgrade-4.7.2]# ./UPGRADE.sh
> Switching the perfigo service to maintenance mode...
> BaseAgent process stopped!
> Stopping DHCP...
> In Maintenance Mode...
> Going to upgrade the server rpm
> Backing up Clean Access Server
> Finished upgrading the system to 4.7.2
> [root@cas3 cca_upgrade-4.7.2]# cd /perfigo/common/bin/
> [root@cas3 bin]# ./showstate.sh | grep INCORRECT
> [root@cas3 bin]#
> c[root@cas3 ~]# cat /perfigo/build
> VERSION=4.7.2
> NAME=Clean Access Server
> DATE=2010/02/05
> AUTHOR=avinkuma
> BUILD_TAG=NAC-4_7_2-RC2
> BUILD_INFO=Release
> BUILT_ON=gvtest5
> REBUILD_COUNT=0
> [root@cas3 ~]#
>
> Don't recall doing an upgrade where at least one rpm was updated? Perhaps those messages were suppressed? Also didn't reboot, instructions stated would be automatic. Joined back to the CAM, no problem. Nice we are back to using the tar file!  :-)
>
> -----Original Message-----
> From: Cisco Clean Access Users and Administrators [mailto:[log in to unmask]] On Behalf Of Tom Stachowiak
> Sent: Tuesday, February 09, 2010 12:28 PM
> To: [log in to unmask]
> Subject: Re: NAC 4.7.2 Released
>
> The bug NAC Agent 4.7.1 fails to posture WSUS on 64 bit OS. Is still
> marked as open in the TAC toolkit.
>
> I have already deployed the client updates and all went well. Trying to
> plan the server side upgrade so I can solve the Windows Starter not being
> supported.
>
> Tom Stachowiak
> D'Youville College
> Helpdesk Coordinator