Exchange 2010 sp2 after patching issue

I have an issue after patching my exchange 2010 environment. I ran all the updates on the  3 servers. I confirmed that all updates installed successfully and after a series of test I determined that mailflow is working and all databases are mounted. My only problem is


Server           : server1
Check            : ClusterNetwork
CheckDescription : Checks that the networks are healthy.
Result           : *FAILED*
Error            : Node 'server3' has a network interface that is down. The IP address is ''. Current
                    state is 'Failed'.

Identity         :
IsValid          : True

This message appears in the system section of event viewer

Cluster network interface 'server3 - LAN-NIC1' for cluster node 'server3' on network 'Cluster Network 1' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

[PS] C:\Windows\system32>ping

Pinging with 32 bytes of data:
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

I validated that the cluster test ran successfully on all components and pinged test passed

Mail flow runs fine and tested.
Mapi connectivity runs fine
When I run the cluster manager there are no red or yellow signs
Inside of the cluster manager under network 2 it does list the card and down on network 1 it is up.
I can RDP to the IP address.

However, when I run the command I have above test-replicationhealth or view this info under database availability tab under the mailbox icon at the organizational level the ipv6 address appears and only for this IP address does it state that it has failed.
Who is Participating?
AmitConnect With a Mentor IT ArchitectCommented:
Give a try. 99% issue fixes with a reboot.
AmitIT ArchitectCommented:
Can you run test-servicehealth on all server.
techdriveAuthor Commented:
All 3 servers do not have any servers that have services that are not started.

Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeIS, MSExchangeMailboxAssistants, MSExchangeMailSub
                          mission, MSExchangeRepl, MSExchangeRPC, MSExchangeSA, MSExchangeSearch, MSExchangeServiceHost
                          , MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeAB, MSExchangeADTopology, MSExchangeFBA, MSExchangeFDS, MSExchangeIMAP4,
                           MSExchangeMailboxReplication, MSExchangePOP3, MSExchangeProtectedServiceHost, MSExchangeRPC,
                           MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost, MSExchangeTranspo
                          rt, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

AmitIT ArchitectCommented:
Can you reboot the server for which it is showing error and test-replication again.
techdriveAuthor Commented:
So is rebooting the server the fix...Your final answer.?
techdriveAuthor Commented:
kicking myself for all that work and research I did.
AmitIT ArchitectCommented:
Did reboot fixed or not? Also note SP2 is very old. You should upgrade to SP3 RU2. Below are the steps, might help you to do smooth upgrade

Steps Upgrading Exchange 2010 SP1 or SP2 to SP3:

My Lab Setup: 2 node Multi-role server with DAG.

1) Upgrade the schema for Exchange 2010 SP3. If you have Enterprise and Schema Admin rights, setup will do it automatically, however if not, then AD team is required to perform this task.

Purpose of this Schema Update:

In Order to have the Exchange 2010 SP3 deployed across the environment, it is a prerequisite to have the Active Directory Schema to be extended for supporting Exchange 2010 SP3. During this upgrade, the Active Directory Schema will be extended to support Exchange 2010 SP3.

Steps to be performed for this upgrade:

Reference Article –

Prerequisites: AD account need to be member of following groups
Member of: Domain Admin, Enterprise Admin, Schema Admin

Install Active Directory Management Tools (Run this Command, if Required)
ServerManagerCmd -i RSAT-ADDS

Software Location Exchange 2010 SP3

Download it and extracting it run below command for preparing the schema.

 setup /PrepareLegacyExchangePermissions (Optional):
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion
 Setup /PrepareSchema
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion
 Setup /PrepareAD /OrganizationName:"Your Org Name"
 Check C:\ExchangeSetupLogs\ExchangeSetup.log for successful completion

How to verify schema version?

2) Steps for Upgrading Exchange 2010 to SP3

Software Location:
1) Exchange 2010 SP3:

Note: Any Interim Updates for Exchange Server 2010 must be uninstalled prior to installing this update.

As I have all roles in one server in a 2 node DAG. Kindly perform the below steps.

Phase 1: Upgrading Database Availability Groups to Exchange 2010 SP3 (Start with Passive)

Note: Make sure to take full Exchange backup, including system state or any custom setting related to CAS role. Do save the OWA folder under bin path too. During SP3 installation, Exchange setup removes all SP2 related folders; in case you have any proxying it might fail, so make sure to upgrade all servers, however one by one.

1) Open Exchange Management Shell, browse to script folder and run below command
.\StartDagServerMaintenance.ps1 -serverName servername

Note: This script move all Exchange related component including database to another server.
2) Disable the Forefront by using below command (It might ask you to stop few Exchange services)

fscutility /disable

3) Stop the OS Antivirus services and Monitoring Agent for Microsoft Exchange Server

4) Verify Backups are completed.

5) Run the SP3 setup files using GUI or goto run setup /m:upgrade. If you are getting IIS component error goto run setup /mode:upgrade /installwindowscomponents

Note: If you are getting this error "A Restart from a Previous Installation is Pending"

Open regedit and delete the HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations key and Rerun Setup.


6) Reboot the server

7) After reboot verify below logs for any error:
Event Logs
Setup Logs (C:\ExchangeSetupLogs)

Services - All Exchange related services are running.
Check IIS Settings are not changed.
Check Authentication settings from EMC for OWA/OMA/ESW. If you find any change revert back to old.
8) Enable Forefront Protection for Exchange. Command fscutility /enable (It might ask you to stop few Exchange services)

9) Start OS Antivirus and Exchange Monitoring Agent Services
10) .\StopDagServerMaintenance.ps1 -serverName servername

11) Now use same steps on another server in DAG.


Phase 2: Upgrade Management Tools

If you have installed management tools in any other machine make sure to upgrade those also.
Finally: - how to verify the upgrade.

Goto Powershell and type below command.

GCM exsetup |%{$_.Fileversioninfo}
techdriveAuthor Commented:
thank you thank you thank you...Sorry I could not reboot the server until last night. I just wanted to thank you for your help.
techdriveAuthor Commented:
I have a 3 node DAG. I notice the cluster is on the first server. Is it necessary for me to fail this over to do a successful patch upgrade. I did not do this the first time and now wonder if I should have done this.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.