Outlook 2003 and Exchange 2013

We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
stage.
We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
connect to remained on Exchange 2007 for the time being ?
Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
I'd be interested to hear other people experiences/opinions on this. Thanks!

Hi,
Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Data sync between exchange 2003 and exchange 2013

Need assistance on a general direction.
There is a 2003 domain with exchange 2003 currently in use. On this domain there is also a contact management application that is heavily integrated and cannot be update at this time. I would like to bring up a new 2013 exchange server.
Is there a method that I could have user data synchronized between the 2013 exchange data and the 2003 exchange? In this manner users could use the 2013 exchange as primary and the Contact manage application could use the sync copy of exchange 2003. For
now I am only concerned about he the calendar however I am sure the other information will need to be sync as well.
Please let me know. Thank you.

Hi There,
Once you install Exchange 2013 it will use the same data your Exchange 2003 is using \ seeing because both of them use Active directory for Directory information.
Exchange 2013 will see all the users that are 2003 without you needing to sync \ move data.
If you need to users to be on Exchange 2013 and keep Exchange 2003 all you need to do is move the mailboxes to Exchange 2013.
Cheers,
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Vista Biz \ DTM 4.7 \ Bold \ Outlook 2007 and Exchange 2003 Nightmare! Help Please

Hi
I am trying to sync my Exchange Pub Folder (Calendar and Contacts) to my BB 9000 and it fails when I select 'MAP' in the DTM sync process.
Vista Biz
DTM 4.7
Outlook 2007
Exchange 2003
Bold
I am local\admin perms and Owner perms on the Exchange \pub folders but it crashes as soon as I select the MAP button.
On my WinXP Pro, using Outlook 2003 and the same exchange it works out of the box, but with Vista and Outlook 07 it crashes. Has anyone experienced this?
Thanks
Karl

It would appear that at least in certain situations Exchange 2003 can't "understand" what Outlook 2007 pushes into the mail store, which is an issue when anything tries to connect via POP or IMAP as the server tries to "render" an Internet standard message, and fails.
Some info here, particularly the bit by Buddha377
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/c63b871 3-9ef9-4076-a11b-5db08255689b
Sounds like your iPhone sync may be suffering the same way??
P.S. Simply reading a message with OWA can "repair" email messages, I've witness this myself seeing Mail.app show "garbage" for a certain message pulled via IMAP, OWA showing the message fine, then all of a sudden Mail.app showing a perfectly formed message.

Migrate windows 2003r2 AD to windows 2012r2 AD and exchange 2003 to exchange 2013 Steps

Hi
requesting advice,
how can i migrate windows 2003 ad + windows 2003 exchange to windows 2012r2 AD+ exchange 2013 DAG (planing to implement 2 mail box and 2 hub+cas hyper-v vm servers )
kindly guide me how can i migrate and what is the best practice method
requesting step by step procedures to follow
Regards
Ratheesh
Ratheesh

Hi Ratheesh,
Migrating AD from Windows Server 2003 domain to Windows Server 2012 R2 domain:
Introducing the first Windows Server 2012 Domain Controller (Part 1 of 2)
http://blogs.technet.com/b/askpfeplat/archive/2012/09/03/introducing-the-first-windows-server-2012-domain-controller.aspx
Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012 R2
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Since we cannot migrate Exchange 2003 to 2013 directly, you can either migrate to Exchange 2007 or Exchange 2010 then to Exchange 2013.
Checklist: Upgrading from Exchange 2003 and Exchange 2007
http://technet.microsoft.com/en-us/library/ff805038(v=exchg.141).aspx
Checklist: Upgrading from Exchange 2003
http://technet.microsoft.com/en-us/library/ee332309(v=exchg.141).aspx
Part 1: Step-by-Step Exchange 2007 to 2013 Migration
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Checklist: Upgrade from Exchange 2010
http://technet.microsoft.com/en-us/library/ee332309(v=exchg.150).aspx
I hope this helps.
Amy

Server 2003 and Exchange 2003 upgrade.

Spin upa new VM as a domain controller and Global Catalog Server. Transfer the FSMO roles to it and let it sit overnight. Do NOT demote the Server 2003 domain controller or you will break Exchange 2003. Exchange 2003, when installed on a domain controller, doesn't properly configure itself to find domain controllers on the network. Instead, it goes into it's SBS configuration where it will only look at the current host for domain services.Next, determine which version of Exchange you want to go to. If migrating to an on-premises Exchange keep in mind that Exchange 2003 works with Outlook 2010 and earlier and that Outlook 2003 and earlier don't work with Exchange 2013. This means you need to upgrade to Exchange 2010 and enable non-secure Outlook connections on it, then upgrade Office to 2007 or later, and then upgrade to Exchange 2013.I...

I'll ask why Server 2012 and not r2 & why exchange 2010 and not 2013? I'll assume budget.
The only difference I think I'd have with Gary is that I'd leave the demotion and removal of the old DC until the end.
New DC, transfer the fsmo roles. Make sure that replication is working properly.
New Exchange box.
Look up the requirements for removing the last exchange 2003 server, there are specific steps for this.Then demote and remove the old DC.Start by checking the Domain and Forest Function Levels :)

Migration of domain 2003 and exchange 2003

dear sir,
presently we have domain controller win2003 std sp2 and exchange server 2003 sp2 ,installed on domain controller
we need to migrate from exchange 2003 to exchange 2010 and then to exchange 2013. please suggest the procedure step by step
can i migrate exchange 2003 to exchange 2010 with win2012 R2 std in domain 2003
or we need to first upgrade domain controller or exchange server.

Hi,
First, we should note that only Exchange 2013 SP1 is supported on Window 2012 R2. And it is not recommended to install Exchange server on DC server.
Since both Exchange 2010 and Exchange 2013 can run at least Exchange 2003 domain/forest functional level, we can upgrade Exchange first and then raise the functional level.
Because Exchange 2013 can't coexist with Exchange 2003, you need to remove Exchange 2003 server before you decide to upgrade to Exchange 2013.
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Problems with a shared calendar using Outlook 2007 and Exchange 2010

Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

ACE 4710 and Exchange 2013

Greetings everyone.
I am curious if anyone has any experiences with Exchange 2013 and ACE SLB functions. I know they changed to RPC over HTTPS on exch side and few other items changed as well. I do not forsee any issues just looking to see if anyone has any feedback from a production deployment.
Thanks
Joel

Joel, I checked internally and only located one case raised against ACE and Exchange 2013. The issue was resolved via defect CSCuc98599 "ACE randomly resets POST requests with SSL offloading". Use A5.2.2 or apply workaround (increase maxparselen to 65k). Matthew

Palm pro wont sync with outlook 2003 and windows device manager?

Palm pro wont sync with outlook 2003 and windows device manager? Files e.g. word docs or excel files sync o.k. but i need my contacts and i only get a error that there is sporblem with my desktop computer.
I am using vista and i have all updates installed.
Post relates to: Treo Pro T850U (Unlocked)

Do you have windows mobile device center installed(WMDC)? If not download it from here http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
Be sure you download the correct version for your PC. If you have 32bit OS or 64bit OS. To find this out, right click on Computer under start and select properties. Near the middle it should say 32bit or 64bit. If you know you have the correct software. Open up the control panel and go to sync settings. Right click on the partnership you have setup and select delete. On your device go to Start-->Programs-->Activesync-->Menu-->Options tap on Windows PC and select Delete. Then once both are done resetup your partnership. But this time uncheck everything. Then once it is done syncing. Go to Mobile device settings and change content sync settings and select Contact. Click save and let it sync. Do the same for calendar, tasks, and notes but leave the last item checked. So when Contacts are done syncing you go and check Calendar and leave Contacts

Outlook App and Exchange Routing Agent data interaction

I hope develop outlook Apps.the outlook app save some data, and send the mail , in exchange routing agent
, i want get the data.
I use Office.mailbox.item.CustomProperties , but the value don't save the receiver
mail， only save my outbox that mail.
the same question :https://social.msdn.microsoft.com/Forums/office/en-US/4fd6e26b-b712-416b-bc7c-7a8c14b257e1/outlook-app-and-exchange-routingagentfactory-some-issue?forum=appsforoffice#9f67a694-cf8f-498e-8dbe-b72fb991a041
how
to do , or have any good suggestions. thanks all.
Anything is Possible！

Hi Harvey,
>> I use Office.mailbox.item.CustomProperties , but the value don't save the receiver mail， only save my outbox that mail.
I think I have reproduced your issue. I created an app for office project, and used the code below:
<script>
// The initialize function is required for all apps.
Office.initialize = function () {
// Checks for the DOM to load using the jQuery ready function.
$(document).ready(function () {
// After the DOM is loaded, app-specific code can run.
var mailbox = Office.context.mailbox;
mailbox.item.loadCustomPropertiesAsync(customPropsCallback);
function customPropsCallback(asyncResult) {
var customProps = asyncResult.value;
var myProp = customProps.get("otherProp");
customProps.set("otherProp", "value");
customProps.saveAsync(saveCallback);
function saveCallback(asyncResult) {
alter("ok");
</script>
If I use this in the received mail, I could get the value of the otherProp which I set original in the same email. But if I create a new email, set the otherProp, and send it, after I received it, I could not get the otherProp.
I think we need to take some time to do some investigation.
Thanks for your understanding.
Best Regards,
Edward
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SCCM 2012 and Exchange 2013 Connector

Hello all,
I hope that you are well!
I have an issue that I can't explain for the moment, maybe someone can help me.
Actually we have SCCM 2012 SP1 and Exchange 2013 Enterprise in our LAN.
Now I did the configuration within SCCM of creating a new Exchange Server Connectors, everything seem's to be okay, no warning, no active alert, the Exchange server connection account and so on..
But I can't see the mobile devices from my user into the All Mobile Devices within SCCM 2012.
Do I miss something into this specific configuration, certificate or something related !
Best regards to all of you
Stephane

Hello Gerry,
This is what I got on EassDisc.log
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."~~
at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)~~
at System.Management.Automation.PowerShell.Invoke()~~   at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501
But that is old error, since I configure the Account properly
Regards to you,
Stephane

Outlook 2003 and Oracle

I have a user running Outlook 2003 and I've just installed the connector (1012 07) and patch 1012 08) but whenever I start Outlook I get a message saying that either the network is down (it isn't) or the server name is misspelled (it isn't either).
Any help?

I have also had the same error - it went away when you use the user name (not login name but the one which is entered in the First / Last fields) for the Calendar setup. For email, you still use the login name.
I'm not sure whether this will help - but you can give it a try

Emails push to iPhone and OWA instantly but greatly delayed to Outlook 2003/2007/2010/2013 Clients

I know this is an Exchange 2013 forum but i can;t seem to locate the 2010 forum.
We recently migrated over to exchange 2010 from 2003 and everything went well until emails were delayed when being delivered to outlook clients. Sometimes up to 15 mins. OWA and ActiveSync clients receive their emails instantly. I know the delay
takes this long because i see it arrive in my phone and then i wait for it to arrive into outlook. i even disabled Cached mode and we still experience delay issues.
Exchange is a single multi role install VM with ScanMail Trend Micro.
Am i missing something here?

Hi Viscor,
How long the emails delayed in Outlook?
Please check the message header to verify whether there is anything abnormal.
How about other Outlook clients? If only one end user has this delay issue, please try to run Outlook under safe mode.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Can not Establish Connection between outlook and exchange 2013

hi guys
i recently install my exchange 2013 sp1. I configured DAG and its working great.
but the main problem is outlook. I deploy all of the dns records in my public dns but now i cannot establish any connection between exchange 2013 and outlook 2013.
I mean when i want to create a new email account for my users i face with this error :
" the name cannot be resoved. the connection to microsoft exchange is unavailable . outlook must be online to connected to complete this action "
and finally when i study an article it refers to enable mapi over https in exchange 2013, I enabled it by powershell cmdlet but when i want to test it it gives me error :D
help me plz :D

Hi,
We need to configure Exchange Server 2013 for mail flow and client access with the following steps.
Create a Send Connecter
Add Additional accepted domains.
Configure the default email address policy.
Configure External URL.
Step5: Configure Internal URL.
Configure an SSL certificate.
For more details, please refer to this document.
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
If there is any further question, please let us know.
Best Regards.

SBS 2011 and Exchange 2013

Hey Experts,
So an associate of mine decided to do a little freelance work for a business who's requirements were;
-File Shares
-AD DS/DNS/DHCP
-Exchange Server
-SQL Server
The current server is a SBS 2003 box, with 2003 Exchange also installed. The plan was to migrate AD/Exchange to SBS 2011, however, he soon ran into a road block. Exchange 2003+ is not supported by SBS 2011, only Server 2008/2012 standard and upwards.
What should he do in this scenario?
Currently we're looking at purchasing Server 2012 R2 Standard and installing Exchange 2013. Advice?

How would we go about licensing, as far as I understand, exchange and 2012 have different CAL restrictions.
I'm not a licensing advisor.
Exchange and Server 2012 indeed have separate licensing requirements, each have a Server License requirement (for the server), and you each product also requires their own Client Access Licenses for users/devices who will be accessing the products.
You're looking at Windows Server 2012 license, and Exchange Server 2013 license, and probably 15 client access licenses for each (15 for Server, 15 for Exchange).
Windows Server 2012 specifically has a 1+2 server license. With this, you can install the Server license on a system (that's the "1"). If you enable only the Hyper-V role on the physical server, and run Virtual Machines as children in
this parent server, you are entitled to run two Virtualized instances of this same license on that hardware (that's the "2). This also applies if you are virtualized on another virtualization platform; one license for Server 2012 allows 2 virtualized
instances on the same host hardware. If you don't virtualize your workloads and you have two hardware installs of Server 2012, well you'll need two server licenses in that model. For a small business such as described, I'd virtualize every time.
Larry mentions a good point; you can enable the 'Essentials' role on the Server 2012 R2 platform that provides wizard driven interfaces for enabling Remote Web App, and PC backups from a Dashboard console. Weigh the value in this, as you will have
more work in front of you if you want to enable this and still provide remote access to email on your Exchange 2013 system (multiple external IP's and a modern firewall or the Microsoft ARR utility can address this). Generally OWA and Outlook Anywhere require
HTTPS redirection at your gateway to the Exchange server. RWA in Essentials uses the same protocol, so plan accordingly.
Hope that helps,
Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Outlook 2003 and Exchange 2013

Similar Messages

Maybe you are looking for