While this is probably not going to be a common problem to many administrators out there, I figure I’d blog this issue I encountered today in case I come across
Those who are familiar with the certificate warning message: Lync cannot verify that the server is trusted for your sign-in address. Connect anyway? … that is presented by the Lync
I recently completed a Lync Server 2010 to 2013 migration and found that setting up RCC integration between Lync Server 2013 and Avaya AES (Application Enablement Services) was exactly the
Ran into an interesting problem today as I was asked to have a look at an Exchange Server 2010 resource mailbox issue since I was already in working on some
One of the tricks I use most over the years while working or troubleshooting issues with OCS and Lync was to manually force the Lync 2010 and 2013 client because
I’ve recently been asked several times to look at why a Lync Server 2013 server’s LS Address Book Server consistently logs the event ID 21054 error whenever the address book
Problem You currently have the following telephony solution in your organization: PBX: Avaya Aura Communication Manager Version R016x.02.0.823.0 Voicemail: Exchange Server 2010 Unified Messaging The Avaya Aura Communication Manager PBX
Veeam has probably been one of the backup applications I’ve recommended to mid sized clients that does not use SAN specific backup features due to how simple it is to
