Upgrading from 3.2 to 3.3 1

[AdmanOK]

Has anyone tried to do an upgrade from 3.2 to 3.3 on generic boxes using the reg hacks? I can get 3.3 installed, but what I would really like to do is load up my 3.2 config to check if everything works. The documentation says that to do this you need to boot from the HW Detection CD and do an in place upgrade, but these CDs don't work on non MCS boxes. Anyone know of any other way to upgrade all your stuff? I tried just doing a restore of an STI file from my 3.2 boxes, but the 3.3 machine puked and didn't load anything in. I wasn't smart enough to do a backup of the 3.3 config before I tried the restore either so back I go to the install CDs to build a 3.3 environment again!

 

[talbotpat]

What you are talking about is possible if your registry settings are correct. Did you upgrade the Spirian backup utility on the 3.2 environment to the proper version for a 3.3 restore? If you can't get the non-MCS testing to work, let me know, I have a MCS we can use to get your testing done.

 

[AdmanOK]

Yeah I did upgrade the Spirian backup on my 3.2 publisher to 3.5.44 before doing the backup that I tried to transfer to the other servers... didn't seem to help. I guess when you do the inplace upgrade it has some scripts or something to convert db format.

 

[talbotpat]

Yes, the upgrade asks for the location of your backup file and then goes and grabs the .sti for restore to the 3.3 box. I haven't tried a simple restore like that outside of the upgrade utility. As long as you have 3.2 installed on the non-MCS box and have the proper registry settings for a 3.3 install, then you should be able to do the in place upgrade. I have used the new installation/upgrade CD to start this process, however, not the hardware detection CD. The install will start, and you should be able to select the upgrade option instead of the new installation.

 

[AdmanOK]

Okay, I'll try that... do you have any 3.2 CDs? I only have 3.1 discs and would prefer to just install from 3.2 to avoid confusing the issue more than necessary?

 

[BuckWeet]

You have to reinstall anyways going from 3.2 to 3.3 because of the different versions of SQL server..

BuckWeet

 

[commsguy]

Buckweet,

What are you saying? That you can't upgrade from 3.2 to 3.3?

commsguy

http://www.convetech.com

 

[killthemall]

hello,

can you help me to know the URL to download Ip telephony applications backup utility 3.5.44...

as per the cisco web site this utility can be downloaded from the web.. but not able to find the location..

request you to share the url in case you have..

thanks in advance


regards
atul

 

[BuckWeet]

Commsguy, you can upgrade from 3.2 to 3.3

you have to backup 3.2, reinstall the OS image and then tell it you're restoring from a backup.

This is because of the changes of SQL7 to SQL2000


BuckWeet

 

[UncleCracker]

Having issues installing CM 3.3 fresh on non-standard H/W. Installed vanilla Y2k SP4; did the reg hacks; then started CM install. About 20 mins into the install I get a message that CM cannot continue since it cannot determine if the Cisco directory installation was successful. Any ideas ?

 

[danipell]

UncleCracker et al..
Did the CM 3.3(3) on non-standard (whitebox) hardware with Cisco CCM disks. Steps used...
-installed W2K Server
-installed Reg hacks.
-installed OSBIOS disk. win2000.2.5 Came with CCM disks.
-installed CCM disk.
- install hung, rebooted server,
- reinstalled CCM. Installation went through.

Issues left over...
- CCM does not start up on reboots. Needs to be started manually in services. (thoughts anyone?)
cheers, dan