Here is an outline of how I back up and upgrade ShoreTel 14.2 and below systems. This process is pretty easy and if anything goes wrong you have all the back up needed to re-configure a new server if needed. I have used this info a lot and it has worked really well for me. I hope you are able to get some use out of it and it helps you.
Things to consider
- This
cannot be stressed enough. READ THE BUILD NOTES for
the final version you are upgrading to. This information tells
you if your 3rd party software is supported and what version. (ex. Exchange,
Outlook, Double Take, VMWare, etc..)
- Migration
to Connect CAN NOT be rolled
back to ShoreTel 14, 13, 12, ECT
- Please
make sure you have someone available at your remote sites during or early the
next day after the install. You want to plan for any
unforeseen scenario's. Having someone available will allow you to hard
reboot any devices in case there are any network issues, or power outages
during the install.
- If
you have additional sites. Be sure that the WAN link is stable and not running
any errors. If not, then this could increase the time to perform the upgrade at
remote sites significantly.
- Use
the Compatibility checker to make sure you have no issues with upgrading to the
new version.
Back up the current system
- Databases .sql files
- Navigate to C:\Program Files (x86)\Shoreline
Communications\Shoreware Server\MySQL\MySQL Server 5.0\Examples and run the following files
- BackupCDR.bat -> Will output an .sql file to
the root of C:
- BackupConfig.bat -> Will output an .sql file
to the root of C:
- BackupWebridge.bat -> Will output an .sql
file to the root of C:
- Only required if there is an SA-100/SA-400 in
use.
- BackupMonitoring.bat-> Will output an .sql
file to the root of C:
- Only required for ShoreTel 14.x
- Copy the resulting .sql files folder to a safe
location (Network Share, Thumb drive, etc...)
- Shoreline Data folder
- Stop all ST services from script at C:\Program
Files (x86)\Shoreline Communications\ShoreWare Server\Script\ hq_shoretel-stop-svcs (make sure to run as
administrator)
- Copy the VMS, User Data, & Prompts folder
from Shoreline Data, to a safe location (Network Share, Thumb drive, etc...)
- Start all ST services from script at C:\Program
Files (x86)\Shoreline Communications\ShoreWare Server\Script\ hq_shoretel-start-svcs (make sure to run as
administrator)
- Reboot the ShoreTel server
Upgrade ShoreTel ShoreWare Director
- Run the compatability checker to verify that there are no issues
- Upgrade
the HQ server to the next version
- After
the upgrade make sure that you can open Director and ensure all your users are
there and you are able to run reports.
- If
this these are successful, then please perform steps 3 through 6 until you are
running on the final version you want
- Once
the HQ server is running the final version, now we can upgrade any DVS's
(Distributed Voicemail Servers)
- Once
the DVS's are good, then please reboot your ShoreTel switches
- If
you have a 50v or 90v the upgrade will take between 30-45 minutes on a decent
network connection
- All
other switches will take usually 5-10 minutes depending on the network
connection
- Once
all of your switches are rebooted and showing up in Director, then please
reboot all the phones
- ** I will sometimes go site by site and upgrade the ShoreTel swithes at a site and then upgrade the phones, and then move to the next site. I always start at the HQ site first though.
- Once
all of the phones and switches are running on the newest firmware, then we want
to address the Communicator client. They can be upgraded by using GP, or the
user can click on help and the upgrade in the Communicator Client
Test after Upgrade
- Check inbound dialing
- Check outbound dialing
- Check work groups
- Check Route Points
- Check Hunt groups
- Check Voice mail
- Check communicator
Mobility Upgrade
- Upload
/ Install software to the ShoreTel Mobility router
- Reboot
the ShoreTel Mobility router
- Verify
everything is working
- Inbound
calls
- Outbound
calls
- Wifi
calls
- Cell
calls
