February 2008 - Posts
When we are talking about Exchange 2007 Resource Mailboxes the Delegate feature becomes essential because the mailboxes defined as Delegate can approve meeting requests.
In order to define the Delegates in the resource mailboxes using Exchange Management Shell, we can use the following cmdlet:
Set-MailboxCalendarSettings <Resource Mailbox> -ResourceDelegates <Mailbox>
The second way to define a Resource delegate is using Outlook, in the current post we are going to use Outlook just to validate the new entry created by EMS. Just open the Resource Mailbox using the Outlook and check Delegates Tab out as shown below (To get there click on Tools / Options and Delegates tab).
To understand and configure approval process for a resource mailbox, you can use the following MS document: http://technet.microsoft.com/en-us/library/aa996338(EXCHG.80).aspx
If you still have Exchange Server 2007 RTM the Rollup update #06 was released yesterday. This update can be found at http://www.microsoft.com/downloads/details.aspx?familyid=0b2993a3-d290-453e-85fe-108867865731&displaylang=en&tm
Please pay attention to the note section of the download page:
This update rollup does not apply to Exchange Server 2007 Service Pack (SP1). For a list of update rollups applicable to Exchange Server 2007 SP1, refer to the section Update rollups for Exchange Server 2007 Service Pack 1 in the Knowledge Base article KB937052.
This is a follow-up to an earlier post: Single-label Domain Names and Exchange Server 2007 SP1. Please refer to it for background information on this issue.
After investigating Exchange 2007 Service Pack 1 installed in an Active Directory domain with a Single-label Domain (SLD) name, Microsoft has changed the Setup prerequisite rule for SLDs from an Error to a Warning, thereby allowing Service Pack 1 installation to continue in SLD environments.
There are a few items that I want to point out:
- Not a recommended configuration
While Exchange 2007 SP1 is supported with SLDs, the Exchange product team's view is that SLDs are not a recommended configuration. While we will allow installation of Exchange 2007 SP1 in an SLD, we strongly recommend that you take step to move your organization out of this configuration.
- Not fully tested
Exchange 2007 and Exchange 2007 SP1 have not been fully tested in SLDs. The Exchange team investigated known issues and determined that there were sufficient workarounds to safely allow installation of SP1 to continue; however, there may be unknown issues that could arise from operating Exchange 2007 in an SLD environment.
- Deprecated in the next version of Exchange
The next version of Exchange will not support Active Directory domains with single-label domain names. Similarly, upgrades of Exchange servers currently deployed in single-label domains will not be supported. In this case, "next version" means the next major release of Exchange Server. Customers that intend to deploy the next version of Exchange must use fully qualified domain names.
- Documentation being updated
Currently, the existing TechNet documentation states that SLDs are not supported in Exchange 2007. We are working to change the documentation to reflect that SLDs are supported but not recommended configurations. The updated documentation is expected to be published on TechNet as part of the March 2008 document refresh in early March.
- Exchange 2007 does not support Domain Rename, and there are currently no plans for a Domain Rename Fixup Tool for Exchange 2007
The possibility of creating a domain rename fixup tool for Exchange 2007, similar to the one that was written for Exchange 2003, was discussed internally. The decision is that there will not be a similar tool written for Exchange 2007. The Domain Rename Fixup tool written for Exchange 2003 is not compatible with Exchange 2007, and should not be used in Exchange 2007 environments.
Read more at source: http://msexchangeteam.com/archive/2008/02/15/448140.aspx
System Center Capacity Planner 2007 is a pre-deployment capacity planning and post-deployment change analysis solution for Exchange Server 2007.
Get it here: http://www.microsoft.com/downloads/details.aspx?FamilyId=E754F35D-59DB-4BC4-8386-E83E66A16FAD&displaylang=en
If you are going to use the Microsoft Transporter to copy content from a POP3/IMAP4 to Exchange Server 2007, the Exchange Impersonation permission must be done before using the Microsoft Transporter. This permission can be assigned in a specific CAS Server, but if you are going to use a single one you must specifiy it during the wizard. There is an example in the documentation that explains how to apply the permission for all CAS Servers, in this post we will be applying in a single CAS server.
First of all, get the Client Access Server distinguishedname attribute, through the following cmdlet:
get-clientaccessserver | select name,distinguishedname | fl
Now that we have the distinguesdname handy, we can assign the permission using the following cmdlet:
add-adpermission -Identity <CAS distingueshed name> -User <user> -ExtendedRights ms-Exch-EPI-Impersonation
Now, we can move on and use the Microsoft Transporter to copy content from POP3/IMAP4 servers.
If you are experiencing a failure in the Hub Transport service and the eventid 5023 is appearing in your event viewer. Then, there is a new kb to fix it, check this out: http://support.microsoft.com/default.aspx?scid=kb;en-us;948000&sd=rss&spid=10926
Basically, the msExchHomeRoutingGroup attribute is empty and must be filled up with the value of the Exchange Server 2007 unique routing group name.