I came across an unusual one today whereby one of the Exchange 2013 servers for a client had stopped accepting POP3 connections. If you were to telnet to the server on port 110 you would just get a blank connection and if you type anything it would end the connection.…
Having recently completed an Exchange 2013 deployment for a large organisation that has a global presence, one of the things that came up was having multiple copies of the Offline Address Book with the generating mailboxes for those OABs located in the different datacentres so its closer to the users…
I had this occur to me recently as I had an Exchange 2010 environment and having installed my first Exchange 2013 server as a CAS & Mailbox. I tried logging into the Exchange Admin Center using the URL https://localhost/ecp and noticed that after I logged in it looked very much…
I was spending some time going through Exchange PowerShell cmdlets to create an Admin Role with the least permissions required for an account for the System Center Configuration Manager Exchange Connector when I stumbled across this excellent script. It was hard to find so I am putting it out there…
Earlier this year Microsoft released an important hotfix for .NET 4.5: A .NET Framework 4.5-based application that excessively uses ExecutionContext objects or WCF may result in too many objects being pinned on the Garbage Collector heap. This causes heap fragmentation along with an increase in memory and CPU usage by the Garbage Collector.
So after installing more than a few times I thought about writing my own powershell script to automate some of the process, there was no need though when I stumbled across this great script..check it out here You wont be disapppointed, I know I wasnt.
I came across an interesting issue the other day whilst working with a client and setting up a new PC for them. The PC had come with Office 2013 OEM which as you know is the latest edition of the popular Microsoft Office suite of programs. What struck me as…