Exchange 2010 RPC Encyption question

Quick question. We are running Exchange 2010 SP3 RU 5 (latest and greatest). All of our CAS servers have RPC Encryption disabled. If clients are enabled for Encyrption will this encrypt traffic to the CAS servers? Question is we're
seeing issues with some of our Cisco Wan Optimizers. I just want a better understanding if only the client side (Outlook 2007/2010) is enabled does that encrypt.

Hi,
Agree with above opinion, if all cas servers have disabled RPC Encryption, Clients will not be encrypted traffic to the server regardless of whether the client encryption is enabled.
More details refer to the following articles:
RPC Encryption Required
Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
In addition,Microsoft strongly recommends you leave the encryption requirement enabled on your server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

Exchange 2010 RPC issue, "The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process"

Hi All,
this is the first time iv had to post on here on a forum since ive been doing IT but here goes.
Server background:
SBS 2011
Exchange 2010 SP3 RU6
Installed 2 years ago and has run relatively smooth since installation
Possible Cause: a recent application that had created a virtual directory in IIS.
Issue:
A user recently reported an issue with Outlook Anywhere, i did an exchange connection test and reported the following error
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3834 ms.
Fixes Tried so far
- Reg fix for ports 6001,6002,6004
- Telnet 127.0.0.1 6001 all returns expected results
- Disable RPC then Re-enable via the management console
-Ran fix my network wizard which has shown an error in compenent 3 which it fixed
Component ID #3
If the Fix My network wizard shows that component ID #3 is broken, this means that within IIS the RPC virtual directory settings are incorrect.
Continuing to fix this error within the wizard will correct the RPC virtual directory to support both Basic and NTLM authentication to this virtual directory.
Any suggestions would be great as im running out of ideas, i have thought about rebuilding outlook anywhere but unsure of the implications on an SBS

Hi,
In order to check whether it is an RPC Virtual Directory issue, you can open IE and input:
Https://mail.domain.com/RPC/RPCProxy.dll
After inputting the credential, the expected result is a blank page. If not, I means the issue resides on the RPC VD. You can try rebuilding the RPC VD for the first try.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2010 SP3 install question

Greetings! I am planning on installing the SP3 update for Exchange 2010 in preparation for a Hybrid deployment with O365. After installing the SP3 update to all Exchange servers in our environment, I was going to then install the RU8 on the servers.
Hopefully I can perform all of this during one maintenance window. I have already performed the schema update for SP3 during our most recent maintenance window.
I have been scouring the forums for any potential upgrade issues. I wanted to know if there was any concern about the RU8 update for SP3 that might affect our environment from past experience of other admins; whether it be Outlook clients (we use mostly
Outlook 2010 with some Outlook 2013) or OWA. We are currently on SP2, RU6.
Thanks in advance!

Hi,
As what Amit mentioned above, you can upgrade from Exchange 2010 SP2 RU6 to SP3 RU8, as long as this version is supported for Hybrid deployment with O365.
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
To DAGs, please consider the following conditions:
Upgrade passive servers first. Place server in maintenance mode if any monitoring applications are in use. Stop any scheduled tasks or other processes running on the DAG member or within that DAG that could adversely affected the DAG member being upgraded
or the upgrade process.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Quick Exchange 2010 Perfmon Counter question

So in the following article:
http://technet.microsoft.com/en-us/library/ee832791.aspx
Under the section where it speaks about calculating your IOPS per Mailbox Server is says to track the Perfmon Counter "MSExchange Database ==>
Instances ->Database Maintenance IO Reads/sec" to use in your calculations.
My issue is that I don't see that counter at all when pulling counters from my Exchange 2010 mailbox servers. I have "Database Maintenance
Duration" and "Database Maintenance Pages Bad Checksums" but no "Database Maintenance IO Reads/sec" under "MSExchange
Database ==> Instances"
Am I looking in the wrong spot?
Exchange 2010 SP2

Hi
Sorry, this link was kept in my Favorite years ago, I did not notice it had be removed.
After researching, I found
"It is no longer necessary to pick the correct counters for the Exchange Server Roles that are installed as this script will automatically detect the roles installed and will add the appropriate counters for each role detected."
http://archive.msdn.microsoft.com/ExPerfwiz
So on that link, you can ExPerfWiz, it is a powershell based script to help automate the collection of performance data on Exchange 2007 and Exchange 2010 servers, you can download from here
http://archive.msdn.microsoft.com/ExPerfwiz/Release/ProjectReleases.aspx?ReleaseId=5859
Hope that could help
Cheers
Zi Feng
TechNet Community Support

Exchange 2010 RPC over HTTPs failing with authentication error

Hi. I have my remote.xxx.co.uk domain and autodiscover.xxx.co.uk domain pointing to my SBS2011 server, have ports 25, 80, 443 open. The Microsoft Connectivity Analyzer fails with the below error.
Outlook will autodiscover happily on the local network, and works fine. Phones etc do too.
Outlook at a remote VPN connected site won't connect through autodiscover, but will if you do it manually (ignoring the RPC Proxy settings). Everything works for a while, but then I guess outlook decides to use autodiscover to complete all the connection
details, and then these machines can no longer connect to exchange as I guess they decide the speed is too slow and try to connect using RPC instead.
Users can access OWA happily, and activesync is working on phones etc.
SSL cert is a wildcard type on my domain, and certs are installed - all green and happy when visiting OWA on both remote.xxxxx.co.uk and autodiscover.xxxxx.co.uk domains.
I cannot work out why I have an authentication error for RPC?
Any advice would be great!
Testing HTTP Authentication Methods for URL https://remote.xxxxx.co.uk/rpc/rpcproxy.dll?xxxxxx.xxxxxx.local:6002.
The HTTP authentication test failed.
Additional Details
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()
Elapsed Time: 100065 ms

Hi.
To update.
I tried to recreate the virtual directories in the Exchange Management Console, using the recreate links and via the shell, but while they were recreated, they did not function as they should due to issues in the meta database.
I then found the following which worked.
Looking at the ActiveSync virtual directories, when running the below command, the result showed the directory was there, so I then knew to delete it.
In EMS I ran,
=> Ran "$site = [ADSI]"IIS://localhost/W3SVC/1/Root/Microsoft-Server-ActiveSync""
Result: Carriage return.
=> Ran "$site"
Result:
distinguishedName:
Path: {C:\Program Files\Microsoft\ExchangeServer\V14\Client Access\Sync}
In EMS I then ran,
=> Ran "$Site = [ADSI]"IIS://localhost/W3SVC/1/Root""
Result: Carriage return.
=> Ran "$site.Delete("IIsWebVirtualDir","Microsoft-Server-ActiveSync")"
Result: Carriage return.
=> Ran "$site.SetInfo()"
Result: Carriage return.
=> Ran "$site"
Result: Carriage return.
=> Ran "iisreset"
I then recreated the virtual directories.
In EMS I ran,
=> Ran "New-ActiveSyncVirtualDirectory -WebSiteName "Default Web Site""
Results: Successfully recreated.
=> Ran "iisreset"
I am not sure exactly, but I did this for multiple virtual directories, and everything came to life just as it should.

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010 SP3 Rollup Update 6

Our Exchange environment is currently on Exchange 2010 SP3 RU3 and the Forefront Protection 2010 for Exchange server version is 11.0.713.0 (Rollup 3).
We planning to upgrade Exchange servers and install Exchange 2010 SP3 RU6, question which I have is it Mandatory to upgrade the Forefront Protection 2010 for Exchange server version is 11.0.727.0 (Rollup 4) before we install Exchange 2010 SP3 RU6 on the
Exchange servers.
Thanks,
AJ

Thanks Adam for the prompt response and yes I recall these cmdlets to disable and there is a similar cmdlet to enable it. Also after Exchange 2010 SP2 after some RU there is no need to disable FPE before installing RU however it is recommended to disable
it.
If you refer the comments section mentioned in the blog below it talks about it:-
http://blogs.technet.com/b/exchange/archive/2014/05/27/released-update-rollup-6-for-exchange-2010-service-pack-3.aspx
If you read the comment posted by James Knoch posted on this blog which is as below,
SP3 & the Rollup Updates are not supposed to require you to disable Forefront anymore, but it doesn't hurt to be safe and disable/enable it anyways. Make sure you are running Forefront Rollup 4 (http://support.microsoft.com/kb/2619883)
& the latest security update (http://www.microsoft.com/en-us/download/details.aspx?id=41836).
Above stated confused me a bit, is it mandatory to upgrade Forefront or it is NOT.
Thanks,
AJ

ISA 2006 publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation

Hi,
I have two Exchange 2010 Sp1 CAS with Windows Network Loadbalancing. I set up an alternate Serviceaccount and mapped the http,ExchangeMDB,PRF and ExchangeAB SPNs.
Then i published the Exchange Services via ISA 2006. OWA is working using Internet -> via NTLM -> ISA(webmail.domain.com) -> via KCD -> CAS-Array(ex2010.domain.com)
I tried the same with Outlook Anywhere (RPC over HTTP) without success.
Authentication to the ISA via NTLM works fine, but i think the isa server cannot delegate the Credentials successfully to the CAS-Server.
The ISA Log looks like:
Allowed Connection ISA 24.11.2011 15:50:40
Log type: Web Proxy (Reverse)
Status: 403 Forbidden
Rule: Exchange 2010 RPC
Source: Internal (172.16.251.33)
Destination: (172.18.10.182:443)
Request: RPC_OUT_DATA
http://webmail.domain.com/rpc/rpcproxy.dll?ex2010.domain.com:6001
Filter information: Req ID: 108b89d8; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: https
So i always get a 403 Forbidden from the CAS.
I the IIS logfile from the cas server i see this entry:
2011-11-24 15:51:37 172.18.10.182 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.domain.com:6001 443 - <ISA IP> MSRPC 401 1 2148074254 203
I use the same Listener for OWA and Outlook Anywhere. Authentication Methods are Basic and Integrated. I forward the request to a webfarm which exists of the two physical CAS. Internal Site Name is set to the NLB name ex2010.domain.com, SPN is set to http/ex2010.domain.com
Thanks for your support

Hi, i ran into the same Problem.
the steps above solved mine too (Creating a custom AppPool which runs under LocalSystem).
I wonder why they included only the Script: convertoabtovdir.ps1
http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/thread/dc24ccd3-378a-47cc-bbbf-48236f8fe5b0
Ist this a supported configuration (changing AppPool of RPC)?

Exhcange 2003 to Exchange 2013 Through Exchange 2010

Hello everyone and thanks for your help in advance. I have been tasked with the upgrade of an exchange 2003 server to Exchange 2013. After reviewing the lack of upgrade paths directly to 2013, I think the best path would be to transition through
2010. The domain controller is also 2003. If I understand the process correctly, I should join the new Exchange box to the current domain. Then install Exchange 2010. My questions are:
1. Is installation as simple as the way I described?
2. After installation, is there a way to port the Exchange data from the old machine to the new machine without taking down the Exchange 2003 machine?
Unfortunately, I have only a very basic understanding of Exchange, so I need to take this in small steps. Any help would be appreciated.

Hi Kmcnet,
Base on my experience , if only a small number of mailboxes, the most convenient way is to export/import PST files.
I recommend you consider using the following method to upgrade the exchange to 2013:
1.Export all the users mailbox contents into a PST since its only 35 users
2.After you confirm the exported pst are fine remove the exchange 2003 server
3.Install Exchange 2013 in your environment and create new mailboxes for 35 users
4.Import the pst to their new mailboxes
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

Unity 5.0(1) with Exchange 2010

According to the following link, Unity 5.0 supports Exchange 2010 as the partner Exchange server.
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html#wp47622
However, when I get to step 14 of this document (installing ExchangeMapiCdo.exe) I get an error saying it can't be installed with this version of Exchange.
I was just wondering if anyone elsel had tried to run Exchange 2010 with Unity 5.0 and if so, how you were able to get it to work. I followed all the steps in this document and everything seemed to be working until this step.

3 things:
1) You should get a TAC case going, if you haven't already.
2) For Unity 5x, ES83 was replaced by ES85 (which was yanked off the download site almost like a ghost in the night) and now there is ES86. You may want to read up on what is fixed here in this ES.
3) I think you may have your service account mailboxes homed in the wrong place. If you note there, is a section for where to put the mailbox for the UnityMsgStoreSvc. Excerpts I'm looking at are:
Adding One or More Exchange 2010 Servers to an Existing Cisco Unity 7.0 and/or 5.0 Installation
Step 14 On the Cisco Unity server, install ExchangeMapiCdo.exe, which you downloaded in Step 4.
Step 15 On the Cisco Unity server, install the version of the Permissions wizard that you downloaded in Step 2.
Step 16 Run the Permissions wizard, and select the Exchange 2010 message stores in which mailboxes for Cisco Unity subscribers will be homed.
Step 17 At the end of the Permissions wizard, on the You Have Completed the Cisco Unity Permissions Wizard page, click Granting Microsoft Exchange Administrator Rights, and do the procedure in the Help file to add the installation and directory services accounts to the Exchange 2010 Organization Management role group.
Step 18 Restart the Cisco Unity server.
Step 19 Move or create a mailbox for the Cisco Unity message store services account (typically UnityMsgStoreSvc), as applicable:
Exchange 2003 or Exchange 2007
mailbox already exists
Move the mailbox for the account to Exchange 2010.
No mailbox
Create a mailbox for the account in Exchange 2010.
Step 20 Remove the Exchange 2010 RPC limit for the message store services account by creating and applying a new mailbox policy to the message store services account:
a. Open an Exchange 2010 Management Shell window.
b. Create a new policy with unlimited RPC connections, for example:
new-throttlingpolicy -name "Unity Exchange 2010 Policy" -RCAMaxConcurrency $null
c. Apply the new policy to the message store services account, for example:
set-mailbox -identity "UnityMsgStoreSvc" -throttlingpolicy "Unity Exchange 2010 Policy"
d. Confirm that the mailbox is using the new policy, for example:
get-mailbox -identity "UnityMsgStoreSvc" | fl | findstr "Throttling Policy"
e. If you have more than one Cisco Unity server: Repeat Step c and Step d for every message store services account in the forest.
We recommend that you apply the policy to all message store service accounts, even the accounts for Cisco Unity servers for which you do not currently intend to home subscriber mailboxes in Exchange 2010 message stores. Applying the policy does not affect Cisco Unity performance, and it ensures that you will not encounter problems if you later move mailboxes to an Exchange 2010 server.
f. On each Exchange 2010 server with the CAS role, restart the Microsoft Exchange RPC Client Access service.
Personally, I would make sure you have all of these items down to a tee because, IMO, there is likely something that went astray in the install/backout/fix process.
Hailely

Upgrade From Exchange 2010 SP1 to SP3 - Schema Upgrade Question

Hello,
We're currently running Exchange 2010 SP1 in our environment and want to upgrade to SP3. I just had a couple of questions related to preparing AD for this new SP that I was hoping that someone could answer.
Setup
We have a single forest with two domains within it (A and B for example). The schema master is in Domain A but this domain doesn't contain any Exchange 2010 servers. Domain B contains our 2010 CAS and Mailbox servers.
Both domains have Windows 2003 SP2 domain controllers.
I understand that before I proceed with the upgrade to SP3, I first need to update the AD schema on our schema master. I was planning on doing the following :
Log onto an existing Windows 2008 R2 64 bit "member" server in domain A (containing the schema master) with an account which is a member of the Schema Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareAD.
Do I need to also run SETUP.EXE /PrepareDomain on domain A as well or does the /PrepareAD sort this out ?
I was then going to turn my attention to domain B (which contains the 2010 CAS and Mailbox servers) and do the following :
Log onto an existing Windows 2008 R2 64 bit 2010 Mailbox server with an account which is a member of the Domain Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareDomain
Is this the correct procedure to follow ? I assume that I can then go ahead and start to upgrade the Exchange 2010 SP1 servers in the following sequence :
CAS\HUB Server(s)
Mailbox Server(s).
Clarification on the AD upgrade steps would be appreciated.
Thanks
Mark

This has all the info you need:
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Prepare Active Directory and Domains
and
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
Note: There is no harm in simply running setup/PrepareAllDomains.
You should break out each Prep step since you have multiple domains:
setup/PrepareSchema
setup /PrepareAD
setup /PrepareAllDomains
you can run all of these from the same DC you run the setup/PrepareSchema step!
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
Current Exchange Server details:
Exchange 2010 Standard
Version: 14.0 (Build 639.21) - from Exchange Management Console
Version: 14.0.702.4000 - from Outook client
Active Directory forest and domain levels: Windows 2008 R2 native
The questions I have are:
1. Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
2. Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
3. Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

Hi,
Here are my answers you can refer to:
1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
And I check my version from both EMC and Outlook client. It’s same.
2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Catalyst SLB - Exchange 2010 CAS RPC

Hi.
We're currently testing out SLB for load balancing a pair of Exchange 2010 CAS servers. The config seems straightforward enough for single port services like 'Outlook Anywhere' or 'Outlook Web Access' (all on https).
Does anyone have real life experience with getting straight MAPI Outlook load balancing to work? According to Microsoft, there's only 3 ports to be concerned with - endpoint mapper, rpc.clientaccess, and address.book. I've got the latter two set for static across both of these servers, and have 3 appropriate vservers in place pointing to the serverfarm, but a capture shows the process getting hung up on tcp135. It's as if whatever server the endpoint request is landing on doesn't know what to do with the request.
Thanks in advance for any replies.

Hello Jay!
Take a look at this doc:
http://www.cisco.com/en/US/docs/solutions/Verticals/mstdcmsftex.html#wp609677
RPC requires source ip sticky in order to operate correctly through a loadbalancer. In the doc, they also walk through doing RPC over http/https - however, I have seen configurations where ACE is not L5-L7 that use RPC on port 135 as a L4 rule with sticky and it appears to work ok.
Regards,
Chris Higgins

Exchange 2010 to 2013 Migration Question

Hi Folks,
This is where I'm at: We have 2 Exchange 2010 servers (both multi role) and I was given 4 VM's for exchange 2013. I just completed installing Exchange on the four 2013 VM's (2 dedicated CAS and 2 dedicated MBX) and applied SP1. I documented all
of the 2010 server config info (i.e. all the URL's for the namespaces, etc). We have a hardware NLB and a MacAfee host in the DMZ where all inbound/outbound email routes to check for AV/Spam. My question is, what are my next steps that
take place so that I'm truly in co-existence mode? I'm assuming I want to make the 2013 servers primary now so that all mail routes to/from them and all client connections are made to them? Could someone point me in the right direction maybe
to an article on what my next steps are? I want to get everything cut over while in co-existence so that I can start moving mailboxes. Thanks a lot !

Exchange Server Deployment Assistant is good starting point:
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e
Upgrade from Exchange 2010 to Exchange 2013:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
http://msexchangeguru.com/2013/05/10/exchange2013-migration/
http://www.petenetlive.com/KB/Article/0000788.htm
Below is high level migration plan:
1. Update active directory schema for exchange 2010 sp3.
2. Install Exchange 2010 SP3 and rollup updates on existing servers.
3. Update active directory schema for exchange 2013 CU3.
4. Install and configure new Exchange 2013 CU3 servers.
5. Install public SSL Certificate.
6. Configure Web URL's for Exchange 2013 servers.
7. Configuration Hardware Load Balancer for:
a) High availability of Client Access roles.
b) Reverse Proxy for outlook web app.
8. Create mailbox databases and configure database copies for the corresponding DAG.
9. Test High Availability environment.
10. Test mail flow to & from internet/internally for all locations.
11. Test BlackBerry device connectivity with Exchange 2013 environment (if nay)
12. Test migrate mailbox from Exchange 2010 to Exchange 2013.
13. Test Outlook & OWA connectivity for migrated test mailbox.
14. Validate new Exchange 2013 environment.
15. Pilot mailboxes migration from Exchange 2010 to Exchange 2013.
16. Migrate mailboxes from Exchange 2010 to Exchange 2013.
17. Migrate Public Folders from Exchange 2010 to Exchange 2013
18. Dismount & stop Exchange 2010 services on all servers for few days before decommissioning of Exchange 2010 servers.
19. Decommission Exchange 2010 servers gracefully.
If this will help then please mark it as answer...thanks
Best of luck!
Liaqat

Exchange Server 2010 - RPC

Hi there,
I have Microsoft Exchange 2010 SP3 RU8 installed on Windows Server 2008 R2 x64. This is all running from one box (DC, Exchange, File & Print etc). I am in the process of ordering a separate server to run Exchange.
Also run Symantec backup Exec 2014 (fully patched).
Hardware spec of server is:
HP ProLiant ML350 G6
2 x Intel Xeon 2.67GHz 6 Cores - 12 logical processors
36GB RAM
Our end users use Office 2010 and Office 2013 to connect to Exchange from primarily Windows 7 systems (x86 and x64)
We have a lot of connectivity issues where Outlook will disconnect and then reconnect. Sometimes the reconnection takes a few seconds, at other times you need to kill the Outlook process and reload Outlook.
If I RDP onto our server, there is a notification stating:
Visual Studio Just-In-Time Debugger
An unhandled exception ('CrashNowException') occurred in Microsoft.Exchange.RpcClientAccess.Service.exe. It will then ask if I wish to debug.
If I say yes, then Visual studio states 'Invalid license data. Reinstall is required.
Finally, the following event is logged at the same time:
System
Provider
[ Name]
Service Control Manager
[ Guid]
{555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName]
Service Control Manager
EventID
7031
[ Qualifiers]
49152
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x8080000000000000
TimeCreated
[ SystemTime]
2014-12-11T10:51:15.748585500Z
EventRecordID
371034
Correlation
Execution
[ ProcessID]
640
[ ThreadID]
12572
Channel
System
Computer
IMASSDC.imassgroup.local
Security
EventData
param1
Microsoft Exchange RPC Client Access
param2
1
param3
5000
param4
1
param5
Restart the service
Any help would be gratefully received!

Remove CU8. Its been retracted my Microsoft.
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 RPC Encyption question

Similar Messages

Maybe you are looking for