Cookies CSS

Wednesday, August 8, 2018

Which version of Skype for Business is recommended.

We recommend matching the architecture of the OS on which you are running.

If you are on a 32 bit OS, you must run 32 bit Skype for Business.  If you are on a 64 bit OS, the choice gets a little more complex.

While it is technically possible to run 32 bit Skype for Business on a 64 bit OS, there are some complicating factors.  Our recommendations are based on the need for scalability and performance.

The primary purpose for running our application is to handle larger volumes of calls than would be handled by the average user.  In addition, the operator is also a very customer facing of representation of the company.  Therefore, the performance of Skype is paramount.  We recommend running 64 bit Skype for the following reasons.

  • 4gb memory limit imposed by 32 bit architecture.  32 bit applications must reside under the 4gb memory limit regardless of the amount of memory in the machine.
  • 32 bit applications are handled by an emulation subsystem called WoW64.  All inter-program communication and access to hardware must cross this emulator.
For simple day to day applications, these differences are insignificant.  Often times, 32 bit applications are deployed for greater compatibility with 3rd party applications which do not offer a 64 bit options.  However, for a primary application, they can affect stability and performance.

And for these reasons, we recommend 64 bit Skype for Business for operators running our application.

Wednesday, April 4, 2018

Configuring m365 Exchange account for Exchange on the TAPI Connector

To set up Application Impersonation to allow the BOC Exchange Connector to connect and gather calendar information, you will need to configure the user in your Microsoft 365 portal.









Create a new Role Group.  The name is unimportant, but should help you identify it.
Add to the group, the user you've designated for the Exchange Connector.








Wednesday, January 17, 2018

Error Exception has been thrown by the target of an invocation.

There is an issue with a Microsoft security patch and .Net 4.7.1 on Windows 7 or Windows 2008.
It does not appear to affect Windows 10 or Server 2012 and later.

Microsoft is releasing new information on this issue daily.
It is not natively a 4.7.1 issue, but rather a security update that accompanies it. (KB4055002 or KB4055532)

Removing the patch and/or .Net 4.7.1 will resolve the issue. You will need a version of .Net for the application to run.  You can install .Net 4.5.2 to satisfy the requirement.

If you still need 4.7.1, you can follow this. (It will be secure according to these steps)

More information can be found here.