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

  • Connect Client MSI

    we are moving customer to connect. we have a MSI installer package ready to push out to all the client machines 300+ computers. the question is there a way to populate the servername in the installer package so we dont have to on each instance of connect client? this is across 5 sites all with DVS servers. So we would have to create 5 installer packages, Mitel TAC says there is no way but there has to be.

  • #2
    This was posted by ShoreTel_Dave..

    It's DNS magic rather than group policy magic

    For automatic configuration of the ShoreTel Connect Client for internal users, there are a couple of magic SRV record that can be added to the internal DNS Zone
    Inside the _TCP tree.

    Add a couple of TCP SRV records in the DNS zone containing the user PCs called _shoretel-connect
    make one with Port number 443 and the other 80.
    both should have the target host set ideally to the DNS fqdn of shoretel HQ but IP address should work if you don't care about certificate potions and voodoo.

    using both records will make the clients connect over https but be able to fallback to http.

    (im using a cellphone right now, I can add more detailed instructions with pictures when I'm at a PC.

    note you need to tell the users to check the box to use Windows credentials to make it fill in the server name. If you are not using Windows credentials the uncheck it again afterwards and the server name will remain filled but the user will have to enter their shoretel credentials manually.


    • #3
      so not really msi related but works for us :-)


      • #4
        Ok cool i'll take a peek! thanks for the info.


        • #5
          Note: you'll either need to tell users to check the "use windows credentials" checkbox twice in order to get the server name to populate, then check the box again (a total of 3 times - you'll see what I mean)

          OR just recently on the last partner forum I learned that if you open the client for the first time, click "show advanced" choose "use windows credentials" then minimize the advanced options and click login - it will work too...

          Either way stupid cumbersome for first day users. We find using the registry settings is the way to go. Use DNS SRV record as backup.
          Last edited by augie; 06-05-2019, 01:22 PM.


          • #6
            Still asking for server

            Microsoft Windows [Version 6.1.7601]
            Copyright (c) 2009 Microsoft Corporation. All rights reserved.

            Default Server:

            > ?
            Commands: (identifiers are shown in uppercase, [] means optional)
            NAME - print info about the host/domain NAME using default server
            NAME1 NAME2 - as above, but use NAME2 as server
            help or ? - print info on common commands
            set OPTION - set an option
            all - print options, current server and host
            [no]debug - print debugging information
            [no]d2 - print exhaustive debugging information
            [no]defname - append domain name to each query
            [no]recurse - ask for recursive answer to query
            [no]search - use domain search list
            [no]vc - always use a virtual circuit
            domain=NAME - set default domain name to NAME
            srchlist=N1[/N2/.../N6] - set domain to N1 and search list to N1,N2, etc.
            root=NAME - set root server to NAME
            retry=X - set number of retries to X
            timeout=X - set initial time-out interval to X seconds
            type=X - set query type (ex. A,AAAA,A+AAAA,ANY,CNAME,MX,NS,PTR,
            querytype=X - same as type
            class=X - set query class (ex. IN (Internet), ANY)
            [no]msxfr - use MS fast zone transfer
            ixfrver=X - current version to use in IXFR transfer request
            server NAME - set default server to NAME, using current default server
            lserver NAME - set default server to NAME, using initial server
            root - set current default server to the root
            ls [opt] DOMAIN [> FILE] - list addresses in DOMAIN (optional: output to FILE)
            -a - list canonical names and aliases
            -d - list all records
            -t TYPE - list records of the given RFC record type (ex. A,CNAME,MX,NS,
            PTR etc.)
            view FILE - sort an 'ls' output file and view it with pg
            exit - exit the program

            > set type=SRV

            Non-authoritative answer:
   SRV service location:
            priority = 0
            weight = 0
            port = 443
            svr hostname =
   SRV service location:
            priority = 0
            weight = 0
            port = 80
            svr hostname =


            • #7
              Did you happen to read my last post - and try either of those to test?


              • #8
                We upgraded to build 21.90.9743 a month ago. I reviewed the release notes and didn't see anything mentioned there about a change to this behavior, but it appears there has been a change as of this build. Prior to Connect, we used to deploy a GPO that dropped the reg keys needed to preconfigure the Call Manager client. When we upgraded to Connect, we lost that capability. Even though it looked like we could drop the needed reg keys into HKCU, the Connect logon process seemed to need to write the connection info first to a .db file in the users appdata/local/Mitel directory before populating the keys in the registry. On this new build, I can successfully write the needed reg keys to HKCU and the user can launch Connect seamlessly.

                Here are the keys needed if you are using AD integration and you want the client to auto login when the user opens it up:

                Windows Registry Editor Version 5.00