Pages

Search This Blog

Showing posts with label Exchange. Show all posts
Showing posts with label Exchange. Show all posts

Thursday, May 16, 2013

Converting a shared mailbox to user mailbox [ Exchange 2013 & Office365 ]

Recently I was working on a migration from on-premises Exchange 2010 servers to Office365 . As Office365 is based on Exchange 2013 I decided to created the multi-accessed mailboxes as a shared mailboxes rather than user mailboxes.

After a while a request was raised requesting changing one of the shared mailboxes to a user mailbox ( as it will be used for an authenticated application )

The conversion is doable using PowerShell , as follow :

  • Connect to Office365 using remote PowerShell using the following steps
    • Store your Office365 credentials , as follow

$Office365Cred=Get-Credentials

    • At the credentials popup enter your credentials and hit Enter
    • Create a remote session using the following PowerShell cmdlet

$Office365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $Office365Cred -Authentication Basic –AllowRedirection

Sunday, March 17, 2013

“Sent Items Management” feature for Exchange 2010 SP3

As Exchange team released Exchange 2010 SP3 which was majorly released to allow Exchange 2010 to be installed on the latest Windows Server edition – Windows Server 2012 and also to allow coexistence with Exchange 2013 . In addition , it adds what is called Sent Items Management feature .

In this post I will explain what this feature was created to do and how to use it . let’s consider that we have User1, User2 and User3; for User2Send on behalf right was granted on User1's mailbox while for User3  “Send as right was granted on the same mailbox ( User1’s mailbox )  

The situation prior Exchange 2010 SP3 :

If User2/User3 used his/her right on User1’s mailbox the sent message will be kept on at their mailbox’s sent items folder and none of those message will be saved at User1’s mailbox.

Wednesday, February 20, 2013

Controlling the database path/location for Exchange 2013 database

As Exchange 2013 comes with the new management paradigm Exchange Administration Center ( EAC ) which is a web based management interface some of the basic functions were found to be missing. One of the missing functions is the ability to relocate ( move ) mailbox database(s) and log files via the console !

In order to overcome this there are some tips that will help you in minimizing the need of moving the databases of your Exchange 2013 servers , as below :

- Use the command line for installing the mailbox servers to control the name and the path of the initial server’s mailbox database by using /MdbName , /DbFilePath and /LogFolderPath switches :

Setup.exe /Mode:Install /IAcceptExchangeServerLicenseTerms /Roles:Mailbox /MdbName:MBDB-01 /DbFilePath:”D:\Exchange Databases/MBDB-01/MBDB-01.edb” /LogFolderPath:”L:\Exchange Logs
image

Once completed both database and logs will be at the assigned within the installation paths .


Friday, February 15, 2013

Creating a shared mailbox using Exchange 2013 Exchange Admin Center ( EAC )

Creating of a mailbox that allows multiple users to monitor and reply to email sent to its email address (for example, an address used specifically by the help desk) is a common tasks for each organization .

For old Exchange version such accounts were created as normal mailboxes then the required permissions are granted to all recipient that require access to these mailboxes . With Exchange 2013 things changed ! as a dedicated new recipient type – namely shared was added to the allowed to be created recipients which facilitates creation of such accounts ( mailboxes ) .

In this post I will show how you can create a shared mailbox and assign the required access levels to it .

First of all , login to the Exchange Admin Center and navigate to the Recipients from the left side menu , choose Shared from the available options then click + to start with a new shared mailbox creation :

image

Wednesday, January 30, 2013

File Share Witness failed and resist deletion ( Microsoft Failover Cluster )

I was working on building an Exchange 2007 SCC lab for testing one of our customers scenarios prior applying to production . I built the cluster and all was going great till I want to change the file share witness folder name . I used the configure cluster quorum setting wizard and the new file share witness was created successfully .The problem is that there was another ( the old ) file share witness that mapped to a non existing folder . I tried to remove it from the failover cluster snap-in but there was no way to do it !

image

I tried also to use the Cluster.exe command line with the /delete switch but it also failed as the unneeded file share witness is a core resource .

Tuesday, December 11, 2012

Exchange 2010 SP2 RU 5-v2 , Exchange 2010 SP1 RU8 and Exchange 2007 RU9 are here !

Today’s early morning Exchange team released a bunch of Exchange server rollups , as follow :

image

Saturday, December 8, 2012

“Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization Container” while installing Exchange Server 2013

As Exchange 2013 reached general availability and as I was working on building my Exchange 2013 lab I got into the following issue while preparing the Active Directory :

image

Here is what I found at ExchangeSetup.log :

image

Monday, December 3, 2012

IBM ASR ( Automatic Server Restart ) issue with Exchange 2010 rollup installation

Today , I was installing rollup 4 v2 for Exchange 2010 SP2 servers at one of our costumers . The installation was proceeding normally , when suddenly the server rebooted Surprised smile. After the server came online and upon investigating with its system logs , the following was found :

image

Thursday, November 29, 2012

"Process execution failed with exit code 5" while uninstalling Exchange 2007 Server

Recently I was working with one of our customers in an Exchange 2007 migration to Exchange 2010 SP2 . After installing , configuring and moving all mailboxes to the new Exchange servers and while trying to uninstall the old Exchange 2007 servers an error appeared as follow :

Error: Process execution failed with exit code 5

image

Wednesday, September 26, 2012

OMG !! Store.exe is memory insatiable

Few days ago , I was working with one of our customers for a minor support incident ; while working he informed that the performance of the server is low so he checked the status from Task Manager and noticed that Store.exe process is consuming around 11 GB of server’s memory !!

image

I advised him that for Exchange It is absolutely normal for Store.exe to grab as much RAM on the server as it can possibly get – as long as Store thinks it needs it to optimize performance. Store was written to do so. It does this as it wants to do as much stuff in memory as possible, without having to go to the slow page file ( A default behavior since Exchange 5.5 ) and hence , this is a feature, not a bug . Exchange will use as much memory as it can for store.exe to optimize performance, another service runs and need some of the RAM itself then exchange will release some. ( You can read more about this here )

The default amount of consumed memory ( cache ) by Store.exe for Exchange 2010 mailbox server are listed below ( With my customer case highlighted ) :

Server physical memory (RAM)

Database cache size: (Mailbox role only)

Database cache size: Multiple-role (for example, Mailbox + Hub Transport)

2 GB

512 MB

Not supported

4 GB

1 GB

Not supported

8 GB

3.6 GB

2 GB

16 GB

10.4 GB

8 GB

24 GB

17.6 GB

14 GB

32 GB

24.4 GB

20 GB

48 GB

39.2 GB

32 GB

64 GB

53.6 GB

44 GB

96 GB

82.4 GB

68 GB

128 GB

111.2 GB

92 GB

You can read more about Mailbox database cache and its enhancements with Exchange 2010 Here

Saturday, September 15, 2012

Microsoft Exchange Information Store service fails to start with events 5000 and 1121

I was working with one of our clients with an Exchange 2010 server issue , the issue was as follow:

  • Microsoft Exchange information store goes to starting state then stopped and so on
  • Events 5000 & 1121 at application log

image

imageimage

This issue may occur if the Default Policy was deleted from the E-mail Address Policies tab and if it was replaced by a custom e-mail address policy. By default, Exchange 2010 – as its successor - Exchange 2007 – which was mentioned here - is hard-coded to look for the default recipient policy which have the lowest priority when the Information Store starts.

image

Friday, September 7, 2012

How to find the current Exchange Server Schema Version

In a previous post I showed how to determine the current version of Schema version for Active Directory for this one I will show how to determine the Schema version for Exchange server.

In contrary to Active Directory , installing of a higher in service pack within the same edition can cause schema version change , as you can see below ( I added Forest ObjectVersion and Domain ObjectVersion as a bounce ) :

Exchange edition

Schema version

Forest objectVersion attribute of Organization container

Domain objectVersion attribute on Microsoft Exchange System Objects

Exchange 2000 RTM

4397

-

4406

Exchange 2000 SP3

4406

-

4406

Exchange 2003 RTM

6870

6903

6936

Exchange 2003 SP1

6870

6903

6936

Exchange 2003 SP2

6870

6903

6936

Exchange 2007 RTM

10628

10666

10628

Exchange 2007 SP1

11116

11221

11221

Exchange 2007 SP2

14622

11222

11221

Exchange 2007 SP3

14625

11222

11221

Exchange 2010 RTM

14622

12640

12639

Exchange 2010 SP1

14726

13214

13040

Exchange 2010 SP2

14732

14247

13040

Now , here are how to find your current Exchange Schema version ( for all , replace data in italic with yours )

Sunday, August 26, 2012

Creating a routing group connector for Exchange 2010 / 2003 coexistence

Today , I was working at one of our customers site with Exchange migration ( from 2003 to 2010 ) . As part of the installation a routing group connector is need to be created automatically upon the first Exchange 2010 Hub Transport server installation – as below - but for some reason it was not created ! , and hence mail flow between 2003 and 2010 servers was not feasible .
image
So in order to maintain message routing between Exchange 2003 and the new Exchange 2010 server a routing group connector needs to be in place . I will share here how you can do it , so mail flow is maintained during coexistence .

Thursday, August 23, 2012

"440 Login Timeout" error with Exchange 2007 OWA

Today I was working with one of our clients with an Exchange 2007 OWA issue . The issue was that for every time he tries to connect to OWA he got error “440 Login Timeout” either via browser or via IIS manager , as below :
image
This error indicates corruption of Outlook Web Access related virtual directories , and hence the solution was to rebuild it again as follow :

Wednesday, August 22, 2012

Exchange 2010 SP1 rollup 7 was released !

Without telling anyone !! Microsoft Exchange team has released rollup 7 for Exchange 2010 SP1, This update contains a number of customer reported and internally found issues. See KB2743248: Description of Update Rollup 7 for Exchange Server 2010 Service Pack 1 for more details

image

  • Download rollup 7 for Exchange 2010 SP1 from here 

Note for Forefront Protection for Exchange users  : For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable Forefront by using this command: fscutility /disable. After installing the update, re-enable Forefront by running fscutility /enable.

Tuesday, August 21, 2012

Manual registration of Office 2010 Filter Pack ( IFilters ) post Exchange 2010 SP1 | SP2 installation

Exchange Search uses IFilters to index text content in different file formats. Microsoft Office 2010 Filter Packs includes filters for Microsoft Office 2010 and Office 2007 file formats. Installation of the Filter Pack is a pre-requisite for Exchange 2010 Mailbox and Hub Transport servers.

The following file name extensions are supported by the filter pack :

.docm, .docx, .one, .pptm, .pptx, .vdx, .vsd, .vss, .vst, .vsx, .vtx, .xlsb, .xlsm, .xlsx, .zip

After you install the Filter Pack, the included IFilters are registered with Windows Search. To allow Exchange 2010 to index Office 2010 file formats, the IFilters must also be registered with Exchange Search. This is done by modifying the registry.

With Exchange 2010 RTM , you must register the IFilters from Office 2010 Filter Packs manually , post Exchange 2010 RTM installation .

In Exchange 2010 SP1 & SP2 , Exchange Setup registers the IFilters from Office 2010 Filter Packs with Exchange Search. But what if you installed your Exchange 2010 SP1 | SP2 server and forgot do to installation of Office 2010 Filter Packs ? ( Unattended installation will proceed even if it isn’t installed )

image

Calendar and tasks retention tags with the release of Exchange 2010 SP2 rollup 4

Till Exchange  2010 SP2 rollup 3 assigning a retention tags to either calendar or tasks items were not feasible. Now , With the release of Exchange 2010 SP2 rollup 4 and to continue maintaining compliance requirements ,the assignment of retentions tags to both calendar and tasks folders items become feasible.

Exchange 2010 SP2 with rollup 4 allows the following :

  • Creating of retention tags using Exchange Management Shell ( EMS ) that can be used to alter items at both calendar and tasks folders
  • Using of Default Policy Tags ( DPTs ) to move / delete items from calendar and tasks folders

By knowing that , deploying of Exchange 2010 SP2 rollup 4 can be accomplished using different techniques :

I. If you don’t want to implement specific retention tags for tasks and calendar items or don’t mind applying DPTs settings to your calendar and tasks items , go and install rollup 4 directly.

II. If you want to keep the same behavior for calendar and tasks items as that prior rollup 4 ( No retention tags allowed for calendar and tasks items ) , add a registry key to your mailbox servers prior deploying of Exchange 2010 SP2 rollup 4 . The value can be created by executing the below command at an elevated command line :

RegAdd “HKLM\System\CurrentControlSet\Services\MSExchangeMailboxAssistants\Parameters” /V ELCAssistantCalendarTaskRetentionEnabled /t Reg_DWORD /d 0 /f

III. If you want Calendar and Tasks folders to expire at a different interval than Default Policy Tags ( DPTs ) , you can follow the following steps:

  • Place all mailboxes on Retention Hold , by executing the below command at an elevated EMS :

Get-Mailbox | Set-Mailbox -RetentionHoldEnabled $true

  • Apply Exchange 2010 SP2 RU4 to your Mailbox servers.
  • Create RPTs for Calendar and Tasks folders with the desired retention settings ( Using Exchange Management Shell ).
  • Inform users about the changes.
  • When ready, remove the retention hold from mailboxes , by executing the below command at an elevated EMS :

Get-Mailbox | Set-Mailbox -RetentionHoldEnabled $false

Additionally , you can also read on how to :

  1. Create a retention tag : Here
  2. Create a retention policy : Here
  3. Apply a retention policy to mailbox(es) : Here

Sunday, August 19, 2012

OMG !! All Exchange services are disabled by a rollup (un)installation

I was (un)installing Exchange rollup when (un)installation completed successfully , I noticed that it left all  Exchange services disabled Surprised smile.
As Exchange services needs to be started with automatic startup mode , I was going to do it one by one using Services snap-in . Just as I went to Start to open Services snap-in I noticed the Windows Power Shell shortcut pinned to my taskbar , so I decided to use it to achieve my goal and here is how I did that.

Friday, August 17, 2012

Enable expired password change feature in Outlook Web App

One of the enhancements that was introduced with Exchange 2010 SP1 and Exchange 2007 SP3 is the ability to change expired passwords using OWA .

This feature is disabled by default ! . You can enable and start use this feature by creating a registry value on all Client Access Servers ( CASs ) within your Exchange organization ; the value have the following settings :

Adding of this value can be simplified by executing the following command at an elevated command line :

Reg Add “HKLM\System\CurrentControlSet\Services\MSExchange OWA” /V ChangeExpiredPasswordEnabled /t Reg_DWORD /d 1

image

Thursday, August 16, 2012

ActiveSync device cannot retrieve mails but can send normally !!!

One of the strangest situations that Exchange admins may face after deployment of a Exchange server antivirus ( e.g. Forefront protection for Exchange 2010 ) is that no mails can be retrieved via ActiveSync devices even it is retrievable with either Outlook or OWA . The situation could get worse , as mails start to flow to ActiveSync device as soon as it is opened by Outlook client !!

This can sometimes be caused by the way antivirus software scans new emails. Some anti virus programs only scan new emails when they are accessed (either via Outlook, or OWA, but not by ActiveSync). The problem with this, is that the emails don’t get delivered to the user until they have been scanned. The easiest way to determine if this is the problem, is to open outlook, and see if you get emails straight away on your ActiveSync/mobile device. Then close outlook, and see if you still get new emails come in straight away. You might need to send a test email from another PC or different email provider to test this.

In order to overcome this issue , all you need is to enable Proactive Scanning ( disabled by default ) on you server , as follow :

  • From Run , type RegEdit and hit enter

image