Currently I am working with Exchange 2010 in my home lab.
I have set up a Exchange 2010 organization in the following manner using VMware ESXi 5.1:
The following are some notes on some issues I ran into with working through various lab exercises.
Configuring of routing between sites:
Set a persistant route on NYDC1 and NYDC2 to 10.1.1.0/24 via Teal so traffic could get back to CHIDC1.
Set a static route on wireless router to 10.1.1.0/24 via Teal (192.168.1.106) on the LAN interface so that NAT'd traffic to the internet would know where to be sent.
After removing persistant route from NYDC1 and NYDC2, replication to CHIDC1 stopped working.
After running a packet capture on teal it was found that replication traffic was going out from CHIDC1 but not going back to it. No traffic was going back to CHIDC1 at all from NYDC1 and NYDC2. This caused issues with install Exchange 2010 SP2 on the mailbox server.
dcdiag reported replcation errors. When replicated was forced via sites and services, a schema mismatch was found. After waiting for 15 - 20 mins, the schema mismatch resolved itself and Exchange 2010 SP2 installation completed successfully.
What is strange is that there is a static route on my router that points to the network that CHIDC1 is in, so it should forward traffic to it, however it did not seem to work properly for NYDC1 and NYDC2.
Removing public folder database:
Tried the following and ran into permissions errors: http://technet.microsoft.com/en-us/library/bb201664.aspx
Ensured administrator to public folder management group and gave administrator AllExtendedRights on \non_ipm_subtree public folders. Still wasn't able to remove system public folders.
Found that all mailbox databases were using public folders (get-mailboxdatabase | ft name, publicfolderdatabase).
Used ADSIedit to remove public folder configuration from mailbox databases and to delete the public folder database. (http://exchangeserverpro.com/remove-default-public-folder-database-exchange-mailbox-database)
Troubleshooting OWA not working:
Found that OWA wasn't accessible after upgrade to Exchange 2010 SP2.
Found that all Exchange services weren't started on mailbox and client access server. Started/restarted all services. Didn't fix issue.
Checked event logs and found that there was an error in the web.config file for the OWA IIS site. Tried commenting out the line with the error and tried using the backup web.config file, neither fixed issue.
Checked in Exchange installation log and found that the Service Pack 2 installation hadn't completed successfully. Re-installed service pack 2 on the client access/hub transport server and rebooted. Fixed issue.
Later found that OWA access was timing out. Believe that I restarted Microsoft Exchange RPC Client Access service to fix the issue.
Later found out that mail wasn't being sent within the organization. Restarted Microsoft Exchange Information Store service to fix the issue.
I'm still working through the material so most likely there will be more to follow.
I have set up a Exchange 2010 organization in the following manner using VMware ESXi 5.1:
The following are some notes on some issues I ran into with working through various lab exercises.
Configuring of routing between sites:
Set a persistant route on NYDC1 and NYDC2 to 10.1.1.0/24 via Teal so traffic could get back to CHIDC1.
Set a static route on wireless router to 10.1.1.0/24 via Teal (192.168.1.106) on the LAN interface so that NAT'd traffic to the internet would know where to be sent.
After removing persistant route from NYDC1 and NYDC2, replication to CHIDC1 stopped working.
After running a packet capture on teal it was found that replication traffic was going out from CHIDC1 but not going back to it. No traffic was going back to CHIDC1 at all from NYDC1 and NYDC2. This caused issues with install Exchange 2010 SP2 on the mailbox server.
dcdiag reported replcation errors. When replicated was forced via sites and services, a schema mismatch was found. After waiting for 15 - 20 mins, the schema mismatch resolved itself and Exchange 2010 SP2 installation completed successfully.
What is strange is that there is a static route on my router that points to the network that CHIDC1 is in, so it should forward traffic to it, however it did not seem to work properly for NYDC1 and NYDC2.
Removing public folder database:
Tried the following and ran into permissions errors: http://technet.microsoft.com/en-us/library/bb201664.aspx
Ensured administrator to public folder management group and gave administrator AllExtendedRights on \non_ipm_subtree public folders. Still wasn't able to remove system public folders.
Found that all mailbox databases were using public folders (get-mailboxdatabase | ft name, publicfolderdatabase).
Used ADSIedit to remove public folder configuration from mailbox databases and to delete the public folder database. (http://exchangeserverpro.com/remove-default-public-folder-database-exchange-mailbox-database)
Troubleshooting OWA not working:
Found that OWA wasn't accessible after upgrade to Exchange 2010 SP2.
Found that all Exchange services weren't started on mailbox and client access server. Started/restarted all services. Didn't fix issue.
Checked event logs and found that there was an error in the web.config file for the OWA IIS site. Tried commenting out the line with the error and tried using the backup web.config file, neither fixed issue.
Checked in Exchange installation log and found that the Service Pack 2 installation hadn't completed successfully. Re-installed service pack 2 on the client access/hub transport server and rebooted. Fixed issue.
Later found that OWA access was timing out. Believe that I restarted Microsoft Exchange RPC Client Access service to fix the issue.
Later found out that mail wasn't being sent within the organization. Restarted Microsoft Exchange Information Store service to fix the issue.
I'm still working through the material so most likely there will be more to follow.
No comments:
Post a Comment