Exchange 2010 Migration to 2013 Coexistence url's

Hello,
What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Read the article below from Ross Smith. There can't be better article than this:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
If exchange 2010 and 2013 are on same site, then you need to:
1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
2. Move the SSL certificates from Exchange 2010 to Exchange 2013
3. Point the external URL to Exchange 2013 instead of Exchange 2010
4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
- Sarvesh Goel - Enterprise Messaging Administrator

Similar Messages

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Case of the Missing User Exchange 2003 - Exchange 2010 Migration issue

Hey All,
I am in the middle migrating from Exchange 2003 to Exchange 2013 by way of Exchange 2010 and going through the final parts of my Exchange 2010 portion of the migration I found that one of the users on Exchange 2003 is not showing up in the EMC to migrate.
In EPS I can find the user with Get-User username but I cannot get the mailbox or kick off the mailbox move from EPS giving me the error of "Object could not be found" It is a valid user with a valid user mailbox and I can log into the
mailbox in OWA for Exchange 2003. Any thoughts as to why the user's mailbox is not showing in EMC or that I can't get it to move via PS?
Thanks,
Joe

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
S#
Virtual Directory
URL
Exchange Server 2010
Exchange Server 2007
1
Web Services Virtual Directory
Internal URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
2
Web Services Virtual Directory
External URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
3
ActiveSync Virtual Directory
Internal URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
4
ActiveSync Virtual Directory
External URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
Following error is logged on Console on Mac when this issue happens:
30/10/12 3:27:28.398 AM
Mail
*** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
EWS fetchRootFolderId: expected one folder in response, received: 0
0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
10 Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
11 Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
12 libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
13 libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
14 libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
15 libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

Hi Akebono,
Let's check a few things in your server:
1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
5. If you still experience such problems - post the ExRCA error report here.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Exchange 2010 OWA and ASA5510 - Wrong URL?

I'm in the final steps of migrating my customer's Exchange server from Exchange 2003 to Exchange 2010. I've got all the mailboxes moved and am testing the OWA access. Under Exchange 2003, the internal/external users were able to access OWA thru the following URL:
http://mail.mycustomer.org/exchange
It would pop up a login box, they'd put in their domain info and get connected to their mailbox.
After migrating to Exchange 2010, the user had to change the URL to httpS://mail.mycustomer.org/exchange or httpS://mail.mycustomer.org/owa, but it worked internally. When I test it externally, I get the following page:
https://mail.mycustomer.org/+CSCOE+/wrong_url.html
I have next to no experience with Cisco devices, management, and/or maintenance, but what I've found in my research points to an issue w/ our ASA5510 and the port 443 required by the SSL connection to the Exchange server. Any help to resolve this issue so that my external users will be able to access OWA would be greatly appreciated. Thanks.

Hi,
Can you check the output of the following commands
show run http
show run webvpn
These are basically the 2 services that utilize the port TCP/443 port on the ASA.
The first commands output will show some settings related to the ASDM which is the GUI for the ASA management. The second command output will show settings related to the SSL VPN.
Both of these services can be modified to use some other port than TCP/443 which would leave the port free for your server.
I assume that you only have one public IP address at your disposal which is configured on the ASA interface and you have no extra public IP address? Otherwise this should be no problem at all.
Naturally if you change the port on ASDM or SSL VPN it will cause some inconvinience for users of those services. Ofcourse you have the option to map the local TCP/443 port of the server to some other public port like TCP/444 but again this might cause inconvinience to the users also.
- Jouni

Exchange 2003 Exchange 2010 migration confusing?

Hi,
I have searched several articles for this migration in this forum and other forums (ie
petenetlive,
simple-talk,
Exchange Server Deployment Assistant,
Technet) but when you start reading the guides there are discrepancies between one and the others and vice versa.
I have this scenario:
1) Old server windows 2003 R2 std + exchange 2003
2) New server windows 2012 R2 + exchange 2010
I have not installed exchange 2010 yet because I had to first update Active Directory schema to W2012 (adprep /forestprep, adprep /domainprep) R2 and also update exchange schema using setup /PrepareSchema from the exchange 2010 media.
Then I read that I have to install Exchange 2010 in stages ie Client Access Role first, then Transport Hub and then Mailbox role.
Also a digital certificate i required and was wondering if I could still use a self signed certificate.
Does anyone know of a very good article or video that explains this process consistently STEP by STEP?
Thanks
Regards
Ipnotech

Hi,
Here are more good articles about install Exchange 2010 in Exchange 2003 environment:
Exchange 2003 - Planning Roadmap for Upgrade and Coexistence:
http://technet.microsoft.com/en-us/library/aa998186(v=exchg.141).aspx
Install Exchange 2010 in an Existing Exchange 2003 Organization:
http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
Create a New Exchange Certificate:
http://technet.microsoft.com/en-us/library/dd351057(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2003 to Exchange 2010 migration steps

HI ,
I have migrated windows 2003 to windows 2008.Its successfully migrated.
Second phase i have a plan to migrate exchange 2003 to exchange 2010.
My current setup
windows 2008 64bit (DC)
exchange 2003 sp2
1
Bring the Exchange organization to Exchange Native Mode.
2
Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
3
Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4
Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
to Windows Server 2003 SP2 or greater.
5
Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6
Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7
Install any necessary prerequisites (WWW for CAS server role).
8
Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
at the command line.)
9
Install CAS server role servers and configure per 2010 design. Validate functionality.
10
Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11
Install Hub Transport role and configure per 2010 design.
12
Transfer inbound and outbound mail traffic to the HT servers.
13
Install mailbox servers and configure Databases (DAG if needed).
14
Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
Public Folder tool.
15
Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
16
Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17
1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
18
Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19
Delete Public and Private Information Stores from Exchange 2003 server(s).
20
Delete Routing Group Connectors to Exchange Server 2003.
21
Delete Recipient Update Service agreements using ADS Edit.
22
Uninstall all Exchange 2003 servers.
This is my plan to migrate.But i have a doubt in installing exchange 2010 in this scenario.
Is it necessary to use
Setup.com /PrepareLegacyExchangePermissions,
Please help me what excactly i have to do

I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
Migration</a> is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips.
Some Articles I would like to share as well:
<a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
Exchange Server Migration to the Cloud</a>
It takes a lot of time and effort to get it right. Thank you for helping
Here some information about services for migrations
<a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

Exchange 2010 Migration of 200 Users/Force Archiving

Exchange 2010 Outlook 2007
Here's my situation. We are migrating 200 mailboxes from our current domain which will be absorbed into another company/organization. The new organization is putting limits on our users mailboxes of 100 Mb or 5000 items in order to make a smooth
transition from our Exchange environment prior to them absorbing all of our mailboxes. Of the 200 users a quarter of them are way over that limit. We have sent out numerous emails informing the users (mostly offsite) to archive all of their emails
and clear out the "deleted"/"sent" items. Obviously no one has listened to our requests to get their mailboxes down to the limit the new organization has set for us. I just recently migrated all of the users mailboxes to .pst's
via a powershell script, but as you know, that only copies the data. Is there a way via powershell to move or force all of the users data (sent/deleted/inbox) to an archive thus freeing up their mailboxes for the upcoming migration? The new org
will not approve the migration of any mailboxes over the 100 Mb/5000 item limit. I'm not limiting a solution to powershell -- I will take any solution that is Microsoft-centric. I will not be able to use third party tools or solutions due to the
nature of my job.

Hi,
Since the target domain set a policy to limit the migration, I suggest kindly let the target domain disalbe or expand the limitation for a while to complete the migration, if it is possible.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2007 to Exchange 2010 Migration

Hi all,
I am migrating to exchange 2007 to exchange 2010 .This is not a migration data only migration like i am exporting mailboxes and importing it to new mailboxes .But email address and SAM account name will be same as per the source.Post migration i will point
the auto discover to new organisation.May i know what will be the impact to users??need to reconfigure outlook profile or does it will look for auto discover and prompt for new email id?
Jayakumar K

Is it in the same forest of or both the servers are different forest?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 - Virtual Directory Internal & External URL's with Wildcard Cert

Hi Guys
I am trying to determine if my Exchange 2010 server Virtual Directory URL's are setup according to best practice. I'm sure anyone with good Exchange experience will instantly be able to tell me if my Virtual Directory DNS is correct or could cause issues.
Scenario:
Hosted Exchange 2010 SP1. Multiple client mail domains hosted
2x CA, 2x HT, 2x MB, 2x DC
Wildcard *.example.co.za certificate being used on CA servers
AD domain is he.example.za.net
CA Server naming example: ca1.he.example.za.net, ca2.he.example.za.net
he.example.net DNS is done by DC servers
External name used by clients: outlook.example.co.za (For Outlook setup and OWA access)
outlook.example.co.za has two A records pointing to the CA IP's
PROBLEM/CONCERN:
We have a random OWA log out issue that we believe might be due to ambiguous DNS names being used.
If I change the Virtual Directories External URL to be the FQDN of the server, we get a Certificate Error in clients (due to the .co.za Wildcard). The external URL clients use
must be on .co.za.
So are the Virtual Directory URL's causing the CA servers to loose track of who is authenticated in where (leading to OWA disconnection)? Is it fine to load balance the CA servers with the DNS the way we are doing currently? Any other issues you see?
Current Virtual Directory settings:
Note that they are identical on CA1 and CA2
[PS] C:>Get-OabVirtualDirectory -server ca2 |fl *url
InternalUrl : https://outlook.example.co.za/OAB
ExternalUrl : https://outlook.example.co.za/OAB
[PS] C:>Get-WebServicesVirtualDirectory -Server ca2 |fl *url
InternalNLBBypassUrl : https://ca2.he.example.za.net/ews/exchange.asmx
InternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
ExternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
[PS] C:>Get-ActiveSyncVirtualDirectory -Server ca2 |fl *url
MobileClientCertificateAuthorityURL :
InternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
ExternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
[PS] C:>Get-EcpVirtualDirectory -Server ca2 |fl *url
InternalUrl : https://ca2.he.example.za.net/ecp
ExternalUrl : https://outlook.example.co.za/ecp
[PS] C:>Get-OwaVirtualDirectory -Server ca2 |fl *url
Url             : {}
Exchange2003Url :
FailbackUrl     :
InternalUrl     : https://ca2.he.example.za.net/owa
ExternalUrl     : https://outlook.example.co.za/owa
[PS] C:>Get-AutodiscoverVirtualDirectory |fl *url, server
InternalUrl :
ExternalUrl :
Server      : CA1
InternalUrl : https://outlook.example.co.za/
ExternalUrl : https://outlook.example.co.za/
Server      : CA2
REALLY APPRECIATE SOME EXPERT ADVISE. Thanks.

Hi Kane,
Why did not you use cas array to load balance client connectivity?
If you create a CAS array, you can assign an virtual IP (VIP) for the CAS array FQDN (e.g CASarray.example.za.net), and then point all the Virtual Directories internal URL to CAS array fqdn;
For external, you can point outlook.example.co.za to VIP which had been assigned to CAS array.
I recommend you refer to the following article to understand CAS array:
http://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx#CASarray
http://blogs.technet.com/b/ucedsg/archive/2009/12/06/how-to-setup-an-exchange-2010-cas-array-to-load-balance-mapi.aspx
http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx
Best regards,
Niko Cheng
TechNet Community Support

Latency leads to full system Failure in Exchange 2010 - Resolved in 2013?

My work encountered a bug - and for no lack of trying - I could not find any bug submission for Ex2010 anymore. Since Most programming relies on the foundation of the past - if replication service was implemented the same in 2013 than it could leave
to a full system failure.
The issue is something happened in REPLICATION service in such a fashion that it accepted a connection, and in the programming it set a variable to a LARGE NUMBER (fail closed) to replace for "Copy Queue
length" in the ball park of 922 quadrillion.
The service never updates this value because of its quasi-state and some timeout occurs and now the GOOD servers think their copy is ludicrously behind. This causes the GOOD servers to attempt to fail-over - as they believe their copy from the BAD
server has failed or perhaps another check fails...
[6 DAG pieces on 3 servers, 4 pieces per server]
In my scenario Server 3 holds:
1 part of server 2 <= Tells server 2 you're bad - don't fail over
1 part of server 1. <= Tells server 1 you're bad - don't fail over
2 parts its own <= "good" - though dead replication service
As I do not know if this exploitable by simply placing a listener in place of replication service to accept and do not respond to connections - I do not know. However, there is a "bug" or flaw in my opinion to allow 1 bad server to superceed
two good servers based on a partial service crash. Simply stopping replication service on Server 3 allowed Server 1 / 2 to take over with out issue - I then restarted replication service and no issue since.
Since i wasted an hour looking where to submit this - this forum will hopefully do - I am very much a white hat - but I am dislike the non-simple way before me to disclose said information to the creator. I want my hour back for their non-intuitive
process, or maybe the simply don't care about Exchange 2010.
- Dan

Please note "LATENCY" in my topic is not network but inter-process on a single host, and is used as saying a timeout occurs without value.

Upgraded to Exchange 2010 now outlook 2013 can't connect externally

Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHC

Hi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2003 to Exchange 2010 Migration

Is there anything I have to do to migrate Exchange 2003 to Exchange 2010 aside from migrating the database(s)? I believe autodiscover picks up the new server when people open Outlook?

It will definitely HELP
you with the migration process, its not a guaranty for a successful one.
You should be familiar with both systems (Exchange 2003 & 2010) and know the migration process and be familiar with each step .
Best practice is to make the migration in lab environment that is a copy of you production environment first. that way you will get an experience with the process and know in advance if there are any issues before go to production. I
know that in real world this is not always possible.
Here is another grate guide from Pete Long:
http://www.petenetlive.com/KB/Article/0000234.htm
As a side note, Exchange SP1 or SP2 no longer supported, so make sure your Exchange 2010 is installed with minimum SP3 (RU5 is better).
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Exchange 2010 and Outlook 2013

please read my question and comments carefully before replying.
We just upgraded to Outlook 2013 x64bit and exchange 2010. there is only one exchange server with all updates and fixes installed, and Outlook is up-to-date as well.
User A sends a meeting request with tentative appointment to user B
User B accepts the appointment and it shows on his calendar as tentative
User A changes the appointment from tentative to out of the office or busy and sends update to user B
User B receives the update and click on No Response Required
User B's calendar does NOT change from tentative to out of the office or busy.......
we tried OWA as well as tried this in cached mode and online mode and made no difference.
you can see that communiation is real time between the two clients and exchange because as a test, I changed the words and client machine immediately updated but the free/busy/out of the office status never changes unless you change the time of the appointment.
Please let me know
David

Hi David,
It is by design.
The Free/Busy status is a private property that can be changed but
only with a full update. A full update is practically a new meeting invitation to the same event, replacing the old properties with the new ones. Full updates are sent when one or more of the following properties are changed:
Start Date/Time
End Date/Time
Recurrence
If you only send a update about free/busy status, it is an informational update instead of a full update. Thus, the free/busy status of the meeting is unchanged. For more information about meeting updates, we can refer to the following blog:
http://blogs.technet.com/b/outlooking/archive/2012/06/11/understanding-meeting-updates.aspx
If you have any feedback for TechNet Subscriber Support, contact
[email protected]
Best Regards,
Winnie Liang
TechNet Community Support

Decommissioning Exchange 2010 Casarray (contains 2013 Mailbox Servers?)

I'm in the process of decommissioning exchange 2010. I went to remove the 2010 casarray and see that my 2013 mailbox servers are a part of the array? Can I still remove the array? Do I leave it?

Hi,
Please have a look in to the below mentioned article especially the reply from Off2work
http://social.technet.microsoft.com/Forums/office/en-US/c10550fa-b735-48ee-ad52-a75f0176e1de/cas-array-in-exchange-2013?forum=exchangesvrdeploy
As an additional info , as per my knowledge there is no use of cas array in exchange 2013 and at the same time exchange 2013 servers will not make use of it even though if it is an member of an casarray in exchange 2010.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010 Migration to 2013 Coexistence url's

Similar Messages

Maybe you are looking for