Exchange 2010 Migration of 200 Users/Force Archiving

Exchange 2010 Outlook 2007
Here's my situation. We are migrating 200 mailboxes from our current domain which will be absorbed into another company/organization. The new organization is putting limits on our users mailboxes of 100 Mb or 5000 items in order to make a smooth
transition from our Exchange environment prior to them absorbing all of our mailboxes. Of the 200 users a quarter of them are way over that limit. We have sent out numerous emails informing the users (mostly offsite) to archive all of their emails
and clear out the "deleted"/"sent" items. Obviously no one has listened to our requests to get their mailboxes down to the limit the new organization has set for us. I just recently migrated all of the users mailboxes to .pst's
via a powershell script, but as you know, that only copies the data. Is there a way via powershell to move or force all of the users data (sent/deleted/inbox) to an archive thus freeing up their mailboxes for the upcoming migration? The new org
will not approve the migration of any mailboxes over the 100 Mb/5000 item limit. I'm not limiting a solution to powershell -- I will take any solution that is Microsoft-centric. I will not be able to use third party tools or solutions due to the
nature of my job.

Hi,
Since the target domain set a policy to limit the migration, I suggest kindly let the target domain disalbe or expand the limitation for a while to complete the migration, if it is possible.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Case of the Missing User Exchange 2003 - Exchange 2010 Migration issue

Hey All,
I am in the middle migrating from Exchange 2003 to Exchange 2013 by way of Exchange 2010 and going through the final parts of my Exchange 2010 portion of the migration I found that one of the users on Exchange 2003 is not showing up in the EMC to migrate.
In EPS I can find the user with Get-User username but I cannot get the mailbox or kick off the mailbox move from EPS giving me the error of "Object could not be found" It is a valid user with a valid user mailbox and I can log into the
mailbox in OWA for Exchange 2003. Any thoughts as to why the user's mailbox is not showing in EMC or that I can't get it to move via PS?
Thanks,
Joe

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Migrate Exchange 2010 to Exchange 2013, Need to defined win 7 users logon to Exchange 2010 & Win 8.1 users logon to Exchange 2013

Hi,
My organization have few win 7 and windows 8.1 clients. Now I want to migrate exchange server 2010 to 2013. And I don't want to remove exchange 2010 from the organization. Because I want to connect win 7 client through exchange 2010 and windows 8.1 user
connect to exchange 2013. Is there any way to define the win 7 users to connect to exchange 2010 and Windows 8.1 users to connect to exchange 2013?
Md. Ramin Hossain

The client connections are proxied to the mailbox servers that hold the mailbox.
You would need to have 2010 MBX servers with the mailboxes for the XP users, and 2013 MBX servers holding the mailboxes for the 7 users. And of course, the appropriate CAS servers.
Realistically, you need to migrate away from Windows XP. It is no longer supported.

Exchange 2007 to Exchange 2010 Migration

Hi all,
I am migrating to exchange 2007 to exchange 2010 .This is not a migration data only migration like i am exporting mailboxes and importing it to new mailboxes .But email address and SAM account name will be same as per the source.Post migration i will point
the auto discover to new organisation.May i know what will be the impact to users??need to reconfigure outlook profile or does it will look for auto discover and prompt for new email id?
Jayakumar K

Is it in the same forest of or both the servers are different forest?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2003 to Exchange 2010 migration steps

HI ,
I have migrated windows 2003 to windows 2008.Its successfully migrated.
Second phase i have a plan to migrate exchange 2003 to exchange 2010.
My current setup
windows 2008 64bit (DC)
exchange 2003 sp2
1
Bring the Exchange organization to Exchange Native Mode.
2
Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
3
Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4
Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
to Windows Server 2003 SP2 or greater.
5
Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6
Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7
Install any necessary prerequisites (WWW for CAS server role).
8
Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
at the command line.)
9
Install CAS server role servers and configure per 2010 design. Validate functionality.
10
Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11
Install Hub Transport role and configure per 2010 design.
12
Transfer inbound and outbound mail traffic to the HT servers.
13
Install mailbox servers and configure Databases (DAG if needed).
14
Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
Public Folder tool.
15
Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
16
Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17
1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
18
Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19
Delete Public and Private Information Stores from Exchange 2003 server(s).
20
Delete Routing Group Connectors to Exchange Server 2003.
21
Delete Recipient Update Service agreements using ADS Edit.
22
Uninstall all Exchange 2003 servers.
This is my plan to migrate.But i have a doubt in installing exchange 2010 in this scenario.
Is it necessary to use
Setup.com /PrepareLegacyExchangePermissions,
Please help me what excactly i have to do

I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
Migration</a> is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips.
Some Articles I would like to share as well:
<a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
Exchange Server Migration to the Cloud</a>
It takes a lot of time and effort to get it right. Thank you for helping
Here some information about services for migrations
<a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

Exchange 2010 SP3 UR9 OWA users cannot open mail items

We recently had users reporting unable to open items in OWA. Issue is confirmed across all CAS servers.
Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
3 AD Site DAG, multi-role servers
So far we have done the following to troubleshoot:
* Check security propagation for account permissions.
* Check security on all virtual directories.
* Check permissions on web.config
* Re-run PrepareAD
* Uninstall and reinstall CAS role
Please review the errors below and let me know if you have any words of wisdom on this issue. Thanks!
Errors:
Request
Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request
Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi Noel,
Base on my search, it may be due to IRM feature been enabled for OWA.
I recommend you use the following command to check if the value of IRMEnabled parameter is true:
Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
S#
Virtual Directory
URL
Exchange Server 2010
Exchange Server 2007
1
Web Services Virtual Directory
Internal URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
2
Web Services Virtual Directory
External URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
3
ActiveSync Virtual Directory
Internal URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
4
ActiveSync Virtual Directory
External URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
Following error is logged on Console on Mac when this issue happens:
30/10/12 3:27:28.398 AM
Mail
*** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
EWS fetchRootFolderId: expected one folder in response, received: 0
0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
10 Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
11 Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
12 libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
13 libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
14 libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
15 libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

Hi Akebono,
Let's check a few things in your server:
1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
5. If you still experience such problems - post the ExRCA error report here.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Exchange 2010 Migration to 2013 Coexistence url's

Hello,
What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Read the article below from Ross Smith. There can't be better article than this:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
If exchange 2010 and 2013 are on same site, then you need to:
1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
2. Move the SSL certificates from Exchange 2010 to Exchange 2013
3. Point the external URL to Exchange 2013 instead of Exchange 2010
4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
- Sarvesh Goel - Enterprise Messaging Administrator

Error in uninstall Exchange 2003 after Exchange 2010 migration.

Setup encountered an error while checking prerequisites for component "Microsoft Exchange": 0X80072030 (8240): There is no such object on the server. I searched about the error and most of the hit is referring to postmaster account point
to the old server and that doesn't apply to our environment.
http://support.microsoft.com/kb/283089
below is the errors from the setup log. Other users had reported this problem but didn't find any solution other than manually uninstall the last Exchange 2003 server.  The problem is I couldn't find any official KB for manually
remove legacy Exchange server from Exchange 2010 org, bb288905 or kb833396 do not provide enough information. So is my only choice is to call Microsoft Support?
thanks
[22:38:41] Entering ScConstructAddressListServiceDNAndCN
[22:38:41] Leaving ScConstructAddressListServiceDNAndCN
[22:38:41] === IGNORING PREVIOUS ERRORS === ScPRQ_ServerGroupsHaveNotBeenMovedOrRenamed (f:\titanium\admin\src\udog\excommon\prereq.cxx:8080)
           The operation has completed successfully.
[22:38:41] Entering CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Leaving CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Entering ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Using cached result for domain "/dc=org/dc=cityofwpg/dc=ad"
[22:38:41] The required permissions have already been set
[22:38:41] Leaving ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Attempting to create the SRS DOB [checking whether SRS is installed].
[22:38:41] Entering ScFindRoutingGroupThatContainsServer
[22:38:41] Leaving ScFindRoutingGroupThatContainsServer
[22:38:41] Entering ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41] This prerequisite has PASSED -- ID:62235 --
[22:38:41] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41] ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
           The operation has completed successfully.
[22:38:41] Setup encountered an error while checking prerequisites for the component "Microsoft Exchange":
0X80072030 (8240): There is no such object on the server.
[22:43:09] CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
           Error code 0X80004002 (16386): No interface.

Did you also check for other accounts, i.e. non-postmaster?
Setup will check to make sure that there are no mailboxes homed onto this server.    This attribute homeMDB could still be set for a mailbox that has the Exchange attributes remove. Seen that before when people set attributes directly
via scripts.....
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Yes, I did. Nothing has MDB = the legacy server.    The error from setup log seems to suggest a different problem.

Exchange 2003 to Exchange 2010 Migration

Is there anything I have to do to migrate Exchange 2003 to Exchange 2010 aside from migrating the database(s)? I believe autodiscover picks up the new server when people open Outlook?

It will definitely HELP
you with the migration process, its not a guaranty for a successful one.
You should be familiar with both systems (Exchange 2003 & 2010) and know the migration process and be familiar with each step .
Best practice is to make the migration in lab environment that is a copy of you production environment first. that way you will get an experience with the process and know in advance if there are any issues before go to production. I
know that in real world this is not always possible.
Here is another grate guide from Pete Long:
http://www.petenetlive.com/KB/Article/0000234.htm
As a side note, Exchange SP1 or SP2 no longer supported, so make sure your Exchange 2010 is installed with minimum SP3 (RU5 is better).
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Exchange 2003 Exchange 2010 migration confusing?

Hi,
I have searched several articles for this migration in this forum and other forums (ie
petenetlive,
simple-talk,
Exchange Server Deployment Assistant,
Technet) but when you start reading the guides there are discrepancies between one and the others and vice versa.
I have this scenario:
1) Old server windows 2003 R2 std + exchange 2003
2) New server windows 2012 R2 + exchange 2010
I have not installed exchange 2010 yet because I had to first update Active Directory schema to W2012 (adprep /forestprep, adprep /domainprep) R2 and also update exchange schema using setup /PrepareSchema from the exchange 2010 media.
Then I read that I have to install Exchange 2010 in stages ie Client Access Role first, then Transport Hub and then Mailbox role.
Also a digital certificate i required and was wondering if I could still use a self signed certificate.
Does anyone know of a very good article or video that explains this process consistently STEP by STEP?
Thanks
Regards
Ipnotech

Hi,
Here are more good articles about install Exchange 2010 in Exchange 2003 environment:
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence:
http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
Install Exchange 2010 in an Existing Exchange 2003 Organization:
http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
Create a New Exchange Certificate:
http://technet.microsoft.com/en-us/library/dd351057(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 Migration - Decommissioning Multi Role Server and Splitting Roles to 2 new servers - Certificate Query

Hi,
I have been tasked with decommissioning our single Multi Role Server (CAS/HT/MB) and assigning the roles to 2 new servers. 1 server will be dedicated to CAS and the other new server will be dedicated to HT & MB roles.
I think I'm OK with the moving of HT and MB roles from our current server to the new HT/MB server by following "Ed Crowley's Method for Moving Exchange Servers", my focus is on the migration of the CAS role from the current to the new server as
this one has the potential to kill our mail flow if I don't move the role correctly.
The actual introduction of the new CAS server is fairly straight forward but the moving of the certificate is where I need some clarification.
Our current multi role server has a 3rd Party Certificate with the following information:
Subject: OWA.DOMAIN.COM.AU
SANs: internalservername.domain.local
autodiscover.domain.com.au
The issue here is the SAN entry "internalservername.domain.local" which will need to be removed in order for the certificate to be used on the new CAS server, firstly because the CAS server has a different name and secondly the internal FQDN will
no longer be allowed to be used from 2015 onwards. So I will need to revoke this certificate and issue a new certificate with our vendor who is Thawte.
This presents me with an opportunity to simplify our certificate and make changes to the URLs using a new certificate name, so I have proposed the following:
New Certificate:
Subject: mail.domain.com.au
SANs: autodiscover.domain.com.au
OWA.DOMAIN.COM.AU
I would then configure the URLs using PowerShell:
Set-ClientAccessServer -Identity NEWCASNAME-AutodiscoverServiceInternalUrl https://mail.domain.com.au/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity " NEWCASNAME\EWS (Default Web Site)" -InternalUrl https://mail.domain.com.au/ews/exchange.asmx
Set-OABVirtualDirectory -Identity " NEWCASNAME\oab (Default Web Site)" -InternalUrl https://mail.domain.com.au/oab
Set-OWAVirtualDirectory -Identity " NEWCASNAME\owa (Default Web Site)" -InternalUrl https://mail.domain.com.au/owa
I would also then set up split DNS on our internal DNS server creating a new zone called "mail.domain.com.au" and add an host A record with the internal IP address of the new CAS server.
Now I know I haven't asked a question yet and the only real question I have is to ask if this line of thinking and my theory is correct.
Have I missed anything or is there anything I should be wary of that has the potential to blow up in my face?
Thanks guys, I really appreciate any insights and input you have on this.

Hi Ed,
Thanks for your reply, it all makes perfect sense I guess I was being optimistic by shutting down the old server and then resubscribing the edge and testing with mailboxes on the new mailbox server.
I will make sure to move all of the mailboxes over before removing the old server via "Add/Remove Programs". Will I have to move the arbitration mailboxes on the old server across to the new mailbox server? Will having the arbitration mailboxes
on the old server stop me from completely removing exchange?
Also, the InternalURL & ExternalURL properties are as follows:
Autodiscover:
New CAS - InternalURL: https://svwwmxcas01.pharmacare.local/Autodiscover/Autodiscover.xml
Old CAS - InternalURL: https://svwwmx001.pharmacare.local/autodiscover/autodiscover.xml
WebServices:
New CAS - InternalURL: https://svwwmxcas01.pharmacare.local/EWS/Exchange.asmx
New CAS - ExternalURL: https://owa.pharmacare.com.au/EWS/Exchange.asmx
Old CAS - InternalURL: https://svwwmx001.pharmacare.local/ews/exchange.asmx
Old CAS - ExternalURL: https://owa.pharmacare.com.au/EWS/Exchange.asmx
OAB:
New CAS - InternalURL: http://svwwmxcas01.pharmacare.local/OAB
New CAS - ExternalURL: https://owa.pharmacare.com.au/OAB
Old CAS - InternalURL: https://svwwmx001.pharmacare.local/oab
Old CAS - ExternalURL: https://owa.pharmacare.com.au/OAB
OWA:
New CAS - InternalURL: https://svwwmxcas01.pharmacare.local/owa
New CAS - ExternalURL: https://owa.pharmacare.com.au/
Old CAS - InternalURL: https://svwwmx001.pharmacare.local/owa
Old CAS - ExternalURL: https://owa.pharmacare.com.au/
ECP:
New CAS - InternalURL: https://svwwmxcas01.pharmacare.local/ecp
New CAS - ExternalURL: https://owa.pharmacare.com.au/ecp
Old CAS - InternalURL: https://svwwmx001.pharmacare.local/ecp
Old CAS - ExternalURL: https://owa.pharmacare.com.au/ecp
Our Public Certificate has the following details:
Name: OWA.PHARMACARE.COM.AU
SAN/s: autodiscover.pharmacare.com.au, svwwmx001.pharmacare.local
From your previous communications you mentioned that this certificate would not need to change, it could be exported from the old server and imported to the new which I have done. With the InternalURL & ExternalURL information that you see here can you
please confirm that your original recommendation of keeping our public certificate and importing it into the new CAS is correct? Will we forever get the certificate warning on all of our Outlook clients when we cut over from the old to the new until we get
a new certificate with the SAN of "svwwmx001.pharmacare.local" removed?
Also, I am toying with the idea of implementing a CAS Array as I thought that implementing the CAS Array would resolve some of the issues I was having on Saturday. I have followed the steps from this website, http://exchangeserverpro.com/how-to-install-an-exchange-server-2010-client-access-server-array/,
and I have got all the way to the step of creating the CAS array in the Exchange Powershell but I have not completed this step for fear of breaking connectivity to all of my Outlook Clients. By following all of the preceeding steps I have created a Windows
NLB with dedicated NICs on both the old CAS and the new CAS servers (with separate IP addresses on each NIC and a new internal IP address for the dedicated CAS array) and given it the name of "casarray.pharmacare.local" as per the instructions on
the website, the questions I have on adding the CAS array are:
1. Do you recommend adding the CAS array using this configuration?
2. Will this break Outlook connectivity alltogether?
3. Will I have to generate a new Public Certificate with an external FQDN of "casarray.pharmacare.com.au" pointing back to a public IP or is it not required?
4. If this configuration is correct, and I add the CAS Array as configured, when the time comes to remove the old server is it just as simple as removing the NLB member in the array and everything works smoothly?
So, with all of the information at hand my steps for complete and successful migration would be as follows:
1. Move all mailboxes from old server to new server;
2. Move arbitration mailboxes if required;
3. Implement CAS Array and ensure that all Outlook clients connect successfully;
4. Remove old server;
5. Shut down old server;
6. Re-subscribe Edge from new Hub Transport server;
7. Test internal & external comms;
We also have internal DNS entries that would need changing:
1. We have split DNS with a FLZ of "owa.pharmacare.com.au" that has a Host A record going to the old server, this would need changing from "svwwmx001.pharmacare.local" to "svwwmxcas01.pharmacare.local";
2. The _autodiscover entry that sits under _TCP currently has the IP address of the old server, this would need to be changed to the IP address of the new CAS;
3. The CNAME that sits in our FLZ for "pharmacare.local" would need to be changed from "svwwmx001.pharmacare.local" to "svwwmxcas01.pharmacare.local".
4. Or rather than using the FQDN of the server where applicable in the DNS changes would I be using the FQDN of the CAS Array instead? Please confirm.
Would you agree that the migration path and DNS change plan is correct?
Sorry for the long post, I just need to make sure that everything goes right and I don't have egg on my face. I appreciate your help and input.
Thanks again.
Regards,
Jamie

Clear out old messages in Exchange 2010 journal mailbox after messages are archived to .PST Getting Error on Date

# THIS IS THE FIRST COMMAND THAT I RUN IN A SEPARATE .PS1 FILE. THIS SEEMS TO WORK FINE:
New-MailboxExportRequest JournalMailbox -FilePath '\\dfsdr.dc.pud\PowershellEmailArchive\Journal.pst'
# NEXT I AM TRYING TO CLEAN OUT EVERYTHING ELSE UP UNTIL 1-2 DAYS AGO BUT GETTING THIS ERROR:
[PS] C:\scripts>.\CleanOutOldMsg.ps1
Please adjust the date time. Make sure it is in the correct format.
    + CategoryInfo          : InvalidArgument: (:) [], ParserException
    + FullyQualifiedErrorId : 44F6D37F
# HERE'S WHAT I'VE DONE:
$global:startDate = (Get-Date).AddDays(-31).ToString('MM/dd/yyy')
$global:endDate = (get-date).AddDays(-1).ToString('MM/dd/yyy')
# HAVE TRIE THIS DATE FORMAT TOO:
$endDate = (Get-Date).AddDays(-1).ToShortDateString()
$startDate = (Get-Date).AddDays(-31).ToShortDateString()
# AND ALSO THIS DATE FORMAT:
# $endDate = Get-Date -Day 2 "00:00:00"
# $startDate = $endDate.AddDays(-30)
# $endDate = $endDate.ToShortDateString()
# $startDate = $startDate.ToShortDateString()
# THIS COMMAND GIVES DATE ERRORS:
Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:'${startDate}'..'${endDate}'" -DeleteContent -Force
# THIS COMMAND GIVES DATE ERRORS TOO:
Get-Mailbox -Identity "JournalMailbox" | Search-Mailbox -SearchQuery "Received:'${startDate}'..'${endDate}'" -DeleteContent -Force
# THIS WORKS:
Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:02/07/2014..03/07/2014" -DeleteContent -Force
# I FOUND SOME OF THE INFORMATION HERE:
https://serverfault.com/questions/511610/how-can-i-move-exchange-items-to-a-pst-using-powershell
Thanks in advance! Jim
Sorry if I wasn't as clear as I could have been. I'm trying to clean out the Journal mailbox after exporting the messages to a .PST file. I've tried formatting the date different ways and when I check it the format seems OK. For some reason I'm
still getting the same error. I've tried this which was suggested and I received the same error listed above:
Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:'${$startDate}'..'${$endDate}'" -DeleteContent -Force
For some reason the -SearchQuery is not accepting the variable.
Thanks, Jim

Thank You Yan Li!   I ran commands both ways and still received errors. Here's the first command and the error message:
Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -SearchQuery "Received:"$startDate".."$endDate"" -DeleteContent -Force
Error:
[PS] C:\scripts>.\CleanOutOldMsg.ps1
A positional parameter cannot be found that accepts argument '02/10/2014..03/12/2014'.
    + CategoryInfo          : InvalidArgument: (:) [Search-Mailbox], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Search-Mailbox
Here's the result of the following command which is formatted a bit different per your suggestion:
Search-Mailbox -Identity JournalMailbox -TargetFolder inbox -TargetMailbox jimk -searchQuery "Received:>$startDate and Recieved:< $enddate" -DeleteContent -Force
[PS] C:\scripts>.\CleanOutOldMsg.ps1
The property keyword isn't supported.
    + CategoryInfo          : InvalidArgument: (:) [], ParserException
    + FullyQualifiedErrorId : 34A6B2A1
Would you happen to have any other suggestions? Thanks in advance! Jim

SBS 2011 STANDARD Exchange 2010 Migration to Office 365

done

Hi
If you manually setup an outlook profile and enter in all the settings does it work?
In you local DNS you still have an autodiscover record for your local exchange server? Correct?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Exchange 2010 Migration of 200 Users/Force Archiving

Similar Messages

Maybe you are looking for