Announcement

Collapse

Welcome to ShoreTelForums.com

Welcome to ShoreTelForums.com!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
BTX
See more
See less
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Split 2 sites into 2 isolated ShoreTel networks

    I have a question about separating our HQ server to 2 different sites (isolating out our Georgia site). Here is the basic scenario:
    • There are 2 sites (CA HQ, and GA)
    • DVM and ECC are in GA
    • We would like to separate CA from GA.
    • What is the easiest way to build/migrate an additional separate ShoreTel HQ server in GA? Can we “copy” our HQ to GA, then remove all CA information from that Database? If so, how do we “promote” GA to an “HQ” under the Sites category in the ShoreTel directory?

    The issue I am going to run into is swapping the HQ site and its child site in the ShoreWare Director (if we make a copy).

    Here is a breakdown of what I have:

    "Migrate" HQ to new server in GA
    1. New GA HQ server
    a. Install Server 2003 SP2.
    b. Install ShoreTel recommended software
    2. Current CA HQ server
    a. Backup D:\Shoreline Date folder
    b. Copy over Shoreline Data folder to new HQ server
    3. Install ShoreTel server software on new HQ server
    a. Purchase license to new HQ server
    4. Configure ShoreTel recommended software/fixes
    5. Erase CA site information
    a. Users accounts, HGs, WGs, AAs, RP’s, Sites, Applications servers, Licenses, Schedules, Switches, Phones, and Trunks.
    6. Modify Parent/HQ site to use GA info
    a. Migrate all user’s/application servers/phones/etc… to new GA HQ/parent site
    7. Change ECC Remote software registry to point to new HQ server
    8. Change DVM remote software registry to point to new HQ server
    9. Change Switches to point to new HQ server.
    10. Change all users’ PCM settings to point to new HQ.
    11. Move all user’s voicemails to HQ server
    12. Pull DVM off of network
    a. Delete DVM from application servers in ShoreWare Director
    13. Leave HQ in CA to keep it running.
    a. Erase GA site information

    Please let me know if you need any more information.

  • #2
    There is no easy way to do this, ShoreTel may have some scripting (You will Pay) to have this done and contracted with them.

    In my minds eye, your going to have to remove delete the DVM altogether. If the ECC is going to stay in Georgia, then that may have to be reloaded, I wont speak on that part.
    Your going to have to purchase an entire new license for HQ enterprise, users and all the other needed features. This is not transferable if you split the system, you effectively now have two ShoreTel Enterprise servers distinctly different. Your current licensing will not work on two machines

    Comment


    • #3
      How about a "simple" solution:
      1. Move all mailboxes to HQ site
      2. Copy over shoreline data folder (migration on a new HQ with new IP)
      3. Change IP in switches in the database to new GA IP
      4. Install Shoreware server software on new HQ
      5. Delete switches from old HQ
      6. Redirect Switches to new HQ IP
      7. Run brunflash on all GA switches
      8. Redirect Phones' DHCP to new HQ IP

      Comment


      • #4
        Originally posted by jcogorno View Post
        How about a "simple" solution:
        1. Move all mailboxes to HQ site
        2. Copy over shoreline data folder (migration on a new HQ with new IP)
        3. Change IP in switches in the database to new GA IP
        4. Install Shoreware server software on new HQ
        5. Delete switches from old HQ
        6. Redirect Switches to new HQ IP
        7. Run brunflash on all GA switches
        8. Redirect Phones' DHCP to new HQ IP
        Nope, your Database is tied to the MAC address of the existing server, this is why you will need a new license for the new server as well as user licenses. This may had worked prior to ST 6.1, but now with the Hard encrypted licensing, you will need to create a who new system.

        Now, you probably can copy the Vmails over to the new system and create exactly the exts, the names and profiles for each user. If, IF it works, users would have the correct messages in their Vmails. I am leaving out some details but this is speculation if it would work

        Comment

        Working...
        X
        😀
        🥰
        🤢
        😎
        😡
        👍
        👎