itech

Script Supports - Exchange 2007,2010,2013 In some situations we had to Export all the Distribution group and all the members of it to a CSV file I have wrote a script which will make Exchange Administrators life Easy Change LogV1.1, 02/07/2014 - Added "Enter the Distribution Group name with Wild Card" .Requires -version 2 – Runs in Exchange Management Shell .\DistributionGroupMemberReport.ps1 – It Can Display all the Distribution Group and its members on a List Or It can Export to a CSV file Download the Script Browse the Shell to the Appropriate Location Run it as above Output of CSV file look like Below You can add some more entries if required PowerShell <#    .Requires -version 2 - Runs in Exchange Management Shell    .SYNOPSIS  .\DistributionGroupMemberReport.ps1 - It Can Display all the Distribution Group and its members on a List    Or It can Export to a CSV file      Example 1    [PS] C:\DG>.\DistributionGroupMemberReport.ps1      D

This procedure describes how to export all mailboxes from one Exchange Server to a PST files and how to import the PST files to another Exchange Server in a different domain. Before you begin make sure that: You have a computer that has Outlook 2003 (SP2) or 2007, Exchange 2007 Management Tools (32-bit version), PowerShell and .NET Framework installed Logon with an account that has Exchange Server Administrator and Local Administrator rights You have full access to the users’ mailbox on both servers. See the note below on how to do it. Start the Exchange Management Shell and type the following: [PS] C:\>Get-Mailbox –Database “ \ ” | Export-Mailbox –PSTFolderPath C:\PSTFiles  to export all users mailbox to a PST file. Press A for Yes to All. Depending on the size of your database, the export procedure could take a long time to complete. Now the mailboxes are exported to the PST files, make sure that the PST file name matches the alias of the users’ account in the other d

The 500 – Internal Server Error is displayed when you access Outlook Web Access from https://CASServer/exchange  while  https://CASServer/owa  works fine. This happens when you have separate Exchange 2007 Mailbox and CAS servers. Ideally the request should be redirected to /owa but you get the 500 – Internal Server Error right after typing in your credentials in the forms login page. The redirection is not working because  ISAPI Extensions are not installed on the Mailbox Server . ISAPI extensions handle specific incoming requests to the IIS server. The extensions are loaded when they are first needed and kept in memory until the host process shuts down. To fix this issue, install the ISAPI Extensions on the mailbox server. This can be done by using the following command: ServerManagerCmd -i Web-ISAPI-Ext When the install is complete, restart IIS.

Here’s an Exchange Management Shell command that generates a report with mailbox sizes and item counts of all mailboxes within the Exchange Organization, sorted by mailbox size: Get-MailboxStatistics | Sort -Property TotalItemSize | ft DisplayName, @{expression={$_.totalitemsize.value.ToMB()};label=”Mailbox Size (MB)”}, itemcount If you require to have this report exported to a text file, the command below will do the trick. Get-MailboxStatistics | Sort -Property TotalItemSize | ft DisplayName, @{expression={$_.totalitemsize.value.ToMB()};label=”Mailbox Size (MB)”}, itemcount > C:MailboxSizeReport.txt

If you’re in need to recreate the IIS virtual directories of Exchange Server, below commands will do exactly that. Launch the Exchange Management Shell on the CAS server and enter below commands as needed. “Exchange (Default Web Site)” Remove-OwaVirtualDirectory “exchange (Default Web Site)” New-OwaVirtualDirectory “exchange” -OwaVersion Exchange2003or2000 -VirtualDirectoryType Mailboxes -WebSiteName “Default Web Site” “Exchweb (Default Web Site)” Remove-OwaVirtualDirectory “exchweb (default web site)” New-OwaVirtualDirectory “exchweb” -OwaVersion Exchange2003or2000 -VirtualDirectoryType Exchweb -WebSiteName “Default Web Site” “OWA (Default Web Site)” Remove-OwaVirtualDirectory “owa (default web site)” New-OwaVirtualDirectory -name “owa” -OwaVersion Exchange2007 -WebSiteName”Default Web Site” “Public (Default Web Site)” Remove-OwaVirtualDirectory “public (default web site)” New-OwaVirtualDirectory “public” -OwaVersion Exchange2003or2000 -VirtualDirectoryTy

You might have encountered the case where you (or someone else) created a regular mailbox, that should have been a shared mailbox? There is help. The type of mailbox can easily be changed by using the appropriate Exchange Management Shell command from below. Regular Mailbox Set-Mailbox -Identity {Mailbox Name} -Type Regular Room Mailbox Set-Mailbox -Identity {Mailbox Name} -Type Room Equipment Mailbox Set-Mailbox -Identity {Mailbox Name} -Type Equipment Shared Mailbox Set-Mailbox -Identity {Mailbox Name} -Type Shared Note:  There might be further setting changes required in addition to above commands, i.e. for a shared mailbox: granting people access, for room mailboxes: setup of auto-accept features etc.

By default the Display Name of Exchange Mailboxes is in the format of “Firstname Lastname”. To change this for an existing mailbox to “Lastname, Firstname”, use the Exchange Management Shell command below. Get-Mailbox “User Name” | Get-User | ?{ $_.Lastname -ne $null } | %{ $dispName=$_.LastName + “, ” + $_.FirstName ; set-mailbox $_.SamAccountName -Displayname $dispName } In case you want to revert back to the format “Firstname Lastname”, here’s the command for that. Get-Mailbox “User Name” | Get-User | ?{ $_.Lastname -ne $null } | %{ $dispName=$_.FirstName + ” ” + $_.LastName ; set-mailbox $_.SamAccountName -Displayname $dispName }

Viewing  the current time-out values can be done by running the following PowerShell commands: “This is a Public Computer” setting get-ItemProperty ‘HKLM:SYSTEMCurrentControlSetServicesMSExchange OWA’ -name PublicTimeout “This is a Private Computer” setting get-ItemProperty ‘HKLM:SYSTEMCurrentControlSetServicesMSExchange OWA’ -name PrivateTimeout Use below PowerShell commands to  set  the values: “This is a Public Computer” setting se t-ItemProperty  ‘HKLM:SYSTEMCurrentControlSetServicesMSExchange OWA’ -name PublicTimeout -value -type dword “This is a Private Computer” setting set-ItemProperty ‘HKLM:SYSTEMCurrentControlSetServicesMSExchange OWA’ -name PrivateTimeout -value -type dword Note:  You must restart Internet Information Services (IIS) by using the command  iisreset /noforce for these changes to take effect.

The members of Distribution Groups can be viewed and modified through the Outlook Address Book. However, Outlook doesn’t offer a way to export a list of all the members. Administrators can run the following Exchange Management Shell commands to display/export the memberlist, sorted by DisplayName. Single Distribution Group Display Memberlist Get-DistributionGroupMember {Name of Group} | Sort -Property DisplayName | Select DisplayName, Alias, Department Export Memberlist to TXT file Get-DistributionGroupMember {Name of Group} | Sort -Property DisplayName | Select DisplayName, Alias, Department > C:DGmemberlist.txt Export Memberlist to CSV file Get-DistributionGroupMember {Name of Group} | Sort -Property DisplayName | Select DisplayName, Alias, Department | Export-CSV C:DGmemberlist.csv All Distribution Groups in the Exchange Organization Display Memberlist (create a script file called something like C:scriptsGet-DGmembers.ps1, paste below commands into it, and run

Exchange Management Shelli açın ve aşağıdaki script kodu yapıştırın. Get-MailboxStatistics | Sort-Object TotalItemSize -Descending | ft DisplayName,@{label=”TotalItemSize(KB)”;expression={$_.TotalItemSize.Value.ToKB()}},ItemCount

Eğer bir mail server kurdunuz ancak gönderdiğiniz mailler karşı tarafa spam olarak gidiyor veya hiç ulaşmıyor ise ve yine size bu konu ile ilgili olarak dönen NDR mesajlarında 550.5.7.1 hataları alıyorsanız muhtemel RBL listelerindesinizdir. Peki bunu nasıl doğrularız. Öncelikle mail domaini için MX kaydınızın olup olmadığınız kontrol edin, bunun için aşağıdaki adresten domain isminizi yazarak karşılığında minimum 1 adet mx kaydı olması gerekmektedir. http://mxtoolbox.com/ Muhtemel bir kayıt olacaktır ve bu kayda karşılık gelen ip adresi için RBL kontrolü yapın http://www.anti-abuse.org/multi-rbl-check/ Eğer bir veya bir kaç RBL de listeleniyorsanız silin.. Peki baktınız RBL ile ilgili sorun yok bu durumda bu domain için SPF kaydını kontrol edin http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ Eğer SPF kaydınız yok ise bu durumda DNS sunucunuzun üzerinde SPF kaydı açınız Peki SPF var, RBL de değilsiniz geriye sizin ip adresinizin için yüksek mail gönderimini

Add-AdPermission "Group ismi" -user "User Name" -AccessRights extendedright -ExtendedRights "send as"