Decommissioning Exchange 2003 Server

Follow the Exchange Deployment Assistant to the letter and you will not have issues.
http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspx
(after the migration it shows you how to decommission it properly.)

Hello All,
My Exchange server setup is in coexistence mode (1 Exchange 2003 server entp and 2 Exchange Severs 2010 DAG is in place)
only 2 mailboxes are left on Exchange 2003 and will be moving them soon.
So I wish to know the what all precautions I should be take and what all action items are there.Recommended link will do
regards
Atul A
This topic first appeared in the Spiceworks Community

Similar Messages

Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003

I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Set-PublicFolder
Failed
Error:
You must specify a value with the Replicas parameter.
OK
Not sure where to go with this error. Could someone point me in the right direction?
Thank you,
Wade Harris

Hi,
For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Removing the last Exchange 2003 server from an Exchange 2010 organization

We're in the process of decommissioning our last Exchange 2003 server, I have proceeded through the steps in the Microsoft guide on how to do this and have deleted both the Mailbox and Public Folder stores, removed the RUS policies for Domain and Enterprise.
All mailboxes and public folders are now homed on the new Exchange so nothing resides on the old Exchange 2003 server.
I have today inserted the Exchange 2003 media into the Exch 2003 server and chosen the remove action, but it keeps telling me;
'The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Remove" because: - One or more users currently use a mailbox store on this server.
I checked the server by searching ADUC and also checked this KB article http://support.microsoft.com/kb/279202 and nothing shows up.
I also checked this article on someones blog but no such luck http://smtp25.blogspot.co.uk/2007/04/having-trouble-to-uninstall-exchange.html
However someone made a comment that the used an ADSIedit query (&(objectCategory=user)(msExchHomeServerName=*)) however I am unsure how to do this in ADSI.
Any advice would be gratefully received.
Thanks!

Fantastic post ... thank you so much!
I found three active directory users account using that search which never had a mailbox assigned to them. I removed the exchange attributes from each account and the uninstall proceeded
flawlessly!

Decommissioning Exchange 2003 after Office 365 Migration

Hello,
My company recently migrated from Exchange 2003 to Office 365 and are working on decommissioning our on-premises Exchange 2003 server. We believe everything is ready to go, however this Microsoft article: http://help.outlook.com/en-us/140/ff959224.aspx#nextsteps has
a big Caution box warning of "unintended consequences" and recommending I contact Microsoft Support:
I've tried my Office 365 support options, but they only tell me that Exchange 2003 is no longer supported and they can't help me, despite the fact that I'm trying to remove it, not maintain it. So
I'm allowed to pay for a new service, but shouldn't expect assistance in safely moving from my old service...
Regardless, they directed me here, so I was hoping someone might be able to advise about what these "unintended consequences" actually are so I can feel fully prepared to decommission.
Thanks in Advance,
Jim

Hi,
After you’ve verified that all e-mail is being routed directly to the cloud-based mailboxes, completed the migration, and no longer need to maintain your on-premises e-mail organization or don’t plan on implementing a single sign-on solution, you can uninstall
Exchange from your servers and remove your on-premises Exchange organization. For more information, see the following:
How to Uninstall Exchange Server 2003
http://technet.microsoft.com/en-us/library/bb125110(EXCHG.65).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Changing the Default OAB from an Exchange 2003 server to an Exchange 2010

I am in the process of decommissioning my old Exchange 2003 servers. All mailboxes have been moved over to Exchange 2010. I already have OABs and Public Folders created on the Exchange 2010 servers. Since I see the "Default Offline Address List",
which is pointing to my old Exchange 2003 server and the Default OAB is set to "True", can I just make an existing Exchange 2010 OAB the "Default OAB"? I have read that I have to perform a move on the "Default Offline Address List"
OAB. Is this required?
thanks
Noe

Configure the Exchange 2010 mailbox databases to use the Exchange 2010 OAB, and leave the Exchange 2003 databases alone. You can delete the old OAB just before taking the Exchange 2003 servers out of production. The "Default" setting
means the OAB is the one that's assigned by default when you create a new mailbox database, so yes, you should set that.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Office 365 Deployment w/Decommissioned Exchange 2003 environment

Hello,
I'm having an issue creating Office365 mailboxes. Here's my situation:
In 2011 we we migrated off of an on-premise Exhange 2003 server and on to Google Apps (Gmail). To my knowledge the on-premise Exchange 2003 server was fully decommissioned and removed from our network. Now we're try to move from Google Apps (Gmail)
to Office365. I've set up AD synchronization and all my AD accounts synchronize as expected. However, only some of my synchronized accounts are provisioning mailboxes correctly. After some troubleshooting on the Office365 community we were
able to narrow down the issue: http://community.office365.com/en-us/f/156/t/252194.aspx. It appears that the only accounts that are successully provisioning mailboxes are accounts that DID NOT previously have a mailbox associated on the on-premise
Exchange 2003 server...Accounts that DID hold a mailbox on the on-premise Exchange 2003 server are NOT being successfully provisioned with an Office365 mailbox. My understanding is that this is actually expected functionality...Per MS support techs:
If an AD account has attributes indicating an on-premise Exchange server, then Office365 will not provision a mailbox until the on-premise mailbox is migrated. The issue I have is, I do not have an on-premise mailbox to migrate or an on-premise Exchange
server at all.
My on-premise Exchange 2003 server no longer exists. What attributes do I need to remove and/or reset on my accounts for Office365 to be able to provision a mailbox correctly?
Thank you in advance!

Hi,
What’s the error message do you receive when trying to create the mailbox?
You can check the user’s AD properties by:
ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"
Here is the detailed steps for getting the
distinguishedName of a user:
a. Run the Adsiedit.msc from a command prompt.
b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
c. Right click on ”CN=the problematic user name”, click “Properties”.
d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.
Thanks,
Simon Wu
TechNet Community Support

Trying to recover a mailbox from an old Exchange 2003 server

I still have a 2003 server in my environment but all functions and mailboxes are on Exchange 2010. The only reason the 2003 server is still around is for the off chance of requiring a restoration which has now come up. I have successfully restored a
mail store to a recovery storage group but I am unable to export mailboxes from it using exmerge.
I get the following error:
[10:16:16] Copying data from mailbox 'Jacques Legare' ('LEGARE') on Server 'MAIL-SERVER' to file 'C:\TEMP\LEGARE.PST'.
[10:16:16] Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0x8004011d)
[10:16:16] Errors encountered. Copy process aborted for mailbox 'Jacques Legare' ('LEGARE').
I have read many, many articles regarding the requirement for “send as” permission. I have granted send as permissions to several different domain accounts and local accounts on the Exchange server but I get the same result with all of them.
It looks like the problem may be because the mailbox no longer exists on the Exchange 2003 server.
So what do I have to do to recover this mailbox? Can I create a mailbox for this user on the 2003 server without messing up his the mailbox on the 2010 server? Instead of restoring to the recovery storage group, should I restore and overwrite the original mailbox
store? Again, will that mess up anything with the 2010 server?

0x8004011d is permission related Error.
Refer to the link below and download EXMERGE guide which has complete procedure documented.
https://gallery.technet.microsoft.com/office/Guide-to-Use-Exmerge-to-fd00af49
If the mailbox that need to be restored has to be extracted from RSG is already moved to Exchange 2010 then you will not be able to run exmerge against it.
You might have to update the attribute MsExchOrigMDB on the RSG to point to Exchange 2010 Database where the mailbox is now located.
even this information is enclosed in the EMERGE Guide.
Revert back for any queries/outcome.
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!!

SAP Internet Mail Gateway for MS Exchange 2003 Server

Hi,
Has anybody successfully configured the IMG to work with MS Exchange 2003?
We have our 4.6C currently configured to talk to Exchange 2000 through SXC
Note 594428 - SXC: Exchange 2003 Server is not supported
Solution
R/3 Basis Release 3.1I to 4.6D:
Use IMG 4.6D and sendmail instead of the SXC (see note 101573), or
Upgrade your SAP system to Web Application Server (WAS) 6.10 or later and then use the SMTP plugin.
We only use outbound mail from SAP and this is sent to intranet users only, we are not planning on upgrading for a at least a year and would like to avoid installing another mail server.
Note 363154 - Internet mail gateway: use other MTA than Sendmail
This note suggests that any MTA (Mail Transfer Agent) can be used so long as it can be called from the command line, Exchange is an MTA, anybody now how to do a command line call for Exchange?
I have read the documentation
http://help.sap.com/saphelp_46c/helpdata/en/0c/39c93589c5ab53e10000009b38f839/frameset.htm
Jasper

hi,
we are in the process of configuring the Internet Mail Gateway on R/3 4.6c on Unix platform.
I have created the RFC Destinations in SM59 and also checked the Test Connection and its working fine. I then did the Unix configuration and went on to the check whether the configuration was successful in SO01 by sending a sample text message to my company's mail address. but i did not recieve any mails on my Microsoft Outlook, instead the count under the errors column increased by one.
on checking the status for the sent message in SO01, its saying "No Delivery to [email protected](for reason, see long text)... but there's no long text either...
Can anyone please let me know the reasons for it and it would also be really helpful if someone can let me know whether i have missed any configuration settings.
Also, can someone send the list of parameters that are to be entered for the Unix configuration under mlsomadm mailgw.ini, so that i can verify whether i have entered the parameters correctly....
Kindly revert back at the earliest...
Thanks & Regards
Manicks

Creating email address using Microsft exchange 2003 server

Hi. Have a MacBook Pro 2008. I need to add my new company email and we are having trouble creating it on my Macbook Pro. The pepole here only use PCs and they have a Microsoft exchange 2003 server. They are suggesting I buy Microsoft Office for Mac because of Outlook? Is this the only solution or is there another one? Thanks.

I'm not using IMAP. I've tried that before. This time around I'm using the Exchange Account connection. I recall seeing where you could select to delete email from the server with IMAP, but I can't find the same or similar setting in the Exchange settings.

NO INCOMING POP MAIL from exchange 2003 server.-

My university uses a exchange 2003 server for mail and pop access is enabled on all professor accounts. Since a couple of weeks ago I had no problem at all with my university mail account on apple mail, although I had to use :
incoming mail server: "mail.myuniversity.edu.do"
user: "DOMAIN\username"
Password: "mypassword"
Authentication: Password
After december the 5th I'm not getting any mail at all, even thou the activity monitor says "incoming messages.... 83 of 83" but no message shows up on the inbox. I have noticed that the number keeps growing (84, 85, 86...) but still no message in my inbox.
the weird thing is that I'm able to see my university mail in my iphone using the synced account settings in Itunes. I thought it was a problem of my machine I have made a clean format and reinstall of osX 10.6 with the 10.6.2 combo update. I did not transfered files nor configuration, just copied my documents and reconfigured mail from scratch. I did not imported any message. After all that, the problem persist.
I have used Connection Doctor and everything looks ok. The Detail window shows this:
******************************** BEGIN OF LOG ********************************
CONNECTED Dec 25 20:37:28.201 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
CONNECTED Dec 25 20:37:28.216 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
READ Dec 25 20:37:28.648 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7638.1 (SvrMailAdm.rsta.pucmm) ready.
WROTE Dec 25 20:37:28.656 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
USER RSTA\sterlingjimenez
READ Dec 25 20:37:28.682 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
220 mail.pucmm.edu.do Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Fri, 25 Dec 2009 20:38:10 -0400
WROTE Dec 25 20:37:28.695 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
EHLO [10.0.1.33]
READ Dec 25 20:37:29.012 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK
WROTE Dec 25 20:37:29.019 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
PASS ***********
READ Dec 25 20:37:29.030 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
250-mail.pucmm.edu.do Hello [200.88.1.167]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
WROTE Dec 25 20:37:29.036 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
AUTH LOGIN
READ Dec 25 20:37:29.391 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK User successfully logged on.
WROTE Dec 25 20:37:29.397 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
QUIT
READ Dec 25 20:37:29.436 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
334 VXNlcm5hbWU6
WROTE Dec 25 20:37:29.447 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
UlNUQVxzdGVybGluZ2ppbWVuZXo=
READ Dec 25 20:37:29.823 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7638.1 signing off.
READ Dec 25 20:37:29.927 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
334 UGFzc3dvcmQ6
WROTE Dec 25 20:37:29.954 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
READ Dec 25 20:37:30.410 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
235 2.7.0 Authentication successful.
WROTE Dec 25 20:37:30.425 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
QUIT
******************************** END OF LOG ********************************
Can Anyone HELP ?
I'm Out of ideas.
Best Regards,
Sterling Jiménez R.

Hello metalcraft,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
OS X Mountain Lion: Cannot connect to Exchange server in Mail after upgrading
http://support.apple.com/kb/TS4363
If you have issues connecting to the Exchange server or don't know what server addresses to use, contact your Exchange administrator or IT administrator.
Best of luck,
Mario

Installing certificate for access to exchange 2003 server

My exchange server requires that a certificate be installed to enable remote access. Since the iPhone does not support disk mode like the iPod there appears to be no way to install the certificate. Are there any workarounds?
iPhone Windows XP

Whole migration from Exchange 2003 server to Exchange 2010 server has been done and applied 3rd party SSL certificate on Exchange 2010 servers also.
Hi,
According to your description, everything about exchange 2010 is ready.
Why don't you follow the mail flow as below?
Internet Emails > Ironport > Exchange 2010 (smart host) > Exchange 2003 servers
Please refer to the following article:
Move Internet Mail Flow from Exchange 2003 to Exchange 2010
Configure mail flow by using one of the methods listed below depending on the needs of your organization. This will enable Internet message flow through your Exchange 2010 Hub Transport servers.
Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway
Configure Internet Mail Flow Directly Through a Hub Transport Server
Remove the SMTP connector in Exchange 2003 that is used to handle Internet mail. Your account needs to be a member of the local administrators group and a member of a group that has had the Exchange Administrators role applied at the administrative group
level.
In Exchange System Manager, expand the Organization node, expand
Administrative Groups, expand <AdministrativeGroupName>, expand
Routing Groups, expand <RoutingGroupName>, and then select
Connector.
In the right-hand pane, right-click the connector you want to delete and select
Delete.
Click OK to confirm the deletion.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2003 server email

The company I work for uses MS Exchange 2003 Server for its email. iPhone with either iOS 4 or iOS 5 does fine synching with Exchange 2003. I would like to access my work email on my Mac. Microsoft says that the only way to do this is to buy MS Office 2008 Home Business Version, and as far as I can tell, this is correct. Does anybody know of a workaround, perhaps syncing my email from iPhone to Mac. Thanks.

KiltedTim wrote:
My bad. I seem to recall, though setting up mail to talk to our Exchange 2003 server before we migrated over to Exchange 2010 this year. My memory of the timing must be off.
There's always OWA in a pinch.
Not for Exchange 2003 users, /OWA came in with 2007 sp1 and all that, before that it was /exchange. Everyone is dropping support for E2003, even Microsoft (see Outlook 2011), Entourage is actually a good client, different, but better than it looks. You can also use 3rd party connectors, DavMail is a common choice but I found it close to incomprehensible, and then unreliable (especially with contacts)

Phones cannot connect with mailboxes homed on a remote Exchange 2003 server.

Lost our frontend server and setup new services on an existing Exchange 2003 server.
The now current Frontend server is one of 3 Exchange 2003 servers.
The Frontend server and one more Exchange server are on the same subnet and the 3<sup>rd</sup> is at a remote location.
It is this remotely located Exchange server that users with phone cannot access their mailboxes homed on that server.
This is what is working now.
All remoter Outlook clients can connect via rpc over http to all Exchange 2003 servers
Phones can only connect to mailboxes homed on the Exchanged server located on the same subnet as the Frontend server.
Can you offer any direction?
As a business decision, we are gearing up to put new Exchange 2013 servers into a new forest and migrate the users.
we are now looking at rehome affected users' mailboxes to the exchange server that is accepting the phone connections.
Thank you,
Stephen

Hi Stephen,
In your case, I recommend you move the problematic mailboxes to the Exchange server that is accepting the phone connections for troubleshooting.
About the steps to move Exchange 2003 mailboxes, here is a kb for your reference.
Moving mailboxes in Exchange Server 2003
http://support.microsoft.com/kb/821829
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Errors Decommissioning Exchange 2007 Server

We are attempting to decommission an Exchange 2007 Server (single server). We have already gotten 2010 set up, installed, mailboxes moved and public folders moved. We went through and removed the replicas on the old server as well as removing the mailbox
database and public folder database.
From this point we are attempting to Uninstall Exchange 2007 using either the Wizard or through cmd using setup.com /mode:uninstall after navigating to the Bin folder in the Exchange server. Each time however, we get the same error regardless of how we are
doing it.
We uncheck all roles, hit Next, and it fails during the Readiness Check within 10 seconds on each role (Mailbox, Client Access, Hub Transport) each time saying: 'An error occurred while running the test. The Computer may be out of Memory, or the XML files
have been modified. Parameter name: ConfigurationFileLocation'
I've gone through using ADSI Edit and removed the server from the Configuration>Services>SiteDomain>Administrative Groups>Exchange Administrative Groups>Servers
and it was none existent in the Databases section.
Even after all of these steps I'm still getting the error about the memory or XML file issue. Is there a way to replace the XML files with 'clean' ones or a way to repair the existing ones? I'm just simply wanting to uninstall it at this point.
Thanks!

Hi,
From your description, I would like to clarify the following things:
1. It is not recommended to uninstall Exchange server in ADSIEdit.
2. The above error indicates that one of the xml files is corrupted, you need to re-download it for troubleshooting.
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Disable link state updates Exchange 2003 server

Good Day ,
Current Environment: Exchange 2003 SP2 server and one Exchange Front-End Server
What I will have: Two Exchange 2010 servers with DAG
After running the Exchange Pre-Deployment Analyzer I see the message :Before introducing Exchange Server 2010 into this topology, the 'SuppressStateChanges' configuration parameter should be set to '1' on server
server.com. This parameter is essential if you plan to create multiple connectors to the dedicated Exchange 2010 routing group.
So I must do it ?if yes is safe for my exchange 2003
Many Thanks
Regards
e

After doing the Pre_Deployement Analyzer :
Found 1 Active Directory domain(s) containing Exchange servers: companydomaine :
Found 1 Active Directory domain(s) in the forest. :
Found 1 Active Directory site(s) containing Exchange servers: Terminal. :
Found 1 Active Directory site(s) in the forest. :
Found 1 Active Directory tree(s) in the forest. :
Found 1 administrative group(s) in the organization. :
Found 1 DNS domain(s) containing Exchange servers: companydomaine.com. :
Found 1 routing group(s) in the organization. :
Found 148 pre-Exchange 2010 mailboxes in the organization. :
Found 2 Active Directory server(s) running Windows Server 2003 Service Pack 2. :
Found 2 Active Directory server(s) running Windows Server 2008 R2. :
Found 3 server(s) running Exchange Server 2003.
so that I understand I have just one routing group ?
Regards
e

Decommissioning Exchange 2003 Server

Similar Messages

Maybe you are looking for