Have you encountered an instance where Exchange cannot deliver mail to a destination on the Internet? This is becoming more and more common. You may question why this is happening in the first place and why it’s becoming more common.
ENow Software's Exchange blog built by Microsoft MVPs for IT/Sys Admins.
Lasse works as a consultant performing almost anything related to Exchange server, Architect/Reviewer/Design/development and teaching, and sometimes MOC material but also client specific. Lasse understands large enterprise environments as well as the small environment. His knowledge and understanding of customer needs makes him the perfect team member of migration/consolidation projects. Besides doing consulting he speaks at conferences and seminars and if time permits, he writes technical articles. Lasse Pettersson has been awarded the title MVP (Most Valuable Professional) by Microsoft since 2005 for his work with Exchange server. Lasse focus on Exchange server but also work with other products and technologies such as Lync server, Active Directory, firewalls and network communications. You can read his blog "a new message has arrived".
The anti-spam agent installation process with Exchange 2013 is similar to previous versions of Exchange. When you install anti-spam agents on Exchange 2013 servers, most agents will be installed on the mailbox role but not the Connection filtering agent, also known as RBL, DNS Block List, etc.
Face it, most Exchange administrators look forward to their weekly patching projects about as much as you and I look forward to our next trip to the dentist. Throw in the extra complications of switching from a non-clustered environment to one that is clustered and the word root canal comes to mind. When working with non-clustered servers one can usually just use WSUS or other patching products which require simple install patches and then a restart or a reboot of the windows box. If this is done in an Exchange environment with clusters however, the same process could end in disaster.
Exchange admins are from time to time doing mailbox moves. There could be several reasons for doing this, but the goal is often to create some white space in the mailbox databases.
Ever tried to publish Outlook Anywhere using NTLM with TMG and use Kerberos Constrained Delegation? Many people have tried and failed, or at least had some major trouble before they were finally able to get things going.
To help make things a little easier, here is a simple checklist on how to publish Outlook Anywhere using NTLM with TMG, using Kerberos Constrained Delegation.
For many generations, Outlook Web Access allowed users to change their password, but only after they had successfully logged on to OWA. With Exchange 2007 Service Pack 3 and the upcoming Exchange 2010 Service Pack 1, administrators now have the ability to change the password pretty much the same way users do when they log on to Windows on their PC.