No announcement yet.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Installation 101

    Always consult your Partner or Shoretel TAC before doing any upgrade install or maintenance

    Many of the items encountered on new installs are varied, specifically though permissions issue on the server is one of the biggest downfalls.

    Before you install, a few items should be considered
    1. What version of ST software are you installing ie. 7.x or 8
    2. What Windows Server OS is installed, Including SP level
    3. From the ST software requirements, does the Server in step 2 meet the requirements
    4. Is your LAN / WAN capable and has it been analyzed for Voip

    There are more options to look at for more detailed installs, this is simply a basic look.

    For instance, if you going to Vlan your install, use QOS, MPLS or Cable / DSL for remotes. For simplicity lets just focus on the Server Install and Requirements

    ShoreTel 7.x and ST 8 have an entirely new set of Server Requirements including for the SBE, so upgrading you must first bring your Server up to the requirements. ST 7.x and 8 at minimum require 1 GIG Memory, ST 8 requires at minimum 5 gig free space on the C drive to Install. (SEE RELEASE NOTES & CONTACT SHORETEL TAC OR PARTNER)

    Installing ShoreTel 6.1 and higher (Fresh Install New Server)
    1. Server OS should be Server 2003 (Read Release Notes for Supported OS)
    2. Latest Service Packs from MS (See Release Notes FIRST)
    3. Server "MUST" be in Stand Alone Work group on Install
    4. Server must only Host ShoreTel Software

    Pretty simple, one of the biggest mistakes an installer makes is to install the Server onto a Server that is already on a Domain. There is nothing wrong with pushing the ST Server on to a domain, as long as it is done "After" the Install and the system is stable. (Believe me, you will save yourself a major headache, just install as a Work Group Stand Alone Server)

    Pushing the Server on to a Domain is fine, after the install and you have run system checks. However, do not PUSH "ANY" policy onto the ShoreTel Server that will hinder or remove any of the Standard ShoreTel users. It is best to just Add the Server with no Policy push at all. (Consult ShoreTel TAC or your Partner for explanation)

    Install / Basic Configuration
    New in ST 7 and above is the DB import tool, this is a great tool to use if you have a large system. Just remember, the CSV format, do not put any spaces in your syntax it will fail. Read the Server Release Notes and consult with your Partner or Shoretel for assistance.

    IP Phones, can be a pain in the rear, DHCP options 156 is a must to be added to every scope for each DHCP range you will use. If you are using multiple DHCP server for Vlan then make sure your relay agent is configured correctly as well as you have option 156 on each DHCP server.

    In IP Phones > Options Ensure you have your SG config switches set and in each of these SG's you have enough IP ports enabled. (REMEMBER) if your using Softphone, you need to take into account for those as well.

    IP Phone Map: it is good practice to establish an IP Phone map, especially if your a multi site system, if the remote sites do not use a DVM, then check Teleworker for the Map, this will auto set G729 for that range.

    ShoreGear SG install, it is best to allow the system to find the SG, best practice is to Static set the ShoreGear Switches. If this is not possible then to use a Reservation list in the DHCP server for each SG. In Director, add the New SG in the Switches Page, then choose Find Switch, this will pop up the SG of Choice, choose the correct SG and install.

    ShoreTel Server: Always Make the ShoreTel Server a Static IP assigned Server. Same for any DVM

    ShoreTel DMV or Distributed Voicemail: Use the IP address of the HQ server (NOT THE FQDN or Short Name) the reasoning is an IP is always Routable, if your having DNS issue or WAN Issues, the IP will always be routable (See PIG)

    Everything Points to Headquarters:
    This means any installed product (I.E. PCM, ShoreGear Switches, DVMs and IP Phones) all point to the Head quarters server. The reason for this is the HQ is the Only server that has the Data Base. Any change is direct to the HQ server. Even if you have a DVM (Remote Server) the PCM users when installing will point to the HQ IP address. Here is Why Lets say you have an HQ and a Remote DVM, you just installed a New ShoreGear SG 60/12. The config of the 60/12 (i.e. Host Inet aka Server) should be the HQ server, not the DVM. When you add the ShoreGear SG to the systems, you will add this to Site and make the Remote Server the controller in Director. The HQ will then PROXY all requests directly to the Remote Server, unless that remote server is unavailable (More on that Later Thread) This is the same for any user (PCM) as well, once that user is assigned to the site / Remote DVM all processing will be proxied to the Remote Site.

    That should cover a basic install of a ShoreTel Server
    Last edited by Jlorenz; 07-10-2008, 11:49 AM.