AD DS 2012 R2 and Exchange 2003

First, yes I understand that Exchange 2003 is no longer supported. :) However, in the real world there are still companies running Exchange 2003 in production. Hopefully not for long.
The client I am at is in the middle of a Exchange 2003 to O365 migration. They are a few months from wrapping the project up. I am in the middle of doing an Active Directory upgrade from 2003 functionality to 2012 R2. Currently all their
domain controllers in the forest that Exchange is in are running Windows 2003 and of course it is set at 2003 functionality. They had a few NT 4.0 domains left that we finally decommissioned during this project. Yuck!
My question is, I have read that Exchange 2003 isn't supported with 2012 R2 domain controllers. However, I can not find what will happen if we start to introduce 2012 R2 domain controllers. The plan is to bring up all of the DC's and then cut
over to 2012 R2 functionality.
Does anyone have or know what exactly will happen if we go ahead with deploying 2012 R2 domain controllers. I can't find any information documented except for it isn't supported. We have other projects waiting the AD upgrade to be complete and
can't wait for the O365 project to be completed.
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

Hi Kristopher,
As you mentioned that Exchange 2003 does not support Windows Server 2012 Domain Controllers, which will lead to unexpected issues.
Here is a similar thread below for you:
Adding Windows 2012 DC to 2003 Level Domain (with Exchange Server 2003)
https://social.technet.microsoft.com/Forums/en-US/29301f55-531e-40e7-9a9d-bab4d0b05b33/adding-windows-2012-dc-to-2003-level-domain-with-exchange-server-2003
Best Regards,
Amy

Similar Messages

Business Package for Communication with NW04 and Exchange 2003?

Hi, we are evaluating opportunities to realize a groupware integration in the SAP Portal EP60SP2. A upgrade to Netweaver is planned, so the possible solution should work with Netweaver too. Our Exchange version is 2003.
I'm thinking about the standard SAP Groupware-Integration in combination with the Business Package for Communication.
Has anyone expirences with the Business Package for communication, Netweaver and Exchange 2003, yet?
I know, it's not officially supported, but maybe it works.
With the OWA-iViews we've got problems to implement our Styleguide and to devide into different iViews. The informations shown in the iViews of the Business Package are adequate and we would save ActiveX.
Is there another solution that works?
Are there other iViews from 3rd party developers, that show Outlook informations? Has anyone realized something like this in a project yet?
I would be grateful for any ideas.
Sandra

Hi Sandra,
Please note that the Business Package for Communication was only available for SAP EP 5.0. Newer releases of SAP EP contain the groupware (GW) functionalities and some GW iViews automatically as soon as KM is installed with the EP. The integration with MS Exchange 2003 should work. If you look for iViews such as Send EMail, Create Appointment, Show availability and Room Calendar, you can use the iViews shipped by SAP. If however you need the EMail inbox or the personal calendar and tasks, then the native OWA iViews are the way to go. For further details please refer to the SAP NetWeaver admin guide http://help.sap.com/saphelp_nw04/helpdata/en/0c/30d624a0fae949902f7a4b2a8f98bd/frameset.htm.
Hope that helps
Christian Stadler

Single Inbox on Unity Connection 8.5 and Exchange 2003 SP2

Hi,
We have Unity Connection 8.5 (with SU2) and Exchange 2003 SP2
We want to setup the Single Inbox feature that works well with Exchange 2007 and 2010, but my customer is running Exchange 2003 SP2.
We met all of the requirements outlined in: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp459928
I configure a new "Unified Messaging Services" profile for Exchange using Exchange 2003 and enabled for Single Inbox. When I run "Test" it displays the following errors (other validation is successfully)
The service port for IMAP is not functioning.
The system failed to connect to the server with a socket connection through port beatles.clubone.com:993. The error is error:0200206F:system library:connect:Connection refused. Refer to the tomcat log file for more details. If you are using secure connection, confirm that SSL is enabled on the server.
Why is it trying to connect using IMAP, that wasn't the case when I used for Exchange 2007 or 2010 when IMAP was not enabled.
Is there something else I'm missing for configuration with Unity Connection to support Single Inbox with Exchange 2003 SP2?
Thank you!
-rya

Hi Rya,
I just wanted to add my +5 vote for this great catch by Aaron (nice work "A")
If you are going to upgrade to Unity Connection 8.6
Check out this great doc from Saurabh for the refresh upgrade notes to 8.6.
https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen

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?

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

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 :)

Win 2012 AD for Exchange 2003

Hello there,
Our messaging system is running on Exch 2003 and we would like to upgrade our AD from Win 2003 to Win 2012. Does Exch 2003 support Win 2012 AD?
Would Exchange 2003 also support Win 2012 R2 as AD?

The dedicated Exchange forums are here:
http://social.technet.microsoft.com/Forums/en-US/home?category=exchangeserver
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

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

Account Lockout issue between Apple devices and Exchange 2003

I have been having an ongoing issue for a couple of months with a few different users Apple devices locking out their accounts in AD when they try to authenticate to ActiveSync. This doesn't happen every time they authenticate, it seems to be random,
while the rest of the time they have access to their email. It might occasionally happen with an Android, but not on a repetitive basis like this.
Primarily this has been four different iPads, running different versions of iOS, and an iPhone running the latest release of iOS 7. Other iPhones and iPads function without having the problem, including iPhones on iOS 7.
The user accounts in question are set to never have their passwords expire, but again, they aren't the only users that are set like this, and those other users, even with Apple devices are not having the same problem.
I used NetWrix to trace out the source machine, which is my Exchange 2003 server and times, and I've checked the W3SVC1 log file, and come up with the following as an example with identification details masked:
<internal IP>, <Domain\Username>, 4/30/2014, 8:10:04, W3SVC1, <ServerName>, <internal IP>, 15, 329, 3367926, 200, 0, GET, /exchange-oma/<[email protected]>/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplV50462*****/eb53cd5d5b9fcf40****************-20ef44,
As I was typing this, the owner of the iPad from the log file above came by my desk, so I asked a couple more questions. He's never had another iPad, it's a gen 1, and he's never updated the iOS on it. I know one of the other iPads in question
has the most up to date iOS, and the other one is brand new, replacing one that was broken, but the owner of that one had the same issue on a 3 year old iOS.
There is nothing special about the user accounts, no special privileges or restrictions.
Has anyone encountered this before? Exchange 2003, Server 2003 in a 2008 domain. Promotion to the 2008 domain was 2 years ago.

Hi Brian,
I am so sorry for the delay.
Do you have any progress by now?
Since there are lots of devices which use user accounts to log on, failed logon attempts on these devices could be the cause for account lockout.
If this issue persists, I suggest you refer to these troubleshooting articles below:
Troubleshooting account lockout the PSS way
http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
In addition, you can also get efficient support at Active Sync forum below:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy
Best Regards,
Amy

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
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.

OUTLOOK 2013 permission shared calendar Free/Busy doesn't work for some the users Exchange 2010 and Exchange 2003 that use outlook 2007/2010

Hello,
We are in coexitence organisation (transition Migration) Exchange 2003 sp2 and Exchange 2010 sp1.
Users in Exchange 2003 use outlook 2007 and outlook 2010
Users in Exchange 2010 use outlook 2007, outlook 2010 and outlook 2013.
Issue: users in Exchange 2003 can't open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
User in Exchange 2010 with outlook 2007 can't also open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
Is it normal ? or exist some configurations to do in order to coexist all thoses clients and servers ?
Thanks in advance

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

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.

Single Inbox Issue with Unity Connection 8.5 and Exchange 2003

Hello Unity Gurus,
I recently upgraded our Unity server to Unity Conenction 8.5. We are pressing hard to have unified messaging. However theres always problems it seems.
We have several 2003 exchange servers, two of the exchange servers split up our organization and one has half of the users mailboxes and the other server has the remaining half. So far the only way that I can get Unified messaging is if I create two separate Unified Messaging Services one for one half, the other for the other half.
This becomes a problem since now when I create the Unified Message account I have to know what server the user is on and the problem being is that I have 700 voicemail users ill have to look up. Not only that but, if our employees move from one site to the next and if the mailbox gets moved then I imagine most likely break unified messaging for that account.
I've read the install guide for Unity connection Unified Messaging and I understand that the second option is to have Connection to search for Exchange servers via Active Directory however, when I set that up and test it via unified messaging services I get an error " searching network...failed to locate domain controller via DNS. Failed to locate an exchange 2003 server."
DNS seems to work if I create single Unified Messaging Service and use the host name that way.
Anyone have any thoughts or found a work around to this issue?
Thanks,
Dan

We have 41 exchange UM services configured in Unity Connection on 10 clusters, each one to the 2003 exchange servers. This is the only way it will work for us, as e2k3 can not search for and find other exchange services. For 2010, it is able to search by AD domain and site name, and we only have one connector configured on each server to the e2k10 environment. I believe this is the way it works, and is difficult to manage but works. Just my two cents.

Mail and Exchange 2003

I am having a heck of a time getting Mail in Snow Leopard to work with Exchange 2003. Since Mail natively supports Exchange 2007 I have to use IMAP to connect to Exchange 2003. The problem I have is when Mail is running and communicating with Exchange it slows the server down to a point where it affects all other users connecting to Exchange. It causes long delays and Outlook displays a message stating it lost connection to Exchange and is waiting for a connection. If the user running Mac Mail closes Mail then the server is back to normal. I have seen other references to this in various forums however I am unable to find a fix. I tried configuring Mail to connect directly to Exchange via IMAP, and I have also tried using DavMail as a local mail gateway however Exchange slows down in both scenarios. What can I do?? The Mac user really wants to use Mail however I am close to the point of telling him it is not possible with Exchange 2003.

I'm having some kind of related problem, not slowness but connection to Exchange.
I have been successful in connecting my Iphone, and it works great with calendars and address book, but no way to get Mail to connect...
Any body who could help me would be more than welcome, as I feel the problem being around domain or something.
What is weird is that on the Iphone the number of parameters to set is limited to 5 plus description:
Email
Server
Domain
User
Pwd
Description
Plus a toggle switch for SSL
In mail
Description : Ok
Address : Ok
Complete name : I think I know
Internal server :
External Server :
User ID : Ok
Pwd :
Then I advance
External server Path: ???
Internal Port:???
External server Path : ???
External Port :???
Then in "sending server"
Port: ??
User ID : Ok
Pwd : Ok
This a bit complex and I really do not understand why I can make it work on an Iphone seamless in a couple of minutes, and after hours of sweating this thing refuses to work on Snow Leopard.
Many Thanks in advance.
PS : options are translated from French that's why they might not be the exact naming in Mac OS X 10.6.3 in English.
Message was edited by: Gillesb15

Ipad and exchange 2003 downloads all email every time and is very slow. We get "no sender" dated 1/1/70 during process.

Ipad has become very slow to sync with exchange 2003. suspect IOS releases have IPad beyond older exchange software but need to understand why sync email is so slow and seems to re-download entire mailbox every time sync runs. Android phones do not have the issue, only ipad. ipad are up do date, mix of 1,2 and new

i have two iPads running different mail, one is my work gmail, one my personal mail. Upgraded my personal mini iPad to iOS 7.1.2 and started getting emails dated 1/1/1970, no sender no content coming I daily, the disappear after a few seconds.
on my other work iPad I haven't upgraded yet am still on iOS 7 but it stopped syncing my email on Friday. I generated a new google password and entered it and when my mail came in there were many emails dated 1/1/1970 with no sender or content, again they disappeared a few seconds later.
What's going on with the mail?

AD DS 2012 R2 and Exchange 2003

Similar Messages

Maybe you are looking for