Exchange Server 2010 SP2 Microsoft download sayfasında yayınlandı. Daha önce SP2 ile birlikte gelecek yenilikler hakkında bilgi sahibi olmuştuk. Artık bunları PROD ortamlarımızda kullanabilir durumdayız.

Bana göre en önemli özelliklerden birisi farklı sitelardaki bulunan CAS sunucuları arasındaki silent redirection mekanizmasındaki gerçekleştirilen geliştirme.

Exchange 2007 ve SP2 öncesi 2010 ile birlikte birden fazla active directory site’ına sahip bir organizasyonda redirection mekanizması aşağıdaki gibi çalışmaktaydı;

Exchange 2010 organizasyonunda iki farklı internet facing CAS sunucusunun iki farklı active directory site’ında yer aldığını düşünelim.

Yukarıdaki gibi bir senaryoda iki farklı datacenter üzerinde bulunan CAS sunucular internet facing şekilde konfigure edilmiştir. Yani kullanıcı mail.datacenter1.com adresine girdiğinde ilk site üzerindeki CAS sunucusu kendisini karşılayacak, mail.datacenter2.com adresine girdiğinde ise ikinci site üzerindeki CAS sunucusu karşılama gerçekleştirecektir. Yapının bu şekilde çalışması için CAS sunucular için external url konfigurasyonlarının doğru yapılması gerekiyor.

Ancak eğer mail.datacenter2.com owa adresine bağlantı gerçekleştiren ancak mailbox’ı site 1 üzerinde tutulan bir kullanıcı için redirection mekanizması devreye girmektedir.

• Eğer site1 üzerindeki CAS sunucu için bir external URL adresi belirtilmediyse site2’deki CAS sunucusu istemciyi proxy ederek site1’e gönderecektir. Eğer site1 CAS IIS dizinleri için integrated authentication konfigurasyonu gerçekleştirildiyse kullanıcı SSO şekilde tek auth bilgisi girerek doğru site’a yönlendirilecektir.
• Ancak site1 üzerindeki CAS sunucuda external URL değeri null olarak konfigure edildiyse site2 CAS sunucusu istemciyi proxy yerine redirect mekanizması ile yönlendirecektir. Bu şekilde bir yönlendirmede kullanıcıya aşağıdaki gibi bir ekran çıktısı gösterilir.

Ancak bu şekilde bir yönledirmede ne yazıkki SSO mekanizması devreye girmeyecek ve istemciden bir kez daha auth bilgileri doğru CAS site için istenecektir.

SP2 ile gelen yenilikte ise bu şekilde bir senaryoda FBA auth mekanizması kullanılsa dahi (integrated dışında SSO desteklenmiyordu) SSO ile silent redirection’ın desteklendiğidir.

Aşağıda Technet sayfasında Exchange 2010 implementasyonu sırasında sanallaştırma altyapısı kullanılacak ise dikkat edilmesi gereken noktalar belirtilmiş.

Only management software (for example, antivirus software, backup software, or virtual machine management software) can be deployed on the physical root machine. No other server-based applications (for example, Exchange, SQL Server, Active Directory, or SAP) should be installed on the root machine. The root machine should be dedicated to running guest virtual machines.

Microsoft doesn’t support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between clustered root servers. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn’t employ clustered root servers, or the clustered root servers have been configured to never failover or automatically move mailbox servers that are members of a DAG to another root server.

Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it’s running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren’t application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn’t supported.

Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the host system. On a system with this configuration, don’t allocate more than a total of 16 virtual processors to all guest virtual machines combined.

When calculating the total number of virtual processors required by the root machine, you must also account for both I/O and operating system requirements. In most cases, the equivalent number of virtual processors required in the root operating system for a system hosting Exchange virtual machines is 2. This value should be used as a baseline for the root operating system virtual processor when calculating the overall ratio of physical cores to virtual processors. If performance monitoring of the root operating system indicates you’re consuming more processor utilization than the equivalent of 2 processors, you should reduce the count of virtual processors assigned to guest virtual machines accordingly and verify that the overall virtual processor-to-physical core ratio is no greater than 2:1.

The operating system for an Exchange guest machine must use a disk that has a size equal to at least 15 GB plus the size of the virtual memory that’s allocated to the guest machine. This requirement is necessary to account for the operating system and paging file disk requirements. For example, if the guest machine is allocated 16 GB of memory, the minimum disk space needed for the guest operating system disk is 31 GB.
In addition, it’s possible that guest virtual machines may be prevented from directly communicating with fibre channel or SCSI host bus adapters (HBAs) installed in the root machine. In this event, you must configure the adapters in the root machine’s operating system and present the LUNs to guest virtual machines as either a virtual disk or a pass-through disk. 

Özellikle işaretlediğim kısımlar birçok proje planlamasında atlanan nokta olabiliyor.Nedir bunlar?

Microsoft, Exchange yüksek erişebilirlik çözümleri kullanılacak ise bunun hyper visor tabanlı cluster çözümleri, migration seçenekleri ile kullanımını desteklememektedir.DAG yapısını ancak root cluster çözümünün kullanılmadığı durumlarda aktif edebiliyorsunuz.

Vmware bu konuda ne diyor?

Enhanced Clustering Support for Microsoft Windows – Microsoft Cluster Server (MSCS) for Windows 2000 and 2003 and Windows Server 2008 Failover Clustering is now supported on an VMware High Availability (HA) and Dynamic Resource Scheduler (DRS) cluster in a limited configuration. HA and DRS functionality can be effectively disabled for individual MSCS virtual machines as opposed to disabling HA and DRS on the entire ESX/ESXi host

Eğer Vsphere update 1 geçerseniz, içerideki sanal makineyi HA disable duruma getirdiğiniz takdirde çözümünüz vmware tarafında supported hale geliyor.

Bir diğer önemli kısım ise processor ratio değerleri.

Exchange server, üzerinde çalıştığı sanal makine konfigurasyonunda virtual processor-to-logical processor oranının 2:1′den büyük olmaması istiyor.Bunun dışında kalan konfigurasyon aynı şekilde unsupported olarak görülmektedir.

As you know, standard Get-Mailbox cmdlet don’t have stateorprovince and description properties.Just check with

[powershell] Get-Mailbox | Get-Member [/powershell]

Well then, what is the best way to get these properties within one single script?

In the script below, all users which has mailboxes, are exported with Organizational Unit, Display Name, State or Province, Description and Primary SMTP Address fields.

[powershell]import-module activedirectory
$exchangesunucular = Get-MailboxServer
$tumkullanicilar = @()
$tumkullanicilarexport = @()

foreach ($sunucu in $exchangesunucular)
{
$tumkullanicilar += Get-Mailbox -Server $sunucu
}
foreach ($kullanici in $tumkullanicilar)
{
$obj = new-object psObject
$info1 = get-mailbox -identity $kullanici.displayname | select PrimarySMTPAddress,Office, DistinguishedName
$tmp = [adsi](“LDAP://” + $info1.DistinguishedName)
$info2 = get-user -identity $kullanici.displayname | select distinguishedname,stateorprovince
$tmp2 = [adsi](“LDAP://” + $info2.DistinguishedName)

$obj |Add-Member -MemberType noteproperty -Name “Display Name” -Value $kullanici.DisplayName
$obj |Add-Member -MemberType noteproperty -Name “Description” -Value $tmp.description.value
$obj |Add-Member -MemberType noteproperty -Name “OU” -Value $kullanici.organizationalunit
$obj |Add-Member -MemberType noteproperty -Name “Alias” -Value $kullanici.alias
$obj |Add-Member -MemberType noteproperty -Name “SMTP Address” -Value $kullanici.PrimarySmtpAddress
$obj |Add-Member -MemberType noteproperty -Name “Database” -Value $kullanici.Database
$obj |Add-Member -MemberType noteproperty -Name “State” -Value $info2.stateorprovince

$tumkullanicilarexport += $obj
}

$tumkullanicilarexport |Export-Csv c:\Export.csv –NoTypeInformation [/powershell]

[powershell]Get-Mailbox | where { $_.ExchangeUserAccountControl -eq “Accountdisabled” -and $_.recipienttypedetails -eq “usermailbox”  } | select name | Export-Csv c:\disableduserswithmailboxes.csv[/powershell]

Want to create a group of test users in your lab? Use this command:

1..100 | ForEach { Net User "User$_" MyPassword=01 /ADD /Domain; Enable-Mailbox "User$_" }

Now let’s comment about how to remove these 100 users with powershell ?

If you previously implemented Exchange Server 2010 RTM and after a while ,you upgraded to SP1, you should realize about mailbox move process times.Now it is taking more.

This is because parallel move values is set to 2 on Exchange Server SP1.

In RTM version;

MaxActiveMovesPerSourceMDB : Number of mailboxes that can be moved on source mailbox database.Default value was 5.

MaxActiveMovesPerTargetMDB : Number of mailboxes that can be moved on target mailbox database.Default value was 5.

But in Service Pack 1;

MaxActiveMovesPerSourceMDB : Default value is 5

MaxActiveMovesPerTargetMDB : Deafult value is 2

That means we can only move 2 mailbox concurrently.

Also you can edit your MSExchangeMailboxReplication.exe.config file and customize as you want.

You can use the

script to balance the active mailbox databases copies across a DAG. This script moves databases between their copies in an attempt to have an equal number of mounted databases on each server in DAG. If required, the script also attempts to balance active databases across sites.

The script provides two options for balancing active database copies within a DAG:

BalanceDbsByActivationPreference   When this option is specified, the script attempts to move databases to their most preferred copy (based on Activation Preference) without regard to Active Directory site.
BalanceDbsBySiteAndActivationPreference   When this option is specified, the script attempts to move active databases to their most preferred copy, while also trying to balance active databases within each Active Directory site.

All parameters from Technet;

DagName

Specifies the name of the DAG you want to rebalance. If this parameter is omitted, the DAG of which the local server is a member is used.

BalanceDbsByActivationPreference

Specifies that the script should move databases to their most preferred copy without regard to Active Directory site.

BalanceDbsBySiteAndActivationPreference

Specifies that the script should attempt to move active databases to their most preferred copy, while also trying to balance active databases within each Active Directory site.

ShowFinalDatabaseDistribution

Specifies that a report of current database distribution be displayed after redistribution is complete.

AllowedDeviationFromMeanPercentage

Specifies the allowed variation of active databases across sites, expressed as a percentage. The default is 20%. For example, if there were 99 databases distributed between three sites, the ideal distribution would be 33 databases in each site. If the allowed deviation is 20%, the script attempts to balance the databases so that each site has no more than 10% more or less than this number. 10% of 33 is 3.3, which is rounded up to 4. Therefore, the script attempts to have between 29 and 37 databases in each site.

ShowDatabaseCurrentActives

Specifies that the script produce a report for each database detailing how the database was moved and whether it is now active on its most-preferred copy.

ShowDatabaseDistributionByServer

Specifies that the script produce a report for each server showing its database distribution.

RunOnlyOnPAM

Specifies that the script run only on the DAG member that currently has the PAM role. The script verifies it is being run from the PAM. If it is not being run from the PAM, the script exits.

LogEvents

Specifies that the script logs an event (MsExchangeRepl event 4115) containing a summary of the actions.

IncludeNonReplicatedDatabases

Specifies that the script should include non-replicated databases (databases without copies) when determining how to redistribute the active databases. Although non-replicated databases can’t be moved, they may affect the distribution of the replicated databases.

Confirm

The Confirm switch can be used to suppress the confirmation prompt that appears by default when this script is run. To suppress the confirmation prompt, use the syntax -Confirm:$False. You must include a colon ( : ) in the syntax.

With Exchange Server 2010 SP1, several scripts came available for High Availability actions.

StartDAGServerMaintenance.ps1

• Suspends Mailbox Database Replication
• Pauses High Availability Node
• Sets the DAG node on blocked
• Movel databases to other nodes

You can use this script to safely upgrade operating system or Exchange Server (rollups or service packs)

StopDAGServerMaintenance.ps1

After the maintenance process is done, you can execute stop script.This script resumes mailbox database replication and remove DAG node from being blocked.

CheckDatabaseRedundancy.ps1

This script includes metrics for continuous replication , block mode, replay pipeline.

RedistributeActiveDatabases.ps1

With using this script, you can balance your database copies across a DAG.Each server in DAG will have an equal number of mounted databases.

The Certificate Status could not be determined because the revocation check failed

In one of my customer, Exchange Server 2010 could not be determined for certificate status because the revocation check failed.After some research I discover that Exchange was not configured to use right proxy server and exceptions.

By default Exchange Server 2010 uses WinHTTP to check the validity of certificate.If you have not a Proxy Address Control (PAC) file which configured on IE, it is possible that WinHTTP is not configured with necessary proxy settings.

To determine settings for WinHTTP :

netsh WinHTTP show proxy

If it is not showing the right proxy server, then you should run the following command and set the right proxy server with exceptions.

netsh winhttp set proxy proxy-server="http=myproxy:80;https=sproxy:8080" bypass-list= "*.domain.com"

While you are creating new mailboxes , in previous versions of exchange server, you must specify the mailbox database that will hold the mailboxes.

In exchange 2010, in new mailbox wizard, if you forget to specify a mailbox database, you will not get an error.But Where’d it go?

Automatic mailbox distribution is a new feature of Exchange 2010.If you don’t provide a mailbox database during creation, Exchange Server picks a random database.This is a great feature especially bulk mailbox creation processes.

But think about there is a one special mailbox database that has a high profile quota configurations.And so you will want to exclude this database from automatic picking feature

There are two commands to exclude such a database;

isExcludedFromProvisioning

isSuspendedFromProvisioning

As you see above,it is enough to be excluded  if one of this properties is set to True.

To set a database as permanently excluded from automatic mailbox distribution;

Set-MailboxDatabase “databasename” –IsExcludedFromProvisioning $True

To set a database as temporarily excluded from automatic mailbox distribution;

Set-MailboxDatabase “databasename” –IsSuspendedFromProvisioning $True

If you are planning to deploy your Exchange Server 2010 Database Availability Group on VMware environment, there is a certain misunderstanding about the configuration.

From VMware side ;

While the use of database availability groups on top of hypervisor based clustering is not a formerly (sic) supported configuration, internal VMware tests have shown that the two technologies can co-exist and can be a viable solution to ensure maximum recoverability in the case of a host failure

From Microsoft side;

Microsoft doesn’t support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between clustered root servers. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn’t employ clustered root servers, or the clustered root servers have been configured to never failover or automatically move mailbox servers that are members of a DAG to another root server.

That means, VMware says that it isn’t supported but we think you are ok.

But Microsoft says, this type of configuration is not supported by us.

So be careful about planning Exchange if your environment contains clustered virtualization root servers.

Organizations who use Exchange server typically develop checklists or procedures for day-to-day maintenance operations. This includes updates, backups, security, disaster recovery planning, etc. Sometimes, new Exchange orgs cobble together these checklists based on other server platforms already in place, or from colleagues at other organizations, online materials, etc. Microsoft has made available several checklists for each version that will allow an organization to provide comprehensive checklists for maintaining Exchange. These can be used as-is, or customized for each environment.

Daily Operations Checklist

Weekly Operations Checklist

Monthly Operations Checklist

Summary Checklist

I have just read that, with a cumulative update, Outlook 2007 is now supporting Exchange 2010 archive mailboxes.

Following Office editions are supported for archival support:

Office Ultimate, ProPlus, Office Enterprise, Outlook Standalone

Microsoft has released the following update rollup for Exchange Server 2010:

• Update Rollup 2 for Exchange Server 2010 SP1 (2425179)

If you’re running Exchange Server 2010 SP1, you need to apply Update Rollup 2 for Exchange 2010 to address the issues listed below.
Remember, you only need to download the latest update for the version of Exchange that you’re running.

Here is a list of the fixes included in update rollup 2:

2322161 Passive DAG Copy Doesn’t Replay Logs if "Don’t mount this database at startup" is Checked

2431500 Cannot connect using Outlook Anywhere as the same user from multiple XP Clients

2409597 Implement OpenFlags.AlternateServer for PublicLogon

Download the rollup here.

If you want to upgrade your legacy Exchange organization to Exchange 2010, first part of this process is to prepare existing forest and domain structure. To achieve this goal, adprep command line tool which is located in Exchange 2010 DVD, will be helping u.

For a single forest and multiple domain environment,

You must run the following commands on a computer in the same domain and in the same Active Directory site as the schema master

setup.exe /preparead (or /ad)in root, then – Enterprise admin and schema admin
setup.exe /preparealldomains (/pad) – enterprise rights

Then, in each child domain that is hosting:
-Exchange 2000, Exchange 2003, Exchange 2007 or 2010 servers
-Mail-enabled objects
-Global catalog servers that Exchange directory access components might use

Run the following:

-Setup /pl:domain.fqdn
-setup /preparedomain (/pd):domain.fqdn

Note: You must run this in the same AD site as the domain controller you are running this against, which should be in the domain you are running against.

In Exchange Server 2010, to determine which throttling policy was associated with a specific user, you would use;

Get-mailbox anilErduran | dl ThrottlingPolicy

And to assign a policy to a user;

Set-Mailbox anilerduran – ThrottlingPolicy POLICY1

As you see above, in exchange 2010 you can only assign a Throttling Policy to a specific mailbox account.

But Exchange 2010 SP1 introduces two new cmdlets:  get-ThrottlingPolicy and Set-ThrottlingPolicy

Now you can assign these kind of policies for machine accounts and a cross forest contact object.

Let’s look at the example scenarios;

Machine account:

Assume that you design a web site that uses Exchange Web Services and to run as a Network Service.Then EWS call will come from the machine account.On exchange 2010 you can not assign a policy to the machine account and set-mailbox cmdlet is not applicable for such a object.Now you can use new cmdlets.

Cross forest Contact:

In cross forest migration scenarios, you can create linked mailbox for cross forest mailbox accesses.When a cross forest account calls into exchange via web services, the user is authenticated via the userforest, but active directoryobject is contained in the exchange forest.

Now you can assign Throttling Policies for machine accounts and specific cross forest contact objects.

Following script will look for disabled users with mailboxes and will remove mailbox attributes on these objects.

Get-Mailbox | where { $_.ExchangeUserAccountControl -eq "Accountdisabled" -and $_.recipienttypedetails -eq "usermailbox"  } | select name | Export-Csv c:\disableduserswithmailboxes.csv
Import-CSV C:\disableduserswithmailboxes.csv | ForEach-Object { remove-mailbox -identity $_."Name" -Confirm:$false }

If you have migrated to Exchange 2007 or Exchange 2010 from legacy versions, and changed shared smtp namespaces, then unused mail address attributes will remain on migrated user objects.

Following script will read users.txt and look for specific text in mail addresses , and then will remove finally.

Get-Content C:\users.txt |Get-Mailbox | foreach{   

    for ($i=0;$i -lt $_.EmailAddresses.Count; $i++)
    {
        $address = $_.EmailAddresses[$i]

        if ($address.IsPrimaryAddress -eq $false -and $address.SmtpAddress -like "*YOURTEXT*" )
        {
            Write-host("Remove smtp adress: " + $address.AddressString.ToString() )           

            $_.EmailAddresses.RemoveAt($i)
        }
    }   

        Set-Mailbox -Instance $_
}

One of my customer ask me that is there any way to obtain sent and received message counts on Exchange 2010 for specific timelines.With following script, you can get all transport servers on your organization, read sent and received message counts for last 24 hour period , save this to the local disk, and email to the specific user with this attachment. Nice right? : )

Now I’m building a windows form that you will be able to choose specific hub transport servers and timelines.

$Hubs = @(Get-TransportServer)

$date = ( get-date ).ToString(‘MMddyyyy’)

$Out = c:\temp\Gunluk_Mesaj_Adet_Raporu.txt

$Sent = 0
$Sent1 = 0
$Rcvd = 0
$Rcvd1 = 0

$EDate = get-date -uFormat ‘%D %r’

$SDate = (get-date (get-date).AddDays(-1) -uformat ‘%D %r’)

foreach ($Hub in $Hubs)
{
      #count Sent messages
      $msg = @(get-messagetrackinglog -Server $Hub -EventID Send -Start $SDate -End $EDate -ResultSize Unlimited)
      $Sent1 = $msg.Count
      #add to total for all Hub servers
      $Sent = $Sent + $Sent1
     
      #Count received messages
      $msg2 = @(get-messagetrackinglog -Server $Hub -EventID Receive -Start $SDate -End $EDate -ResultSize Unlimited)
      $Rcvd1 = $msg2.Count
      #add to total for all hub servers
      $Rcvd = $Rcvd + $Rcvd1
}     

out-File $Out -InputObject $date
$inp = Son 24 Saat Icerisinde Tum Hub Sunucular Tarafindan Gonderilen Mailler  + $Sent + adet
out-File $Out -InputObject $inp -Append
$inp2 = Son 24 Saat Icerisinde Tum Hub Sunucular Tarafindan Alinan Mailler  + $Rcvd + adet
out-File $Out -InputObject $inp2 -Append

Function Send-Mail
{
$mail = New-Object Net.Mail.MailMessage
#Specify what email address to send the report from
$mail.From  = exchange2010@anilerduran.com
#Specify the recipient’s email address
$mail.To.Add(admin@anilerduran.com)
$mail.Subject = Gunluk Mail Analiz Scripti Sonuclari
$mail.Body = Gunluk Mail Analiz Scripti Sonuclariniz Ektedir.
$Attachment = New-Object Net.Mail.Attachment($Out)
$mail.Attachments.Add($Attachment)
$smtp = New-Object Net.Mail.SmtpClient
#Specify you SMTP Server
$smtp.Host = smtpservername
$smtp.Port = 25
$smtp.Send($mail)
}
Send-Mail

Exchange 2010 yapısına geçirdiğimiz bir müşterimizden şöyle bir talep geldi.

Yapıda varolan tüm Mailbox veritabanlarındaki varolan mailboxların totalitemsize,kota,varolan sizeları gibi bilgileri belirli periyodlarla edinebilirmiyim?

Burada tabiki powershell komutlarını kullanarak bazı taklalar atmamız mümkün.Hatta artık Exchange 2010 ile ilgili gelen taleplerin neredeyse tamamına aklımda powershell komutları olduğu müddetçe “œmümkündür” cevabını veriyorum.

Burada yapmamız gereken Get-MailboxStatistics cmdlet ini kullanmak.Bu komut ile belirli mailboxlar için belirli değerleri çekebiliyoruz.

Burada gördüğünüz gibi bizden hangi mailbox için bu istatistikleri çekmemiz gerektiğini soruyor.Benim amacım varolan tüm veritabanları yada belirli veritabanları içerisindeki tüm mailboxlar.Bu sebeple aşağıdaki gibi komutu genişletebilirim.

Aynı zamanda burada get-mailboxdatabase ““identity “œMailboxdb” | get-mailboxstatistics komutu ile spesifik bir veritabanı üzerinden de bilgi çekebilirsiniz.

Ardından bu çıktıları itemsize’ına göre sıralamak için komutu aşağıdaki haline getirelim.

Get-MailboxDatabase "MailboxDB1" | Get-MailboxStatistics | Sort totalitemsize ““desc

Bizden istenen bu verilerin bir excel tablosu halinde çıktısı.Bunun için hemen çok güzel çalışan Export-CSV parametremi kullanıyorum.

Get-MailboxDatabase "MailboxDB1" | Get-MailboxStatistics | Sort totalitemsize ““desc | Export-CSV c:\MailboxDB1Sizes.csv

Yukarıdaki komut tüm çıktıları csv dosyasına yazacaktır.

Ve powershell’in son güzelliğinden faydalanarak varolan bu çıktıyı attachment olarak mail ile istediğim kullanıcılara göndermek.Buda oldukça basit.

Get-MailboxDatabase "MailboxDB1" | Get-MailboxStatistics | Sort totalitemsize -desc | Export-CSV c:\MailboxDB1Sizes.csv | Send-MailMessage ““To musteri@domain.com ““From powershell@domain.com -Subject "MailboxDB1 icin aylik size degerleri" -SmtpServer exchserver -Attachments c:\MailboxDB1Sizes.csv

Oldukça kullanışlı bir komut değilmi?

Bu işlemden sonra yukarıdaki komutu ps1 uzantısı ile kaydedip schedule tasktan aylık çalıştırılacak şekilde ayarladığınız takdirde kullanıcıya bu mailbox server içerisindeki tüm mailboxlar ile ilgili aylık csv dosyası mail ile otomatik gönderilecektir.