Exchange 2010 SP1 Information for Hosted Service Providers

http://social.technet.microsoft.com/wiki/contents/articles/exchange-2010-sp1-information-for-hosted-service-providers.aspx

Several features and functionality that aren't available or supported in the hosting version:

• Exchange Management Console
• Public Folders
• Unified Messaging Server role
• Federation
• Global Address List Synchronization (GalSync)
• Business-to-Business features such as cross-premises message tracking and calendar sharing
• Information Rights Management (IRM)
• Managed folders
• Outlook 2003 support (EnableLegacyOutlook)
• Edge Transport Server role (more specifically EdgeSync support)
• In-place Upgrades (upgrading current Exchange 2003/2007 org to Exchange 2010)
• Resource forest topologies (separate Exchange forest and account forests)
• Parent-child domains
• Multiple AD sites (where there's a mix of hosted and non-hosted)
• SSO AD Trusts
• Dis-contiguous namespace
• Disjoint namespace

Exchange 2010 - Messaging Policy and Compliance

Configuring retetion tag and policy.

There are three steps involved in configuring Exchange retention tag and policy.

First we need to create retention tag using the cmdlet new-retentionpolicytag. Secondly, it has to be associated with a retention policy (new-retentionpolicy). This policy can be assigned to users using the parameter -retentionpolicy of Set-Mailbox cmdlet.

To see the results immediately you can run the cmdlet Start-ManagedFolderAssistant

Example:

[PS] C:\Windows\system32>New-RetentionPolicyTag -Name "One day retention"`
-AddressForJournaling u5@contoso.com -AgeLimitForRetention 1 -Comment`
"Retention Test" -JournalingEnabled $true -RetentionEnabled $true -RetentionAction`
movetoarchive -Type all

[PS] C:\Windows\system32>New-RetentionPolicy "Move in 1 day policy"`
-RetentionPolicyTagLinks "One day retention"

[PS] C:\Windows\system32>Set-Mailbox tariq.admin -RetentionPolicy `
"Move in 1 day policy" -Force

[PS] C:\Windows\system32>Start-ManagedFolderAssistant

More reading:
http://technet.microsoft.com/en-us/library/dd351165.aspx
http://technet.microsoft.com/en-us/library/dd335226.aspx
http://technet.microsoft.com/en-us/library/dd297970.aspx

Managing Exchange Server 2010 - Powershell Remote Session

First time you may have to set execution policy, enable remote session and allow unencrypted traffic.

Set the Execution Policy:
Set-ExecutionPolicy RemoteSigned

Enable Remote Session:
Enable-PSRemoting

Allow Unencrypted traffic:
set-item -force WSMan:\localhost\Client\AllowUnencrypted $true

To connect to a remote Exchange Server 2010 using different credentials, you need to create credential variable in order to pass it to Exchange Server.

$credetials = get-credential

Create a session:
(Example)

[PS] WSMan:\localhost\Client>$session = New-PSSession -ConfigurationName` microsoft.exchange -ConnectionUri https://mail.contoso.com/powershell`
-Authentication basic -Credential $credetials

Importing the session:

Import-PSSession $SessionFigure

Exchange 2010 Update Rollups

Read more information about fixes and improvements included at the below URL

Rollup 1
http://msexchangeteam.com/archive/2009/12/09/453485.aspx

Rollup 2
http://msexchangeteam.com/archive/2010/03/05/454155.aspx

Rollup 2
http://msexchangeteam.com/archive/2010/03/19/454335.aspx

Installing Exchange 2010 rollups on DAG servers

Great post on installing rollups on DAG

http://www.ucblogs.net/blogs/exchange/archive/2009/12/15/Installing-Exchange-2010-rollups-on-DAG-servers.aspx

Exchange Server 2010 - Database Portability

Mounting Mailbox Database on Alternate Servers - Database Portability
Database portability is a feature that enables Exchange Server 2010 mailbox database to be moved to or mounted on any other mailbox server in the same organization.
Steps:
Source database name: movedatabase
Target database name: movedatabase1

1. Make sure to commit any uncommitted transaction log files to the source database.
Dismount the source database (in our case it is movedatabase)
Command: dismount-database "movedatabase"
Command to commit transaction logs: eseutil /r Enn
Note: To determine the logfile prefix (Enn): get-mailboxdatabase "movedatabase" fl logfileprefix

2. Create a new mailbox database on the target server
Command: New-MailboxDatabase -Name "movedatabase1" -Server Exch2010 -Edbfilepath c:\mdbdata\movedatabase\movedatabase.edb -Logfilepath c:\mdbdata\movedatabase

3. Do not mount the database, just enable the database to be overwritten
Command: Set-MailboxDatabase -identity "movedatabase1" -AllowFileRestore $true

4. Move the database files manually from source server to target (.edb file, log files and Exchange Search Catalog)

5. Mount the target database (movedatabase1)
Command: Mount-Database "movedatabase1"

6. Now you must modify the user account settings point to the mailbox on the new mailbox server. Command: Get-Mailbox -database "movedatabase" where-object {$_.objectclass -NotMatch '(SystemAttendantMailbox ExOleDbSystemMailbox)'} Set-Mailbox -database "movedatabase1"

Reference: http://technet.microsoft.com/en-us/library/dd876926.aspx

Exchange VSS Writer Error

The consistency check for the component '27303ddc-08f7-4007-ac1f-13a07ed65d30'\'Microsoft Exchange Server\Microsoft Information Store\EXCH2010' has failed. The application 'Exchange' will not be available in the backup created at '‎2010‎-‎05‎-‎09T17:17:20.601180800Z'. Review the event details for information about consistency check issues.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Replay\Parameters
Create a DWORD "EnableVSSWriter" with a value 0

Sending mail from Exchange Management Shell in Exchange Server 2010.

Syntax for Send-MailMessage:






Administrator are not allowed to send mail by default for security reasons.

























Ref:
http://technet.microsoft.com/en-us/library/dd347693.aspx
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/using-send-mail-feature-exchange-server-2010.html

Common Client Access Considerations for Outlook 2003 and Exchange 2010

http://msexchangeteam.com/archive/2010/04/23/454711.aspx

Exchange 2007 / 2010: Upgrading your default Email Address Policy and Address List

Error:"Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the 'Set-EmailAddressPolicy' task, with the Exchange 2007 Recipient Filter specified."

Check for legacy filter "RecipientFilterType is "Legacy" " using the commandlet below

Get-EmailAddressPolicy | Format-List Name,*RecipientFilter*,ExchangeVersion

or

Get-EmailAddressPolicy | where { $_.RecipientFilterType -eq "Legacy" }

Upgrading the legacy EAP

Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients

Upgrading your Default Address Lists

Check for legacy filter "RecipientFilterType is "Legacy" " using the commandlet below

Get-AddressList | Format-List Name,*RecipientFilter*,ExchangeVersion

Get-GlobalAddressList | Format-List Name,*RecipientFilter*,ExchangeVersion

Upgrading the legacy AL

Set-AddressList "All Users" -IncludedRecipients MailboxUsers

Set-AddressList "All Groups" -IncludedRecipients MailGroups

Set-AddressList "All Contacts" -IncludedRecipients MailContacts

Set-AddressList "Public Folders" -RecipientFilter { RecipientType -eq 'PublicFolder' }

Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}


Reference: http://msexchangeteam.com/archive/2007/01/11/432158.aspx

OWA Password Reset Error

When you try to change the user password via Outlook Web Access (OWA), you get the following error

Exchange 2003 OWA Password Change – “Object Required” error

Registering the following iispwchg.dll resolve the issue.

regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll

Ref: http://telnetport25.wordpress.com/2007/07/25/exchange-2003-owa-password-change-object-required-error/

Spam Issues

I was recently having a chat with our mail hosting company as some of our outgoing mails are rejected because of unacceptable content.
The support personal gave me a listed of words that we need to avoid in mails and the list made me wonder whether I would be able to safely send emails to Inbox anymore.

Few words are not to be used:
Word: Group+wins (0.990)
Word: GCC+states (0.990)
Word: properties+city (0.990)
Word: unit+bank (0.990)
Word: Foreign+banks (0.990)
Word: gas+ovens (0.990)
Word: composite+href (0.990)
Word: slump+new (0.990)
Word: moves+set (0.990)
Word: package+government (0.990)
Word: General+Mohammed (0.990)
Word: points+Nasdaq (0.990)
Word: F2F2F2+EN-US (0.990)
Word: Bin+Zayed (0.990)

Exchange Tool – SMTPDIAG.EXE

SMTPDIAG is a tool supplied by Microsoft to test SMTP and DNS related issues in Exchange server.
Download SMTPDIAG

Syntax:

Usage:
C:\SmtpDiag>SmtpDiag.exe tariq@microsoft.com tariq@cisco.com /v
You can also specify an external DNS with –d switch

Report:

What to look:
White text indicates action being taken.
Gray indicates informational results.
Green indicates a successful test result.
Red indicates a failed test result.

Successful mail flow:

Complete Output SMTPDIAG:
Searching for Exchange external DNS settings.
Computer name is FPDMBX01.
VSI 1 has the following external DNS servers:
213.42.20.20,195.229.241.222
VSI 3 has the following external DNS servers:
213.42.20.20,195.229.241.222

Checking SOA for cisco.com.
Checking external DNS servers.

Checking TCP/UDP SOA serial number using DNS server [213.42.20.20].
TCP test succeeded.
UDP test succeeded.
Serial number: 9154727

Checking TCP/UDP SOA serial number using DNS server [195.229.241.222].
TCP test succeeded.
UDP test succeeded.
Serial number: 9154727

Checking TCP/UDP SOA serial number using DNS server [213.42.20.20].
TCP test succeeded.
UDP test succeeded.
Serial number: 9154727

Checking TCP/UDP SOA serial number using DNS server [195.229.241.222].
TCP test succeeded.
UDP test succeeded.
Serial number: 9154727
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [192.168.100.150].
TCP test succeeded.
UDP test failed.
Serial number: 9154727

Checking TCP/UDP SOA serial number using DNS server [192.168.100.110].
TCP test succeeded.
UDP test succeeded.
Serial number: 9154727
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: microsoft.com.
MX: mail.global.frontbridge.com (10)
Checking MX records using UDP: microsoft.com.
MX: mail.global.frontbridge.com (10)
A: mail.global.frontbridge.com [216.32.181.22]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: cisco.com.
MX: rtp-mx-01.cisco.com (15)
MX: ams-inbound-a.cisco.com (20)
MX: syd-inbound-a.cisco.com (25)
MX: sj-inbound-a.cisco.com (10)
MX: sj-inbound-b.cisco.com (10)
MX: sj-inbound-c.cisco.com (10)
MX: sj-inbound-d.cisco.com (10)
MX: sj-inbound-e.cisco.com (10)
MX: sj-inbound-f.cisco.com (10)
A: sj-inbound-a.cisco.com [128.107.234.204]
A: sj-inbound-b.cisco.com [128.107.234.205]
A: sj-inbound-c.cisco.com [128.107.234.206]
A: sj-inbound-d.cisco.com [128.107.243.13]
A: sj-inbound-e.cisco.com [128.107.243.14]
A: sj-inbound-f.cisco.com [128.107.234.207]
A: rtp-mx-01.cisco.com [64.102.255.47]
A: ams-inbound-a.cisco.com [64.103.36.153]
A: syd-inbound-a.cisco.com [64.104.252.248]
Checking MX records using UDP: cisco.com.
MX: rtp-mx-01.cisco.com (15)
MX: ams-inbound-a.cisco.com (20)
MX: syd-inbound-a.cisco.com (25)
MX: sj-inbound-a.cisco.com (10)
MX: sj-inbound-b.cisco.com (10)
MX: sj-inbound-c.cisco.com (10)
MX: sj-inbound-d.cisco.com (10)
MX: sj-inbound-e.cisco.com (10)
MX: sj-inbound-f.cisco.com (10)
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for tariq@cisco.com.
Connecting to sj-inbound-f.cisco.com [128.107.234.207] on port 25.
Received:
220 sj-inbound-f.cisco.com ESMTP

Sent:
ehlo microsoft.com

Received:
250-sj-inbound-f.cisco.com
250-8BITMIME
250-SIZE 33554432
250 STARTTLS

Sent:
mail from:

Received:
250 sender ok

Sent:
rcpt to:

Received:
250 recipient ok

Sent:
quit

Received:
221 sj-inbound-f.cisco.com

Successfully connected to sj-inbound-f.cisco.com.
Connecting to sj-inbound-e.cisco.com [128.107.243.14] on port 25.
Received:
220 sj-inbound-e.cisco.com ESMTP

Sent:
ehlo microsoft.com

Received:
250-sj-inbound-e.cisco.com
250-8BITMIME
250-SIZE 33554432
250 STARTTLS

Sent:
mail from:

Received:
250 sender ok

Reading Message / Email Header

Overview:
Message header is a set of information attached to every email. It contains the sender, recipient and the hop details. Message Header can be used to check the original sender, time is takes to arrive to the recipient, the route it takes to travel before reaching the final destination etc.

Viewing Message Header:
Viewing Header information depends on the application used for email. A comprehensive list is available at the below link.
http://www.spamcop.net/fom-serve/cache/19.html

Parsing Messaging Header:
------------------------------------------------------------------------------------------------
Microsoft Mail Internet Headers Version 2.0
Received: from FPDMCR01 ([192.168.100.201]) by fpdmbx01.MCNMENA.LOCAL with Microsoft SMTPSVC(6.0.3790.3959);
Mon, 19 Jan 2009 19:36:15 +0400
Received: from mail68.messagelabs.com [193.109.255.67] by xxxx.com
(SMTPD-9.23) id ADD704C8; Mon, 19 Jan 2009 19:35:51 +0400
X-VirusChecked: Checked
X-Env-Sender: network@etp2101.etp.eu.blackberry.net
X-Msg-Ref: server-6.tower-68.messagelabs.com!1232379332!111038693!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [93.186.17.11]
X-SpamReason: No, hits=0.0 required=7.0 tests=UPPERCASE_25_50
Received: (qmail 16168 invoked from network); 19 Jan 2009 15:35:32 -0000
Received: from c17-011.eu.blackberry.net (HELO smtp.eu.blackberry.net) (93.186.17.11)
by server-6.tower-68.messagelabs.com with SMTP; 19 Jan 2009 15:35:32 -0000
Received: from etp2101.rly2.ad0.blackberry (etp2101.etp2.blackberry [172.25.129.17])
by mailrouter2108.mail2.blackberry (Postfix) with ESMTP id 0FA342A2A32
for ; Mon, 19 Jan 2009 15:35:32 +0000 (UTC)
From: network@etp2101.etp.eu.blackberry.net
Subject: RIM_bca28a80-e9c0-11d1-87fe-00600811c6a2
To: xxxxx@xxxx.com
MIME-Version: 1.0
Content-Type: MULTIPART/mixed; BOUNDARY="826332926-30626-1232379331=:4032"
Message-Id: <20090119153532.0fa342a2a32@mailrouter2108.mail2.blackberry>
Date: Mon, 19 Jan 2009 15:35:32 +0000 (UTC)
X-RCPT-TO:
Status:
X-UIDL: 524799496
X-IMail-ThreadID: 9dd701560000a7aa
Return-Path: network@etp2101.etp.eu.blackberry.net
X-OriginalArrivalTime: 19 Jan 2009 15:36:15.0274 (UTC) FILETIME=[AA2950A0:01C97A4B]

--826332926-30626-1232379331=:4032
Content-Type: TEXT/plain; CHARSET=US-ASCII

--826332926-30626-1232379331=:4032
Content-Type: APPLICATION/octet-stream; name=ETP.DAT
Content-Transfer-Encoding: BASE64
Content-Description: ETP.DAT
Content-Disposition: attachment; filename=ETP.DAT


--826332926-30626-1232379331=:4032--
------------------------------------------------------------------------------------------------

Received Tags (Bold and Italicized) in the above message header was added by the mail servers as the email travels from the sender to recipient.
Origin Details:
· The original sender of this mail (highlighted) was xxxxx@xxxx.com
· The message was sent via etp2101.etp2.blackberry
· From the IP address [172.25.129.17]
· The email was sent using SMTP from the mail server mailrouter2108.mail2.blackberry (Postfix)

Originating IP address:
X-Originating-IP: [93.186.17.11]

Ofcourse there are other information like whether the message is scanned for virus / spam, the mailer information etc.

Unable to bind to the destination server in DNS - Exchange 2003 Server Routing Group

I had a problem with my Exchange Routing Group Connector. We have 12 Routing Groups. Our setup is hub and spoke model.

For some reason mails between three of the spoke and hub stopped flowing. To pin point the issue mail flow from hub is fine, only the mail flow from three of the remote office via their respective Routing Group was having the problem.

Routing Group Connector status was always in “Retry” state. When I force the connection, few mails are flushed. The error message is “unable to bind to the destination server in DNS”.

The following Microsoft KB article didn’t fix the issue.
http://support.microsoft.com/default.aspx/kb/822939

So I have to log a case with Microsoft.

The resolution gave by them is to run a tool called remonitor.exe which fixes and routing table issue. I believe that it recreates the routing table.

This tool was run from command prompt under system privilege. To do so we started the command prompt by running a job.

C:\Program Files\Exchsrvr\bin>at 5:55 /interactive cmd.exe

From command prompt we run the remonitor to repair the link state table.

C:\Program Files\Exchsrvr\bin>remonitor.exe -i servername
Note: This tool is extracted to bin folder.

After running this utility, all we did is restarted SMTP and Routing Engine.

Publishing OWA 2003 with ISA 2006

Recently I have published OWA 2003 with ISA 2006 as part of my work. I have followed the articles by Shijaz and Dr. Thomas W Shinder M.D.
http://www.shijaz.com/isaserver/isa2006_publish_owa.htm

I would like to share couple of issues that I have faced during OWA ISA configuration.

1. My ISA 2006 is not in domain
Export Root Certificate along with web certificate

2. Entering incorrect URL
http://blogs.isaserver.org/pouseele/2006/11/01/redirecting-owa-users-to-the-correct-directories-and-protocols-with-isa-server-2006/

3. Should I have to enabled form based authentication is System Manager?
No

4. To configure SSL OWA in defferent port
http://4itpeople.blogspot.com/2008/12/changing-ssl-port-number-used-by-owa.html

Changing the SSL port number used by OWA

(Assuming we want to change the port# from 443 to 10001:)

1. Go to Exchange System Manager, Protocols -> HTTP. Right-click New HTTP Virtual Server.
2. Specify "Exchange OWA 10001" for the name.
3. Click Advanced, modify, change the port from 80 to 81. SSL port is not available, that's OK.
4. After you click OK and Applied, go back to the same screen. Now remove port 81 and specify 10001 as the SSL port. Click OK all the way.
5. Follow the steps below to force the DS2MB replication.
a. Go to IIS, right-click servername (local computer), Properties. Backup/Restore configuration to save a copy of IIS settings
b. Right-click servername (local computer), Properties. Check Enable Direct Metabase Edit.
c. Open MetaBase.xml with Notepad.
d. Locate the following object where ID = 61472
ID="61472" (<---- This one)
Value="53322"
e. Change the Value to "0". Your original number will not be "53322".
f. Save the file.
g. From a command prompt, type "iisreset"
h. Restart Exchange System Attendant
6. Now, OWA is available via https://FQDN:10001

Exchange Server 2003 Interview Questions

1. What are the key features of Exchange Server 2003?
2. What are the Exchange Server 2003 Versions?
3. What is DSAccess?
4. What is DSProxy?
5. Exchange Server 2003 Organizing Components?
6. Exchange Server 2003 Core Components?
7. What is a Routing Engine
8. What are Connectors?
9. Name few Clients for Exchange?
10. What is the Day−to−Day Management you perform on the Exchange Organization?
11. What is a routing Group?
12. What is an Administrative Group?
13. Difference between Routing Group and Administrative Group?
14. What is System Policy?
15. What is RUS?
16. What is Recipient Policy?
17. What is ELHO command?
18. How do you test SMTP connectivity?
19. What are different log files in Exchange Server 2003?
20. What is a Transaction Log?
21. What is Reserve Log?
22. When do you use ESEUTIL and ISINTEG commands?
23. What is soft recovery and hard recovery?
24. What is backend server and front end server?
25. How do you configure HTTP Proxy?
26. How do you configure Front End Server?
27. Where do you place your Front End Server in you IT Infrastructure?
28. What are the command line utilities you have used to manage your Exchange Organisation?
29. What is OWA?
30. What is RPC over HTTP?
31. How do you configure SSL for OWA?
32. Exchange Administrative Delegation
33. Advantages of moving to native mode?
34. Difference between mailbox and mail enabled user?
35. Describe query based distribution group?
36. When and why we need WINS in Exchange 2003 Server environment?
37. What is the benefit of Cached Exchange Mode?
38. Can you block Outlook client access?
39. Where does OAB is stored on a server?
40. How do you repair a corrupted PST?
41. Have you worked with outlook command line switches?
42. Describe OWA Architecture?
43. How do you administer OWA features?
44. How do you enable form based authentication for OWA?
45. How do you prepare active directory for Exchange?
46. What is GC’s role with MAPI client?
47. How do you check that you have performed a successful full backup?
48. What is are WebBeacons, why it is used in OWA?
49. What is the use of DS2MB process?
50. Have you configured Password Change Option to work in OWA?
51. How do you recover a hard deleted item from a folder say for example “test folder” using OWA?
52. Can you say few URL suffixes for OWA?
53. How do you secure front end and back end server communication?
54. How do you connect a Mac system to an Exchange Server?
55. What is the difference between EDB and STM file?
56. What is a check point file?
57. Have you used PFDAV utility?
58. Do you have any experience on Exchange Clusters?
59. How do you implement five nodes Exchange Cluster?
60. Briefly explain Link State Routing?
61. How do you enable SMTP logging?
62. Have you used any archiving solutions?
63. Have you used EXCHDUMP?