I am migrating from Exchange 2007 to 2013. I would like to know is it possible to move a users mailbox (from 2007 to 2013) while they are working (during business hours)? Will they still have access to their mailbox during the move?
Thanks
WWT IT
I am migrating from Exchange 2007 to 2013. I would like to know is it possible to move a users mailbox (from 2007 to 2013) while they are working (during business hours)? Will they still have access to their mailbox during the move?
Thanks
WWT IT
Hi
So far this has driven me crazy. I cannot seem to get this to work. I am going to try and explain the situation fully. What we have is a hosted Exchange environment where we have multiple tenants with their own domains. We have a SSL certificate for our own domain domain.com. It has the following domain names linked to it:
webmail.domain.com (Primary)
autodiscover.domain.com (SAN)
mail.domain.com (SAN)
We have multiple tenants with each a unique domain (i.e. tenant.com). We have setup CNAME records for this domains so that they point to our HTTP redirection website which in turn
redirects them to our autodiscover website (= autodiscover.domain.com). This is to avoid having to buy an SSL certificate with several SAN hostnames. Our domain domain.local or domain.com (= externally) also hosts a series of other servers including terminal
servers which are tenants/clients use.
The autodiscovery service works externally (which means devices that are not within our domain.local domain). It is able to use the autodiscover service for i.e. autodiscover.tenant.com Internally it does not work for some strange reason. It is able to reach
the redirect website and it is able to get to the right web server hosting the autodiscover website but it fails when it tries to find the hostname autodiscover.domain.com in the SSL certificate webmail.domain.com. Even though the hostname autodiscover.domain.com
is included in the SAN. It says that they can't validate the certificate name. Externally it is able to find this and validate the certificate but not internally for some strange reason. Why would this be?
Thanks again for all your help. It is much appreciated.
Daniel
Hi,
We are in process of migrating from Exchange 2007 to Exchange 2013 Servers.
To meet the migration requirements we have changed the standard single name SSL certificate with UCC Certificate having multiple SAN values using the exchange 2013 EAC wizard. Later on we applied the same certificate to both Exchange 2013 and 2007 CAS servers.
Outlook Anywhere was enabled since long on exchange 2007 servers and was working fine till we made the certificate change. After we make the change of certificate given were the error message we started encountering:
Another change which we noticed were of Domain Controllers names in the same AD site as exchange getting added to VALID PORTS key under given HASH:
HKLM\Software\Microsoft\RPC\RPCProxy
As per my understanding Valid ports entry is populated with all the mailbox servers in organization only until unless we define DC there, which we never did until now. I can also see values for Exchange 2013 mailbox server there.
And now since Valid ports entry contains reference for domain controller i have to made following registry entry on my domain controllers to make it work :
On the Global Catalog servers: a REG_MULTI_SZ entry needs to be created on each GC named NSPI interface protocol sequences at HKLM\System\CCS\Services\NTDS\Parameters\ and the value set to ncacn_http:6004
I have tried modifying the Valid Ports entry manually and removing the domain controllers reference from there but then my Outlook Anywhere doesn't work anymore. Yes i know that RPCConfigurator again populate the entry every 15 minutes and i can turn it off,i have tried that but no luck.
Result of the above change now my CAS is directly speaking for my domain controllers which earlier mailbox server was doing through DSPROXY.
Can anyone suggest me what is happening wrong here...given are the environment details:
2 CAS +HUB Exchange 2007 SP3 RU13 server on windows 2003 R2
Exchange 2007 Mailbox Server SP3 RU13 SCC on Windows 2003 R2
Exchange 2013 CU5 CAS + Mailbox Server on Windows 2012 R2
Windows 2003 AD with mix of 2008R2 DC.
Regards,
Vishal Malhan
I have 3 AD forests, ForestA, ForestB, and ForestC. Each forest has Exchange 2010 with mailboxes and the associated user accounts for those mailboxes in that same forest. My goal is to move all the mailboxes to ForestC (user accounts will still live in ForestA and ForestB, just mailboxes move to forestC).
I would like to know the following migration path is possible:
1. Configure AD synchronization between ForestA and ForestC using the free Microsoft tool (IIFP?), migrate the mailboxes, and decommission Exchange in ForestA (AD user accounts that "own" those mailboxes will still stay in forest A).
2. Remove AD synchronization between ForestA and ForestC
3. Configure AD synchronization between ForestB and ForestC using the free Microsoft tool (IIFP?), migrate the mailboxes, and decommission Exchange in ForestB (AD user accounts that "own" those mailboxes will still stay in forest B).
4. Remove AD synchronization between ForestA and ForestC.
Some questions, thanks in advance for your help:
1. Is this possible?
2. Is this the best way to do it?
3. Can this be done with the free directory synchronization tool for Microsoft instead of buying the full Forefront Identity Manager tool?
4. Do I even need directory synchronization for this?
Thanks!
Hi, have a successful federation configured between Exchange 2010 SP3 (latest Roll up) and Office 365. This is to allow free/busy lookups during various migration stages (this is not Exchange Hybrid). Autodiscover works well and all functions work ok.
On-premise users can see cloud users free/busy
Cloud users cannot see on-premise users free/busy.
All local based free/busy works on-premise and in the cloud.
The Exchange Connectivity tool returns the below error from all accounts, this is the only error:
(A wildcard certificate is in use and am wondering if this could be contributing to the problem as I have seen this once before)
![]() | Attempting to send an Autodiscover POST request to potential Autodiscover URLs. | ||||||||||||||
Autodiscover settings weren't obtained when the Autodiscover POST request was sent. | |||||||||||||||
| |||||||||||||||
|
Any help or guidance would be appreciated as this is the only error we receive now and everything else works.
Kind Regards, Antonio.
I seem to be getting this error when selecting the public folder in mfcmapi. I'm using the Feb 2014 release of mfcmapi.
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function CallOpenMsgStore( lpMAPISession, (ULONG_PTR)m_hWnd, lpEntryID, ulFlags, (LPMDB*)lppMAPIProp)
File MainDlg.cpp
Line 437
I can access the private mailbox without issue using mfcmapi, but the public folders I'm not able to. This problem is causing my backup software not to do document level backups. So I need to resolve this issue.
Also, if I create another user and give them the same access as administrator, the new user cannot access both the private mailbox nor the public mailbox when using mfcmapi so it must be a rights issue, but I can't find where it is!
Any idea's would be appreciated.
Thanks
Hi Guys,
I wanted to migrate from exchange 2007 to 2013.
How can migrate my existing 2007 CCR ( 2 HUB/2 Mailbox) environment to exchange 2013.
Please send me the steps & what do need to take care while doing this step of migration?
Regards
Arshad Shaikh
Hello
I have a new domain with Exchange 2010 server. I plan to join users to this domain but would like to know the best plan in moving the existing Exchange 2003 mailboxes over. Can I just import the PST files into their new Exhaneg 2010 mailboxes or is there a better easier solution?
Thank you
I followed the steps linked below, or tried to but there is no Message Trace tab in Exchange 2013 administrator panel
I can not send any outgoing mail VIA the internet on a new install
port 25 is blocked by my ISP so I changed it to port 26
ALL send and receive connectors are created and appear correct per all the KB's I have read
I want to see a message trace to find out exactly where the send is failing.
Please help me save my sanity!!! :)
David Sheetz MCP
Hello,
Domain A - Source domain with Exchange Mailboxes and AD account
Domain B - Target domain which will host only mailbox (Linked). AD account will remain in Domain A.
If I have an existing "Mail User" in Domain B with a matching External SMTP address of a user mailbox which is to be moved from Domain A I find that the target address is not set correctly when running the following preparemoverequest.ps1 script.
prepare-moverequest.ps1 -remoteforestdomaincontroller sourcedc.source.local -remoteforestcredential $remotecredentials -localforestdomaincontroller targetdc.target.local -localforestcredential $localcredentials -targetmailuserou "ou=migrated,dc=target,dc=local" -verbose -identity testuser -mailboxdeliverydomain source.ex.local -linkedmailuser -overwritelocalobject -uselocalobject
I specify "-mailboxdeliverydomain" to set the required target address but this is not set and the targetaddress remains the same.
I guess I could workaround this by scripting the change but I wonder why it does not set the target address as I have specified. Note if a Mail User does not already exist the script correctly sets the target address to the domain specified in -mailboxdeliverydomain.
In addition after the mailbox is moved the mailbox is set to a User Mailbox and not linked mailbox. In the preparemoverequest I specify the -linkedmailuser switch and disable the AD account for the mail user in the source domain. This can be fixed after the mailbox move by running the following command but I wonder why this is happening?
set-user -id user1 -linkedmasteraccount source\user1 -linkeddomaincontroller sourcedc.source.local -linkedcredential(get-credential)
Many Thanks
Mark
Greetings,
In the Microsoft documentation says:
You can migrate a maximum of 2,000 mailboxes from your on-premises Exchange organization to Exchange Online using a cutover migration. This migration method only moves mailboxes,
mail users, mail contacts, and mail-enabled groups.
But in the EAC migration console when I select cutover migration it says the limit is 1000 mailboxes
I need to validate if the limit is 2000 mailboxes or 1000, and also if I can migrate more than 1000 mailboxers without issues even when EAC says the maximum is 1000.
Thanks in advance for the help!
Hi Guys,
Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.
step by step docs will be more helpful to achieve this goal..
Regards,
Aanand Singh
Hi,
we are currently in the progress of migrating more and more customers to Exchange 2013. Now there is a limit for large Items within public folders. We do know that we have large items and it is OK to wait for the replication to be done but how can we also migrate those large items?
For instance within the public folder Migration-Request log we find:
15.06.2014 22:28:37 [EXCHANGE] A large item was encountered: Item (IPM.Note) Subject:"MESSAGESUBJECT",
Size: 22.69 MB (23,795,978 bytes), Folder:"PF Folder Name"
Now I'm aware of the switch -LargeItemLimit but with that we will loose those large items. I haven't found any switch to enable the move of those large items - anyone an idea to also get those items moved to modern public folders?
Thanks!
Peter Forster | MVP Virtual Machine 2002-2011 | Austria |
We have an internal help desk app that needs to use POP3 to send acknowledgements. Everything worked fine with the previous Exchange 2010 server, but I am getting "Connection reset" from the help desk app and unexpected terminations (0x800CCC0F) from an Outlook Express client I am using to test this scenario.
The two POP3 services: the Microsoft Exchange POP3 service and the Microsoft Exchange POP3 Backend services are running.
My Test-PpoConnectivity returns this:
RunspaceId : 4d16307d-e2e0-4a98-b69d-f05d1a778351
Name : 1
ProtocolName : POP3
MaxCommandSize : 512
MessageRetrievalSortOrder : Ascending
UnencryptedOrTLSBindings : {0.0.0.0:110, [::]:110}
SSLBindings : {0.0.0.0:995, [::]:995}
InternalConnectionSettings : {Mail.WTI.LOCAL:995:SSL, Mail.WTI.LOCAL:110:TLS}
ExternalConnectionSettings : {}
X509CertificateName : Mail
Banner : The Microsoft Exchange POP3 service is ready.
LoginType : PlainTextLogin
AuthenticatedConnectionTimeout : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections : 2147483647
MaxConnectionFromSingleIP : 2147483647
MaxConnectionsPerUser : 16
MessageRetrievalMimeFormat : BestBodyFormat
ProxyTargetPort : 9955
CalendarItemRetrievalOption : iCalendar
OwaServerUrl :
EnableExactRFC822Size : False
LiveIdBasicAuthReplacement : False
SuppressReadReceipt : False
ProtocolLogEnabled : False
EnforceCertificateErrors : False
LogFileLocation : C:\Program Files\Microsoft\Exchange Server\V15\Lo
LogFileRollOverSettings : Daily
LogPerFileSizeQuota : 0 B (0 bytes)
ExtendedProtectionPolicy : None
EnableGSSAPIAndNTLMAuth : True
Server : MAIL
I need some help regarding what might be wrong.
Thanks!
Our Exchange stopped working after I made some changes to the Remote access and the VPN Connection.
When i try to Open exchange management console I get his error:
[<var style="color:#333333;font-family:'Segoe UI', Arial, Verdana, Tahoma, sans-serif;font-size:13px;line-height:normal;background-color:#f5f5f5;"><server name></var>] Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service.
I have had problems with myexchange bindings disappearing after the server was rebooted, and I did reboot the server when making changes to the VPN setup.
MY bindings for Exchange back end are:
http port 80 ip address *
httpsPort 443ip address *
Yes SSL and ignore
My MY bindings for Default web site are:
http port 80 ip address 192.168.0.19 (Servers IP address)
httpsPort 443ip address 192.168.0.19 (Servers IP address)
Yes SSL and ignore
I have tryed this but it did not help and I turned SSL back on. With SSL turned off I get this error.
http://www.exchangedictionary.com/articles/winrm-client-received-an-http-status-code-of-403-when-opening-emc-ems
The WinRM client tried to use Kerberos authentication mechanism, but the destination computer (ServerName.domain.local:80)
I have turned SSL back on for PowerShell
I can't access OWA or exchange management console.
Help ?