?
Solved

Remove Exchange 2007 from Server Installation

Posted on 2014-10-19
3
Medium Priority
?
116 Views
Last Modified: 2014-11-02
Hi Guys,

We recently upgraded our Exchange 2007 to Exchange 2013.  (Separate server)
The Exchange 2007 server is still part of the installation.

I assume all the roles were transferred correctly.  Switching off the Exchange 2007 server, Exchange 2013 seems to be functioning as expected.

I am in the process of removing Exchange 2007 from the installation.  Is there a single-test or check that I can run to confirm that all functionality is now residing with Exchange 2013?  (We can't afford any downtime after the removal)
0
Comment
Question by:Rupert Eghardt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 27

Assisted Solution

by:☠MAS☠
☠MAS☠ earned 750 total points
ID: 40389900
Switch off the server for couple of days before uninstalling and check for any error in server and issues from clients
1. Try to check mail flow. Both internal and external.
2. Check public folder files if you have any.
3. Check for system mailboxes and user mailboxes using the below command
Get-Mailbox | FT NAME,SERVERNAME

Open in new window

Get-Mailbox -ARBITRATION | FT NAME,SERVERNAME

Open in new window

4. Make sure Outlook anywhere enabled on all PCs.
5. Try to download Addressbook (Though it is a not files as in Exchage2007, check to be safe).
6. check you internal applications (if any apps using Exchange server).
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 750 total points
ID: 40390106
To add onto what MAS has already recommended in point 6, you can check for this in the SMTP protocol logs.

Client explains it in his blog here.
http://clintboessen.blogspot.com/2009/06/exchange-2007-smtp-protocol-logging.html

Ultimately, these logs should be empty. If not, see what IPs are populating them.
0
 
LVL 19

Expert Comment

by:suriyaehnop
ID: 40391144
Personally, i would keep the Exchange 2007 shutdown for 2 or 3 months and let user using Exchange 2013.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Sometimes clients can lose connectivity with the Lotus Notes Domino Server, but there's not always an obvious answer as to why it happens.   Read this article to follow one of the first experiences I had with Lotus Notes on a client's machine, my…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question