In office 365 when you’re working on Exchange 2010,2013, 2016 or 2019 in a hybrid environment things might look easy but in a big enterprises where Internet security is something being taken into account very seriously. It might cause many issues that you don’t expect at all.
One of my clients whom I was doing Exchange Migration for had an issue with the Migration. The error was as follows:
Error occurs after Office 365 Exchange online connects to Exchange on-premises 2010 mailbox server
RPR05DG049-db131′, Mailbox server ‘DB3PR05MB0778.eurprd05.prod.outlook.com’
Version 15.1 (Build 466.0).RequestExpiryTimestamp : 03.04.2116 07:42:38
ObjectState : New
Troubleshooting:
To troubleshoot issues, You need to put so many things into account! The architecture of the infrastructure of where you are doing the project is very important and the need of knowing how things are working matters.
Things that could always come in mind and handy are what you will need to start your troubleshooting:
To troubleshoot the MRs, You need to know what kind of error you’re getting and to see this you can use the following powershell after you connect to Office 365 powershell.
The resultant report will reveal the error and shows you where is the exact culprit.
– Disk Latency
– Firewall Configuration (IPS/IDS)
From Exchange 2016 to 2019 or 2013 to 2016 The transient error might be related to MRSProxy or at least this is the case with me 90% of the time. To resolve this issue you will need to change the MRSProxy values on the target server and depending on the error might also be the Source server too.
SOLUTION:
===========
1. Some instability was detected in communications as well as saturation by the size of the link.
2. The procedure to increase the timeout for the service through the file MRSProxy
This guide will show you how to installing order to Install “Only” Trend Micro 11.0 on Exchange 2013 server
You will have to make sure that before you install Trend Micro you have enough resources on the mail servers or Edge servers depending on where you are intending to install it.
Prerequisites:
You will need to install Windows IIS CGI role.
Net Framework 3.5
Trend Micro Setup.
If you did not install CGI you will get the following error, so you must install it
To install it you will need to go to Add Roles and then choose and install it.
If Net Framework 3.5 is not install the setup won’t proceed unless you do so and you will get the following error:
To install Net Framework 3.5 , you can use the wizard or you can use the Powershell but you’ll need to attach Windows Server ISO File to the VM or the physical machine.
Setup will restart from the beginning
NetFrame work fails from the Server Manager
Instead, I imported the Windows 2012 r2 server ISO into the VM and ran the powershell command line
Restarted the Trend Micro Setup and the setup is working
I already have copied the setup files on my mailbox servers, in my scenario I have 2 mail box servers which I am going to install it on.
I will launch the setup and go through the following wizard
As I mentioned earlier, I am planning to install it on Exchange 2013 Mailbox servers, so I will go ahead and choose Mailbox servers
I will click Browse and Add exchange servers and as in the following snapshot it’ll show me total server count
Next I will type the Exchange Admin account which I used to setup Exchange with and login to the admin Center which is also a local admin.
This is set by default so you will need to leave it as it is.
You can keep the following default settings or change the port in case it’s already used or enable SSL.
In my case I will enable SSL as well as it’s more preferable for security purposes.
Trend micro setup will check if there’s any previous instance on the target Mailbox server in order to check if it’s an upgrade or a fresh install.
I have no proxy so I will proceed without it.
I’m planning to ignore this now and register later, so you can provide the key if you already have it and want to register.
When you continue without activating the product you will get the following warning.
Depending on if you wanna be useful or not, you can just to participate with this program or just ignore it.
In case you would like to direct or send all incoming spam messages to the user to take the decision him/her self you can choose to integrate with Outlook junk e-mail or integrate with End user’s quarantine. In this case incoming infected or suspicious mails will be delivered to the user’s Quarantine but can be restored from/with trend micro.
Trend Micro have also a control manager for centralized management, so if you have it you can configure it and manage all those scanmail from one location. If not then just click next
Click browse and choose your domain in order to select the domain admin groups to manage the trend micro scan mail application.
All server details and configuration is going to be listed in the next snapshot.
And now installation should start.
The credentials to login might be standard but you could also try your domain admin which you have assigned during the setup to login to the portal.
Any configuration that you do on the Mailbox server 1, you will have to re-do it on Server 2 since this is not centralized management.
So first thing I’ll do is update the product to the latest version.
After selecting the components to update click on Update and wait for the process to finish.
After setting and configuring couple of rules and restarting Exchange transport service on each server . I was able to test It and see that it works as in the following snapshot.
In order to export mails from Exchange 2003 (should not exceed 2 GB) you will have to copy Administrator user into another user “admin” and give that user the rights to access all other mailboxes.
You will have to navigate to the Mailbox store
Right click the mailbox store and click on Properties
Go to Security tab and add the new user (Admin) and give it full control as below
Apply, then sign out of the windows session to the Exchange machine and use the newly added domain admin to login and then open the Exmerge application
Select the second step (Extract or Import)
Select step1
Select the Exchange name and the DC (They should be set automatically)
Select the users that you want to be exported (shouldn’t exceed 2 GB).
Select the local language
Select the destination folder (In my case I mapped a network drive)
Save settings for later use if you want or just click Next.
Once done, the mailbox will be exported.
Importing into Exchange 2013
In exchange 2013 Open the EMS as administrator
Before you start, you should move all the PST files into a shared folder in the network and add the “Exchange Trusted Subsystem” user to its permission.
The same user should be added to the security tab
Providing import and export permission on Exchange 2013
In order to import the PST files to Exchange 2013 users you will have first to assign the Exchange Admin account the capability of importing these PST files then sign out from the EAC portal and back in
To do so you will have to go to EAC then go to Permissions and double click on the Recipient Management
Click Add and select the Mailbox Import Export and click Add then OK
I will add members to this role group
After signing in back to the EAC with the administrator I got the Import PST options.
Step by Step Installing Exchange server 2013 from scratch (Part 1)
In this part, I will be demonstrate how to Install exchange 2013 and prepare new Databases along with preparing the servers for high availability (DAG).
Prerequisites:
– Two Microsoft Windows 2012 R2 servers with 16 GB ram and 200GB disk divided unto two partitions.
– Two NIC, one for MAPI and one for replication.
– Exchange 2013 CU8 setup to directly go to the latest available update.
Installing Prerequisites on all exchange servers
Launch Powershell as administrator and copy then paste the following.
You should download and install the following software prerequisites as per Microsoft’s TechNet article regarding the installation. the software is available the link I posted earlier above or through this link Exchange_Prerequesties
After running all the prerequisites , we can start installation of Exchange 2013
Here I am going to change Exchange’s default installation path and place it on a different partition to avoid any data loss in case of Windows server crash or booting issues.
Now we install the second Exchange server, that will hold the same roles on it as the first one (Mailbox and CAS).
The steps are going to be exactly the same except that you won’t have to prepare the schema or AD since it’s already prepared.
Installation has finished for both servers
Creating DATABASES:
NOTE:
It’s better to mount the database upon creation and not restart the IS instantly after that.
Now it’s time to create new Databases and replace them with the default ones that come with the Installation
First we’ll have to start off by creating our targeted databases which we want to use them. Note that for the standard version of Exchange 2013 you can only create up to 5 databases per mailbox server.
In order to demonstrate all benefits of Exchange 2013 and its features including DAG. I will create 2 databases. One database on each server.
The first database will be called DB1SRV1
As soon as we have created the Database, we faced the following error with event ID 106
Then another warnıng from MSExchangeFastSearch wıth event id 1006
This indicates that a database should not be mounted upon creation, you should untick the mount DB option when you create one.
After waiting a bit the following logs should appear and show a healthy indexing start.
Once the DB has been created, Exchange AC will require that you restart the IS (Information store Service) in order for replication to happen without an issue.
Database is showing healthy and no issues so far.
Now we’ll create a new DB on the second server without ticking the mount DB option.
Microsoft Exchange Server Locator Service failed to find active server for database ‘de5f3051-c202-4976-b8e4-65bbbe0c2395’. Error: The database with ID de5f3051-c202-4976-b8e4-65bbbe0c2395 couldn’t be found.
The same exact errors came after creating the Database without mounting it.
Now let’s restart the IS service and mount our database then see what happens..
Upon restarting the service, we get the following error which is related to the MS Exchange replication service . It noticed that the database that we have created has never been mounted in order to start the indexing.
Let’s mount the database and see the changes
Mounting the database have got the AM to report successfully and after couple of seconds the MSExchangeFastSearch will check out if the database have any indexing files.
No indexing state have been found and so the FastSearch service will give you a 1013 warning report. This is a good warning because it reports that the service is working properly and that it will create the indexing folder after couple of minutes as we’ll see later.
It takes approximately 3-5 minutes for the database to start the indexing.
Now on the EAC, the DB should report healthy. Let’s see
Removing Default databases
First step before deleting the default databases is to move any system mailboxes or arbitrary mailboxes in them to the newly created databases…
Paul Cunningham wrote a great article on how to do this using Powershell … in the following link
The warning above is apparently due to Exchange permission on AD. It has been described in detail on how to solve this warning by Nuno Mota in the following Link.
Stack trace: at Microsoft.Exchange.Clients.Common.UserAgent.HasString(String str)
at Microsoft.Exchange.Clients.Common.UserAgent.get_Layout()
at Microsoft.Exchange.Clients.Common.UserAgent.get_LayoutString()
at ASP.auth_logon_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
at System.Web.UI.Page.Render(HtmlTextWriter writer)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
OWA PAGE
Solution:
On Exchange servers, Make sure that Exchange servers are not members of Organization Management group and if they are then remove them and run this cmdlet anyway on all Exchange Servers then restart the Servers.
After you attempt to try Hybrid Configuration Wizard between Exchange 2013 SP1 and Exchange online (Office 365) .. You are unable to login to your OWA/ECP Page and instead you get an error:
Once you look at your event viewer you notice it records the event ID 4 with the following error
Cause:
The HCW or “Hybrid Configuration Wizard” In Exchange 2013 (CU6 or 8) might cause some changes to your CAS folder in the following path and file
“c:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp\DDI”` the file name is RemoteDomains.xaml and multiply some variables which causes ECP to fail and report that error.
System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.DuplicateNameException: A column named ‘TargetDeliveryDomain’ already belongs to this DataTable.
at System.Data.DataColumnCollection.RegisterColumnName(String name, DataColumn column)
at System.Data.DataColumnCollection.BaseAdd(DataColumn column)
at System.Data.DataColumnCollection.AddAt(Int32 index, DataColumn column)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase.CreateColumn(DataTable table, Dictionary`2 rbacMetaData)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase..ctor(Service profileBuilder)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase..ctor(String schemaFilesInstallPath, String schema)
at Microsoft.Exchange.Management.ControlPanel.WebServiceReference.GetList(DDIParameters filter, SortOptions sort)
at Microsoft.Exchange.Management.ControlPanel.OrganizationCache.LoadTargetDeliveryDomain(AddValueHandler addValue, LogErrorHandler logError)
at Microsoft.Exchange.Management.ControlPanel.OrganizationCache.TryGetValue[T](String key, T& value)
at Microsoft.Exchange.Management.ControlPanel._Default.RenderMetroTopNav()
at ASP.default_aspx.__RendermainForm(HtmlTextWriter __w, Control parameterContainer)
at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)
at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at ASP.default_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
at System.Web.UI.Page.Render(HtmlTextWriter writer)
at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.DuplicateNameException: A column named ‘TargetDeliveryDomain’ already belongs to this DataTable.
at System.Data.DataColumnCollection.RegisterColumnName(String name, DataColumn column)
at System.Data.DataColumnCollection.BaseAdd(DataColumn column)
at System.Data.DataColumnCollection.AddAt(Int32 index, DataColumn column)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase.CreateColumn(DataTable table, Dictionary`2 rbacMetaData)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase..ctor(Service profileBuilder)
at Microsoft.Exchange.Management.DDIService.AutomatedDataHandlerBase..ctor(String schemaFilesInstallPath, String schema)
Looking in the path I have wrote above “\Microsoft\Exchange Server\V15\ClientAccess\ecp\DDI” and opening the file that I have mentioned “RemoteDomains.xaml” you can clearly see there are incorrect format that have been duplicated 3 times.
To make sure that this was the cause, I have another server with CU8 on it so I went and checked the same file which was in the same location to find the result different.
This is the server that works in another environment and doesn’t have any issue.
So, the solution was to remove the two duplicates and correct the format of the variable line… I corrected the first line that includes
And deleted the other two identical lines.. then I saved the file and closed notepad.
Next: Open IIS on the same server and go to “Application Pools” right click on the affected pools and Recycle them.. You don’t need to reset IIS as the fix should work right away.
Recycle ECP Pool
After recycling checking if the pool is reporting started or not…
I have previously done a Hybrid integration with Office 365 with my Exchange 2010 server and enabled Archiving online when I migrated my user to Exchange online but then I finished my demo and decided to bring the user back on-premises. Now I have deployed Exchange 2013 and wanted to migrate the same user to Exchange 2013 from 2010 but the migration request fails with the following message.
6/7/2015 1:23:24 PM [EXCH2K13] ” created move request.
6/7/2015 1:23:57 PM [EXCH2K13] The Microsoft Exchange Mailbox Replication service ‘EXCH2K13.demotesas.local’ (15.0.1076.6 caps:1FFF) is examining the request.
6/7/2015 1:23:59 PM [EXCH2K13] Connected to target mailbox ‘b6ee5dd7-beab-45a0-9933-8e926a694de3 (Primary)’, database ‘Mailbox Database 0439787427’, Mailbox server ‘EXCH2K13.demotesas.local’ Version 15.0 (Build 1076.0).
6/7/2015 1:23:59 PM [EXCH2K13] Connected to source mailbox ‘b6ee5dd7-beab-45a0-9933-8e926a694de3 (Primary)’, database ‘Database1’, Mailbox server ‘EXCH01.demotesas.local’ Version 14.3 (Build 174.0).
6/7/2015 1:23:59 PM [EXCH2K13] Cleared sync state for request b6ee5dd7-beab-45a0-9933-8e926a694de3 due to ‘CleanupOrphanedMailbox’.
6/7/2015 1:23:59 PM [EXCH2K13] Mailbox signature will not be preserved for mailbox ‘b6ee5dd7-beab-45a0-9933-8e926a694de3 (Primary)’. Outlook clients will need to restart to access the moved mailbox.
6/7/2015 1:25:10 PM [EXCH2K13] Mailbox ‘Mohammed JA. Hamada’ was loaded from domain controller ‘ad.demotesas.local’.
6/7/2015 1:25:18 PM [EXCH2K13] Fatal error UpdateMovedMailboxPermanentException has occurred.
On Exchange 2010, I launched Exchange Management shell and ran the following cmdlet which will show any attribute that has arch in it for the user Mohammed
Get-mailbox User | fl arch*
Since there’s no archive mailbox then the archive domain is invalid and I don’t even own it anymore as it has expired a while ago.
Resolution:
I will try to remove the archive domain object from the user’s properties using the following cmdlet
Set-mailbox mailboxname -ArchiveDomain $null
Using the above cmdlet seems to fail due to this property being administered by Exchange server so it’ll have to be removed manually.
I will open the user’s attribute and delete the value and try to continue the migration again.
In a very interesting situation that I came through I had an environment with two DCs and Exchange 2010 that I had previously setup for Hybrid integration with Office 365 for demonstration with a trial subscription but I haven’t removed the integration after I finished my test and the trial expired and the tenant was deleted.
Next I intended to upgrade my existing Exchange 2010 to Exchange 2013 and setup coexistence between them however, I have stumbled in the step of preparation of AD schema for Exchange 2013. While trying to prepare the schema I got the following error
Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
Copying Files…
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
A hybrid deployment with Office 365 has been detected. Please ensure that you are running setup with the /TenantOrganizationConfig switch. To use the TenantOrganizationConfig switch you must first connect to your Exchange Online tenant via PowerShell and execute the following command: “Get-OrganizationConfig | Export-Clixml -Path MyTenantOrganizationConfig.XML”. Once the XML file has been generated, run setup with the TenantOrganizationConfig switch as follows “/TenantOrganizationConfig MyTenantOrganizationConfig.XML”.
If you continue to see this this message then it indicates that either the XML file specified is corrupt, or you are attempting to upgrade your on-premises Exchange installation to a build that isn’t compatible with the Exchange version of your Office 365 tenant. Your Office 365 tenant must be upgraded to a compatible version of Exchange before upgrading your on-premises Exchange installation. For
)/ms.exch.setupreadiness.DidTenantSettingCreatedAnException.aspx The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
The Office 365 Hybrid setup was still there in my Exchange Console and since I couldn’t follow MS’s recommended steps to connect to O365 tenant and get the XML file then I had to do things manually.
First I connected to the EMC and removed all the instances that were created during the Exchange Hybrid Wizard Configuration
1- Removing Organization Relationships
2- Removing Federation Trust
3- Removing Remote Domains
4- Removing Accepted Domains
5- Removing Send and Receive Connectors
6- Lastly the Hybrid Configuration object…
Since remove-hybridconfiguration cmdlet is not supported to remove the hybrid configuration object from AD then we have no choice but to use ADSIEDIT tool to do so.
I will navigate to Configuration > Services > Microsoft Exchange > First Organization > Delete “CN=Hybrid Configuration”
Restart MSExchangeServicehost
Now I will try again to prepare AD schema for Exchange 2013 but I got a different error
Extending Active Directory schema FAILED
The following error was generated when “$error.Clear);
RoleSchemaPrefix + “schema0.ldf”)” was run: “Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running ‘ldifde.exe’ to import the schema file ‘C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf’. The error code is: 8224. More details can be found in the error file: ‘C:\Users\Administrator.DEMOTESAS\AppData\Local\Temp\2\ldif.err’at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchem
cessRecord()at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.The Exchange Server setup operation didn’t complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Checking the ldif.err file mentioned in the error above it seems that Exchange is complaining because the changes of the AD schema is not being replicated to the other AD partners which is true since I have another additional DC that’s turned off.
After turning on the other DC we’ll see what happens
The other DC had another issue as I have turned it off for long time and it was not syncing due to expired Tomb stone life so I had to fix this issue as well and I have published it in a different article.
Please click here to see how the replication issue was fixed.
![clip_image001[4]](https://www.moh10ly.com/wp-content/uploads/2019/12/clip_image0014.png "clip_image001[4]")
![clip_image001[6]](https://www.moh10ly.com/wp-content/uploads/2019/12/clip_image0016.png "clip_image001[6]")
![clip_image001[5]](http://lh3.ggpht.com/-dDGI380VnFY/VN5jQVDnbdI/AAAAAAAAMyE/M5Q8ZrjE96M/s1600-h/clip_image001%25255B5%25255D%25255B2%25255D.png)
![clip_image002[5]](http://lh4.ggpht.com/-rikPuuQXiBU/VN5jR8PCvyI/AAAAAAAAMyU/26AfD8H_aC4/s1600-h/clip_image002%25255B5%25255D%25255B2%25255D.png)
![clip_image003[4]](http://lh4.ggpht.com/-_mB2PtU2DTQ/VN5jTLXtKQI/AAAAAAAAMyk/vG5d45uTJS8/s1600-h/clip_image003%25255B4%25255D%25255B2%25255D.png)
![clip_image004[4]](http://lh3.ggpht.com/-0Qqghl9OHu0/VN5jUuwufkI/AAAAAAAAMy0/FYegPqp4X1I/s1600-h/clip_image004%25255B4%25255D%25255B2%25255D.png)
![clip_image005[4]](http://lh3.ggpht.com/-nCadhgGizuA/VN5jWik-PJI/AAAAAAAAMzE/-iRadVZPBVU/s1600-h/clip_image005%25255B4%25255D%25255B2%25255D.png)
![clip_image006[4]](http://lh6.ggpht.com/-mZCI4EKYUyk/VN5jYcluKZI/AAAAAAAAMzU/dIABjwji3xI/s1600-h/clip_image006%25255B4%25255D%25255B2%25255D.png)
![clip_image007[4]](http://lh6.ggpht.com/-yYeBlYfSCC4/VN5jZ3gMzZI/AAAAAAAAMzk/jKPK5JVS8us/s1600-h/clip_image007%25255B4%25255D%25255B2%25255D.png)
![clip_image008[4]](http://lh5.ggpht.com/-0X0m-C8sX6M/VN5jbROpkgI/AAAAAAAAMz0/0loDe6sPgLk/s1600-h/clip_image008%25255B4%25255D%25255B2%25255D.png)
![clip_image009[4]](http://lh4.ggpht.com/-8_staw7_RZY/VN5jdSi8JSI/AAAAAAAAM0E/42xEHa2n4HI/s1600-h/clip_image009%25255B4%25255D%25255B2%25255D.png)
![clip_image010[4]](http://lh3.ggpht.com/-mr7bsVnU1io/VN5jfdOrW_I/AAAAAAAAM0U/5znuYzgk8C4/s1600-h/clip_image010%25255B4%25255D%25255B2%25255D.png)
![clip_image011[4]](http://lh4.ggpht.com/-fUsuWWVSZGY/VN5jg6E6NtI/AAAAAAAAM0k/xjCyBuasWLY/s1600-h/clip_image011%25255B4%25255D%25255B2%25255D.png)
![clip_image001[4]](http://lh3.googleusercontent.com/-XXtVNxuZ5z8/VXMWlWKSEII/AAAAAAAAPPo/EV4rhXgJ7ZM/s1600-h/clip_image001%25255B4%25255D%25255B2%25255D.png)
![clip_image001[6]](http://lh3.googleusercontent.com/-k_2UrOC8msw/VXMWqPZLUTI/AAAAAAAAPQI/aoa4-s_Imy4/s1600-h/clip_image001%25255B6%25255D%25255B2%25255D.png)
![clip_image001[8]](http://lh3.googleusercontent.com/-C6mmc8CrhzU/VXMWwS-xk4I/AAAAAAAAPQo/0QT-gs1xn7U/s1600-h/clip_image001%25255B8%25255D%25255B2%25255D.png)
![clip_image002[4]](http://lh3.googleusercontent.com/-IC-5rtrV8Gw/VXMWyhYdb0I/AAAAAAAAPQ4/Q7C6tchAuQg/s1600-h/clip_image002%25255B4%25255D%25255B2%25255D.png)
![clip_image001[10]](http://lh3.googleusercontent.com/-QK0BMtmTDQU/VXMW1NykwrI/AAAAAAAAPRI/FIK-If4zW2w/s1600-h/clip_image001%25255B10%25255D%25255B2%25255D.png)
![clip_image002[6]](http://lh3.googleusercontent.com/-e4580NxBzaw/VXMW38lLT5I/AAAAAAAAPRY/NZXv5Uqbnhw/s1600-h/clip_image002%25255B6%25255D%25255B2%25255D.png)
![clip_image001[12]](http://lh3.googleusercontent.com/-I6xmLYqpilg/VXMW6KchDZI/AAAAAAAAPRo/OXmfd81Xcc0/s1600-h/clip_image001%25255B12%25255D%25255B2%25255D.png)
![clip_image002[8]](http://lh3.googleusercontent.com/-5YOy8DyRD1w/VXMW82kdfjI/AAAAAAAAPR4/yS2JUjZul2I/s1600-h/clip_image002%25255B8%25255D%25255B2%25255D.png)
![clip_image001[14]](http://lh3.googleusercontent.com/-npkovi6FGPY/VXMXKQSSl6I/AAAAAAAAPTI/cGRSPiPiGYw/s1600-h/clip_image001%25255B14%25255D%25255B2%25255D.png)
![clip_image001[16]](http://lh3.googleusercontent.com/-X0OddyoEoXc/VXMXPoRFy3I/AAAAAAAAPTo/-GEeLU3c6aU/s1600-h/clip_image001%25255B16%25255D%25255B4%25255D.png)
![clip_image001[19]](http://lh3.googleusercontent.com/-2lPpk3aXgH0/VXMXR-Zc8rI/AAAAAAAAPT0/0zGvNSF7bbo/s1600-h/clip_image001%25255B19%25255D%25255B2%25255D.png)
![clip_image001[21]](http://lh3.googleusercontent.com/-zce7PfwKYow/VXMXTSfZ-0I/AAAAAAAAPUI/RpL1e8iIglg/s1600-h/clip_image001%25255B21%25255D%25255B2%25255D.png)
![clip_image002[10]](http://lh3.googleusercontent.com/-6WpCOePGowU/VXMXVB7FAII/AAAAAAAAPUY/mpL2D9ekf2o/s1600-h/clip_image002%25255B10%25255D%25255B2%25255D.png)