08-30-2003 02:49 AM - edited 03-13-2019 01:24 AM
Has anyone applied the above upgrade yet(released 28/8)? Anyone had any problems since applying it?
regards
D
08-30-2003 03:36 PM
Applied it yesterday. Everything has been running smoothly up to this point.
08-31-2003 08:34 PM
Hi, I applied the following to my CM (is 3.1 3a spd)
win-OS-Upgrade-K9.2000-2-5.exe
win-OS-Upgrade-k9.2000-2-5sr1.exe
SQL7-ServicePack4.1-0-2.exe
SQL7-MS03-031.exe
XNTP.4-1-1a.exe
MCSbackup.3-5-44.exe
ciscocmac-fmu.1-1-3.exe
Will be installing Anti-virus soon (probably on Wed)
Will be doing the following this Sat (if the System is stable until then.
ciscocm.Health-Check.1-0-1.exe
ciscocm.3-1-4b-spD.exe
art-ffr.1-1-1.exe
art.1-1-1-spD.exe
James.
09-02-2003 01:30 AM
I've noticed in the readme for win-OS-Upgrade-K9.2000-2-5.exe that "Cisco CallManager version 3.3(2) cannot be installed after running this upgrade."
There's no information on if this can be uninstalled in order to later convert to 3.3(2). The implication being that if you are running CM 3.1 or 3.2, and you want to patch the OS to the latest level, then you've closed the door on upgrades to 3.3(2) in the future. Am I reading this right ?
09-02-2003 01:55 AM
I think I've answered my own question, - I presume the upgrade process would broadly be:
Back up the database on your CM 3.1 win2000-2-5 using the latest version of the backup utility.
Rebuild the Server using win2000-2-4 disks, then load CM 3.3(2), patch to win2000-2-5 (and any win2000-2-5 service realses, SQL patches etc), finally restore the database.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide