Connecting CAS Server to Mailbox Server in Exchange 2010

Currently, we are running the CAS,HUB,and Mailbox role on the same Exchange 2010 SP3 server. At some point I would like to separate this out. Should be an easy question: what command gets/sets the settings which points a CAS array to a mailbox database?
So I want CAS_SERVER1 -> DB1,DB2 and CAS_SERVER2 -> DB3,DB4

Hi,
In Exchange 2010, Outlook look for the “rcpclientaccessserver” attribute on the user’s Database to find the CAS server. You can manually set it by the following command:
Set-mailboxdatabase –rcpclientaccessserver xxx
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Owa working but outlook cant connecting to the new mailbox in Hosted exchange 2010 SP1

hi i recently join one organization they having Hosted Exchange 2010 Sp1 i created one new organization Unit and created
new MailBox but didnt give any permissions so when i try to connect to OWA then i log in and send and recive e-mails but when i try to connect to Outlook it say the name not found ...........
please help me

Hi sorry for so late respons i was on leaves .
new User not connected automatically getting the message "user name Not found " also when i try to connect manually the error message " there is problem with the security certificate. the name on the security certificate is invalid or does not match ..." also
Outlook some problem with some old Mailboxes
from Exerca i get the following errors i.e Certificate related
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
Autodiscover was tested successfully.
Additional Details
Elapsed Time: 2927 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.
Attempting to test potential Autodiscover URL https://xyz.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 417 ms.
Test Steps
Attempting to resolve the host name xyz.co.uk in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host xyz.co.uk to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server xyz.co.uk on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to test potential Autodiscover URL https://autodiscover.xyz.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Test Steps
Attempting to resolve the host name autodiscover.xyz.co.uk in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.xyz.co.uk to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 270 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.co.uk on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.
.......................... Please help me how to resolve

New mailbox move request Exchange 2010 : queued

I have deployed new Exchange 2010 server in Exchange 2003 Organization. It is simple setup one Exchange 2003 and New Exchange 2010.
I was trying to move mailbox from Exchange 2003 to 2010 and it has status of QUEUE “indefinetly”.. I have tried several mailboxes and result is the same.
Then I decided to create new database on Exchange 2010 sever. I have crate new mailbox on Exchange 2010 sever, send and receive some emails. And then try to move mailbox to new database. Same results.
I run test MSR replication and is ok.
I have increase msr LOGGING TO Maximum, no errors. I have rebooted server several times, no differences…

Hi,
Based on the description, status of mailbox move request from Exchange 2003 to Exchange 2010 is "indefinitely".
Please make sure mailbox databases in Exchange 2010 and Exchange 2003 are mounted.
Have you moved mailbox using the New-MoveRequest with the BadItemLimit and the AcceptLargeDataLoss parameters? If not, it's worth to do it again. Before you create a new move request, please check if there is any previous move request. If there is, please
clear the previous move request and then move the mailbox.
If the issue persists, please try to move mailbox to another database in Exchange 2003 and then move to Exchange 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

OOF not working for mailboxes homed on Exchange 2010 server during migration

Hi There
I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
enable OOF via exchange powershell.
Users homed on the exchange 2013 servers does not have any issues.
The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
in the meantime I'm checking if anyone else had similar issues.
Any pointers will be welcome.

Hi ,
1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
3.Then please un check the proxy settings in browsers and check the same.
4.please use the command to check the auto discover
test-outlookwebservices
Please check the below links also.
http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010 - Moving mailbox database from exchange 2010 server to another exchange 2010 server

Hi,
I have a current existing exchange server running on 2008 R2. apparently the partition that holds the mailbox database is getting full and i need to move some user mailboxes to another environment ( exchange 2010 running on 2008 R2). i transferred some users
successfully to the new location, but am not able to transfer the rest. I am getting the errors:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Erastus XXXXX
Failed
Error:
The queue in 'MBX2010_STAFF' database already contains a move request for 'Erastus XXXXX', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD
replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5 -IncludeReport | fl'. If you believe this to be an abandoned move request,
you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5'.
Exchange Management Shell command attempted:
'xxxxxxxx.co.ke/Training Department/XXXXXXX/XXXXXXX/Erastus XXXXX' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:00
AND
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01
George XXXXX
Failed
Error:
Service 'net.tcp://win-u5bjh2oamaa.xxxxxxxxx.co.ke/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exception details: MapiExceptionNoAccess (80070005): MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exchange Management Shell command attempted:
'xxxxxxxxxx.co.ke/Training Department/xxxxxx/xxxxxxx/George xxxxxxx' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:01
I have all the proper rights.
YOUR ASSISTANCE WILL BE HIGHLY APPRECIATED. THANX :)

0x80070005 is pretty standard access denied entries. I would start digging into ACLs on a handful
of mailboxes.
Is there another Admin that can give it a shot to test their permissions vs yours?
- If you find my post to be helpful, or the answer, please mark it appropriately. Thank you.
Chris Ream

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

Database mailbox grow quickly Exchange 2010 SP3

Hello.
Since we migrated from Exchange 2003 to
2010, the growth of our databse mailbox
is excessive. We have a total mailbox
size hovering around 75 GB and the size of
the database is 120 Gb.
Mailbox quotas are very
limited and 90% of users move emails
from mailbox to PST personal folders.
I get the impression that the space freed by removing
emails or move them to PST
is not claimed as White Space
and hence the excessive growth of
the DB.
I have seen that there is a fix to solve this
problem for versions prior to Exchange 2010
SP3 but the current version we have
implemented and it is with SP3.
Any idea to find out what is happening and
how to fix it?
Thanks in advance and best regards.
tzariksi

Hi.
I have reviewed the total size the mailboxes
and Dumpster with the following command:
Get-MailboxDatabase"MailboxDatabase"|Get-MailboxStatistics|SortTotalItemSize-desc|ftdisplayname,TotalItemSize,itemcount,TotalDeletedItemSize
The result is:
•Total Mailbox size(GB)->82,213
•Total Dumpster size(GB)->14,531
•Total ->97,344
The size of the DB using the command:
Get-MailboxDatabase-Status|Sort-ObjectDatabaseSize-Descending|Format-Table
Name,DatabaseSize,AvailableNewMailboxSpace
Is as follows:
Name
DatabaseSize                            AvailableNewMailboxSpace
MailboxDatabase         107.4 GB (115,302,531,072 bytes)        1.438 GB (1,544,486,912 bytes)
The actual disk size occupied
by the MailboxDatabase is->112GB
What else may be using the space in theMailboxDatabase?.
Thanks and regards.
Pedro.
tzariksi

How to run the Server Side Existing rule in Exchange 2010

Hi All,
There were requirement to create a auto forward rule for almost more than 5000 users, which we did, but the we want to apply this rules to the messages which are already in the inbox for all those users where we have created the rule.
Right now the problem what we are facing is for each individual we have to take full access to their mailbox and execute the rule first time and then it works.
this is becoming challenging for us to making this for all 5000 users. the other problem is those user are not regularly login to this mailbox, they are using some other Org mailbox, so even we can not communicate to all of them.
Q1) How to run the Server Side Command which should forcefully apply whatever rules is created for that user should execute for the messages which are already in the inbox.
Q2) or the powershell for for specific rule name, which can apply on the for all the messages which are there in the inbox.
Any help would be appriciated!
Thanks in adv champions!
Ashku

Hi Ashku,
If these 5000 users are all users in your Exchange organization, a inbox rule can be created by the following commands:
Get-Mailbox | foreach {New-InboxRule -Mailbox $_.Name -Name AutoForward -From [email protected] -ForwardTo UserB}
Based on my test, the Inbox rule created in server side also cannot work on the message that have already been in the Inbox unless users click “Run Rules Now…” in their Outlook client. And the transport rule in Exchange server only works
during the message sending process.
Therefore, there may be no feature in Exchange server side to meet your requirement.
Thanks for your understanding.
Thanks,
Winnie Liang
TechNet Community Support

Planning for CAS Array with DAG intergation on Exchange 2010

We currently have 2 Exchange servers and have plans to add 2 more servers so it will be 2 servers with DAG and 2 servers with CAS array
Here is our current setup: EX01 has HUB, CAS and MAILBOX roles EX02 has MAILBOX only with DAG configured between 2 servers.
Should I install another Exchange (EX03) with Mailbox role and remove it from EX01 and then have another EX04 to setup CAS array? What is the best practice ?
alex serdyukov

Hi,
In your case, you can install another Exchange (EX03) with Mailbox role and remove Mailbox role from EX01 and then have another server EX04 to setup CAS array.
Then you can deploy DAG using server EX02 and EX03, and add server EX01 and EX04 to CAS array.
Best regards,
Belinda Ma
TechNet Community Support

Could not open connection to the host on port 25 exchange 2010

We have exchange hosted in the company with the public IP from our ISP, now we are facing the bounce back emails from some domains
Could not be delivered because of
Server refused mail at END OF DATA - 554 5.7.1 The message from (with the subject of (RE: Schon Properties - Final Discounted Offer - Golden System.)
matches a profile the Internet community may consider spam. Please revise your message before resending.
only few domains bounce back the emails.
aslo i cannot telnet our mail server.
so what could be the issue.
please help someone to solve this issue.
Fuad

Looks like some domains you are sending to have implemented spam filters and they consider your email content to be spam. You'll need to contact them and have them set up any whitelists for your domain as needed.
http://www.faq.nuvotera.com/error%E2%80%845-7-1-the-message-from-with-the-subject-of%E2%80%84-matches-a-profile-the-internet/
As far as telnet goes make sure you are using port 25 and your static IP. Firewalls sometimes block this internally.
-- Al

Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

Hi Guys,
I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
1 Exchange server MBX role For journlaing Exchange 2010
1 CAS for internet owa access Exchange 2010
Now i will be installing exchange 2013 CAS on 2 box and MBX on 3 box
will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
will keep the Journaling server as it is will not be decomming it as of now.
My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
Please suggest on the same.
BR/Deepak

Hi TheLearner,
Thank you for your question.
Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010 could communicate
with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

A Unified Messaging server running the same version of Exchange as the Mailbox server that hosts the user's mailbox couldn't be found.

Hi Team-
we are getting below alert in Exchange 2013 on UM server
a Unified Messaging server running the same version of Exchange as the Mailbox server that hosts the user's mailbox couldn't be found.
eventID 1647
The Microsoft Exchange Unified Messaging Call Router service rejected the call for the following reason: 15505;source="Exchange 2013 server ";reason="Couldn't find a valid Unified Messaging server to redirect the call." Microsoft.Exchange.UM.UMCore.CallRejectedException:
An incoming call with ID for user was rejected because a Unified Messaging server running the same version of Exchange as the Mailbox server that hosts the user's mailbox couldn't be found.
we have exchange 2010 and Exchange 2013.
Sender of the voice mail is on the Exchange 2013 and receiver of the voice mail is on Exchange 2010
Is this not supported scenario of Exchange 2013 UM server and Exchange 2010 mailbox server
ksrugi

You cannot and should not expect Exchange 2013 UM function for mailboxes housed in Exchange 2010. And the reverse is true as well. If you want Exchange 2013 UM to function for users, their mailboxes need to be in Exchange 2013. Exchange
2013 UM should be able to redirect calls to an Exchange 2010 UM server if it detected a call was destined for a mailbox being hosted by Exchange 2010, assuming the UM servers/roles/services are within the same UM Dial Plan.

Reconnect Disconnected Mailbox Server for Exchange 2010- VBScript

Hello everyone. I am trying to run a program where a user can reconnect a disconnected mailbox through 2010 Exchange Servers.
This is an example of the method that I need except this is for 2003 servers but I am looking for 2010. If you can, please help me out.
VBScript Example
'===============================================================
' Purpose: Reconnect a Diconnected Exchange_Mailbox
' to another user object
' Change: cComputerName [string] the computer to access
' Change: cDisconnectedMbox [string] the disconnected mailbox name
' Change: cConnectTo [string] the user account to connect the mailbox to
'===============================================================
On Error Resume Next
Dim cComputerName
Dim cDisconnectedMbox
Dim cConnectTo
Dim objWMIService
Dim oDisMbox
Dim mBox
Const cWMINameSpace = "root/MicrosoftExchangeV2"
Const cWMIInstance = "Exchange_Mailbox"
cComputerName = "MyComputerNETBIOSName"
cDisconnectedMbox = "TestUserA"
cConnectTo = "TestUserB"
strWinMgmts = "winmgmts:{impersonationLevel=impersonate}!//"& _
cComputerName&"/"&cWMINameSpace
Set objWMIService = GetObject(strWinMgmts)
Set oDisMbox = objWMIService.ExecQuery("Select * from Exchange_Mailbox WHERE MailboxDisplayName = '" & cDisconnectedMbox & "'",,48)
For each mBox in oDisMbox
mBox.Reconnect cConnectTo
Wscript.Echo "Mailbox Reconnected"
Next

On Exchange 2010 you need to use the Exchange Management Shell so you need to use the connect-mailbox cmdlet see
http://technet.microsoft.com/en-us/library/bb123490(v=exchg.141).aspx
If your trying to do this from managed code then you can run that cmdlet from managed code see
http://msdn.microsoft.com/en-us/library/bb332449(v=exchg.80).aspx and
http://blogs.technet.com/b/exchange/archive/2009/11/02/3408653.aspx
Cheers
Glen

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

This is somewhat of an emergency, since Exchange is down completely for us right now.
I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
The plan was this:
Install Exchange 2013 on another server (Windows 2008R2)
Wait until everything is replicated
Remove the Exchange 2010 server from the organization
Uninstall Exchange 2010
Install Exchange 2013 on the Windows 2012 server
Wait until everything is replicated
Remove Exchange 2013 from the Windows 2008R2 server
But here is what actually happened:
Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
At step 11 of 15 (not sure what that was, though), received this error message:
Error: The following error was generated when "$error.Clear();
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
" was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.".
And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
but stays at 0%. But here is the most immediate issue:
Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
variables with variations on this error:
"...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
netsh (windows exe)
sc.exe (windows exe)
hostname (windows command that returns workstation name)
These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
argument to remove it instead.
At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

Connecting CAS Server to Mailbox Server in Exchange 2010

Similar Messages

Maybe you are looking for