Server Migration 101

[Jlorenz]

**Disclaimer: Consult first with ST TAC or your Partner before attempting an major upgrade as below

Moving ShoreTel from one server to another is not as daunting a task as one may think. Actually it is pretty simple, all that is involved is time really. Below you will find the needed steps to migrate a Shoretel System to a new server.

First the finer notes.

• Windows 2000 Pro (aka Desktop), Windows 2000 Server anything Windows 2000 is no longer supported in Shoretel 7.x & above
• It has been my experience that upgrades from 2000 to 2003 cause nothing but problems. Do yourself a favor, simply build a Fresh, New 2003 Server.
• Never install ShoreTel server that is already part of a domain (Make it Work group)
• Never Install Shoretel on VMware, or any other emulation / mirroring product
• Plan for down time
• It is essential you establish the New Server with the Same IP and Name as the Old (This will save you time and headaches) Unless your changing the entire IP subnet, you will then need to change every SG as well as reinstall each DVM. Caution consult with ShoreTel
• The ShoreTel Build Release Notes is your Friend, read it be aware of OS dependency and support for your release
• Make sure you have the EXACT Build or Higher, you are currently running of ShoreTel. It is best to start with the same build, if you planing to upgrade, ensure the system is fully operational on same build before moving forward *SEE NOTE AT BOTTOM

Step 1 of Migration

1. Build your New 2003 or 2000 Server (Build Dependant) advise to move to 2003 (Do Not, "DO NOT" install ShoreTel Software on this server until steps below)
2. Rebuild all DVM's as well to Server 2003, following the same steps in Steps 2 & 3 for each DVM.
3. Be mindful of your version and the SP level that is supported (Aka ST6 and below No support 2003 SP1)
4. Correct IP and Server Name
5. Work Group Server (NOT ON DOMAIN)*SEE NOTE AT BOTTOM

With the New Server ready and updates applied (Again ShoreTel Version dependent, Se release notes)

Step 2 Old Server

1. Shutdown the Old Server (use Windows Services App, start with ShoreTel Notification Server, then stop all other services manually
2. In Component Services, under My Computer > COM stop Shoreware
3. Copy / Make back up of Shoreline Data Folder and all child folders.
4. Move the Shoreline Data folder off to safe gaurd
5. Shutdown Old Server, do not keep on line

Step 3 New Server

1. Copy the Shoreline Data folder to the new server. (Make note of Drive you copied Folder to)
2. For ShoreTel 7.x and above ONLY After copy of Folder, DELETE the MySQL folder from Shoreline Data\CDR Records2\Data (ONLY DELETE THE MYSQL folder)
3. Install ShoreTel Software on new server, From Step 3-1 make sure you adjust the drive letter when prompted to the proper drive location of Shoreline Data "if needed" Example X:\shoreline data where X is the drive
4. If multiple Sites with DVM's Upgrade the DVMS just as you would in the Release notes Steps
5. Finish the Install, reboot the Server and start your Service checks ensuring system is up and operational
6. Once system is functional, aka all call handling works, Hold, transfer, work group, hunt group and so on. You can then proceed to upgrades if needed as normal.
7. It is not necessary (if your upgrading from multiple Versions to update PCM until Final version is installed) You should update your phones with at minimum each major code base jump I.E. ST5.x to 6.x or 6.x to 7.x (this is not mandatory)

Notes:
Upgrading from ShoreTel Lower then 6.x
Depending on the release you are running (Lets say ST 5.1) you will have to upgrade your old server first to release 6.x *See Release Notes and Consult ShoreTel on this Migration.

Domains:
It is best practice to install ShoreTel as a Stand alone Work Group Server "Initially" Because of Permissions and Policy unknowns, Installing ShoreTel Software on a server already attached to a Domain may and will cause services to not start properly. You can, push the server to a domain, "ONCE" the ShoreTel server is up and operational. Do not Push any Policy that will disrupt the current ShoreTel Users aka IPBX_, IWAM_ and so forth.

[BlenderBoy]

I followed these instructions and when I restarted the new server (after installing Shoretel v6), I get no network connectivity whatsoever. VERY ODD considering I did not have this issue prior to installing Shoretel.

The new server (like the old) is a dual-NIC (one for the voice network and the other for the data network), and I can NOT ping any of the Shoretel phone switches or data switches on either NIC. I could ping my own IP and 127.0.0.1 and I could also login into the ShorewareDirector on the new server, but I could NOT ping any device from the new server or get any other device on the network to ping the new server. And yes, the old server was completely offline (no IP conflicts). I had to revert back to the old server in the meantime. Thus, I uninstalled Shoretel on the new server, renamed it (so it would not conflict with the old server name), and the NICs now can access the network no problem.

A peer of mine suggested restarting the Windows Telephony service, but I have not had an opportunity to try that. As a further note, I have the Windows SMTP service set to port 587 (I don't think this matters, but I'd just thought I disclose it).

Any insight you guys could provide would be greatly appreciated. Thanks!

[eazeaz]

Dual Nic

Multihomed servers = bad

multihomed shoretel servers = really bad

[Telman2010]

Just to re-iterate what eazeaz said
multihomed shoretel servers =REALLY really bad

[matt]

ARP cache on the other devices still seeing the IP(s) tied to the old MAC(s) perhaps? If the network switch is manageable did it see the new hardware adrress(es) on the new server? Did you check the arp cache on something else on the network?

Unless I'm missing something this sounds like a networking issue. (apart from the design issue)

[BlenderBoy]

Thanks Matt. That is one thing I did not check was the ARP tables. Although clearing the ARP on the switches did not solve the problem, I discovered the VLAN set up by the previous administrator; and that was my routing problem (the new server was not on the same VLAN as the rest of the ST equipment). I appreciate the help and support, especially since I'm flying blind here (no documentation left by previous administrator).

BTW, the dual NICs is not causing problems with Shoretel and I believe it was setup that way so the Shoretel server can be a domain member. I've read it's best to not join the ST server to the domain, but again that's how it was setup prior to my arrival. Thanks again!

[JMozee]

Thanks Matt. That is one thing I did not check was the ARP tables. Although clearing the ARP on the switches did not solve the problem, I discovered the VLAN set up by the previous administrator; and that was my routing problem (the new server was not on the same VLAN as the rest of the ST equipment). I appreciate the help and support, especially since I'm flying blind here (no documentation left by previous administrator).

BTW, the dual NICs is not causing problems with Shoretel and I believe it was setup that way so the Shoretel server can be a domain member. I've read it's best to not join the ST server to the domain, but again that's how it was setup prior to my arrival. Thanks again!

The reason for keeping it off the domain is typically the domain policy & Anti Virus Updates. Both of which can cause IIS and ShoreTel services problems. For the most part all my Large deployments of shoretel servers are members of domains.

Now the dual NIC i have one of these as well but it can be problematic should the server reboot and ShoreTel software bonds to the wrong interface. I know this is far few and between but it is a pain right after a power outage and your server comes back online and tapi is not functioning due to this. But besides that as long as there is only one Default Gateway assigned i have not had any other issues with this method.

[BlenderBoy]

Ok, now that we have a successful migration of our Shoretel services to the new server, another problem popped up: user administration option/buttons are now grayed out (disabled), so we cannot manage our users.

Seems like a fairly trivial issue (but can't say for sure). The Shoretel services & database have been working fine since the transfer, and this problem was discovered after an employee left the company and now have to disable the voice mailbox.

Any ideas!

[BlenderBoy]

Figure it out. This was happening because of a database version conflict. I posted my solution at:

http://www.shoretelforums.com/forums/administrators/4572-shoretel-database-error.html