So, you have server-side applications that are internal to your environment and require a mechanism in order to send email, but the system itself cannot use a mailbox account due to application limitations. What do you do? In this case you will likely setup relay connectors on your Exchange servers. Before you set these up however, there is one key question to ask.
Will I allow my users to relay internally, externally, or both?
One of the largest challenges many organizations face is how to secure email. Industries such as healthcare and financial have government regulated policy to adhere to such as HIPPA and Sarbanes Oxley. So how do we ensure that our users are not sending out information they shouldn’t be from their desks or mobile devices? Also with the emergence of Bring Your Own Device (BYOD) securing company data is become even more important than it has in the past.
ExFolders is a Microsoft tool that can connect to Exchange 2010 public folders through a GUI and is separate from the Exchange Management Console. This tool has replaced the old PFDavAdmin public folder administration tool that was used with older versions of Exchange. Microsoft has added some backward compatibility within ExFolders and has configured it to work with Exchange 2007, but it must be run from an Exchange 2010 server.
After some recent Exchange troubleshooting I decided to do a small write-up on an attribute most people working with Exchange know about, the infamous exchangeLegacyDN.
For those involved with Exchange migration projects or managing Exchange environments, at some point you probably have experienced a situation where individuals ended up with duplicate items in their mailbox. Duplicate items can be caused by many things, but most common are:
Many customers nowadays are running a virtualized Exchange environment, utilizing Database Availability Groups, load balanced Client Access Servers and the works. However, I also see environments where it is up to the Hypervisor of choice on the hosting of virtual machines after a (planned) fail-over. This goes for Exchange servers, but also for redundant infrastructure components like Domain Controllers or Lync Front-End servers for example.
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.
Writing your own transport agent for Exchange Server 2010 is not complicated or an unsolvable task to do.
This transport agent example is the outcome of a requirement to modify email attachments with a GUID based filename. Those filenames were not really usable for the recipients. Interestingly, the email subject contained the information of the content of the attachments. The emails were automatically generated by a SAP reporting application.
Ok, yes I know – I said that Part 8 was the last in this particular series – but then Microsoft went and released Cumulative Update 1 (CU1) for Exchange 2013 (on April 2nd) which left me feeling that if I did not cover this – then the LAB series was not properly completed. For those of you who are just joining us – you can find links to the previous parts below.
We are now in the final stretch in this series with this being the second to last part of creating a test lab from scratch with Windows Servers 2012 and Exchange 2013. I could in truth perhaps go on forever as there are loads of things that I have not covered. But that is the beauty of a test lab, once you have one that is up and running – it is yours to do with as you choose and that is what I hope that you will all do.