|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Exchange 2010 : Managing Exchange Recipients (part 4) |
| Moving mailbox content to and from PSTs by using the ExMerge utility has been a normal function of an Exchange administrator's job. Although Exchange 2007 was released without a supported method to import and export mailboxes to PST files, this was promptly rectified in Service Pack 1 and again improved in Exchange 2010 and Exchange 2010 SP1 |
|
| Exchange 2010 : Managing Exchange Recipients (part 3) |
| Exchange 2010 resource mailboxes will be familiar to any administrator that has spent time with a previous version of Exchange. Exchange 2010 has some improvements that will make the Exchange administrator's job a little easier. |
|
| Exchange 2010 : Managing Exchange Recipients (part 2) |
| Mail contacts are mail-enabled Active Directory contacts that contain information about recipients that exist outside your Exchange Server organization. Mail contacts are visible in the GAL, and can be added as members to distribution groups |
|
| Exchange 2010 : Managing Exchange Recipients (part 1) |
| Exchange has several options with which an administrator can successfully manage the environment. These options are through the EMC, EMS, and ECP. The EMC is where a lot of administrators traditionally start to manage Exchange |
|
| Exchange Server 2010 : Designing and Implementing Personal Archives |
| Exchange Server 2010 introduces an integrated archive solution named personal archives; this solution provides an alternative to personal store (.pst) files, providing you with the means to phase out these files by importing them to the personal archive associated with the user's mailbox. |
|
| Exchange Server 2010 : Designing and Implementing Message Journaling |
| Archiving refers to reducing the amount of data in a user's primary mailbox by moving it to different storage (another mailbox, in the case of Exchange Server 2010 archiving); journaling is the ability to record all e-mail communications in an organization for archival purposes to meet with compliance and regulatory requirements. |
|
|
|
|
|
|
|
| Exchange Server 2007 : Manage Resource Mailboxes |
| Managing resources given mailboxes is a key element that is best given to someone else to worry about. As an administrator you don’t want to be responsible for every room, projector, laptop, and so forth your company might have. |
|
| Exchange Server 2007 : Create Resource Mailboxes |
| The calendar and scheduling features in Exchange are excellent and often used to keep track of more than people; it also tracks rooms and equipment (such as projectors and other equipment). Can we create mailboxes that are not for sending and receiving mail, but for scheduling purposes? |
|
| Exchange Server 2007 : Create a Linked Mailbox |
| Linked mailboxes are user mailboxes (they are exactly the same as any other mailbox) that are accessed by users in a separate, trusted forest. The reason for a mailbox of this sort is that when you have Exchange deployed in a resource forest, the resources are in one forest, whereas the user accounts are in another trusted forest. |
|
| Exchange Server 2007 : Configure Mailbox Properties and Settings |
| For the most part, the options and dialog boxes that are part of the mailbox properties for a recipient are self-explanatory. However, three tabs (Mailbox Settings, Mail Flow Settings, and Mailbox Features) are more complicated and seem important. How do we configure a mailbox using these three tabs and their corresponding settings? |
|
| Exchange Server 2007 : Use Managed Content Settings |
| Users require assistance in managing their content, particularly when it comes to permanently deleting items they no longer need. At times, they might also need additional folders they can access and use. How do we resolve the use of managed content settings for both default and custom-made folders? How do we create the policies needed for these settings and then apply those policies to our users? |
|
| Exchange Server 2007 : Work with Offline Address Books |
| The purpose of an OAB is to provide access to the address information while offline, so there are a few things administrators can configure. They can create additional address books, they can choose which ones are made available, and they can determine the distribution method used (either web-based or Public Folder distribution). |
|
| Exchange Server 2007 : Work with Address Lists |
| As a user, when you work with your client application (for example, Outlook or Outlook Web Access) and you attempt to send an email or select the Address Book icon, you are shown address lists that have been created by default |
|
|
|
|
|
| Exchange server 2010 : Troubleshooting Tools (part 1) |
| Even a well-designed and operated Exchange system will eventually experience problems that you need to identify and repair. The previous section explained the troubleshooting methodology. This section highlights some of the top tools available for troubleshooting. |
|
|
|
| Relationship between BizTalk and WCF |
| Given this information, we see that the intersection of these two technologies occurs at the point where the BizTalk messaging and orchestration engine need to communicate effectively with the outside world. |
|
| Monitoring Exchange Server 2010 (part 1) - System Center Operations Manager 2007 R2 |
| System Center Operations Manager 2007 R2 (SCOM) is the platform monitoring and reporting solution from Microsoft. SCOM provides end-to-end service management that includes monitoring, troubleshooting, and reporting tools. SCOM uses the concept of management packs to extend the base framework for specific applications, such as Exchange 2010. |
|
| Monitoring Exchange Server 2010 (part 1) - Performance Monitor |
| With many Exchange projects, monitoring comes late in the project, or even worse, after the project completes. Having a robust monitoring solution and processes can greatly improve your ability to identify, troubleshoot, and repair issues before impacting end users. |
|
