Upgrade BCM To 3.7

[nbowles]

I have been having problems with registry corruption when attempting to upgrade clients to 3.7 from 3.6. It appears that the upgrade gets to ~12% and then just hangs there. I had to bring a 3.6 hard drive to replace the hosed up partially upgraded drive.

Has anyone seen these kind of issues before? I think I am following the proper upgrade procedure, but sure would like to avoid the hung up system. Has anyone else seen other issues when upgrading to 3.7?

Thanks,

N8

 

[aragon]

I have had issues during 3.6 patches, it stands to reason that an upgrade to 3.7 could give you some trouble.
I have seen the latest 3.6 MSC Core patch fail twice.
It is possible that your 3.7 upgrade fails during the MSC upgrade.
Where did you see the upgrade fail?
Try patching the 3.6 first using the MSC driver patch and then install the 6.012 core patch prior to upgrading to 3.7
Also if you wish to reuse the hosed drive you may ghost a virgin drive to the failed drive. Symantec Ghost 2003 seems to do a pretty good job using a floppy boot disk and doing a drive to drive image.

 

[NARSBARS]

My vendor has suspended upgrades to 3.7 after having the same problem. Thanks to Tek-Tips I had insisted that a backup,a fresh HD, and copies of all keycodes be brought along on all upgrades. My vendor thought I was crazy but went along to humor me.
I will pass along whatever I pick up here and post any information I find.

I find that Ghosting the original drive, pre-upgrade to take more time initially, but provides a far faster recovery time.


NARSBARS

 

[acewarlock]

I have a master HD Image that I use to ghost all my new BCM's with all the basic programing we use on all BCM's. This why 90% of our programming is done before it leaves the shop.