Comments (0)

By admin, April 24, 2013 10:00 pm

Whenever there is an issue to talk about troubleshooting OWA which results in resetting  the virtual directories I have always seen the PowerShell version of it but how easy to do it via GUI. so why not to do it

Goto Exchange — Server Configuration — Client Access - Right Click the Client Access Server and follow the steps below

DO NOT FORGET TO RUN iisrest /noforce on the CAS Server/Servers

Cheers:)

Comments (0)

By admin, April 22, 2013 12:51 am

In Exchange 2010, passive database copies have a very low checkpoint depth, which is required for fast failover. In addition, the passive copy performs aggressive pre-reading of data to keep up with a 5-megabyte (MB) checkpoint depth. As a result of using a low checkpoint depth and performing these aggressive pre-read operations, IOPS for a passive database copy was equal to IOPS for an active copy in Exchange 2010.

In Exchange 2013, the system is able to provide fast failover while using a high checkpoint depth on the passive copy (100 MB). Because passive copies have 100-MB checkpoint depth, they’ve been de-tuned to no longer be so aggressive. As a result of increasing the checkpoint depth and de-tuning the aggressive pre-reads, IOPS for a passive copy is about 50 percent of the active copy IOPS in Exchange 2013.

Having a higher checkpoint depth on the passive copy also results in other changes. On failover in Exchange 2010, the database cache is flushed as the database is converted from a passive copy to an active copy.

In Exchange 2013, ESE logging was rewritten so that the cache is persisted through the transition from passive to active. Because ESE doesn’t need to flush the cache, you get fast failover.

One other change is background database maintenance (BDM). BDM is now throttled back from 5 MB per sec per copy to 1 MB per sec per copy.

As a result of these changes, Exchange 2013 provides a 50 percent reduction in IOPS over Exchange 2010.

Comments (0)

By admin, April 17, 2013 7:24 pm

Very common and very know topic for New Exchange Admins.
By default each e-mail address has one default policy and it is setup when you configure your Exchange Server. So if you setup your Exchange with Contoso.local it will setup as yourname@contoso.local and this will become your REPLY Address. What happens is that at recipients side when they hot reply it will be repling to .local address not to the .com and you will never receive the reply. In order to fix it un-check the Automatically upgrade e-mail address based on e-mail address policy and you are all set.

Comments (0)

By admin, April 15, 2013 5:06 pm

Microsoft Exchange Server 2013 provides administrative functionality and other enhancements that improve the overall management of Transport Layer Security (TLS). As you work with this functionality, you need to learn about some TLS-related features and functionality. Some terms and concepts apply to more than one TLS-related feature.

What is the difference between Exchange 2010 and Exchange 2013 TLS?
There is NO difference , it works the same. It uses the same Opportunistic TLS mechanism.

So what is Opprtunitics TLS by definition from TechNet?
Opportunistic TLS In earlier versions of Exchange, you had to configure TLS manually. In addition, you had to install a valid certificate, suitable for TLS usage, on the server running Exchange. In Exchange 2013, Setup creates a self-signed certificate. By default, TLS is enabled. This enables any sending system to encrypt the inbound SMTP session to Exchange. By default, Exchange 2013 also attempts TLS for all remote connections.

My previous post about MS Exchange 2010 TLS

Resource URLS
Exchange 2013 TLS Functionality
Exchange 2010 TLS Functionality

Secure messaging is simple too.