Now that's an interesting thought... Kurt
On Fri, Jul 19, 2013 at 4:54 PM, Kramer, Jack <[email protected]> wrote: > Or Asterisk. > > (sent from a mobile device) > > On Jul 19, 2013, at 7:49 PM, "Brian Desmond" <[email protected]> wrote: > >>> Any remedies for this kind of stupidity that you can recommend? >> >> Lync? >> >> Sorry ... couldn't resist. >> >> Thanks, >> Brian Desmond >> [email protected] >> >> w – 312.625.1438 | c – 312.731.3132 >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Kurt Buff >> Sent: Friday, July 19, 2013 6:15 PM >> To: [email protected] >> Subject: Re: [NTSysADM] A little afield of the normal topic - ShoreTel >> installation >> >> Any remedies for this kind of stupidity that you can recommend? >> >> Other than hunting down and hurting the devs? >> >> Kurt >> >> On Fri, Jul 19, 2013 at 4:05 PM, Webster <[email protected]> wrote: >>> I see mostly the same stupid requirements for most healthcare and finance >>> related software. IOW, their devs are either too stupid or too lazy to >>> build proper Windows apps. But that is just my rant from working so long >>> in the TS/RDS/XenApp world. >>> >>> Thanks >>> >>> >>> Webster >>> >>> >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Kurt Buff >>>> Sent: Friday, July 19, 2013 6:01 PM >>>> To: [email protected] >>>> Subject: [NTSysADM] A little afield of the normal topic - ShoreTel >>>> installation >>>> >>>> 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 >> >> >> > >
