Category Archives: Exchange server 2003

update mail contacts to Exchange 2010

After moving/migrating all mailboxes from Exchange 2003 to Exchange 2010, you have to update several objects to Exchange 2010 level. One of these types of objects are mail contacts. If you see the error message :

“the object must be upgrade to the current Exchange version. After the upgrade the object cannot be managed by an earlier version….”

You can solve this by typing in one of the next commands in powershell, (actually you fill in the customattribute1 field with ‘nothing’)

 Get-MailContact -resultsize Unlimited | Set-MailContact -CustomAttribute1 $null

or

Get-MailContact -resultsize Unlimited | Set-MailContact -CustomAttribute1 Update

 

 

 

 

 

 

 

 

 

 

 

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Exchange telnet test to port 25 for troubleshooting

Well this is a very basic troubleshooting step. With these commands you will see immediately what error your server is throwing and why your server not accepting mail :

• Open a command prompt and type in the following command: telnet <servername> 25
C:\Users\admin>telnet mail.xs4all.nl 25

• Identify yourself by typing: helo <your domain name><enter>
helo exchangedude.net

Continue reading Exchange telnet test to port 25 for troubleshooting

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Upgrade all Exchange 2003 Distribution Groups to Exchange 2010

This powershell command simply retrieves each distribution list and then runs the “Set” command against it. It doesn’t make any modifications to the object though, it just upgrades it to the latest version.

get-DistributionGroup | set-DistributionGroup

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

mail-enabled public folders stopped working after migrating to Exchange 2010

After migrating your Exchange Public Folders from Exchange 2003 ot Exchange 2007 TO Exchange 2010 it is possible to have some problems with mail-enabled public folders.

Sending emails to mail-enabled public folders fails with

#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Continue reading mail-enabled public folders stopped working after migrating to Exchange 2010

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Exchange 2003 and Exchange 2010 Disable public folder conflict messages

When you are migrating a public folder store from Exchange 2003 to Exchange 2010, users can receive public folder design conflict messages.

There are 2 types of messages:

1. A folder DESIGN conflict message will be generated if two folder owners are modifying the
design of a folder from different replicas and their modifications are completed within the same replication interval. Design changes include permissions, forms, and views of a folder. Design conflicts will also be generated if the folder replication list changes in multiple ways during a replication interval. This can be done by Microsoft Exchange Administrator’s changing the replicas. These are purely informational and no action is required.
2. A folder ITEM conflict message will be generated if two or more people modify the same item in a folder on different replicas and they conflict or collide. The owner of the folder will need to decide which version of the item should be saved, which should be deleted, or whether to keep both versions.

For the different Exchange versions, you need different registry keys. To disable the messages try this :

For Exchange Server 2003:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

MSExchangeIS\ParametersPublic

Value Name: Replication Folder Design Conflict Disable

Data Type: REG_DWORD

Value: 1

Restart the MsExchange information store service.

For Exchange server 2010:

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

MSExchangeIS\<ServerName>\Public- <GUID>

Value Name: Replication Folder Design Conflict Disable

Data Type: REG_DWORD

Value: 1

Restart the MsExchange information store service.

 

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.

Page not found – error 404 – in Exchange 2003 OWA

Today I was installing a certificate on Exchange 2003 front-end server IIS Server for Outlook Web Access. The certificate was installed fine, but the website over SSL wouldn’t not come up. Everything looked OK, the 443 socket was opened, even a telnet on port 443 made a connection. All of the certificate chains were trusted on the server. The HTTP SSL service was running OK.

Most importantly, NOTHING was being logged! I couldn’t find anything in either the IIS logs or the event logs.

After doing a packets sniff with Microsoft Network monitor, I saw that the client successfully connected  to the server at 443, but when it tried to set up the SSL connection, the IIS server terminated it.. The only thing sent was a SSL ” client hello” followed by some 4 unreadable packages from the IIS server.

Finally I found the error! The administrator originally imported the web certificate into the user store and then tried to move the  certificate to the local computer store using the GUI.  Of course, the private key did not make the transition so the website could not respond.  However, you should expect that IIS makes some report of the error.  In IIS the certificate was displayed as valid but the server just didn’t respond to an SSL Hello. The certificate even reported that it contained a private key!

After doing an file export to a pfx file from the user store, and importing the pfx file into the computer store everything worked OK!

 

Disclaimer : The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided.