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

Similar Messages

  • Moving from SBS 2011 to Exchange 2013

    Make sure you get a clean DCDIAG before you start any migration.

    Hi fellow spiceworkers,
    I am planning on migrating from SBS 2011 to 2012 r2/Exchange 2013 and having a separate 2012 R2 DC.
    It has been mentioned and my understanding that it is important to raise the forest functional level (currently 2003) before installing Exchange 2013. My intention is to raise it to 2008.
    Current configuration:
    2011 SBS with FSMO ROLE and 2003 functional level.
    2012 R2 DC. 
    3 x 2012 R2 DC's at various remote sites connected via VPN.
    Should I move the FSMO role to the 2012 R2 DC first, wait to replicate, THEN raise the functional level or should I raise the functional level, wait for replication then move the FSMO role? 
    Also, would anyone have any other considerations I should take when doing this?
    Thanks for any advice in advance.
    Ralph
    This topic first appeared in the Spiceworks Community

  • Inplace Upgrade of Exchange 2010 on SBS 2011 to Exhange 2013

    Is it possible to upgrade exchange 2010 that is on SBS 2011 to Exchange 2013?
    George Zugg

    No 'In Place' Upgrade.
    You can move exchange to a new server running 2013.
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • SBS 2011 and upgrading Exchange 2010 to enterprise

    Hi All,
    We have A client running exchange 2010 on sbs 2011.
    The client would like to upgrade to  exchange enterprise so in place archiving can be used.
    Can someone tell me if this can be done with our current install - and what it is I need to purchase to allow it do be done.
    As I said above its exchange 2010 running on SBS 2011. Outlook 2013 and 2010 is used.
    I'm sure this has already been asked at some point, but i just need a clear answer of what my next step is.
    Thanks in advance.

    Hi:
    You need to purchase Enterprise CALs and key in the quantity and license number:
    http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
    You only are required to do this for the users that want/need the additional features.
    Larry Struckmeyer[SBS-MVP] If your question is answered, please mark the response as the answer so that others can benefit.

  • SBS 2011 - Using Exchange / Static IP - Cannot send e-mails to certain domains

    Hi,
    Client is running SBS 2011 using Exchange to send and receive e-mails.  For some reason 5 days ago they got call from clients stating they had not received e-mails from them (stpeterdeland.org). I ran the online Exchange Analyzer - (No errors). The
    strange thing is the client was not receiving "NDRs". i talked with one IT admin for one of the domains. He saw our e-mails being held up by his spam filter and has since "White Listed" the domain IP (65.34.20.210).
    I also ran Exchange BPA - No problems noted. Any help on this would be greatly appreciated.
    Thank you,
    Frank
    Frank

    You have your answer: spam filtering. The clue was 'no NDR', when emails disappear without trace, it is almost always because something has designated them 'spam'.
    You can't really do much about this unless you know why the emails are being flagged. Possibly your contact can help here, most anti-spam systems do explain why they mark down particular emails. Spam filters use many criteria, some of them even rational.
    I once found that a client's emails were disappearing because of a picture used as a signature: it was a .jpg file, and the problem was solved by substituting a .png file. That's one hint: do not include files which can carry malware, or at least not unless
    zipped, preferably with a password. Unfortunately, there are not many file types which cannot include malware. Outlook drops broad hints if you try to attach certain files, and suggests you might wish to reconsider.
    Another minus is the use of HTML email, which is unfortunately almost universal now. Plain text emails are less likely to get the thumbs-down, but I'm not sure if the MS webmail can even originate plain text emails. Obviously, there are certain words to
    be avoided, and I won't mention any here, but many apparently innocent financial and entrepreneurial words will bump up the spam score. Multiple exclamation marks, lots of upper case, the list is endless. I was once trying to help a client's salesman set up
    a VPN connection, and had my email killed by Yahoo because it contained a URL and some other networking information.
    The only really certain way to find out why emails have been dropped is to ask the admin of the recipient, or of any smarthost used on the way. You do have to hope that they actually have an admin to ask...
    Joe

  • 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

  • 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

  • Server 2012 and Exchange 2013 Migration from SBS 2011

    Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
    This topic first appeared in the Spiceworks Community

    I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

  • Send Issues with Outlook for Mac (2011 / V15) and Exchange 2013 SP1

    Hi all,
    we have a strange issue with only with Outlook for Mac Users (version 2011 and the newest Outlook Version (V15) from Office 365) connected to our Exchange Server 2013 SP1. Some emails which we send out to the exactly same recipient are not sent through our
    Exchange Server. 
    We have sent 8 emails with subject "test1, test2, test3...". Only test 3-6 was arriving to the recipient. The other emails are in the "sent" folder but it was not sent out through the Exchange.
    What we can see with "Get-MessageTrackingLog" is, that the Recipients and MessageSubject are empty for these emails:
    Timestamp Sender Recipients MessageSubject
    25.02.2015 16:48:52 [email protected].. {}
    25.02.2015 17:04:43 [email protected].. {}
    25.02.2015 17:08:25 [email protected].. {[email protected]} test 3
    25.02.2015 17:08:56 [email protected].. {[email protected]} test 4
    25.02.2015 17:09:38 [email protected].. {[email protected]} test 5
    25.02.2015 17:09:38 [email protected].. {[email protected]} test 6
    25.02.2015 17:13:45 [email protected].. {}
    25.02.2015 17:13:55 [email protected].. {}
    We can still reproduce the issue on different Mac computers.
    Thanks for any help in advance!
    Thanks and best regards
    Reto

    Here is the mailheader form the successfully sent email:
    Date: Wed, 25 Feb 2015 17:08:25 +0100
    Subject: test 3
    From: sender <[email protected]>
    To: "'[email protected]'" <[email protected]>
    This mailheader is from an email which was not sent out:
    User-Agent: Microsoft-MacOutlook/15.6.0.150113
    Date: Wed, 25 Feb 2015 16:48:52 +0100
    Subject: test 1
    From: sender <[email protected]>
    To: [email protected] <[email protected]>
    Interesting: Only the not received messages contains User-Agent string and have some quotation marks missing in the To field.

  • Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

    I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
    I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
    backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
    failure. I have always felt nervous with SBS because it only runs on a single server.
    My plan is:
    Install Windows Server 2012 Standard on a new server machine
    Join that new server to the existing SBS domain and sync the users, etc.
    Install Exchange Server 2013 on the new 2012 Server
    Migrate the existing Exchange data and account info to the new server
    Demote the SBS Server and promote the new server to primary DC
    Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
    Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
    Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
    services)
    Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
    failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
    SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
    Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
    Thanks,
    Colin
    Colin

    Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
    Constraints/objectives:
    None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
    Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
    Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
    Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
    maintenance.
    Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
    want to keep all IT tasks as simple as possible.
    We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
    A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
    Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
    server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
    to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
    from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
    New Plan:
    Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
    Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
    Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
    Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
    Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
    (or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
    Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
    Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
    Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
    it there. In any case, do NOT install Exchange directly on either DC.
    Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
    the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
    I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
    Thanks so much for all your help,
    Colin

  • SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

    Migrating a customer to Exchange 2013 from SBS 2008.
    Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
    The customer only has a single external IP address...
    So what do I do for this external DNS of legacy.customer.com?

    Hi Allister - 
    You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
    Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
    Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
    is inside AD, Ex2013 will find it.
    These are the URLs you need to change in 2007/2010
    ClientAccessServer
    webservicesvirtualdirectory
    oabvirtualdirectory
    owavirtualdirectory
    ecpvirtualdirectory
    ActiveSyncVirtualDirectory
    AutodiscoverVirtualDirectory You can read more on how to set these here:
    http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
    Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
    If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
    A wise man is a fool, with a good memory.

  • SBS 2011 and E1 Plan for Non profits.

    I've got a charitable client who has SBS2011. The 75 user limit has not been a problem until now.
    They now need all their staff, most of whom are in satellite locations, to each have an Exchange email address. However Office 365 Enterprise
    E1 PLan for Non Profits would be free for them. 
    My question is this; can they use Active Directory integration with SBS 2011 on E1 plan for 350 users, even though SBS 2011 has a 75 user limit? We would just want them all listed in the Global Address Book etc.
    There only other alternative is to spend money on new hardware to upgrade to standard server and full blown exchange to get around the 75 user limit on SBS 2011.

    You could achieve this by migrating the email from the local SBS to Office365, and then adding the additional (non-SBS) users directly in Office365 - that way all users would be in the same Global Address list.
    You have the choice of either:
    1. setting up the Office365 users completely separate from your AD (ie just create all users under Office365, and migrate over the email from those who had onsite mailboxes using something like MigrationWiz)
    or
    2. using the MS migration approach and setting up DirSync on a local server to sync the onsite AD users with Office365, migrating their email over, and then adding the additional Office365-only users directly via the Office365 admin portal
    With either option, as long as your onsite user count remains within the SBS 75 user limit, it won't be an issue.
    Hope that helps
    John
    -- John Murdoch APOJ Ltd

  • Active Directory Sites and Exchange 2013 Deployment

    I've recently took over responsibility of an Exchange 2013 Organization that is deployed as follows:
    Active Directory consists of 4 Sites. AD Site A, B, C, D  Exchange 2013 Enterprise resides in 2 of the 4 AD Sites as follows:
    AD Site A - ExchangeServer 1 and ExchangeServer 2
    AD Site B - Exchange Server 3
    AD Site C - No Exchange Servers
    AD Site D - No Exchange Servers
    All 4 AD Sites are 4 different Physical locations/datacenters. All 3 Exchange 2013 servers are multi-role servers.
    The Forest in which Exchange resides in consists of an empty Root domain, a Production (child) domain and a Test (child) domain. Exchange resides in the Production (child) domain.
    Issue: AD Site A contains DC's from all 3 domains: Root Domain, Production child Domain (this is where Exchange lives) and Test child Domain. I notice that Exchange in AD Site A is using DC's from the Root Domain for it's "DefaultGlobalCatalog",
    "DefaultConfigurationDomainController" and "DefaultPreferredDomainControllers" This to me does not seem to be very efficient as any Address Book queries will have to be referred to by the Root Domain DC's to the Production child domain
    where Exchange lives. All of the AD User accounts and mailboxes are in the Production child domain.
    In a situation such as this, would it be advisable to build 2 additional AD sites specifically for Exchange? Rather than re-IP Exchange or risk the impact of moving several other (non exchange) servers to another AD site, I would add the IP address
    of the Exchange servers /32 to the new Exchange dedicated AD Sites and erect a DC in these new sites adding its IP address /32. Any thoughts on this idea? If the subnet that exchange resides on is (for example) 10.60.3.0 /16 in AD Site A, and
    I build a new AD site for Exchange and add the IP address of the Exchange server such as 10.60.3.141/32 for this new Exchange AD Site boundary, I can still leave the 10.60.3.0 /16 unaffected in AD Site A, correct?
    I'm looking for Microsoft's best practices in terms of laying out AD and domain controllers pertaining to Exchange server 2013.

    Hi Anthouyray,
    Thank you for your question.
    We could use the following command to exclude domain controller which is root domain controller:
    Set-ExchangeServer –Identity  <exchange servername> -StaticExcludeDomainControllers <root domain controller>
    Then we could restart the service of “Microsoft Exchange Active Directory Topology” to check if the issue persist.
    If there are any questions regarding this issue, please be free to let me know.
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • 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

  • 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

Maybe you are looking for