Thursday, February 25, 2010

Tool for testing Exchange connectivity

After all the Exchange 2007 and 2010 we made we had to check if everything is configured correctly and if the external clients can access the server using all kind of email clients. There are two ways to do that, one is to waste time and configure each type of client that you might have, and the other one is to use a very nice tool that was created by Microsoft. It’s a web page that can help you to test different scenarios of exchange connectivity directly to your email server. You can access it at

Here are a few hints to use it with success:
- Even they say it’s secure, do not use an account with extended rights like your domain admin account
- Pay attention to the certificate settings. If you don’t have an trusted certificate use the “Ignore trust for SSL” setting
- Start with simple tests and continue until everything works as expected
- At the beginning use it without using autodiscovery. When everything is working fine, test the autodiscovery service

Sunday, February 21, 2010

Exchange Management Console/Shell errors

Today I encountered a new error when configuring an Exchange 2010 server for a client. The Exchange server was installed on machine that was also a domain controller.
When I was trying to connect to Exchange 2010 Management Console you I’ve got the following error:

I tried to access the Exchange 2010 installation using the shell and I’ve got the same error:
VERBOSE: Connecting to Rombiosrv01.rombiomedica.local
[rombiosrv01.rombiomedica.local] 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 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". For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [] PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
Searching through eventlog, I found the event 10154:
The WinRM service failed to create the following SPNs: WSMAN/Rombiosrv01.rombiomedica.local; WSMAN/Rombiosrv01.
Additional Data
The error received was 8344: %%8344.
User Action
The SPNs can be created by an administrator using setspn.exe utility.

First thing I tried was to check if "WinRM IIS Extension” was installed and surprised it wasn’t.
To add “WinRM IIS Extension”, you have to use “Add features” from Server Manager. After you install the extension, you have to reboot the server and run (with elevated rights) "winrm quickconfig” to configure it.

The second thing I found out was that if you install Exchange 2010 on a domain controller you will lose some permissions and you have to add them manually. If you get the same error, using ADSI Editor, check the Properties of the AD object for this server in the Domain Controllers OU. On the Security tab, check if NETWORK SERVICE has the Validated Write to Service Principal Name permission.
Now, the System event log was clean, but I still coudn't manage the server.

Third thing, and the easiest one, was to check if everything was working fine within IIS and surprise: the default web site was stopped. I tried to start it without success. Soon I found out that the HTTPS port was used by another application. Once I solved this problem, the server was fully operational.

If the steps above does not succed, check if you have the .NET Extensibility role services for IIS installed.  You can read more here

Monday, February 15, 2010

IT Efficiency School - Exchange Server 2010 - Upgrade and Coexistence

A new online meeting will take place The next online meeting will take place on Wednesday, February 17, 2010 4:30 PM-5:30 PM (UTC+02:00) and it will cover Exchange 2010 Upgrade and Coexistence. To register for this, please access the following link:

How to increase the send and receive size for email messages in Exchange 2010

To modify the send and receive settings for your Exchange 2010 server you have to configure:

1. The global transport settings for the organization
2. The settings for all send/receive connectors from your organization

There are two possible way to do that, one is using the graphical interface, and the other is to use the cmdlets. I will describe the second one.

1. To set up global transport settings, first you have to check the current configuration by using the get-transportconfig cmdlet and check the output that is marked bellow

[PS] C:\Windows\system32>get-transportconfig
ClearCategories : True
DSNConversionMode : UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 10 MB (10,485,760 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 10 MB (10,485,760 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : 20 MB (20,971,520 bytes)
MaxRecipientEnvelopeLimit : 5000
MaxSendSize : 20 MB (20,971,520 bytes)
MigrationEnabled : False
OpenDomainRoutingEnabled : False
Rfc2231EncodingEnabled : False
ShadowHeartbeatRetryCount : 3
ShadowHeartbeatTimeoutInterval : 00:05:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowRedundancyEnabled : True
OrganizationRelationshipForExternalOrganizationEmail :
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True

Then you have to run
Set-TransportConfig -MaxReceiveSize "X MB" -MaxSendSize "X MB"
where X is the size in MB.

2. To configure the SEND and RECEIVE connectors, check the current config of all connectors using:

get-sendconnector |fl
get-receiveconnector |fl

then run

Set-SendConnector -Identity "name of  the connector" -MaxMessageSize "X MB"
Set-ReceiveConnector -Identity "name of the connector" -MaxMessageSize "X MB"

If you are using an EDGE server, you wont have to do anything there if the server is syncronized with your internal HUB servers, otherwise you have to repeat the second step there.