Friday, April 16, 2010

First Details of Exchange Server 2010 Service Pack 1 Available!

First Details of Exchange Server 2010 Service Pack 1 Available!

We've also made improvements to the Exchange Management Console (EMC) and the Exchange Control Panel (ECP). For example, one of my favorite changes is in there - new GUI property fields for database availability group (DAG) IP addresses and alternate witness server and alternate witness directory settings:

New High Availability Features in Exchange 2010 SP1

Enhanced datacenter activation coordination support

Exchange 2010 RTM includes a special mode for DAG site resilience support called datacenter activation coordination (DAC) mode. In DAC mode, Exchange cmdlets can be used to perform a datacenter switchover. In the RTM version, DAC mode is limited to DAGs with at least three members that have at least two or more members in the primary datacenter.

In SP1, DAC mode has been extended to support two-member DAGs that have each member in a separate datacenter. DAC mode support for two-member DAGs leverages the witness server to provide additional arbitration. In addition, DAC mode has been extended to support DAGs that have all members deployed in a single Active Directory site.

So basically in SP1, you can now use DAC mode for all DAGs with two or more members.

Troubleshooting WINRM issue Exchange 2010

EMC

[Server.doamin.com] connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absence or invalid. For more information see the remote troubleshooting help topic discover-exchange server –use WIA $ true – suppress error $ true

EMS

[Server.doamin.com] connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absence or invalid.

Step 1:

Run WinRM quick config

WinRM already is set up to receive requests on this machine.

WinRM already is set up for remote management on this machine.

Step 2:

IIS manager à Default website à Edit bindings à Confirm HTTP is configured to work on port 80

(If customer is running more than 1 website make sure default website is working on port 80 )

WinRM 2.0 no longer uses Port 80.

Since Power shell virtual directory is placed under default website if the default website is not configured to work on port 80. We will not be able to browse any virtual directories under default website.

Step 3:

IIS manager à Default website à Edit bindings à HTTP à hostname value should be blank

(Some time you will see hostname as local host)

Step 4:

Try accessing OWA and the default website from the IIS and make sure we are able to access the websites. (Some time we may get HTTP error 500)

SSL is not required on the Powershell virtual directory.

Step 5:

Go to this location

C:\windows\system 32\inetsrv\config àopen Application.config file in a notepad and check for lines starts with (add name)

Below the <global module>

Add this syntax

<Add name = “wsman” image = “%windir%\system 32\wsmsvc.dll” />

Also check for kerburath (if wrong add this line)

<Add name = “kerbauth” image =”c:\program files \Microsoft\exchange server\v14\bin\kerbauth.dll” />

(We have to be careful while doing this step if required involve IIS team consult with TL before performing this step)

Step 6:

IIS Manager à Default website à Module à Make sure we don’t have kerbauth module loaded. If you see Kerbauth in the Default website module remove it.

(By default kerbauth authentication is give to power shell and not for the default website)

Step 7:

IIS Manager à Default website à Power shell virtual directory à Module à check do we have kerbauth module loaded and it should be in Native mode not as a managed mode

If you see in managed mode à remove the kerbauth à add it again and choose native mode

Kerbauth authentication method should be in local and not inherited

Step 8:

Check Exchange is communicating with the domain controller (Nic settings on the Exchange server)

Check for the application logs

 

=================================================

EMS

The term “connect function.ps1” is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again at c:\program files \Microsoft\exchange server \V14\bin\Remote Exchange

EMC

[server.domain.com] connecting to remote server failed with the following error message. The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of failure

Step1:

Check state of configuration settings: WinRM get WinRM/config

WinRM already is set up to receive requests on this machine.

WinRM already is set up for remote management on this machine.

Check the state of WinRM service: WinRM get wmicimv2/Win32_Service? Name=WinRM

Locate listeners and addresses: WinRM e WinRM/config/listener

Address = *

    Transport = HTTP

    Port = 5985

    Hostname

    Enabled = true

    URLPrefix = wsman

    CertificateThumbprint

    ListeningOn = 10.8.8.3, 127.0.0.1

Step2:

Winrm id –r: http://localhost

WSManFault

    Message = The WinRM client received an HTTP status code of 500 from the remote WS-Management service.

Error number:  -2144108273 0x8033810F

The WinRM client received an unknown HTTP status code from the remote WS-Management service.

Step3:

Browse the default website (you will get error 500)

Step4:

Check for the application log

Log Name:      System

Source:        Microsoft-Windows-WinRM

Date:          12/30/2009 4:14:11 PM

Event ID:      10113

Description:

Request processing failed because the WinRM service cannot load data or event source: DLL="%ExchangeInstallPath%Bin\Microsoft.Exchange.AuthorizationPlugin.dll"

Create Environmental variable à computer properties à Advance à system properties à Advance

New system variable à Exchangeinstallpath àlocate the V14 directory in ‘c’ drive (place where you install the exchange)

=================================================

EMS

[server.domain.com] processing data from remote server failed with the following error message. The user “domain/user” isn’t assigned to any management roles.

EMC

[server.domain.com] processing data from remote server failed with the following error message. The user “domain/user” isn’t assigned to any management roles.

Step1:

Create a new user with a mailbox and make the user as a member for the following group

Administrator, Domain admins, Domain users, Enterprise admins, Group policy creator owners, Organization management, schema admins

Step2:

Login to the exchange server with the newly created user account and try to open the EMC& EMS

Step3:

Run the cmdlet add-pssnapin *E2010* to add a new exchange snap in

Run the command

Set-User username  -RemotePowerShellEnabled $true

This command will assign remote powershell role to the new user

=================================================

EMC

[Server.domain.com] connecting to remote server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination server is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM .If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service:”WinRM quickconfig”

Step1:

WinRM e WinRM/config/listener (No output means WinRM is not installed)

Step2:

Check application log

Event id: 10154 Event source: Microsoft. Windows-WinRM

Description: The WinRM service failed to create the following SPNs: WSMAN /server.domain.com;

WSMAN /server name

Also check for event 8344

Step3:

Run the command

Setspn –a WSMAN/server.domain.com server name

Setspn –a WSMAN /server name

=================================================

EMC

Failed to connect to any exchange server in the current site .please enter the server FQDN where you want to connect: server.domain.com connecting to WinRM

WinRM service can’t handle this request. This request should be redirected to another computer send this request to new computer using the redirection information

(WinRM service doesn’t listen WS-Management request)

Step1:

Try restarting the WinRM Service

Check for the application log for Event id: 10149

Step 2:

Run WinRM quickconfig command

Run WinRM Enumerate WinRM/config/listener

Step 3:

Check in IIS is redirect is enabled (if it is enabled try disabling it)

IIS à Default website àHTTP redirect à Redirect to the following URL (Uncheck) Apply ok

(Sometimes customer will forward the HTTP request to the diff URL)

=================================================

EMC

[Server.domain.com] Connecting to remote server failed with the following error message: The WInRM Client sent a request to an HTTP server got a response saying the request HTTP URL was not available. This usually returned by a HTTP server by a HTTP server that does not support the WS_management protocol.

EMS

The WinRM Client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This usually returned by a HTTP server by a HTTP server that does not support the WS_management protocol.

Step 1:

Run WinRM quickconfig

To check the sever is ready receive request on this machine

Step 2:

IIS Manager à Sites à Default website à Right site à Edit bindingsà HTTPà edit à Check HTTP is configure on port 80 and the check for the host name

If customer has configure for a host name try to browse the website with the host and if it is not resolved. Remove the host name entry.

=================================================

EMS

[Server.domain.com] connecting to remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service running on the remote host and configured to listen for request on the correct port and HTTP URL

Step 1:

Browse default website

Https://localhost and while browsing the default website we will get error 503 service unavailable

Step 2:

Check for the Event id 2280

Event description for this event id will be

“Module to load kerbauth.ddl failed to load” or sometime we get “module to load WSMAN failed to load”

Step3:

Open the Application. Config file present in c:\windows\system32\Intesrv\config in a notepad

And search for the line start with <Add name>

Check for the kerbauth module and make the image location specified is valid (kerbauth.dll files always present in the bin and the drive when we install exchange

It looks like

< Add name = “kerbauth” Image =”c:\program files\Microsoft\exchange server\v14\bin\kerbauth.dll” />

Also confirm that WSMAN location

< Add name = “WSMAN” Image =”%windr%\system32\wsmsvc.dll” />

IIS will look in to these locations to load the specified module

=================================================