Response to a not-quite-zombie thread... Finally made the move on Friday night. Worked through the requirements (turn off DEP, etc.), copied over the files and did the installation. This was for 12.3.
Went so very smoothly I was pretty astonished. Then I went back through and turned everything back on except the firewall (The domain profile, that is - turned up the requisite services, though), haven't had time to do that yet. However, the tech gave me a list of ports used by everything ShoreTel 13.x, which should apply to 12.x as well. When I have a few moments to breathe, I'll do that as well. Kurt On Fri, Jul 19, 2013 at 5:50 PM, Richard Stovall <[email protected]> wrote: > What's the big deal? > > I run Shoreware Director in a VM and it works great. > > The bit about MS patches is just a cover. I've never, ever had a problem > keeping my Director server up to date. (If I did have a problem, I would > revert to the backup (that I always make) just before installing updates.) > > The rest of it? Meh. Your LAN is isolated from the world and is generally > secure, right? No non-admin can login to your Director server, right? All > orgs are different, but we're of a size similar to yours (I think, but > without the complication of overseas offices). It's one server with > particular requirements. Do whatever you want, but be prepared to modify > things if you have to engage ShoreTel support to fix a problem. For my > money, it's easier to deal with it up front and comply, and I don't see any > egregious security risks inherent in doing so. > > PS FWIW, Shoretel 13.x rocks if you have SIP trunks. > > > > > > > > > On Fri, Jul 19, 2013 at 7:00 PM, Kurt Buff <[email protected]> wrote: >> >> All, >> >> We are using ShoreTel for our phone solution. Works well. >> >> I have just recently upgraded from 10.2 to 11.2 to 12.3, after I moved >> it to a new VLAN - that was a bit of a late night... >> >> However, it's running on an ancient SuperMicro server, on Server 2003 R2. >> >> It's time to move it to a new Dell machine, running 2008 R2, and to >> get to the current version of 13.2. >> >> I've looked at the prerequisites for installing 12.3, and am appalled >> at what they suggest, and was hoping for a bit of feedback from anyone >> here regarding this. >> >> Here's what they want me to do: >> >> o- Turn off the firewall - disable all of the profiles (Domain, Public >> and Private), then turn off and disable the service. >> o- Turn off the Base Filtering Engine (disable the service) >> o- Set DEP for essential Windows programs and services only >> o- Turn off UAC >> o- Do not apply patches released past a certain date, stating >> "When releasing a new build, ShoreTel publishes build notes >> listing the Microsoft >> patches that are certified against the build. ShoreTel also >> highlights software >> changes required by the Microsoft patches. Note that no >> additional Microsoft >> updates should be applied to your ShoreWare server between >> ShoreTel builds. If >> you install Microsoft updates between ShoreTel builds, they >> may have an adverse >> effect on your telephone system. >> Disable Microsoft updates until you review the detailed >> certification provided with >> each release." >> >> >> If you are running ShoreTel, have you run into this, and how do you >> protect your ShoreTel environment, other than firewalling the subnet >> that it's on? >> >> To me, this seems like egregiously broken software, requiring me to >> reduce the security of the server to near zero. >> >> Thoughts appreciated. >> >> Kurt >> >> >
