Technical Exchange bLog

In certain cases you need to pause access to the user's mailbox without disabling user's account or Exchange mailbox. Therefore mailbox features should be disabled. I created a simple script that disables or enables all mailbox features on specified mailbox. You can download the script here Pause_Mailbox_Features_For_Mailbox.ps1 # ----------------------------------------------------------------------------------- # # Enter mailbox name you want to "pause". Use Get-Mailbox command to get correct name #  # Be careful when using this script since it disables or enables Exchange features # for a specified user mailbox. # # If this is not your intention, don't use it. # This script is provided "AS IS" with no warranties, and confers no rights. # # Check www.exchangelog.info for more useful information # #------------------------------------------------------------------------------------ # BEGIN script $User = read-host "Please enter...

You transitioned to Exchange 2010/2013 server and your organization is sending mass mailings, suddenly mails are leaving slower than before. Check Throttling Policies on your Transport server if levels are too low for your organization. More on  http://technet.microsoft.com/en-us/library/dd297964.aspx

If your computer resides in a different domain than Exchange server that hosts your mailbox, and your e-mail address domain is the same as the domain your computer resides in, and Autodiscover is correctly created and configured (Google for related articles), during profile creation don't enter your password in the password field. The problem is in Outlook which is not asking you for your correct credentials but is instead sending your @email.domain with the password you provided. The same is true for test e-mail AutoConfiguration (Holding CTRL+Right Mouse button over Outlook icon in taskbar). If you leave password field blank, Outlook will ask you to enter correct credentials.

There are many great articles about what could go wrong when accessing Offline Address Book but I would like to expose one related to the ISA 2006 server. Disable Link translation on ISA 2006 Outlook Anywhere rule if you tried anything else before and you are, of course, using ISA 2006. You get " Failed Connection Attempt ISALog type: Web Proxy (Reverse) Status: 1359 An internal error occurred. " error on ISA box. Otherwise, for OAB related problems: - check if Authenticated users group has read permissions on OAB folder on Exchange CAS server - check IIS permissions  http://technet.microsoft.com/en-us/library/gg247612.aspx - check if Autodiscover is functioning - be aware of multi-tenant autodiscover if you are using multiple domains  http://social.technet.microsoft.com/wiki/contents/articles/5787.exchange-2010-multi-tenant-autodiscover-and-dns-configuration.aspx - for other OAB related problems find Dave Goldman's related articles or Dgoldman's WebLo...

Exchange Best Practices Analyzer informs you about this issue and when you click the link offered it gets you to this web page: http://technet.microsoft.com/en-us/library/aa998044(v=exchg.80).aspx There, the text offers you a solution to log in to a system as cluster user account. Log on to a node in the cluster as the Cluster service account. Right-click My Computer and select Properties . Select Advanced . Click Environment Variables . In the User variables for <account name> area, select TEMP and click Edit . In the Variable value field, enter the new path for the TEMP environment variable and click OK . In the User variables for <account name> area, select TMP and click Edit . In the Variable value field, enter the new path for the TMP environment variable and click OK . Click OK to close the Environment Variables dialog box and OK once more to close the System Properties dialog box. Restart the node to apply the change. Repeat steps 1 throug...

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console: The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com': The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are:   -The user name or password specified are invalid.   -Kerbero...

After updating Exchange 2010 SP2 to Rollup Update 4 you might get stuck in your Outlook while downloading OAB from Exchange server. Check if Authenticated users have Read permission on OAB folder on Client Access server. Path is usually: Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB

If by any chance you see the error below after updating the server which is part of DAG, just suspend and then activate the database copy. Exchange will resynchronize the copies and you’ll be able to move the database. You do that by clicking on the database under Database Management, then select non active copy in the Database Copies window, right click on it and select Suspend Database Copy. Repeat the step and select Resume Database Copy. Move-ActiveMailboxDatabase Failed Error: An Active Manager operation failed. Error The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DBx' has been blocked from activation on server 'x.domain.com' by an administrative action. Reason: None specified.. [Database: DBx, Server: x.domain.com] An Active Manager operation failed. Error An error occurred while trying to validate the specified database copy for possible activation. Erro...

I created snapshots of Outlook Admin Console which is Exchange's 2013 native administrative console, thus replacing MMC 3. Exchange 2013 VIEW SLIDE SHOW DOWNLOAD ALL

When you try to remove Public Folder Database from Exchange 2007 server you get Object is read only because it was created by a future version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1 (x.x.x.x) Since you don’t see Exchange 2007 Public Folders Database in Exchange 2010 GUI, you must open Exchange Management Shell on your Exchange 2010 server and run following command: Get-PublicFolderDatabase –Server YOUR EXCHANGE2007 SERVERNAME (this is just security measure not to delete some other database) If Public Folder Database name is correct than run Get-PublicFolderDatabase –Server YOUREXCHANGE2007SERVERNAME | Remove-PublicFolderDatabase

  If such message appears, just run: Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

When you open the Public Folders management console on the mailbox server you get following error: No existing 'PublicFolder' matches the following Identity: '\'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'. In my case the problem was in missing homeMDB attribute value on mailbox server on which I got the error. To resolve the issue: Start ADSI Edit and connect to Configuration Naming Context Navigate to CN=Configuration, DC= , DC= , DC=/Services/Microsoft Exchange/Organization/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/YOURMBXSERVER* *Note : YOURMBXSERVER is mailbox server where you got the error Right-click CN=Microsoft System Attendant and then click Properties to display the Attributes list and find the homeMDB attribute. If the homeMDB attribute has a value, make sure  it points to a valid mailbox database, which is th...

You might find… “ At '12.4.2012 13:11:05' the Microsoft Exchange Information Store Database 'DB' copy on this server experienced a corrupted search catalog. Consult the event log on the server for other "ExchangeStoreDb" and "MSExchange Search Indexer" events for more specific information about the failure. Reseeding the catalog is recommended via the 'Update-MailboxDatabaseCopy' task error in Windows Applications log while you try to activate the database ” …error in Windows Application event log, while you try to activate database copy on mentioned server. The error indicates the problem with search catalog and if you start… Get-MailboxDatabaseCopyStatus | ft name, contentindexstate …you will find that one or more database’s ContentIndexState is in failed condition. To resolve the issue write down the name of the database as expressed in previous result and run… Update-MailboxDatabaseCopy "DATABASE\SERVERNAME" -CatalogOn...

When you try to delete first database created by Microsoft Exchange 2010 server during installation, usually named Mailbox Database xxxxxxxxxx, you get “The mailbox database 'Mailbox Database xxxxxxxxxx' cannot be deleted” error stating that the database includes some user’s mailboxes and/or arbitration mailboxes. More info on arbitration mailboxes can be found here - http://technet.microsoft.com/en-us/library/dd297936.aspx . In order to delete the database, you need to move user’s mailboxes by using: get-mailbox -Database “Mailbox Database xxxxxxxxxx”  | New-MoveRequest -TargetDatabase “NEW Mailbox database” –Confirm Then move arbitration mailboxes: get-mailbox -Database “Mailbox Database xxxxxxxxxx” -arbitration | New-MoveRequest -TargetDatabase “NEW Mailbox database” –Confirm If “NEW Mailbox Database” is in good state (no seeding errors; everything is Healthy), mailboxes will be moved. To check this:  

When running Microsoft Exchange Pre-Deployment Analyzer before installing Exchange 2010 into environment with Exchange 2007 installed, an informational error is shown saying that some legacy connector, you probably never heard of, exists. In my case the environment was Exchange 2007 and the connector was found in Exchange Administrative group (FYDIBOHF23SPDLT) using following steps: Connect to your DC In the Active Directory Sites and Services Microsoft Management Console (MMC), double-click Active Directory Sites and Services . Click on top level in the hierarchy tree aka Active Directory Sites and Services (yourdc.yourdomain.com) On the View menu, click Show Services Node. Double-click Services , double-click Microsoft Exchange , and then double-click the Exchange Organization name. Double-click Administrative Groups , and then double-click the administrative group - OLD one (Exchange 5.5 or 2003) OR Exchange Administrative group (FYDIBOHF23SPDLT) – This connector can be...

During to transition to newer version of Exchange from Exchange 2007, receive connector might include lots of IP addresses and ranges which you want to transfer to your new server. While you can find some scripts on the web which let you export IP addresses to txt file and import it from that same file on your new server, the easiest way to do this is to pipeline with PowerShell. Set-ReceiveConnector ”SERVERNAME2\CONNECTORNAME” -RemoteIPRanges ( Get-ReceiveConnector “SERVERNAME1\CONNECTORNAME” ).RemoteIPRanges Where SERVERNAME2 is the name of your new HUB server and SERVERNAME1 is the name of your old server from where you want IP addresses to be extracted. Information provided thanks to: http://scottsitramblings.wordpress.com/2011/06/23/copypaste-send-or-receive-connectors-exchange-2010/ Check it out for more info!