While migrating from Microsoft Exchange 2010 to Exchange 2016 we came upon a typical issue in which Outlook keeps giving the message: “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook“. This means that users
As part of my Security Best Practices regarding Microsoft Exchange and Microsoft IIS I always implement a couple of configuration settings to harden the underlying IIS, e.g. disabling the “X-AspNet-Version” header, disabling deprecated and/or unsecure protocols, disabling deprecated and/or unsecure
Citrix XenDesktop 7.x – Citrix Session Printers are not visible via Control Panel, Devices And Printers Affected System: Windows Server 2012 R2 as well as Windows Server 2016 Citrix Environment: XenDesktop 7.15 LTSR CU2
Citrix NetScaler – Firmware Upgrade using CLI Upgrade methodology Download latest firmware from Citrix Homepage Backup existing NetScaler config Copy firmware to Netscaler Upgrade firmware via CLI Reboot NetScaler Verify configuration and functionality Requirements Latest NetScaler firmware tar file Windows
Just recently I ran into an error during initial setup of Exchange 2016 on a newly installed Windows Server 2012 R2 stating: “Service ‘MpsSvc’ failed to reach status ‘Running’ on this server“. Further down the troubleshooting road I found out that
As I did quite some Exchange migrations (including single as well as multi tenancy environments) I was always wondering whether there are any additional post migration tasks that need to be addressed before you start removing your legacy Exchange server(s)
Just recently I was tasked to identify all Citrix Receiver Versions connecting to a Citrix XenDesktop 7.x environment. For starters, to get information on current sessions issue the following PowerShell cmdlets on your Citrix Broker Server: Add-PSSnapin *Citrix* Get-BrokerSession |
If you want to use your NetScaler for all things that need to be accessible from the outside, over a single IP address, that poses an issue. As is usually a problem with small to medium sized businesses which only have
After logging into Exchange 2016’s ECP you receive an HTTP Error 500 (same goes with OWA): Searching the internet ends up with several possible solutions to this issue, ranging from missing System Attendant Mailboxes, to bogus ADSI settings regarding the
This short blog describes how to enable NetScaler 11’s Content Switching feature to proxy your AD FS infrastructure thus getting rid of a dedicated AD FS Proxy server.