This post is about a recent migration of legacy public folders hosted on Exchange Server 2007 to modern public folders hosted on Exchange Server 2013.
After preparing federation between Office 365 and the on-premise Active Directory and configuring the Office 365 tenant in the previous post, this article describes the installation of the Microsoft Online Services Directory Synchronization Setup (DirSync).
DirSync is required to synchronize your on-premise accounts and security groups to Office 365.
The setup file has been downloaded from the Office 365 admin center previously. Be aware that you might receive an error during setup
Click Next in the welcome screen.
(click image to enlarge)
After preparing the AD FS requirements and installing the AD FS Server Role in part 1 this article describes the steps to configure the Active Directory Federation Services for further use and the eventual integration with Office 365.
Start the AD FS Management console by selecting the AD FS Management tile on the start screen or be using the link in the Server Manager task list.
Click each photo to enlarge
To configure an Exchange Server 2013 hybrid deployment with Office 365 you need to have Active Directory Federation Services (AD FS) configured properly in your on-premise environment. The short series of articles about AD FS show you the easy steps to configure your AD FS deployment.
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.
Without the new transport agent the original email looks like this:
The automatically generated email contains two attachments (two different file types just for the sake of demonstration).
The email subject contains the report date in dd.MM.yyyy format.
The transport agent should perform the following actions:
When it comes to monitoring application administrators often disagree with system administrators on what to monitor and which thresholds to configure. By nature system administrators focus on system related counters and objects to monitor. They do not care about application related monitoring as those information's are out of scope of their daily work. Vice versa the same is true for application administrators.
Therefore there is no and will never be a single monitoring solution to combine totally different interests in information. On the other hand the business is highly interested in implementing a single monitoring solution to reduce the overall licensing cost (priority 1), reduce the number of servers required to host monitoring solutions (priority 2) and to eliminate the need for technical training (priority 3).
System monitoring and application monitoring systems sometimes share an intersecting set of “things” they are able to monitor. The fact is that both monitoring approaches have totally different procedures on how to monitor.
The following diagram illustrates the system monitoring approach, where a probe connects to a target and queries data using a dedicated protocol supported by the target (e.g. SNMP, WMI, SSH, etc.).