Exchange 2010: event id 16025 : No DNS servers could be retrieved from network adapter

This Error event indicates the specified network adapter that is configured for internal DNS lookups on the Microsoft Exchange Server Hub Transport server or Edge Transport server is invalid.

To resolve this error, do one of the following:

Open the Exchange Management Console locally on the Hub Transport server or Edge Transport server. Configure the internal DNS lookups to use all available network adapters, or a specific adapter that exists on the Hub Transport server or Edge Transport server.


Open the Exchange Management Shell. Run the Get-NetworkConnectionInfo cmdlet locally on the Hub Transport server or Edge Transport server. Note the GUID of the network adapters. Use the GUID of the desired network adapter as the value for the InternalDNSAdapterGUID parameter on the Set-TransportServer cmdlet. If you want to use the DNS settings of all available network adapters, enter a GUID of 00000000-0000-0000-0000-000000000000.

SCOM 2012: Turn on (…and view a log) Network Discovery debug mode

Edit discovery.conf in “C:\Program Files\System Center Operations Manager 2012\Server\NetworkMonitoring\conf\discovery” location:
Remove “#” before “DebugEnabled = TRUE”.
Add line “LogDiscoveryProgress = TRUE” below the DebugEnabled = TRUE.

Restart the Health service on management server.

Run network discovery. Wait for to complete.

Read log “ManagementServer-FQDN.log” from location c:\temp on the Management Server…



Ports Used in System Center 2012 Operations Manager

  • Operations console to management server: TCP 5724
  • Operations console to Reporting server: TCP 80
  • Web console to web console server: selected web site port
  • Agent to management server: TCP 5723
  • ACS forwarder to ACS collector: TCP 51909
  • Agentless management: occurs over remote procedure call
  • Management server to UNIX\Linux computer: TCP 1270
  • Management server to UNIX\Linux computer for special discovery and troubleshooting: TCP 22

Prerequisites in IIS for installing the SCOM 2012 Web Console

Web Server (IIS) role with the follow server role services:

Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Logging
Request Monitor
Request Filtering
Static Content Compression
Web Server (IIS) Support
IIS 6 Metabase Compatibility
Windows Authentication

If you already installed .net 4.0 then you will need to run this command to register IIS with .net 4.0

c:\windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

Error code 80070102 deploying SCOM agent

Fix firewall config:

The resultant error code was 80070102 when the push installation failed.
Looking at the agentinstall.log for the server in c:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs, this had to do with the Windows Firewall on a Windows Server 2008 server.

System Center Operations Manager 2012 fresh install, Server Error in ‘/’ Application (Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=, Culture=neutral…)

Bad (or missing) ASP.NET registration map in IIS.
When multiple versions of the .NET Framework are executing side-by-side on a single computer, the ASP.NET ISAPI version mapped to an ASP.NET application determines which version of the common language runtime is used for the application. The ASP.NET IIS Registration tool (Aspnet_regiis.exe) allows an administrator or installation program to easily update the script maps for an ASP.NET application to point to the ASP.NET ISAPI version associated with the tool. The tool can also be used to display the status of all installed versions of ASP. NET, register the ASP.NET version coupled with the tool, create client-script directories, and perform other configuration operations.

To do:

aspnet_regiis.exe –iru

(from systemroot\Microsoft.NET\Framework\versionNumber (for example: 4.xxxx))