Category Archives: Exchange server 2010

Outlook 2010 : run autodiscover unattended/silent/suppressed without any user intervention

When Outlook 2010 is started for the first time in an Active directory environment that has Exchange 2007 or 2010 servers, the autodiscover wizard – which is basically a Next Next Finish operation – becomes unnecessary, because all the information to configure the outlook client is right there in the background.

Some customers want to run the autodiscover wizard in the background without asking the user to click next next finish to configure and create the outlook profile, if that is your case just add the following registry key to your clients and the wizard will run in the background without showing the wizard for the end user

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\AutoDiscover
Value name: ZeroConfigExchange
Value type: REG_DWORD
Value data: 1

OR

Of you want to do this using a GPO group policy object, enable this Outlook 2010 Policy on your domain :

User configuration / Policies / Administrative templates / Microsoft Outlook 2010 / Account Settings / Exchange

Automatically configure profile based on Active Directory Primary SMTP address

which also auto creates a users Outlook profile at first logon without the need for the user to enter any settings.

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

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 create .ps1 script powershell scheduled task

There lots of reasons why someone would like to run an Exchange powershell .ps1 script as a scheduled task. For example scheduling a delta PST export during a migration.

In this post I will share with you how to achieve this on both Microsoft Exchange 2007 and Exchange 2010.   Obviously you should start by creating your .ps1 script for this article we will assume the script location is c:\pcs\YourScript.ps1

The idea is to run the powershell.exe add pass to it the Exchange powershell console as parameter and then finally specify the desired .ps1 script.

You should notice the difference in the path of the Exchange powershell console between Exchange 2007 and Exchange 2010.

Exchange 2007 exshell.psc1 is located at “”C:\Program Files\Microsoft\Exchange Server\Bin\exshell.psc1″”  

Exchange 2010 exshell.psc1 is located at “”C:\Program Files\Microsoft\Exchange Server\V14\Bin\exshell.psc1″”  

Notice the extra V14 in Exchange 2010 ?

So the full command to run would be

For Exchange 2007

PowerShell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\BinExShell.psc1” -Command “. ‘c:\pcs\YourScript.ps1′”

For Exchange 2010

PowerShell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\V14\Bin\ExShell.psc1” -Command “. ‘c:\pcs\YourScript.ps1′”

Many thanks to zero

 

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

Exchange 2010 force archiving to start

In Microsoft Exchange Server 2010 since Service Pack 1 (SP1), the Start-ManagedFolderAssistant cmdlet has been changed. In the Exchange 2010 release to manufacturing (RTM) and Exchange Server 2007 versions, the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process.

In Exchange 2010 SP1, the Mailbox parameter has been removed, and the Identity parameter now accepts the mailbox or mail user to process.

e.g. : Start-ManagedFolderAssistant -identity JohnDoe

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.

Exchange returns #550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##

This is a very classic error. Exchange 2007 and 2010 have the ability to block access from outside to your distribution list. If someone sends a message, that person will receive the NDR :

Received-SPF: None (servername: sender@xs4all.nl does not designate permitted sender hosts)

Exchange returns #550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ## 

If you see the error the first thing you want to check is your antispam logs, but the problem can be found somewhere else… In your Exchange server itself!! :)

Fix it using the Exchange Management Console:

  1. Click the Distribution Group name as you want to set
  2. Click the “Properties
  3. Click the “Mail Flow Settings” Tab
  4. Click the “Message Delivery Restrictions” item
  5. Click the “Properties…” button
  6. Uncheck the “Require that all senders are authenticated” check-box
  7. Click “OK” button
  8. Click “OK” button again

 

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

owa 2010 cannot delete messages

If you logon to the Outlook Web App GUI you are not able to delete emails. If you try to delete an email you receive the message :

An unexpected error occurred and your request couldn’t be handled.

On your Exchange 2010 server you see the message in the eventlog :

Exchange 2010 Event ID 108

Outlook Web App couldn’t connect Exchange Web Services due to a configuration error. Response code = “null, webException.Status = SendFailure

In my case a binding configuration failure broke the connection between OWA and EWS (Exchange Web Services) on the CAS server.

A lot of people seem to have this problem, if you search the Technet forum you find a lot of solutions. In my case the solution was to add bindings for :

127.0.0.1 80 and 127.0.0.1 443

AND

choose the selfsigned server certificate on both the 127.0.0.1 443 binding and the <internal ip address> 443 binding .

I hope this solves your problem, but once again, there seem to be multiple solutions for this problem.

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