John Yassa's Blog

Home » Exchange 2010 (Page 2)

Category Archives: Exchange 2010

Couldn’t connect to the source mailbox. while running New-MailboxExportRequest

When trying to export a mailbox to PST , we face the error

Couldn’t connect to the source mailbox.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : BEE464B8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

new-mailboxexportrequest

 

Exchange 2010 relies of MAPI when performing any mailbox export. I had to enable MAPI.

So all what you have to do is to enable the MAPI from the mailbox properties as below

EnableMAPI

 

Now run the command one more time after enabling the MAPI

new-mailboxexportrequest2

 

Error When enable archiving on mailbox hosted on office 365

When you try enable archiving on any mailbox hosted on Office 365 (withing hybrid deployment with exchange 2010) , you face the below error

1

“The following error occurred during validation in agent ‘Windows LiveId Agent’: ‘Unable to perform the save operation. ‘Fayis Khader’ is not within a valid server write scope.”

This problem occurs because recipient management must be performed from the on-premises environment when you’re using Active Directory synchronization.

To resolve this issue, enable archiving for the mailbox from the on-premises Exchange server. To do this, use one of the following methods.

Method 1: Use the Exchange Admin Center or the Exchange Management Console

In Exchange 2013
  1. Open the Exchange Admin Center.
  2. Click recipients, and then click mailboxes,
  3. Click the mailbox that you want to change, click Enable under In-Place Archive, and then click yes.
  4. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization
In Exchange 2010
  1. Open the Exchange Management Console.
  2. In the console tree, expand Recipient Configuration, and then click Mail Contact.
  3. Right-click the contact that you want to change, and then click Enable Hosted Archive.
  4. Wait for two cycles of directory synchronization to run (about six hours).to force directory synchronization follow this article Force directory synchronization

Method 2: Use the Exchange Management Shell

  1. Open the Exchange Management Shell, and then run the following cmdlet:
    Enable-RemoteMailbox <UserName> -Archive
  2. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization

Released: Update Rollup 6 for Exchange 2010 Service Pack 3

The Exchange team is announcing today the availability of Update Rollup 6 for Exchange Server 2010 Service Pack 3. Update Rollup 6 is the latest rollup of customer fixes available for Exchange Server 2010 Service Pack 3. The release contains fixes for customer reported issues and previously released security bulletins. Update Rollup 6 is not considered a security release as it contains no new previously unreleased security bulletins. A complete list of issues resolved in Exchange Server 2010 Service Pack 3 Update Rollup 6 may be found in KB2936871. Customers running any Service Pack 3 Update Rollup for Exchange Server 2010 can move to Update Rollup 6 directly.

The release is now available on the Microsoft Download Center. Update Rollup 6 will be available on Microsoft Update in early July.

Download Here: Update Rollup 6 for Exchange 2010 Service Pack 3

Source : Exchange Blog

Cross-premises Calendar viewing is unavailable in a hybrid deployment of Exchange Online in Office 365 and on-premises Exchange Server

We have a hybrid config., with some mailboxes in Office 365, and some mailboxes on-premise.

An Office 365 mailbox cannot view the calendar of an on-premise mailbox, and vice verse.

Error in Outlook trying to open a shared calendar ‘could not be updated’

Error in Outlook trying to view calendar of another mailbox using Scheduling assistant  ‘could not be updated’ as below screen

Error in OWA opening a shared calendar ‘This folder couldn’t be opened.  You might not have permission to open it, or it might not exist anymore’

FreeBusy on outlook 2013

Now the solution will be to run the both command on the exchange server:

Set-AutodiscoverVirtualDirectory “SERVER\Autodiscover (Default Web Site)” -WSSecurityAuthentication $True

Set-WebServicesVirtualDirectory -identity “EWS (default web site)” -WSSecurityAuthentication $true

This two command solved my problem

Exchange Server Mailbox Statistics Report Tool

Here is an exclusive application to retrieve statistics for all mailboxes in a specified database. The tool currently supports Exchange Server 2010 and 2013. Install the product on one of your Exchange servers.

Description:

The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional option named “Archive Statistics Planner” which will let you search mailboxes and provide statistics report with specific dates. More options will be added in future releases.

NOTE:

  • You should run this application directly on one of your Exchange servers which holds any of the following roles: Client Access, Hub Transport and Mailbox. Running the application from servers/workstations without active server role is not supported!
  • Set PowerShell execution policy to either RemoteSigned or Bypass (Launch Windows PowerShell with Run as Administrator > Execute the following command on shell: Set-ExecutionPolicy “RemoteSigned”
  • Exchange Server 2013 Support: It seems to be an old bug (where application failed to load required modules on Exchange Server 2013) reappears in latest version. Download a patch from here (http://sdrv.ms/1dn1fhn) and extract an executable from the zip file and place into the following folder: C:\Program Files\Exchange Server Mailbox Statistics Tool\ (assuming that you already installed latest version of Mailbox Statistics Tool – v1.6.2) Replace an existing executable with this patch. This patch applies to servers running on Exchange Server 2013 only!

Usage Instructions:

  • Domain Controller: Is an additional option and selecting this field is not mandatory.
  • To scan individual mailboxes, Select MAILBOX mode. Specify multiple mailboxes by separating with comma in the “Specify Individual Mailboxes” field
  • To scan individual mailbox, Select MAILBOX mode. Retrieve Exchange Servers > Select Server > Retrieve Databases > Select Database > Retrieve Mailboxes and then select a mailbox
  • To scan all mailboxes in a database, Select DATABASE mode. Retrieve Exchange Servers > Slect Server > Retrieve Databases > Select Database
  • To scan all mailboxes in a server, Select SERVER mode. Retrieve Exchange Servers > Select Server
  • To search mailboxes for statistics with specific dates, go to Options menu and click on “Archive Statistics Planner” which will enable both Oldest Item Date and Newest Item Date fields.
  • To select additional statistics, go to Options menu > Statistics
  • You can select either of the following report formats: HTML or CSV

Below is an example of how to run the report and initiate a Database report

1- Installation

install

2- Run the application

login

3- Now choose the Exchange Server  and the Database you want to run the report on and press on Perform Search

Databasesearch

4- Sample report will be generated as below

DBreport

5- You can send this report to yourself by mail as below

sendmail

 

Download Here

 

Mailbox still marked as being moved after failed move request to Office 365

After a failed move request, sometimes (for unknown reason) the mailbox is still marked is being moved and cannot be removed again… the mailbox is shown with a green icon on the EMC (Exchange Management Console), however it cannot be seen on the “Move Request” section or with Get-MoveRequest command and cannot be cleared with the Remove-MoveRequest command.

Solution

1. Open ADSIEDIT and navigate to the OU where your broken user account is stored.
2. Locate the user account, right-click on it and then choose “Properties”.
3. Click on the “Filter” button and make sure “Show only attributes that have values” is checked.
4. Scroll down the attributes and search for an entry called “msExchMailboxMoveRemoteHostName”.
5. Click on the “Edit” button.
6. Click on the “Clear” button.
7. Click the “OK” button.

Remove the latest Public Folder Database from an Organization

To remove the last public folder database from an organization, perform the following steps:

1- Verify that there is no OAB are configured for Public folder distribution as below

OAB

 

2- Remove all Public Folders from Public Folder Database as below

a- Use Power shell to delete user public folders

Get-PublicFolder -Server <server containing the public folder database> “\” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue

b- Use Power shell to delete System Public Folders

Get-PublicFolder -Server <server containing the public folder database> “\Non_Ipm_Subtree” -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue


3- Remove the Last Public Folder Database using Power shell

a- Remove-PublicFolderDatabase -Identity “PFDB01”

b- A message appears asking you to confirm that you want to perform this action. Enter Y

c- A warning appears, indicating that the database was removed and reminding you to manually remove the database file. The default location for these files is <Exchange installation path\v14\Mailbox\<public folder database name>.

4- Delete the Public folder Database files manually

When you remove a public folder database, the Exchange database (.edb) file for the database and other files associated with the database aren’t automatically deleted. You must delete the public folder database files manually. The default location for these files on an Exchange 2010 server is <Exchange installation path>\v14\Mailbox\<public folder database name>. The default location for these files on an Exchange 2007 server is C:\Program Files\Microsoft\ExchangeServer\Mailbox\<storage group name>\<public folder database name>.

Add or Update a User Picture to the Active directory

This is a quick article to show how easy it is to update an Active Directory user account with a photo of the user.

The Active Directory thumbnail Photo attribute is used by several applications to display a picture for the user account. Microsoft Outlook is one such application that uses this attribute to display the picture of people you send and receive emails to and from (within an Active Directory domain).

Example

Now, for the fun bit! Let’s assume we have user John, and we have saved John’s photo to C:\photos\John.jpg

In two lines of code, we can update John’s photo.

Get the photo, using the Get-Content Power Shell cmdlet, using the encoding type byte. Store the photo as a byte array in the $photo variable. Then update Active Directory using the Set-ADUser cmdlet, passing the byte array ($photo) to the thumbnailPhoto attribute.

$photo = [byte[]](Get-Content "C:\photos\John.jpg" -Encoding byte)            
Set-ADUser John -Replace @{thumbnailPhoto=$photo}

To shorten this to one line of code, we could write this as;

Set-ADUser John -Replace @{thumbnailPhoto=([byte[]](Get-Content "C:\photos\John.jpg" -Encoding byte))}

Now the Photo of John will appear in Outlook and Lync as below:

1- Outlook

outlook

2- Lync

Lync

Exchange Server 2013 Service Pack 1 is released

Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read the release notesbefore installing SP1. The final build number for Exchange Server 2013 SP1 is 15.00.0847.032.

Upgrading to SP1/Deploying SP1

As with all cumulative updates (CUs), SP1 is a full build of Exchange, and the deployment of SP1 is just like the deployment of a cumulative update.

Active Directory Preparation

Prior to or concurrent with upgrading or deploying SP1 onto a server, you must update Active Directory. These are the required actions to perform prior to installing SP1 on a server.

1. Exchange 2013 SP1 includes schema changes. Therefore, you will need to execute the following command to apply the schema changes.

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

2. Exchange 2013 SP1 includes enterprise Active Directory changes (e.g., RBAC roles have been updated to support new cmdlets and/or properties). Therefore, you will need to execute the following command.

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Server Deployment

Once the above preparatory steps are completed, you can install SP1 on your servers. Of course, as always, if you don’t separately perform the above steps, they will be performed by Setup when you install your first Exchange 2013 SP1 server. If this is your first Exchange 2013 server deployment, you will need to deploy both Client Access Server and Mailbox Server roles in your organization.

If you already deployed Exchange 2013 RTM code and want to upgrade to SP1, you will run the following command from a command line.

setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms

Alternatively you can start the installation through the GUI installer.

For More Info : http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx

How to Install Updates on Exchange Server 2010 CAS Arrays

In our case we will assume that we are using Windows load balance and not H/W load balance

Preparing the NLB Cluster for Updates:

The first thing is to remove this server from load balance and make sure there is no active session on that server
1- Issue a Drainstop command to the server (By this you are stop accepting any new session on that server)

nlbdrainstop01

 

When the server has no more active connections it will be in a stopped state

nlbdrainstop02

 

2- Set the default state of the server to Stopped.  This will prevent it from automatically starting and accepting client connections after any reboots that the updates require, to allow you time to verify the updates were successful first before rejoining the NLB cluster.

nlbdrainstop03

 

Stop Conflicting Services:

Stop any service that affect and contact Exchange like (forefront – Antivirus – Anti spam – Backup Solution)

Updating the Server:

Run the setup.exe file and wait till completes
Restart the server

Verifying the Update:

1- Run the command Get-ExchangeServer to get the version of the Exchange server ( Version 14.3 refer to Exchange 2010 SP3)

Confirm

 

2- Run the command get-service *exchange*

getservice


Returning the Server to Production:

1- Return all the third party services that communicate with Exchange to its normal status (Anti spam – Antivirus – Backup – …….)

2- Start the NLB

nlbstart01

 

Set the default status of the NLB to be started

nlbstart02


%d bloggers like this: