This site is now a static archive. No new posts or comments can be made.
While hybrid exchange environments are awesome for stretching your on premise exchange topology to Office 365, they do introduce a bunch of complexity - primarily around user creation, licensing, and mail flow. I recently had an issue at a client where they had email bounce-backs from an on premise service destined for a few Exchange…
Continue readingI've done a few of these.... but most corporates (at least that I've dealt with) use public folders quite lightly - if at all.... so the migrations have been quite simple. Recently, I was tasked with moving a smaller business (through a partner) from 2007 to 2013 then 2016. The mailbox move from 2007 to…
Continue readingI recently had a client experience an issue with their hybrid exchange setup (365/On Premise) - users were suddenly unable to retrieve free/busy and calendar information between the two environments. As it turns out, the certificate used to secure communications to the Microsoft Federation Gateway (MFG) had expired. Federation certificates within exchange are generally created…
Continue readingOn a recent gig, the local tech wanted some more detail on the receive connector selection process... I explained the whole "most defined" IP set wins (i.e. 192.168.0.23 will be selected over 192.168.0.0/24), but was unable to find any TechNet articles to back that up. Fortunately, this guys nails it, with a good explanation and…
Continue readingA patch for exchange 2013 and 2016 sets all exchange services (and IISAdmin and W3SVC) to disabled after installing https://technet.microsoft.com/en-us/library/security/ms16-010.aspx Its not a disaster, just simply set all the services back to automatic, start them, and away you go.... Still, the joke conspiracy from a mate of mine a while back of "The marketing team…
Continue readingDoes it make me nerdy that I found this an interesting/good read ? http://blogs.technet.com/b/exchange/archive/2015/05/05/exchange-server-2016-architecture.aspx
Continue readinghttp://social.technet.microsoft.com/wiki/contents/articles/953.microsoft-anti-virus-exclusion-list.aspx I am still very much of the opinion that file level anti-virus does not belong on servers such as exchange, SQL, SCCM etc... however, for places that flat-out refuse to apply logic - and want anti-virus on everything, this is a very good starting point to apply the mountains of exclusions required.
Continue readingI have a client for whom i recently implemented 2012 Direct Access.... there was a number of teething problems in the implementation - but once its working, DA is actually pretty good. If i could ask the product team for anything in DA 2012 R2, it would be re-introduce wildcard certificate support (it was in…
Continue readingFound this article today http://theessentialexchange.com/blogs/michael/archive/2013/01/06/exchange-server-2013-gotchas.aspx it's nigh on 3 months old - but it lists some of the issues with Exchange 2013 RTM. Prior to finding this article - I hadn't been able to find any list of issues with the release, but my own list of issues was growing. Exchange 2013 release seems to…
Continue readingExchange recoveries don't come up very often these days (for me at least), with exchange 2010 and win 2008R2 being so solid... and virtualisation... the loss of server hardware or corruption of the OS is just becoming less and less common. Anyhoo - a client had a SAN disk die - and for reasons which…
Continue reading