I’ve noticed recently that I’ve been asked about how to determine what version of Citrix XenDesktop is installed in an environment so I thought I’d quickly write a post to demonstrate this. First off, I
I’ve been asked a few times in the past about why the following message: Upgrades for some services are available. Services can be upgrade on the following controller: <controllerFQDN> Learn more about this upgrade …
I’ve recently been asked at least 5 times over the past 2 months a problem that may seem trivial but at the same time be quite the annoyance. An administrator attempts to change the hostname
Problem You’re attempting to install Veeam Backup and Replication 7.0 on a new Windows Server 2012 server but noticed that as you go through the install and enter the license file you received from Veeam
Problem You’re setting up an RCC integration between Lync Server 2013 and Avaya’s AES (Application Enablement Services) server and while you’ve set up all of the configuration required for Lync Server 2013, users see a
Before I begin, let me state that I doubt many others will experienced the same issue I had even though the error message: Error: Your request can’t be completed right now. Please try again later.
Problem You have several remote users who are trying to set up their Outlook via the Outlook Anywhere service using Autodiscover to detect the settings but all of them are continuously prompted for their password.
Problem You attempt to install the Exchange Database iDataAgent with the CommVault Simpana 9.0 R2 installer on Exchange Server 2013 but notice that the option grayed out: Hovering over the option displays the following message:
Problem You’ve set up federation between 2 Lync Server 2013 environments but notice that only 1 of the company can see presence information and have the ability to send messages while the other company is
I recently had to configure a Directory Sync feature between a cloud based SPAM filtering service and a client’s Active Directory and came across the option of either syncing via regular LDAP port 389 (unecrypted)
