We knew it was coming and now you can have it...the ability to use the ShoreTel mobility client on your shiny new Apple watch.  Unfortunately none of us has one to test with at the moment, so we can't give it a review.  One of our sales executives has one ordered, so we'll see if we can convince him to let us try it.

I've been banging my head against the wall for the past few days trying to figure out why my upgrade of ShoreTel 14.2 was failing with WinVerify Trust errors during the upgrade.

Server is running Windows 2008 R2 with latest Microsoft patches as of 02/11/2014.

Extra, Extra read all about it....the ShoreTel Dock Now Shipping!!!  I'm not an Apple iOS fanboy, but I do think this solution from ShoreTel is pretty slick.  I wish they would come out with an Android based dock, but the chances of that happening are probably slim to none, due to the fact that there are so many variants of Android based tablets.

f you are planning to upgrade your ShoreTel system to the latest version (12.3), be aware that the upgrade does not update the boot ROM on non-v switches.  To upgrade the non-v switches you have to manually upgrade the boot ROM on the switches by connecting a serial cable to the switch or telnetting to the switch and following these steps:

This excerpt is from the 12.3 planning/install guide: 

I wanted to let you know that the ShoreTel suggestion portal is now live for customers and partners.  This is the place where you can suggest changes to the existing system or new feature requests for futrue releases.  You can access the portal here.  It's a pretty simple process, simply create an account and you’ll be able to send your product suggestions directly to ShoreTel.  I've created an account and made a few suggestions, one of the features of the portal is that other users can rate suggestions, obviously the suggestions with the most

View from my room @ The Chicago Hilton

The Chicago Hilton

We have seen a couple of installs of ShoreTel's 10.2 (Build 15.41.9301.0) on Windows Server 2008 SP2 (x86) that have had problems generating reports.  When trying to run reports on the HQ server, you receive a 404 error (see image below).