Blogsphere Weekend Read [2010-06-12]
- VBscript to Tell the Last Time the OAB was Downloaded
EXPTA - Download Microsoft Exchange Server 2010 SP1 Beta
Microsoft - Exchange 2010 SP1: Change to how static ports are assigned on a CAS server
MSExchange.org - Exchange 2010 SP1 : Themes in Outlook Web App (OWA)
Nitin Gupta - MS Exchange: Exchange 2010 Role Based Access Control (Part 1)
MsExchange.org - RBAC Database Scopes in #Exchange Server 2010 SP1 Beta
Mike Pfeiffer - TechEd 2010 Recording - Failover Clustering Pro Troubleshooting with Windows Server 2008 R2
MS Teched - TechEd 2010 Recording: Microsoft Exchange Server 2010: High Availability Deep Dive
MS Teched - Exchange 2010 SP1 - Enable Personal Archive (Mailbox)
Nitin Gupta
Backup/Restore/Manage your Exchange whitelist using exchange management shell
I will show you today how to manage, backup and restore you sender safe list on Exchange 2007 and 2010 using exchange management shell cmdlets.
To add a entry
$SafeSenders = (Get-ContentFilterConfig).bypassedSenders $SafeSenders.Add("user@safedomain.com") Set-ContentFilterConfig -BypassedSenders $SafeSenders
To remove an entry
Blogsphere Weekend Read [2010-06-05]
- Multiple Exchange ActiveSync accounts supported in Windows Phone 7
Mobility Minded - Eliminating Traditional Backups using native Exchange 2010 Functionality (Part 3)
MsExchange.org - Allowing End-Users to Manage Distribution Group Membership in Exchange 2010
SysAdmin talk - Customizable Script In Exchange 2007 SP2 Rollup Installation
MS Exchange Team - Using Dynamic Signatures in Exchange 2010
ExPTA - 10 Email Archival Best Practices and Considerations
The Email Admin
Don’t wait for the weekend to get the hottest links. You can get them fresh by following us on twitter
BIS & other EWS applications in Exchange 2007 to 2010 coexistence
I have received comments about my "Installing your first Exchange 2010 CAS" 3 parts - tutorial that it didn't include any reference to services other than OWA. The reason behind this is simply because other services like ActiveSync, POP3, IMAP4, will work through proxying without the need for any additional configuration other than what has already been covered.
However I have faced a strange issue with Exchange Web Services and coexistence of Exchange 2007 and 2010. Since it is clearly stated on technet that
Clients that use Exchange ActiveSync, Exchange Web Services, POP3, and IMAP4 can't use redirection.
I thought it is safe to assume that EWS traffic will be proxied just like it is the case of ActiveSync, POP3 and IMAP4. My thoughts were further confirmed by the same technet article stating that Proxying supported between Client Access servers in the same Active Directory Site for the Exchange Web Services protocol (check section "Client Access protocols for redirection and proxying"), but obviously my thoughts were wrong!
Doing some tests with requests hitting the Exchange 2010 CAS server & using the famous test exchange connectivity website showed failures for users who's mailboxes are still on Exchange 2007 with the following error, while the test passed for users who's mailboxes are now on Exchange 2010.
The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.
So it seems that the only way for EWS to work in a mixed Exchange 2007-2010 environment is that the application itself should support Autodiscover.
This is bad news, it means that my client will need to edit manually the settings for all its Blackberry Internet Service (BIS) users!
At this point I am still unsure if it is a bug but it looks like one, so if someone has more insight about it I would really appreciate the feedback.
Exchange 2010 DAG IP fails to be brought online
While running an Exchange 2010 Database Availability Group you might encounter an error in the System Log of your mailbox server stating that
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 2' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.
Open the Failover Cluster Manager go to Networks and select the faulty network reported in the above error. You will notice that "Allow clients to connect through this network" is enabled.
This seems to be a bug and the solution is pretty easy, you just need to deselect "Allow clients to connect through this network", click on Apply, select it again and apply once more the new configuration, this should take care of the error right away.
Blogsphere Weekend Read [2010-05-29]
- Backing up Exchange 2010 For Free
Simple Talk - NetApp Best Practices for Exchange 2010
NetApp Community - Datacenter Activation Coordination (DAC) Mode In Exchange 2010 DAG
How Exchange Works - 8 Useful Public Folder Management Scripts in Exchange Server 2010
The email admin - Automatic Active Directory RMS protection with transport rules
msExchange.org - Using Cmdlet Extension Agents to cause automatic events to occur in Exchange 2010
Exchange Server Blog
