Archive for category Exchange

Find Your Exchange 2010 Version

From the Exchange Blog

 

So I just installed RU1 on my brand new Exchange 2010 server and then I issue a Get-Exchangeserver -Identity MyExchangeServer and get the following output for AdminsDisplayVersion and ExchangeVersion:

Ok that looks a little familiar for some reason. I go to my Exchange 2010 RTM server and issue the same CMDlet and get:

…The same result! But one server has RU1 installed and the other is RTM. Shouldn’t I get a different version number back?

Well… no. Exchange 2007 and forward do not reflect the version number either in the value for AdminDisplayVersion, ExchangeVersion, or at this registry key HKLM\SOFTWARE\Microsoft\v8.0\<Role>\ConfiguredVersion as influenced by roll ups. This is a common misconception.

The most conclusive way to get the version of your exchange server, rollup and all, is to check the file version of ExSetup.exe in the BIN folder.

Here is Exchange 2010 RU1 version:

And here is Exchange 2010 RTM:

Another way of getting this information is to run the following PowerShell one-liner:

GCM exsetup |%{$_.Fileversioninfo}

The below output is from an exchange 2010 server running RU1:

Here is an exchange 2010 RTM server:

You can then correlate the version number you find with those listed here, here or on the actual rollup update download pages.

No Comments

PowerShell Script to E-Mail User Mailbox Storage Limit Status

A storage status of “NoChecking” means they do not have a mailbox limit.

To schedule the script. Through Windows Scheduler “PowerShell.exe -PSConsoleFile "C:\Program Files\Microsoft\Exchange Server\Bin\ExShell.psc1" -Command “C:\Script.ps1"

Save as a .ps1 file

________________________________________________

$FromAddress=MailboxReport@domain.com

$ToAddress=ExampleUser@domain.com

$MessageSubject="Mailbox Report"

$MessageBody="User Mailbox Storage Limit Status"

$SendingServer="emailserver.domain.com"

$file="C:\Mailboxes.txt"

Get-MailboxStatistics | Sort-Object StorageLimitStatus | ft DisplayName, StorageLimitStatus, ItemCount > $file

$SMTPMessage = New-Object System.Net.Mail.MailMessage $FromAddress, $ToAddress, $MessageSubject, $MessageBody

$Attachment = new-object System.Net.Mail.Attachment $file

$SMTPMessage.Attachments.Add($Attachment)

$SMTPClient=New-Object System.Net.Mail.SMTPClient $SendingServer

$SMTPClient.Send($SMTPMessage)

,

No Comments

Exchange 2010 Requires Client Encryption – Outlook 2003 Encryption Disabled by Default

Solution:

 

1. Enable Encryption in the Outlook 2003 Profile.

image

2. Create a GPO to enable Encryption for Outlook 2003 clients.

http://support.microsoft.com/kb/2006508

 

3. Disable the Encryption requirement on the Exchange 2010 server.

From PowerShell on the Exchange server: Set-RpcClientAccess -Server:ExchangeServerName -EncryptionRequired:$False

No Comments

Outlook 2003 Responds Slowly When Using Exchange 2010

MS KB for this issue – http://support.microsoft.com/kb/2009942

No Comments

Migrate From Exchange 2007 To Exchange 2010

Migrate Mailboxes to Exchange 2010 Server.

Move SSL Certificates to Exchange 2010 Server. Process is the same as Exchange 2007.

Migrate Public Folders. Process is the same as Exchange 2007.

Configure Offline Address Book on Exchange 2010 Server:

Read the rest of this entry »

No Comments

Recreate Offline Address Book (OAB) in IIS and Active Directory

From the Exchange Shell:

get-oabvirtualdirectory | format-list > c:\oab.txt

 

Open the oab.txt file. The Name field will be used in the “Identity” command below. The Internal and External URL will be used in the “InternalURL” and “ExternalURL” below.

 

Remove-OabVirtualDirectory -Identity "OAB (Default Web Site)"

 

A Virtual Directory named “OAB” must not exist in IIS, if it does it will need to be deleted before running this command.

New-OABVirtualDirectory -ExternalUrl http://mail.domain.org/oab  -InternalUrl http://mail.domain.org/oab

No Comments

Active Sync Setup on Single Exchange 2003 Server with OWA SSL Enabled

http://support.microsoft.com/kb/817379

 

Disable the forms-based authentication for the Exchange virtual directory

To create a secondary virtual directory for Exchange that is based on steps 1 through 7 of the following procedure, make sure that forms-based authentication is disabled for the Exchange virtual directory before you make the copy. Before you follow these steps, disable forms-based authentication in Exchange System Manager. Then restart Internet Information Services (IIS). To do this, follow these steps:

  1. Open Exchange Manager.
  2. Expand Administrative Groups, expand the first administrative group, and then expand Servers.
  3. Expand the server container for the Exchange Server 2003 server that you will be configuring, expand Protocols, and then expand HTTP.
  4. Under the HTTP container, right-click the Exchange Virtual Server container, and then click Properties.
  5. Click the Settings tab, clear the Enable Forms Based Authentication check box, and then click OK.
  6. Close Exchange Manager.
  7. Click Start, click Run, type IISRESET/NOFORCE, and then press ENTER to restart Internet Information Services (IIS).

Create a secondary virtual directory for Exchange server

You must use Internet IIS Manager to create this virtual directory for Exchange ActiveSync and Outlook Mobile Access to work. If you are using Windows Server 2003, follow these steps:

  1. Start Internet Information Services (IIS) Manager.
  2. Locate the Exchange virtual directory. The default location is as follows:

    Web Sites\Default Web Site\Exchange

  3. Right-click the Exchange virtual directory, click All Tasks, and then click Save Configuration to a File.
  4. In the File name box, type a name. For example, type ExchangeVDir. Click OK.
  5. Right-click the root of this Web site. Typically, this is Default Web Site. Click New, and then click Virtual Directory (from file).
  6. In the Import Configuration dialog box, click Browse, locate the file that you created in step 4, click Open, and then click Read File.
  7. Under Select a configuration to import , click Exchange, and then click OK.
    A dialog box will appear that states that the "virtual directory already exists."
  8. Select the Create a new virtual directory option. In the Alias box, type a name for the new virtual directory that you want Exchange ActiveSync and Outlook Mobile Access to use. For example, type exchange-oma. Click OK.
  9. Right-click the new virtual directory. In this example, click exchange-oma. Click Properties.
  10. Click the Directory Security tab.
  11. Under Authentication and access control, click Edit.
  12. Make sure that only the following authentication methods are enabled, and then click OK:
    • Integrated Windows authentication
    • Basic authentication
  13. On the Directory Security tab, under IP address and domain name restrictions, click Edit.
  14. Click the option for Denied access, click Add, click Single computer and type the IP address of the server that you are configuring, and then click OK twice.
  15. Under Secure communications, click Edit. Make sure that Require secure channel (SSL) is not enabled, and then click OK.
  16. Click OK, and then close the IIS Manager.
  17. Click Start, click Run, type regedit, and then click OK.
  18. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MasSync\Parameters

  19. Right-click Parameters, click to New, and then click String Value.
  20. Type ExchangeVDir, and then press ENTER. Right-click ExchangeVDir, and then click Modify.
    NoteExchangeVDir is case-sensitive. If you do not type ExchangeVDir exactly as it appears in this article, ActiveSync does not find the key when it locates the exchange-oma folder.
  21. In the Value data box, type the name of the new virtual directory that you created in step 8. For example, type /exchange-oma. Click OK.
  22. Quit Registry Editor.
  23. Restart the IIS Admin service. To do this, follow these steps:
    1. Click Start, click Run, type services.msc, and then click OK.
    2. In the list of services, right-click IIS Admin service, and then click Restart.
  24. If you want to reuse Forms-based Authentication on the Exchange server, follow these steps to re-enable Forms-based Authentication on the /Exchange virtual directory in Exchange System Manager.
    1. Open Exchange Manager.
    2. Expand Administrative Groups, expand the first administrative group, and then expand Servers.
    3. Expand the server container for the Exchange Server 2003 server that you will be configuring, expand Protocols, and then expand HTTP.
    4. Under the HTTP container, right-click the Exchange Virtual Server container, and then click Properties.
    5. Click the Settings tab, click to select the Enable Forms Based Authentication check box, and then click OK.
    6. Close Exchange Manager.
    7. Click Start, click Run, type IISRESET/NOFORCE, and then press ENTER to restart Internet Information Services (IIS).

Note If the server is Microsoft Windows Small Business Server 2003 (SBS), the name of the Exchange OMA virtual directory must be exchange-oma.
The integrated setup of Microsoft Windows Small Business Server 2003 creates the exchange-oma virtual directory in IIS. Additionally, it points the ExchangeVDir registry key to /exchange-oma during the initial installation. Other SBS wizards, such as the Configure E-mail and Internet Connection Wizard (CEICW) also expect the virtual directory name in IIS to be exchange-oma.

No Comments

Find Email Addresses In Active Directory

Using CSVDE/LDIFDE to find an email address:

csvde -f outputfilename.csv -d "dc=domain,dc=com" -r "(&(mailnickname=*)(proxyAddresses=smtp:UserName@domain.com))" -l name

Replace "dc=domain,dc=com" with your AD domain name and suffix, and UserName@domain.com with the exact email address you’re looking for.

To find all recipients who have an email address from a particular SMTP domain, you can use a wildcard, e.g.:

csvde -f outputfilename.csv -d "dc=domain,dc=com" -r "(&(mailnickname=*)(proxyAddresses=smtp:*@domain.com))" -l name

In the above example, only the name field is exported. All CSVDE/LDIFDE queries also return the object’s distinguishedName. To add more fields to the list, insert a coma after name and type new field names separated by a coma: e.g.

name,displayName,sAMAccountName,proxyAddresses,homeMDB

 

Finding email addresses using the Exchange shell (Exchange Server 2007): The Exchange Server 2007 shell makes it easier (once you familiarize yourself with shell basics). To get a list of all recipients with email addresses from a particular domain:

get-recipient | where {$_.emailaddresses -match "domain.com"} | select name,emailaddresses

To get a list of recipients with a particular email address:

get-recipient | where {$_.emailaddresses -match "UserName@domain.com"} | select name,emailaddresses

,

No Comments

Blank OWA Page After Installing Exchange Rollup Patch

OWA Client page error will be similar to this:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.2; Tablet PC 2.0; MS-RTC LM 8 )
Timestamp: Wed, 7 Oct 2009 15:36:45 UTC

Message: Syntax error
Line: 6
Char: 1
Code: 0
URI: https://mail.domain.com/owa/8.1.393.1/scripts/premium/flogon.js

 

The C:\Program Files\Microsoft\Exchange Server\ClientAccess\OWA\8.1.393.1\scripts basic and premium folders were missing files. I copied the files from the 8.1.375.2 folder into the 8.1.393.1\ basic and premium folder, but did not overwrite any files with a newer date. Verified that subfolders in folder 8.1.393.1 were not missing additional files.

I then went into IIS – Default Web Site – OWA – 8.1.393.1 – Directory Security Tab – Authentication and enabled anonymous access for IUSR_SCO-Exchange.

No Comments

Recover Exchange 2007 Server

  1. Use ADSIEdit to find where Exchange was installed. Expand Configuration, CN=Configuration, DC=<domain>, DC=<domain_ext>, CN=Services, CN=Microsoft Exchange, CN=<company name>, CN=Administrative Groups, CN=Exchange Administrative Group (admin group id), CN-Servers, CN=<exchange server>.
    • Right-click the server name, select Properties.
    • Select “Show only attributes that have values”
    • Find the full path of the Exchange server attributes. Make note of each drive letter and path.
    • Display the path of each storage group and database on the server by expanding CN=<server name>, CN=Information Store, CN=<storage group>
    • Examine the properties of each Storage Group and Database.
  2. Configure Drives/Partitions the same as the failed Exchange server.
  3. Install the same OS as the failed server. Install service packs and security updates.
  4. Name the server the same as the failed server.
  5. Reset the old Exchange server computer account in AD by right-clicking it and select Reset.
  6. Join the Exchange server to the domain.
  7. Disable inbound E-Mail at the firewall.
  8. Install Exchange 2007 on the replacement server using Setup /m:RecoverServer
  9. For the databases that will be restored. Check “This Database can be overwritten by a restore”
  10. Reinstall any 3rd party SSL Certs.
  11. Install VSS Snapshot Patch KB940349.
  12. Restore the databases to the Exchange server. (Current databases must be dismounted)
  13. Enable inbound E-Mail at the firewall.
  14. Verify client access, OWA, data, and any other features.

No Comments