Exchange 2003 to Exchange 2007

Hello,
I have inherited a network where the transition was not complete. It Consists of Exchange 2003 and Exchange 2007 Server. Currently all the mailboxes are moved to the Exchange 2007 Server, now I have to remove the
exchange 2003 server and related to that I have few Question to be asked.
1) Exchange 2003 server is also having Active Directory Installed in the Server, is it possible to remove the exchange server without removing the active directory ?
2) Is it possible to shutdown all the exchange 2003 services and creating the send and receive connector on the exchange 2007 server to route the emails. I will delete the old exchange server when every thing works fine with exchange 2007.
3) Currently Exchange 2003 is having public ip and people cannot access there mailboxes as they are located on exchange 2007 how can route people to new exchange 2007 server keeping the public ip on the exchange 2003 server.
4) Do I really have to purchase the certificate in order to run the exchange 2007 server ?
http://www.arabitpro.com

Hi,
I agree with Eric and Andres's suggestion. Before removing your Exchange 2003, please make sure the following points have been successful:
1. All mailboxes have been moved to Exchange 2007.
2. All Public folders are moved to Exchange 2007.
3. OAB generation has been pointed to Exchange 2007.
4. Mail flow is routing through Exchange 2007 transport server.
5. All services (OWA, ECP, Availability service, autodiscover, OOF, OAB etc.) are working well in CAS 2007.
If everything is working well in Exchange 2007, then we can remove the Exchange 2003 from the organization.
Winnie Liang
TechNet Community Support

Similar Messages

Cannot Move Mailbox from Exchange 2003 to Exchange 2007

Hello,
I am migrating exchange 2003 to Exchange 2007 and have moved almost all the mailboxes without any issue, but there are some mailboxes which are not being moved since they are giving me the below error.
Error:
Error was found for John Doe ([email protected]) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
Initially I found that the account was disabled from Active
Directory so enabled it but and also replicated the active Directory but still the problem is there, its not hidden in the GAL aswell.
http://www.arabitpro.com

Thanks everybody .. I have solved the problem myself.
To resolve this issue I had to give the account "SELF" permissions for "Associated external account". If the user does not have these
permissions to its own account it is unable to set the msExchMasterAccountSID attribute for the disabled account causing the error. By setting this permission on the disabled account, it allows it to mark the msExchMasterAccountSID attribute.
To do this follow this procedure:
1. In the Active Directory Users and Computers snap-in, on the View menu, click Advanced Features.
2. In the Exchange Advanced properties of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one
that has the Associated External Account permission.
4. If no account has this permission, grant the SELF account Associated External Account and Full Mailbox Access permissions.
https://support.microsoft.com/kb/278966?wa=wsignin1.0
http://www.arabitpro.com

Server 2003 R2 DC migration to 2008 R2 worked? but exchange 2007 has stopped

Hi everyone,
This is a single DC running on Server 2003 R2 which I migrated to a fresh install of Server 2008 R2. This appears to have worked without issue. DNS is working dcdiag and netdiag didn't report problems.
When I demote the 2003 server however Exchange 2007 stops working. It appears that it is still looking to talk to the 2003 server based on this
EVENT ID: 2012 All DC Servers in use are not responding DC.mydomain.com
Can anyone help fix this issue pls. I cant find where Exchange has stored the old domain name.
TYIA

TY both for taking the time to reply.
I have gotten to the problem. The fact you both pointed me to event 2080 was instrumental in guiding me down the right path. Once I read this MS article I could see the new DC was missing
the SACL rights. This was a tad frustrating as I had previously checked that Manage auditing and security log was correctly configured in the Default Domain Controllers Policy, was applied to Domain
computers and the new server was in the correct container.
However when your up to your ass in a croc filled swamp you sometimes forget the odd thing; I didn't run RSOP, if I had at the time, I would have never have had to post for help. Yes you guessed it the policy wasn't enabled!! A quick enable and gpupdate
/force and all was well.
Still, always the optimist, I learned about event 2080, and uncovered and fixed problems with the clients servers where they had ghost nics....
Just to clarify in case others read this post.
This wan't SBS
It was a single DC domain running on server 2003 R2 x64
Exchange 2007 running on a seperate server 2003 R2 x64.
The domain name didn't change. What I meant was the new DC had a different name
the New DC is a fresh install of server 2008 R2, IPv6 is enabled
The old DC had adprep /forestprep then adprep /domainprep run on it
The 5 fsmo roles were moved from the old DC to the 2008 DC
Just need to move DHCP and other bits n pieces and job done :)
Thanks for the help

Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003

Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
on 2003?
I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported". Something I'm missing here?

These things marked as answers are not answers.
I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
"Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
be recovered only on Windows Server 2008."
This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet). I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
Basically how I do it is like this:
Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server. Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation). Install the relevant windows updates.
Install Exchange 2007 SP3 using setup /mode:recoverserver Install the update rollup.
Copy the storage groups into the relevant folders on the new server and mount them. Migrate any relevant certificates (e.g. for ActiveSync).
Obviously then check it all over with the diagnostic tools and check it with EXBPA. The backups are obviously totally different, but really I think you should be using DPM anyway.
To me that was pretty easy to do, to be honest. About 1.5 on a scale of one to ten. Basically install it, recover it, copy over some files and mount them.
Seriously on a halfway decent server I've done it in under an hour.

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

MS Edge services wont start on exchange 2007 installation on a server 2008 r2 in a 2003 domain

Hi
I had a previous installation of exchange 2007 vanilla that I had to delete because of some errors on the nic card in a 2003 exchange environnement migration preparation. I've build a brand new 2008 R2 and i'm trying to install a new exchange 2007 SP1. When
the service edge try to start it seems that it doenst want to get install. I've disable IPV6 from the nic and still the same problem. Is there something that need to be removed in the AD because of my previous 2007 installation ?
thanks

Hi,
I find this for your reference:
I would install Exch 2007 with SP3 slipstrreamed. The download for SP3 is the full installation of Exchange. The fact that Exch 2007 with SP1 is not R2 compatible, you will run into problems.
http://www.microsoft.com/downloads/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en
"Clean installations of Exchange 2007 SP3 on a new server are possible by using this download in the same manner as you would install Exchange 2007 RTM, Exchange 2007 SP1 or Exchange 2007 SP2.
More details in the following similar thread:
Exchange Server 2007 SP3
http://social.technet.microsoft.com/Forums/en-US/03e7cabd-a002-4920-b2f7-d6d1dd61c76f/exchange-server-2007-sp3?forum=exchangesvrdeploylegacy
Thanks
Mavis Huang
TechNet Community Support

Unity 5 with MS Exchange 2007 and Windows Server 2003 Ent w/ SP2

Hello,
We have Unity 5 with Exchange 2007 SP1 on Windows 2003 SP1 Enterprise server. We want to upgrade Exchange to SP2 or SP3 but I could not find enough information, may not have looked in right places.
Does anyone have Unity with Exchange 2007 with SP2 or SP3? has anyone experienced issues with such upgrade?
Thanks,
Paresh.

Paresh,
Here's what you need:
Recommended Service Packs—Message Store
Revised October 25, 2010
•Exchange 2010 Service Pack 1
•Exchange 2007 Service Pack 3
For support information, refer to the "Support Policy for Microsoft Service Packs and Updates" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
I pulled this straight from a Cisco document so you could be sure that you are moving to the latest recommended SP for Exchange which is SP3. I have clients running this SP without issue.
Hailey
Please rate helpful posts!

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Mailboxes are moved to Exchange 2007 but still appearing in exchange 2003 With Red Cross

Hello,
I am moving mail boxes from exchange 2003 to exchange 2007 sp1. Excahnge 2007. After the mailboxes
are moved successfully to exchange 2007 i can still see some mailboxes in exchange 2003 with red mark on them. Please check the attached snapshot.
http://www.arabitpro.com

Followed this Kb article and finished
http://support.microsoft.com/kb/930363
http://www.arabitpro.com

How to change domain name on Windows 2003 running Exchange 2007

Hi all,
I have a windows 2003 server running Exchange 2007. I am wanting to rename the domain, however when I search the web for the process to perform a rename of the domain I see "The domain rename operation is not supported in Microsoft Exchange Server 2007".
How can a domain name be changed? http://technet.microsoft.com/en-us/library/cc781575%28v=ws.10%29.aspx
The server runs active directory, dns, dhcp, and Exchange 2007.
This change is being inspired by the change with SSL certs where internal addresses like .local will no longer be supported in the third party certificate registrars. Recently we renewed our cert and did not include the .local URL. Now the internal
systems are getting warnings about the cert. I tried generating an internal self signed cert but it seems only one cert can be valid with exchange 2007 running on windows 2003. Thus the internal cert replaced the external cert and allowed
the internal systems to run without complaining about the cert but the external access was causing warnings. I reversed back to the third party cert. This cert has company.com and mail.company.com and autodiscovery. I believe if I rename
the server to server2.company.com the autodiscovery will allow the server2 to be mapped to company.com and the cert will be valid for internal clients.
Do I have this correct? Are there errors with what I have found so far?
Any suggestions about how to solve this issue short of getting a new server? How can I rename the domain?

Hi,
As you mentioned, the domain rename is not supported in Microsoft Exchange Server 2007.
About your question with certificate, we can change URLs to xxx.domain.com. More details about this workaround, please refer to:
https://support.microsoft.com/kb/940726?wa=wsignin1.0
Note: please make sure the same name with certificate.
Additional, Microsoft do not recommended to install Exchange server on a DC. I suggest install Exchange server on a member server. More details to see:
Installing Exchange on a domain controller is not recommended
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller(v=exchg.150).aspx
Best regards,
Allen Wang

Exchange 2007 on Server 2003 - Powershell

Hi all,
i need to upgrade Powershell on one my servers from version 1 to version2. The box is running Server 2003 R2 with Exchange 2007 SP3 on it.
If i install pwoershell 2 how does it effect the exchange shell. is the exchange shell updated as well?
Thanks

Hi PATEL,
Yes, when you upgrade PowerShell on your server, the exchange shell is updated as well.
You can refer to the following article to understand more details about Exchange shell:
Overview of Exchange Management Shell
In Microsoft Exchange Server 2007, the Shell consists of a Windows PowerShell host; a Windows PowerShell snap-in, which contains all of the Exchange cmdlets; and some additional custom scripts. Loading all three components enables you to run Exchange cmdlets
on the Exchange server you opened the Shell on.
When you open Windows PowerShell on a computer, you create a local session. In simple terms, a session is an environment in which Windows PowerShell runs. Cmdlets, variables, and other Windows PowerShell components within the same session can share data
with each other. In Exchange 2007, cmdlets are always run in the local session on the local Exchange 2007 server. Even if you change an object that resides on a different server, the cmdlet is always run on the local Exchange server.
Best regards,
Niko Cheng
TechNet Community Support

Outlook 2013 Exchange 2007 and 2003

I have a client who has Outlook 2013. He needs to connect to a 2007 server and a 2003 server . I have not issues with connecting to the 2007 server. What would be the best way to connect the 2003 server? I have tried connecting the domain directly
but I get an error about setting up the ost file. The system connect to the 2007 domain.
Should I use pop3 or imap to connect? Can you send me an article for configuring the server for either of these?
Thank you for your help.
BW
Bonnie Whalon

Hi,
Outlook 2013 is not supported on Exchange 2003.
Please refer to the following article:
System requirements for Office 2013
Specific requirements for Outlook 2013
Component
Requirement
For integration with Exchange
Be sure to connect Outlook 2013 to the supported versions of Exchange: Exchange 2007, Exchange 2010, or Exchange Server 2013. Outlook 2013 is not
supported on Exchange 2003.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2007 setup, transitioning from Exchange 2003

Hello Exchange Experts,
I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
Thanks in advance!
James

Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role. The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.
Thanks for your input.
James
Thanks Ronnie for your input! Issue resolved

Cross Forest Migration from Exchange 2007 to Exchange 2013

Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
Muralee

Hi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Migrate from Exchange 2007 to Exchange 2013.

Hi All,
Need some advised here,
I am about to migrate Exchange 2007 with Windows Server 2003 to Exchange 2013 with Windows Server 2012 R2.
Which one should I migrate first? Windows Server or Exchange?
I tried to search it, i am a bit confuse with some of the answer. If someone can give some ideas, it will be great.
Thanks,

I'm not really sure what you are asking here. If you are asking here. I think you need to upgrade your Domain Controllers AND Exchange to 2012R2 and Exchange 2013.
I'm going to assume that they are going to be different servers. I would probably do the Exchange Migration first (assuming that you already at a supported level for Exchange 2013 https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.150%29.aspx)
Also, before you actually make the change to your Domain Functional level, take a look at this blog post.
http://blogs.technet.com/b/exchange/archive/2015/02/13/considering-updating-your-domain-functional-level-from-windows-2003-read-this.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange 2003 to Exchange 2007

Similar Messages

Maybe you are looking for