Exchange 2013 migration between AD sites
Hello,
I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
Any advice on performing this migration without issues?
Thanks
Hello,
I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
Any advice on performing this migration without issues?
Thanks
Mailbox Moves are pretty seamless, so not a concern.
As far as the CAS namespaces. How are you handling that ? Load balancing between the CAS? Round Robin DNS? Or are you going to cut everything over at once and change DNS to point to the new server? Are both CAS accessible from the internet?
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Similar Messages
-
Migration Exchange 2010 to Exchange 2013 in a different site
Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server AdministratorHi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator
It is like any other Migration (Same Forest) You just need to make sure that AD is been replicated from Site A (Exchange 2010) to Site B (Exchange 2013).
No Network or replication issue between the sites. Having more than 1 DC on Site B would be good idea.
Once you have all these set, rest of the things are same.
Extend the AD Schema.
Deploy the Exchange Server 2013 CU6
Create the Cert request for 2013.
Install Cert on Exchange 2013.
Configure the Virtual Directories for Exchange 2013.
Test the Coexistence between 2010 and 2013.
Perform the Cutover from 2010 to 2013.
Test the Cutover and start the Test migration phase.
Once the test phase is fine, start the full fledge migration.
Move Mailbox and Public Folder Database.
Cheers,
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. -
Second Exchange 2013 server in remote site
Just finished migrating from 2007 to 2013 and decommissioned 2007. Exchange 2013 is running in site A with 350 mailboxes on it. However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
this site and migrating mailboxes to it. There already exists a DC & GC in both sites.
My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors. Will updating the SCP on the new exchange server to point to the SCP on the exchange
server in site A be enough to mitigate that problem? What other precautions will I need to take? Has anybody been down this road?Hi
You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
records setup correctly.
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. -
RPC error when configuring Exchange 2013 servers in 2nd site
Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you! -
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 advanceHi,
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 High availability between two sites with two servers
Hi Team,
I have a requirement to deploy exchange server 2010 between two sites. but i have limited resources to full fill this. below the summary.
2 servers in two sites
different subnets will user for two sites
Need to deploy DAG.
please let me know the considerations for this deployment.
Thank youHi - In this scenario, you would setup the following: Site 1: Exchange 2010 Multi-Role server File Share location to place File Share Witness for the DAG Site 2: Exchange 2010 Multi-Role server The above will give you 2 nodes in the primary location and
one node in the secondary location so that resources will stay in Site one. You will also need to enable DAC (Datacenter Activation Coordination) on the DAG so that the Cluster group can be managed by Exchange. Last but not least, you will want to restrict
automatic failover of resources to Site 2 by blocking that action on the Exchange server in Site 2 using 'Set-MailboxServer <servername> -DatabaseCopyAutoActivationPolicy Blocked' This will make you manually failover to site 2 and not end up with resources
there after a sudden failure or issue that is not impacting the entire site.Jason Apt Microsoft Certified Master | Exchange 2010 -
Exchange 2013 migration, disable SSLOffloading on 2010 CAS servers
We just going through the Exchange 2013 migration from Exchange 2010. I have one or two questions when following the Exchange deployment Assistant. We have HLB where the certificates and we enable SSLoffload on the CAS server. So we don't have public CA's
on our CAS 2010 servers.
So on the documentation it says to run this command, were it will disable SSLOffloading and change to Basic authentication. Will my running outlook 2010 clients start getting certificate errors and will they work as normal ?
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 14*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod
Basic -SSLOffloading $False -ExternalHostName $Exchange2013HostName -IISAuthenticationMethods NTLM, BasicWe have OA enabled on all CAS 2010 servers with NTLM authentication and SSLoffloading box checked. We have also setup our CAS2013 and is running. My question above was that if I ran that command, Will I break anything since all my users
are still on Exchange 2010 mailboxes.
Then as I mentioned, that command will do nothing as OA is already enabled on CAS 10. It would only make a change if CAS10 had OA disabled.
Where {$_.OutlookAnywhereEnabled -Eq $False}
Where {$_.OutlookAnywhereEnabled -Eq $False}
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. -
Exchange 2013 Migration in a complicated network environment
Hello everyone,
I am conducting an Exchange migration from 2007 to 2013. The client have 4 geographical site and each of those site have an Exchange CAS server on it. The sites
have also DCs on each of them.
There's two types of connection between sites one is MPLS that's 50MBPs and the other is p2p that's 2mbps. Client wants to have only 2 Exchange 2013 Server with
all the roles collocated on them and DAG between them.
I already have installed and configured DAG on the servers. One server is located in the Central data center and the other is located on a second geographical
site that also have a disaster recovery data center.
Client wants to configure the MAPI network on Exchange 2013 to use the P2P 2mbps connection and use the MPLS 50mbps connection for the replication NIC.
The problem is that both networks MPLS and P2P have the same IP subnet, same gateway e.g. (10.1.1.0/16) but a range of those IPs are configured on the router to
use the MPLS connectivity.
I have tried to add static route to the replication network to use the gateway but when trying to add a copy of a centralized database to the DAG. the DAG copies
the connection over the P2P line.
Is it possible to configure this with the same subnet or do I need to have the mpls connection on a totally different network and subnet?
I would appreciate all your suggestions and I am very sorry for my terrible explanation because I am my self confused about their network topology.
I will prepare a visio diagram of the network, IPs and everything to clear everything out.
Mohammed JHI have solved the issue, it was very simple but due to lack of knowledge about networking it got complicated. the way I have configured the replication networks between both sites was that each replication NIC on each site should have a different subnet
that configured on the MPLS network with the high speed and bandwidth. they must be different on each site.
For each replication NIC a persistent static route should be configured on Exchange server to tell the NIC where to direct traffic exactly.
After configuring the subnets on the replication NIC, I added the static routes and the replication started to work flawlessly.
This is the static route command that I run on the first machine on the first site, it tells the Replication NIC to direct traffic to the subnet network on the second site through the gateway 10.1.1.1
route -p add 10.5.1.0 MASK 255.255.0.0 10.1.1.1
On Exchange on the second site, I had to run the same command as well
route -p add 10.1.1.0 MASK 255.255.0.0 10.5.1.1
thanks everyone for the help.
Mohammed JH -
IBM Domino to Exchange 2013 Migration question
I've been tasked with looking into migrating our company of 5500+ Domino users to Exchange 2013. Currently, my Domino servers spread across the county and not all in one location. Is there a document/guide that can help me get an understanding
on what type of environment I can take my hub/spoke Domino environment to in Exchange? Any guidance would be appreciated. Thanks!hi Hoss,
I have done couple of Migrations from Domino to Exchange Migrations and pretty familiar with this. For this to happen, you have to use a third party tool like Quest or Binary Tree.
Since you said, 5500+ users, I would recommend you using one of the quest or binary tree tools to assist you with this migration. The key to the migration is the design and planning phase.
I am familiar with Quest tools and will give you as much as i know but I am sure every other tool out there is pretty similar in terms of functionality.
you have to purchase Quest licenses and for quest to be installed on your server, you have to go through Quest Professional services or a Quest approved vendor. You cannot install Quest on your own - this is a small drawback that I personally think.
While your Quest servers are being setup, you have to plan out your Exchange server design and for a 6000 user mailbox, you wont have a big of a deal. I need the hardware information that you have purchased for the Exchange servers? are you going
to go physical or virtual? I need to know the user message profile in your existing domino environment (how many emails sent/recived /size per day/per mailbox)? I also need your inputs on how many servers are you planning with Exchange 2013 in total (all roles),
Do you need single item recovery? Do you have any storage contrains? and a 100+ questions. If you get me the answers for what I asked, I am willing to help you with the design fo Exchange 2013.
Re: Domino:
What version of domino are you running? What is your max mail file size? how many mailboxes (person documents) how many mail-in databases? how is your user account provisioning currently designed? and so on. user account provisioning could be a challenge
because you have to introduce a 3rd party app like FIM or CA's User Management apps to work between your Domino and Exchange (during the time of coexistence) and there is a lot to it.
All the best!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Regards, Siva -
Exchange 2013, multiple IIS OWA sites with different authentication
Hi
I have an exchange 2013 server with Client Access and Mailbox server installed. The server has an second ip address which I have bound an additional IIS site to. The additional IIS site is named ExchangeExternalFBA.
The default web site is configured for basic and windows authentication with:
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
Then a new ECP and OWA are configured with:
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA"
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA"
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
Then I perform an iisreset.
My problem is that then when I try to access the ECP or OWA on the default website, it loads forms authentication! The ECP or OWA on the ExchangeExternalFBA web site works correctly and also loads forms authentication.
If I run...
get-owavirtualdirectory "owa (ExchangeExternalFBA)"
then it returns:
InternalAuthenticationMethods : {Basic, Ntlm,
WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
If I then run
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
and perform another iisreset then when I try to access the ECP or OWA on the default website it loads correctly. But then the forms based authentication on the ExchangeExternalFBA website can no longer log in, it does not accept the user name and password.
If I then disable and enable FBA on the ExchangeExternalFBA website then it works but forms based authentication takes over the default web site again!
Whether I perform the above from the gui or from powershell it does not make a difference, the same behaviour is observed. Changing the logontype on the FBA does not make a difference.
This has been tested on exchange 2013 cu1 and cu2.
Similar(if not identical until they get sidetracked) issue reported in http://social.technet.microsoft.com/Forums/exchange/en-US/9fcd360f-6658-4940-add7-2f13265cf86b/multiple-owa-sites-on-a-single-server-2012-with-exchange-2013-mailbox-cas.
This worked fine in outlook 2007 and 2010, why now do my virtual directories break each other?
I can reproduce the issue on a test exchange 2013 I built in dev.
Is this a bug or are you no longer meant to host different forms of authentication on a single cas?
I'm mostly interested to see if this works for other people and why it no longer seems to work in 2013, so please no questions; 'why do you want 2 different forms of authentication'.
Much appreciated, Thanks!Based off of your feedback I have run the following:
Remove-OwaVirtualDirectory "owa (ExchangeExternalFBA)"
Remove-EcpVirtualDirectory "ecp (ExchangeExternalFBA)"
iisreset
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
iisreset
After this there has been no change in behaviour. After the iisreset, forms have again hijacked the default web site and re-setting the authentication on the default web site removes the forms but breaks the ability to sign in to the forms based page on the
ExchangeExternalFBA web site again.
Note. '-Role Frontend' did not work. It showed the error:
Cannot process argument transformation on parameter 'Role'. Cannot convertvalue "frontend" to type
"Microsoft.Exchange.Management.SystemConfigurationTasks.VirtualDirectoryRole".
Error: "Unable to match the identifier name frontend to a valid enumerator name. Specify one of the following enumerator names and try again:
ClientAccess, Mailbox"
+ CategoryInfo : InvalidData: (:) [New-OwaVirtualDirectory], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-OwaVirtualDirectory
Running get-help New-OwaVirtualDirectory -detailed shows the correct usage would be '-Role ClientAccess'?
-Role <ClientAccess | Mailbox>
The Role parameter specifies the configuration that should be used
when the virtual directory is created. The following are the values
that can be used with this parameter:
* FrontEnd Configures the virtual directory for use on a Client Access
server.
* BackEnd Configures the virtual directory for use on a Mailbox server. -
Server 2012 and Exchange 2013 Migration from SBS 2011
Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
This topic first appeared in the Spiceworks CommunityI recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...
-
I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
A couple of pieces of information that may be relevant:
1. On exchange 2013, the authentication method for the internal host name is NTLM
2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
Thanks in advance for your help.Hi,
From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
For your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
https://support.microsoft.com/kb/2934750?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Exchange 2013 migration ends as Failed but the migration is OK
Hi
After Exchange 2013 SP1 I started getting this error when migration users to 2013 or within 2013.
We are now at CU5 and the problem remains.
When a migrations has come to the Synced or Successful state the ECP shows status Failed!
If you view details you see the right status. In the report you see no errors, all looks good.
So you you just synced a mailbox you have to complete the migration from PowerShell.
I see no event in the log about this.
I tried recreating the arbitration mailbox but no luck.
Is more a cosmetic problem but a bit annoying!
Anyone seen this?
Regards
RobertHi Robert,
Does the issue happen to all migrated mailboxes or just some specific mailbox?
Please click Refresh
Please use the Exchange Management Shell to display migration user statistics:
Get-MigrationUser -Identity [email protected] | FL
Get-MigrationUserStatistics -Identity TestUser@ contoso.com -IncludeReport | FL
Here is an article about Migration status report in EAC:
http://technet.microsoft.com/en-us/library/jj898491(v=exchg.150).aspx
If possible, please also collect the EAC screenshot about your issue and the commands results here without sensitive information for further analysis.
Regards,
Winnie Liang
TechNet Community Support -
Converting from InMotion Hosting to Exchange 2013 Migration
Hello everyone,
We are looking to convert our current mail service being hosted on InMotion using POP3 to our Exchange 2013 server. Is there a migration guide somewhere I could find or something to lead me in the right direction? We want to forward the mail from InMotion
to the Exchange mailboxes as well. I know this involves converting MX records and the such but I feel like something is missing in the grand scheme of things.Hi,
The migration can include:
1. Account migration.
2. Database migration.
3. Some A and MX records need to be configured.
For more details, you can either consult Inmotion support or Microsoft support below:
Inmotion Support
https://www.inmotionhosting.com/support/launch-chat/?rdid=2324923566971164486&url=http%3A//www.inmotionhosting.com/support/email/general-information/getting-started-guide-email
Microsoft Advisory Support
https://support.microsoft.com/gp/advisoryservice
Thanks,
Simon Wu
TechNet Community Support -
Linux mailserver to Exchange 2013 migration
Hi all
I have a specific question that I am hoping to get some advice on.
I have successfully installed Exchange 2013 and I am able to send email out from it.
We have a set-up whereby we have a webserver than the mx record for our domain points to, based on the incoming email (based on recipient address) it then will either forward on the mail to a linux mail server or the new Exchange server I have built.
Basically we have a problem whereby email sent from an Exchange mailbox to an internal user that does not have a mailbox is bouncing. I know why this is happening but not quite sure how to fix it. Basically I need a rule or send connector (this is what I
am not sure on) that will forward the internal email on to our linux mailserver if the mailbox is not located on the Exchange server I have built (there are reasons we will not be migrating all mailboxes so we need this functionality).
Any help greatly appreciated.
Thanks in advance!Hi George,
Great information from Exchange Queries.
Also complement some useful articles:
Send Connectors
http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
Configure Mail Flow and Client Access
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
Receive Connectors
http://technet.microsoft.com/en-us/library/aa996395(v=exchg.150).aspx
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support
Maybe you are looking for
-
For some reason or other I can't remember my password for my apple id and when I go to reset it I can't find the email they have sent me.I think they are sending it to my apple email [email protected] which I can't access as they are telling me my pa
-
LC Amount in GRN against Stock Transfer PO
Dear Friends, I have noticed that the "Amount in LC" field is not available under "Quantity" tab in display mode of MIGO for GRN made against Stock transfer PO. Hence MB51 also doesnot show any data under "Amount in LC" for report executed for 101 mo
-
Can't accept End User License Agreement
I am being prompted to accept the End User License Agreement for Adobe Reader but I don't know how to accept it. I've uninstalled and installed Reader, that didn't fix it. I'm using Chrome on my iMac Yosemite.
-
Entity EJB Relationships Architectural Question
I need to create a hierarchy of simple objects. I will call my object "Part" for simplicity. I have two Oracle tables to maintain my Part hierarchy. The first table contains the detail for the part: number and name. The second table maintains the rel
-
hi friends, In my company intra company S T O Mov type is 901. now my client want to change this ( 901 to 641) how can i acheive it??? regards raj