Exchange 5.5 to 2013

Hi guys,
Believe it or not a customer asked me today about upgrading Exchange 5.5 to 2013. Are you kidding me? They already purchased Exchange 2013 licenses. I just got the message, haven't spoke to the customer yet so I don't know yet how many
users and are they running AD or NT 4.0. Can you imagine?
Exchange upgrades can normally only support the two previous versions. So I'm thinking I would have to upgrade to Exchange 2003, then upgrade that to Exchange 2010 and finally upgrade that to Exchange 2013. Crazy.
Looking for suggestions here. Dump all the mailboxes to pst's, install Exchange 2013 and import them all? They have to go through some pain points that way such as manually reconfiguring outlook profiles, replies to old messages won't work.
Public folders? Guess I could export them but if there are a lot permissions could be a nightmare.
Any help here is appreciated.
Thank you.

Agree, lots of work involved here. Its not just Exchange but with AD too.
The only way I can think of is...
1: Migrate 5.5 to 2003. (I don't even remember when was the last time I did that ;) )
2: Upgrade the Domain to Windows 2003 SP2 at least.
3: Decommission Exchange 5.5 entirely.
4: Migrate 2003 to 2007 or 2010 (I would recommend 2010.)
5: Decommission Exchange 2003 entirely.
6: Install Exchange 2013 and migrate it to 2013.
Good suggestion from Martina about considering to Cloud solution. Office 365 would be good choice.
Give shot about Office 365 and lets see what the reaction of the client.
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.

Similar Messages

Cannot connect to an Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service"

Dear All,
I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
First I would like to present my network environment, I have 4 physical servers;
The first one is holding the Domain Controller 1, IP@: 192.168.1.10
The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
I am doing the steps below:
1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
2-entering the account name: [email protected]
3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
4-type the exchange CAS Server URL, https://192.168.1.16
5-Check the "Connect using SSL Only"
6-Authentication Settings: "NTLM Authentication", and pressing Apply
7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
username and password in the small window and I still got the same result.
I cannot verify the account name and I cannot complete the process.
I appreciate you kind assistance.

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Try to login the test account through OWA.
2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
3. Check the result of directly accessing the following URL:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
Thanks,
Angela
Angela Shi
TechNet Community Support

Can' add Exchange account to Outlook 2013

Hi,
We have an Exchange 2013 server which as far as I know is fully working - Outlook clients on the domain connect fine, OWA works fine and mobile devices work fine.
However I have a problem when trying to add an Exchange account to Outlook 2013 when this computer is on another domain (separate network, separate domain, separate company).
I assume Outlook is searching for an Exchange server which isn't there but how can I get around this?
Thanks

Hi,
Please try to alter the authentication method on the relevant CAS servers to Basic and test the issue. For details:
http://technet.microsoft.com/en-us/library/bb124503%28v=exchg.141%29.aspx
Thanks,
Rebecca Tu
TechNet Community Support

Migrate Active Directory 2003 to 2012 R2 and Exchange Server 2007 to 2013.

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Md. Ramin Hossain

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Domain. For Exchange installation and upgrading to 2013, you need to make sure that your domain controllers can understand attributes of exchange 2013. Besides if you have DC/Exch on the same server which is 2003 is not supported. Because Windows Server
2003 is not supported.
Migrate your domain to at least 2008 R2 and then proceed with Exchange 2013.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

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

Issues with Hosted Exchange, UM and Lync 2013.

Hello everyone!
I am trying to deploy UM with Office 365 Hosted Exchange. We are using one Lync 2013 Standard Edition FE and have deployed one edge server. We have set up our firewall to host the Reverse Proxy.
We do not use wildcard certs. External DNS resolves the _sipfederation and sip._tls SRV records to the external face of the edge server. The edge server functions as it should for remote users and mobility.
I have tried to follow these instructions to the letter three times over to no avail.
http://y0av.me/2014/01/07/lyncum365/
Neither Snooper or Event Viewer show any particular issue, though when I try to dial out to voice mail I will get one to two rings and then 5 seconds of silence a fast busy, and finally "Call Unsuccessful".
When checking the firewall logs I notice a seemingly random 10.x.x.x address being sent to the firewall by the external leg of the edge server. Wireshark captures it as STUN packets on port 3478 being sent to port 3478. These are being dropped by our firewall.
I believe them to be RTP packets but I do not know if this is normal behavior. Has anyone any ideas?

My mistake. Here is the snooper result.
TL_INFO(TF_PROTOCOL) [edge\edge]0C4C.05E4::06/18/2014-15:43:34.153.0000000C (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [3770767507]
Trace-Correlation-Id: 3770767507
Instance-Id: 2E5A
Direction: incoming;source="external edge";destination="internal edge"
Peer: exap.um.outlook.com:5061
Message-Type: response
Start-Line: SIP/2.0 488 Compression algorithm refused
From: sip:sip.domain.net;tag=08FB9ED133BA396696FE6546EA6F3031
To: sip:exap.um.outlook.com;tag=B8FFE4E9267ED6ECB78ADCC60126B53F
Call-ID: 66602CE1F9980BFA94AD
CSeq: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.11.11.23:50752;branch=z9hG4bK2132316E.5B3AF52DE2753A36;branched=FALSE;received=207.46.5.9;ms-received-port=50752;ms-received-cid=60172700
Content-Length: 0
Server: RTC/5.0
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000D (SIPStack,NegotiateLogic::SetCompressionType:NegotiateLogic.cpp(2701)) [559249495]( 00000079B1274FB8 ) Compression type is now CompOff
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000E (SIPStack,NegotiateLogic::ProcessCompressionResponse:NegotiateLogic.cpp(2217)) [559249495]( 00000079B1274FB8 ) Peer refused [488] our request for compression
TL_INFO(TF_NETWORK) [edge\edge]0C4C.05E4: :06/18/2014-15:43:34.153.0000000F (SIPStack,NegotiateLogic::AdvanceOutboundNegotiation:NegotiateLogic.cpp(910)) [559249495]( 00000079B1274FB8 ) Outbound negotiation sequence is complete
$$end_record
And finally..
TL_INFO(TF_PROTOCOL) [edge\edge0C4C.05E4::06/18/2014-15:43:49.379.0000002E (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265)) [962697980]
Trace-Correlation-Id: 962697980
Instance-Id: 2E61
Direction: incoming;source="internal edge";destination="external edge"
Peer: fe1.domain.net:61254
Message-Type: request
Start-Line: BYE sip:uminternal.um.prod.outlook.com:5066;transport=Tls;ms-fe=CO1PR02MB111.namprd02.prod.outlook.com SIP/2.0
From: <sip:[email protected]>;tag=b736386270;epid=9bcee72318
To: <sip:[email protected];opaque=app:voicemail>;tag=eced411395;epid=07C3F2A933
Call-ID: 4266a095bdef8280d67c7e7df58446fc
CSeq: 2 BYE
Via: SIP/2.0/TLS 10.10.10.25:61254;branch=z9hG4bKC848F11A.A88BCA6858661A50;branched=FALSE
Via: SIP/2.0/TLS 10.10.10.125:49156;ms-received-port=49156;ms-received-cid=401200
Route: <sip:edge.domain.net:5061;transport=tls;opaque=state:Si;lr>
Route: <sip:exap.um.outlook.com:5061;transport=tls;epid=07C3F2A933;lr;ms-key-info=AAEAARc45bIQE6UJAYvPAR8eV4QTvCH3EE2Kxtie7I2PMCSj-2aArKHP8dStYlJe-9jphIkz_mDEkCD_v8hY-mghQEHD6-F12E7E14YG-TJ2gEcQE0Bx2r_rDB3LrzRZzgQ0WVvxreLPWGI80elWF-xfbc_X3JE8mOR2OB9KQM8-e9WOjfq2kj6CnDGeL0yzgz4OB8zm-ao03Yo4gMZ-BpwaxC3BNuvvVDJo9wqrYftq_Z3MIVewWrqcDt5Td4vxCsMiXdwEqtEIRKVvQoqboleBJAyQl-C3qGgfEoSkUnApFuTSnQYRa4kbZ1iPaACpdKT-VTQGjc9HXfps48YJCsIXW0Ab_NSM2uvhUyw900men1ukXSmoZoWZbwqe5siuWVUcFoQl1h1Jcy4lCyZUfDZoqPzDioLqTk9iUmS8fa-PAJjsq72yGjVB_y1aJSxtHVsw7MiDqOGOPqT3dmF-sINkeyuokCy8UCf_cQHmEHwVzZLUJqaVccr3QNCLsBzhcWSypnC60ZZphOKuwl6RvUXWICPf0ubLTL2ppC3tWEgFdUUWOPVd84uGlMcqRLKGb1qrmpj8Nu6Lte7t5n2pMEBCfgAe79t4GO0C5KScdKT_XBM1iIBRXdNkPKHfSgC-wPQgRikdw7vRD-hOWlN5Lay7-zkQ4Ag6rauszFTAwbft99OieAOxKIsgYcxXxcG6;ms-route-sig=fiEMuzbN4_PyEz_I5gG3g8FtqNAonwgZCoRnOq-ByfYEtywTZp-Hk_eAAA>
Max-Forwards: 69
Content-Length: 0
ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";CallerMediaDebug="audio:ICEWarn=0x40003a0,LocalSite=10.10.10.125:6735,LocalMR=10.11.11.23:51430,RemoteSite=10.27.46.15:5286,RemoteMR=207.46.5.80:54106,PortRange=1025:65000,LocalMRTCPPort=51430,RemoteMRTCPPort=54106,LocalLocation=2,RemoteLocation=2,FederationType=0"
$$end_record

"The Connection to Microsoft Exchange is unavailable" when adding second Exchange account to Outlook 2013

I have a problem that I've found to be typical, just haven't found anything that describes my exact problem.
I'm having trouble adding a second Exchange 2010 server account to Outlook 2013 in one of the computers of the domain. Outlook 2013 will complain with "The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete
this action".
I've Googled and found many threads with the same error... however most of those seem to be either a problem with the server, or the Global Catalog in Active Directory, or the "connection method" (I've tried all found solutions to no avail).
This is not the case, since the first account is added with absolutely no problem. It can send and receive and I can delete the outlook profile and recreate it and it'll give no problems. I have this problem only when adding a second account.
This is a fresh Windows 8.1 install with an up-to-date Outlook 2013. I have other computers in the same domain and network, with the same setup (Win 8.1 + Outlook 2013) configured with two exchange accounts with no problem.
There are no connectivity problems, I can access that same account through OWA and in other computers on the network... the Global Catalog seems to be fine (shows two active DCs, which is correct).
I've tried deleting and recreating the outlook profiles, repairing the outlook installation, even deleting all outlook files in AppData and letting it recreate them, with no success.
Any hints of what could be going on?
Before I speak, I have something important to say.

Hi Javier,
Thank you for the update.
I have tested on my lab and get following result.
Lab: Exchange 2010, CAS Array (CAS01+CAS02), MBX01, DC
Type Server Field
Check name result
Changed Server Field
CAS01.domain.com
Yes
CASArray.domain.com
CASArray.domain.com
Yes
CASArray.domain.com
DC.domain.com
Yes
CASArray.domain.com
MBX01.domain.com
No
"The Connection to Microsoft Exchange is unavailable"
Based on my knowledge, the reason why inputing DC FQDN in the Server Field fixes this issue is that Outlook performs AD Lookup and finds the account configuration from AD, then back the CAS Array FQDN in the Server Field instead of DC FQDN.
Exchange 2010 is different from Exchange 2013, if you are using Exchange 2013, we need to input MailboxServerGUID.domain.com into Server Field.
If there is anything I’ve misunderstood, please don’t hesitate to let me know.
Thanks,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Unable to configure multiple Exchange accounts in Outlook 2013

This is a complicated issue so I will try to describe it the best I can.
I have a client with two SBS servers for two different organizations in two different locations. Each server handles completely different domains. Let's call them A and B.
The issue is this...using Outlook 2010 or 2013 on clients at location B, I can configure Outlook for the users mailbox on server B just fine. Some of the users at location B also have mailboxes on server A. When I add a 2nd Exchange account for
the users mailbox on server A, things get weird.
Sometimes, when I start Outlook after adding the 2nd Exchange account, Outlook will show only one mailbox, but it is incorrect. The top level will show it is a mailbox on server B, but it contains email from server A. When this happens, email
actually transfers from one mailbox to the other. I have to close Outlook quickly before things get out of hand. About a year ago, I determined that if the user has the same username and password for their mailbox on server A and server B, this would
cause the problem. So I changed the users' username on server B and it seemed to work with Outlook 2010.
Now, a year later, we have a new user with Outlook 2013 with a mailbox on server A and server B, who works in location B. I setup Outlook 2013 with mailbox B and it's fine. I add a 2nd Exchange account for mailbox A to their Outlook Profile,
and when I launch Outlook, it shows both. BUT, the mailbox A has nothing in it, and the status shows "This folder has not yet updated. CONNECTED". Mailbox B shows "All folders up to date. Connected to Microsoft Exchange".
Also, existing email from mailbox A starts showing up in mailbox B. If I go into mail account settings, I get the "Outlook is using temporary mailbox" dialog, meaning something has moved. If I look at the two accounts, both look
to be using the same OST file, even though under data files, there are two OST files, one for each mailbox account. If I delete the 2nd Exchange account (A), Outlook works again for the single mailbox on server B.
I've tried configuring the accounts without cached mode, but that doesn't work either. Mailbox B had a delegate account (Full access permissions) to another account on server B, but I have tried removing that also, but no change.
I cannot figure out why I cannot have two Exchange accounts, one from each server (A and B) in Outlook 2013/2010 at the same time.
HELP!
Thank for any ideas. I hope I haven't made this too confusing. One last thing...when I add the 2nd Exchange mailbox, I authenticate with the username on server A with domain\username and their password. The authentication seems to be accepted
fine and without error. I have also tried configuring the 2nd account using "automatic" instead of configuring manually. Same problem.

OK, I have done some more testing as you suggested. I created yet another new profile with just mailbox A. When I start Outlook, I see the users mailbox, plus a mailbox that the user has been given Full Permissions to (a delegate?). There
is one more mailbox that this user has full permissions to, but it did not auto-add itself, so I added the mailbox through the account properties. Now, all three mailboxes at location A are in Outlook (users mailbox and 2 delegate mailboxes). In
Outlook, on the left, has at the top the users main mailbox, and then below it are two other "branches" for the delegate mailboxes. I did NOT use cached exchange mode, btw.
I quit Outlook and edited the profile, adding another exchange account for the users mailbox at location B. I did a "check-name" and authenticated OK.
I launched Outlook, and the same (wrong) thing happens. On the left pane of Outlook, at the top, it shows it is the users mailbox at location B (the main branch says Mailbox name -- location B), but all the folders and content are from mailbox at location
A. Outlook has mixed it up, and it is at this point that email starts moving between mailboxes, so I quit Outlook quickly. It did show the two delegate mailboxes from location A, but there were just three "branches", and nowhere is there
the real mailbox B.
Can it have anything to do with the fact that these accounts have delegates (or are given full manage permissions to other mailboxes on the server)??
UPDATE: I just determined something. When looking at the Outlook email accounts dialog, for each account it shows the default delivery location. For the first account (location A), it shows:
"Selected account delivers new messages to the following location: usersemail@locationA\Inbox".
When I add the users mailbox for location B, it shows:
"Selected account delivers new messages to the following location: usersemail@locationB\Inbox".
However, when I start Outlook, and see that things are wrong and quit, I go back into the accounts dialog, and BOTH accounts are set to deliver to the SAME location:
"Selected account delivers new messages to the following location: usersemail@locationA\Inbox".
So now, the 2nd exchange account has changed it's location to deliver to mailbox A instead of B.
Crazy stuff.

Auto-Mapping with Full Access Mailboxes-not working in exchange 2010 clients outlook 2013

hello, I have exchange server 2010, the clients are running outlook 2013, I set an mailbox for automapping (full access) but when i restart client it does not appear in the client. i also did the command in the exchange shell, no errors. how can i fix this.

no sp info shows with the
Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersionName
Edition : Enterprise
AdminDisplayVersion : Version 14.0 (Build 639.21)
chart says
Exchange Server 2010 November 9, 200914.00.0639.021
is that the issue need sp 1?

Publishing Exchange coexistance in 2010/2013 in TMG

I already asked this in the TMG forums and didnt really get the answers there, so hoping I get better luck
here, so slightly rephrased:
Environment:
Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
Scenario:
I need to allow incoming and outgoing emails through TMG to both Exchange 2010 and 2013 as it will take me weeks, if not months before all mailboxes are in 2013.
Question:
1. How do I need to configure TMG to allow both Exchange 2010 and 2013 simultaneously?
2. Do I just redirect all SMTP to Exchange 2010 mailboxes to Exchanges 2013 in TMG and 2013 just pass on the traffic to 2010 if it doesn't have the mailbox?
Hoping to hear from someone whos actually had 2010/2013 in coexistence with TMG doing the publishing and firewalling for Exchange. Thanks.

These answers assume that all servers are in the same Exchange organization.
1. Exchange 2013 will proxy all Exchange 2010 traffic, so all you should route all traffic through and publish the Exchange 2013 servers rather than trying to publish both. Unfortunately, TMG hasn't been updated with a wizard for Exchange 2013.
I've seen this article that explains how to publish Exchange 2013, but I haven't tried it myself since none of my Exchange 2013 customers have deployed TMG with it. It does come from a source I would trust.
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
2. Generally I don't recommend routing SMTP through TMG as it doesn't offer much value for that, but there's no reason you can't do it. You should not have to worry about the server to which you route SMTP since SMTP mail will find
its way to the correct destination regardless of where you submit it. It is my preference to change your routing so that all mail goes through the Exchange 2013 servers early in the project rather than late.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Never ending story: Exchange and Outlook 2010/2013 - Read receipts (reading confirmation) implementation is buggy

OK, I try it again (for the fifth time or so), maybe anywhere in the big microsoft world there is ONE support engineer that is able to recognize a bug and hand it over to the development????
In several cases the read receipt does not contain the sending time of the original message, instead it contains (quite senseless) the time when the receipt itself has been sent.
The only information in the read receipt is the subject of the original mail which may be identical in longer mailthreads to several (dozends of) mails. So in this implementation you are not able to find out to which message a read receipt really relates.
So we cannot prove at all if a single mail in a thread has been read or not. The printout of such a receipt does not have any information that can be used in a meeting or discussion.
Since this situation obviously lasts for several years I'd like to ask
how I can get a working read-receipt-functionality for professional eMail-handling???
It seems that the problem does not lie in the content of the MDN sent by the Exchange server.
If I look into a copy of such a sent MDN with Thunderbird, it tells me for example, that my mail, sent on 15th Juli 2013 14:43:47 (UTC+1) has been read on 15th Juli 2013 14:50:08, which is correct.
But in combination with Outlook I get the same MDN displayed like follows:
Your message at... subject... sent Monday, 15. Juli 2013 14:51:30 (UTC+01:00)... has been read on Monday, 15. Juli 2013 14:51:16 (UTC+01:00) (Text translated from German to English)
So Outlook exchanges the timestamps and falsifies the content of the MDN.
This does only appear in combination with an Exchange server. If I work with a POP3 account and Outlook and send a message to an Exchange 2010 mailbox the correct timestamps are displayed within the returned MDN-message.
All involved systems are set to German (DE-de), the timezone on all systems is UTC+1
Here a small table with my tests
I've used Outlook on all Clients, 2010 and 2013.
Sender: sends initial mail and gets the Reading Confirmation
Receiver: gets the initial mail and sends the MDN
Sender     |     Receiver     |     MDN Display
POP3        |     Exchange   |     correct
Exchange |     Exchange   |     fail (displays wrong "sent"-time)
POP3        |     POP3         |     correct
Exchange |     POP3         |     fail (displays wrong "sent"-time)
It is obvious this cannot be a "feature". This is different behaviour depending on the senders Account type and one of this two scenarios must be a bug.
Could you help me further on this, please?

Almost no - the MS-Support here in this website was completely overchallenged to even understand this issue. I've tried several times to address this in this forum with no success. The "supporters" here had only one target - to quickly get this
"complicated" case off their desks.
The Office 365 support was much more competent and able to understand the problem. They escalated this to the development team (which lasted about 3 months, dozends of telephone calls and about 20 hours working time, which I had to donate to Microsoft freely)
and located the Problem in Exchange Server.
The result was that they promised to fix it in Exchange Server 2013, but there will be no Bugfix in Exchange 2010. I am waiting for the fulfilment of this promise since over 6 months.
Microsoft seems not to have any problem to leave their (professional and very expensive) Exchange software in a buggy state.
My conclusion: If Exchange 2010 runs out of maintenance I'll switch to Linux and Zarafa Server. The Zarafa guys are able to understand and fix their bugs and I do not have to donate thousands of Euros in working time only to get them understanding their
own bugs.
PS: You need only to press F1 in Office, especially in Access in the German language variant and you get an impressing lesson how desolate Microsoft is working today. Pressing F1 in Access 97 or XP lets you know, how much better they were some years ago.
An impressive deep fall down to the ground.
Regards, Conny

Access Exchange Service From SharePoint 2013 Custom Web part getting The request failed with HTTP status 401: Unauthorized.

I want to Fill a drop down with Outlook Meeting of Current log-in user in SharePoint 2013 web part for default credentials I am using the following code
ExchangeServiceBinding binding = new ExchangeServiceBinding();
ServicePointManager.ServerCertificateValidationCallback = (sender, certificate, chain, sslPolicyErrors) => true;
binding.RequestServerVersionValue = new RequestServerVersion();
binding.RequestServerVersionValue.Version = ExchangeVersionType.Exchange2010_SP2;
binding.PreAuthenticate = true;
binding.UseDefaultCredentials = true;
binding.Credentials = CredentialCache.DefaultCredentials ;
string server = "https://*********/ews/Exchange.asmx";
binding.Url = server;
I Am Getting the Error "The request failed with HTTP status 401: Unauthorized."
but when I Replace the line
binding.Credentials = CredentialCache.DefaultCredentials ;
with
binding.Credentials = new NetworkCredential(userName, password, domain);
Its run fine. Is there any way I could able to use default credential.

Hi,
As this question is more relate to Exchange development, I suggest you post it to the corresponding forum, you will get more help and confirmed answers from there.
http://social.msdn.microsoft.com/Forums/office/en-US/home?category=exchangeserver
Best regards
Patrick Liang
TechNet Community Support

Exchange Migration 2010 to 2013 different AD domains....

Here's my situation, I have migrated our users AD accounts to a new domain (newDomain.corp), but still use the exchange server in our old domain (oldDomain.corp) with linked mailboxes, which work fine.
I am now to the point where I want to decommission our old 2010 exchange server in the old domain, or at least have the users mailboxes on a new Exchange 2013 box belonging to the new domain.
I am looking for the best way to migrate the users mailboxes from the EXCH01oldDomain.corp (2010 Exchange server) to the new exchange 2013 server EXCH01.newDomain.corp, yet still have both servers online serving mailbox roles for users for a limited
time. So basically, can i have 2 exchange servers from different domains serving the same users in newdomain.corp?
Free busy and calendaring all have to work.
Thanks!
richard

Hi Richard,
Please make sure the two-way trust between the new domain and old domain has been set up.
Generally, when we run New-MoveRequest cmdlet to move a mailbox from an Exchange source forest (Old domain) to an Exchange target forest (New domain), the target forest must contain a valid Mail-Enabled user account with the set of AD attributes.
Since the mailboxes in old Exchange 2010 are all linked mailbox
which have Mail-enabled user accounts in new forest, we can directly move the mailbox from old Exchange 2010 to new Exchange 2013.
We can use the Prepare-MoveRequest.ps1 script with the -UseLocalObject to move mailbox with the existing AD account in new domain:
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

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

Exchange 2010 onprem to 2013 on prem cross forest LARGEITEMLIME issue

ok i have started migrating some of our users over, however some are failing due to large files.
I know that i can use the -LargeItemLimt switch to have the migration "SKIP" those files. (there seems to be alot of misconception that this will actually COPY the files & the value that you define is the MB limit. this is incorrect,
& this switch just tells the migration that it is ok to skip X (the value you define) amount of messages.)
Ok so now that that is out of the way
how or where would one configure to ALLOW mailboxes to be migrated over that contain large files? Is it in the transport/send/receive connectors size limits? is it else where?
I rather temp allow large files to complete my migrations & copy those files over, rather then skipping those files, & essentially loosing them for ever.

Now here is the thing, "AllowLargeItemLimit" is still mystery (to me at least)
But you can update the size of Send and Receive Connector on 2013 and should work
Set-TransportConfig -MaxSendSize 100MB -MaxReceiveSize 200MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 200MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 200MB
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
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 5.5 to 2013

Similar Messages

Maybe you are looking for