|
Exchange Server 2010 : Risk Mitigation |
Achieving high availability requires that risks are identified and addressed. Many organizations employ risk management practices to capture and address potential disruptions to business processes. |
|
|
|
|
|
|
|
|
|
Using asynchronous services in BizTalk with WCF (part 1) - Consuming asynchronous services |
BizTalk Server natively promotes an asynchronous messaging pattern and readily embraces an event driven architecture. What BizTalk adds to the standalone WCF patterns we've seen above is the injection of a message broker. This middle layer loosely couples the enterprise systems on both ends of the service call while enabling a new set of messaging capabilities not available in standard service implementations. |
|
|
|
|
|
|
|
|
|
Exchange Server 2010 : Achieving High Availability |
A number of barriers stand in the way of achieving high availability. For example, a poor implementation of Exchange might be one where Exchange is installed on improperly sized servers and installed without following best practices. |
|
|
|
|
|
|
|
|
|
Exchange Server 2010 : Federation Scenarios (part 1) - Free/Busy Access |
Let's see how the basic principles of federation and federated delegation and the various components and fundamentals of federated delegation in Exchange Server 2010 all fit together. We'll do this by covering the various federation scenarios in an Exchange Server 2010 environment, and the advantages and drawbacks to each of them. |
|
|