Exchange Load Generator 2013 ActiveSync usage

Exchange Load generator 2013 is announced as supporting ActiveSync. In the modules directory there is a Microsoft.Exchange.Swordfish.Extensions.ActiveSync dll.
I'm looking to find any documentation about how to set this. I am about to conduct a test with a large rate of ActiveSync and need to know how I can specify this. There's nothing I can find in the supplied word document.

Just between you and me, I wouldn't get that clever with LoadGen. It's a great tool for generating transactions primarily for testing disk subsystems, but it's really time consuming to get it configured for testing the various protocols.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Exchange Load Generator 2013 "well known" profiles

We are about to start testing Exchange 2013 implementation in new centralised configuration. We have figures for current user behaviour and need to ensure system can support expected workload.
Cannot find accurate documentation that describes what's in the 'well-known' profiles for Exchange load generator 2013. In previous versions, there were 'light', 'medium', 'heavy' and 'extraheavy' profiles that were totally defined within Loadgen.
The only references I can find are in the Exchange Load Generator word document that encourages the use of these without defining any of them.
The only sample I can find is in the profiles directory where there is how-to.txt that has an example of a customized MailboxStoreProfile with WellKnownProfileType "150M".

Like I said in my response to your other post in this thread, I wouldn't try to be too clever with this tool. Tune the parameters to get the number of IOPS you want in your disk subsystem, and then measure the performance. If you can get the
required I/O performance, i.e., 10ms maximum average log write latency and 20ms maximum average database read latency with peaks not exceeding 100ms, while sustaining the required number of IOPS, your storage subsystem is good.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Problem with public folder initialization on exchange load generator 2010

hi,
we need to make some stress charge for a migration between 2010 and 2013. Before that we need to populate our exchange 2010 lab with full mailbox and public folders. So we tried Exchange load generator 2010 for this task ( initialization only).
Loadgen did well for the mailbox but we have some problems with the public folders. we have an empty public folder database and the user we run loadgen with has organization admin and public folder management right. the problem is that when we run this command
(for initializing public folder only, mailbox's done) :
loadgencmd.exe /p /c config.xml /add trace.log
IT create only one public folder with the user we run loadgen with, and 5-8 objects inside. We need that It create a public folder for each users it created before. Maybe we do not understand loadgen
correctly...

I found my solution :
customize the <PublicStoreProfile> section in the configuration file as follows:
<PublicStoreProfile>
    <MessageFiles />
    <TopLevelFolderCount>1</TopLevelFolderCount>
    <NonTopLevelFolderCount>1</NonTopLevelFolderCount>
    <MinimumFolderDepth>1</MinimumFolderDepth>
    <AverageFolderDepth>2</AverageFolderDepth>
    <MaximumFolderDepth>3</MaximumFolderDepth>
    <MinimumMessageCount>5</MinimumMessageCount>
    <AverageMessageCount>10</AverageMessageCount>
    <MaximumMessageCount>15</MaximumMessageCount>
    <UseOrdinalFolderName>false</UseOrdinalFolderName>
</PublicStoreProfile>
Simply put differents values for each variables.

Exchange 2010 to 2013 Activesync migration

Hey guys got a question, if i'm doing a migration from 2010 to 2013 and i have activesync policies on 2010, will a migrated user still adhere to these policies or do should i create the polcies on 2013 as well before migrated users?
also i've noticed some users arent getting the policies i created, they all have the same phone, brand new from the company, but some mobiles are getting the policy and some others are getting email but the policies just isnt being applied to the phone, is
this a flaw of activesync?

I'm not really sure about your second question. Hopefully someone else can help on that one.
The only things I can think of would be to make sure that ActiveSync is enabled for those users, and that the policy is applied to their mailbox.
You could run the Test-ActiveSyncConnectivity command and use the
Remote Connectivity Analyzer tool to get more information
Test-ActiveSyncConnectivity
Connectivity Analyzer

HP Load Runner: CPU usage for this load generator has exceeded 80%

Recently I have downloaded LR 12.1 and installed. Observed error CPU usage for this load generator has exceeded 80% when executing the test with 5 user load using AJAX Trulcient IE script. For each virtual user in the script one TcWebIELauncher.exe hads been initiated and running during the test execution. Each TcWebIELauncher.exe instance is taking min 14% CPU utilization and CPU utilization for 5 users is around 75% at the time of test execution. What is the reason behind this high CPU utilization for this less user load?. Please suggest how to handle and fix the issue.
regards,
Sreekanth

You can download Trail version of Loadrunner from HP site. That's true. all HP testing tools products are license based.
i) If you want to use for SAP applications, you need to have SAP protocals (SAP GUI and SAP WEB). So how this licenses works is, if you want to buy 50 Vusers for SAP it cost you around $ 32k and it depends on company discount. so you need to work with HP Sales team to get the quotation then based on no of Vusers and you can procure it.
ii) As for as i know, there is no HP LR integration with Solution Manager.
let me know if you have any questions.

ActiveSync in Exchange 2007 and 2013 Coexistence

Hi,
I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
autodiscover works well for users on both 2007 and 2013
I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
I have A records configured for both names on my public DNS and internal DNS
THE ISSUES
testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
Existing users on exch2007 can no longer receive mails on their mobile devices
URLs
Exchange 2007
Exchange 2013
Internal owa
mydomain.com/owa
mail.mydomain/owa
External owa
legacy.mydomain.com/owa
mail.mydomain.com/owa
AutoDiscover
mail.mydomain.com
mail.mydomain.com
EWS
legacy.mydomain.com
mail.mydomain.com
ECP
mail.mydomain.com
Internal ActiveSync
legacy.mydomain.com
mail.mydomain.com
External ActiveSync
$null
mail.mydomain.com
OutlookAnywhere
legacy.mydomain.com
mail.mydomain.com
I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
Any help on this would be much appreciated ..
Richard ..
..forever is just a minute away*

You don't need to use a legacy URL for ActiveSync in Exchange 2013. It will proxy ActiveSync for Exchange 2007 just fine. In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition. I recommend
you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824
Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288
StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115
Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970
StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
Jon

Any update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

Manually Move Public Folders from Exchange 2010 to 2013

Hi all,
I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
The final error is the following:
FailureCode                      : -2146233088
FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
FailureSide                      :
Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                   This could be because of one of the following reasons:
                                     Another administrator is currently moving
the mailbox.
                                     The mailbox is locked.
                                     The Microsoft Exchange Mailbox Replication
service (MRS) doesn't have the correct
                                   permissions.
                                     Network errors are preventing MRS from cleanly
closing its session with the
                                   Mailbox server. If this is the case, MRS may continue
to encounter this error for
                                   up to 2 hours - this duration is controlled by the TCP
KeepAlive settings on the
                                   Mailbox server.
                                   Wait for the mailbox to be released before attempting
to move this mailbox again.
So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                   locked. The Microsoft Exchange Mailbox Replication service
will attempt to continue
                                   processing the request after 2/14/2015 12:38:20 PM.
Finally, digging more into reports of migration I found this:
MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
Regards!

What script and process you are running to migrate the Public Folders?
And what do you mean by Manually?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.comTwitter:
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.

Legacy Namespace for Exchange 2007 to 2013 co-existence

We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.

In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
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. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
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. Thank you! Off2work

Using IIS AAR as a reverse proxy for Exchange 2010 & Lync 2013

hi
i am planning to use IIS AAR as reverse proxy solution for both Exchange 2010 & Lync 2013 . need clarifications on the below.
Is it production ready proof solution of using IIS AAR as a reverse proxy solution , if yes what is the sizing considerations for the same.
Can we have exchange reverse proxy and lync reverse proxy on the same IIS ARR server.
Is there any special consideration(license/certificates/cal licenses) needs to be taken care while using this solution
4. Deployment Guide available?

hi steve.. thanks for reply..
1 have gone through that.. however having both exchange & lync reverse proxy on single server is unanswered and the reason for having this in exchange forum is to have consideration from exchange prospective as well ...
I am also wondering this. Can both exist on the same set of proxy servers? I also plan to have a load balanced solution. Has anyone had any luck with doing that?

Questions about migrating Exchange 2010 to 2013

We currently have two Exchange 2010 servers with roles separated. One local mailbox server without CAS in our building and a CAS with no mailboxes in a remote datacenter.
We plan to migrate to 2013 with two new servers hosting all roles on each and then shut down the 2010 servers. There will be one local and one in a datacenter for Exchange 2013 so that either server could be individually restarted without internal LAN users
losing email access. (We do not want to open network access from the Internet to the onsite CAS). Is it practical to set it up this way?
How do we get the existing certificates (mail, autodiscover, and the local host name etc.) moved from the 2010 to the 2013 to the new servers when I assume they both must be running side by side for at least a short time while mailboxes are moved form 2010
to 2013? Will we need to buy new SSL certificates since the local host machine names for the Exchange server 2013 servers will be new and there will be more than one CAS?

Most of the CAs allow issuing duplicate certificate (as if you are requesting for a new cert) for the servers running same application. If your CA doesn't provide duplicates you can export the certificate and import to Exchange2013. http://msexchangeguru.com/2013/06/29/import-cert-e2013/
In certificate you dont need your internal FQDN. Especially in future you wont be able to add your internal FQDN in your certificate as most of the CAs wont allow you to add internal FQDN.
When you migrate to exchange 2013 you just need to configure the external URLs of Ex2010 in Ex2013 for both (i.e. same URLs for internal and external URLs) and point your common name and autodiscover to Exc2013 as Ex2013 will proxy the requests to your legacy
Ex2010 server. i.e. Your client interface will be Ex2013.
Please check this it will help you configure Split DNS and configure your URLs
http://exchange.sembee.info/2013/install/clientaccesshostnames.asp
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/ GUI
Configure split DNS to resolve external name from internal network.
Keep both Ex2010 CAS and Ex2013 CAS servers till all get logged in atleast once to connect to Ex2013 mailbox automatically.
As your DAG stretched across the data centers make sure
your DAG is in DAC mode.
http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Please read this as well for details about DAG configured in multiple site
http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
Ensure you use Exchange2013 SP1 as it is already released and available for download
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Do you have a load balancer in place?
Regarding internet facing it depends. You can configure CAS2013 server in DMZ if you wish to.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Exchange Load Generator 2013 ActiveSync usage

Similar Messages

Maybe you are looking for