Category: Exchange 2010


If you ever want to export / import a mailbox use the below

1- You need to set a role assignment to the user

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User AD\Administrator

2- To Export Run the following command

New-MailboxExportRequest -Mailbox "SourceMailbox" -IncludeFolders "Namethefolder" -FilePath \\servername\c$\mailboxexport.pst

3- To import run the following command

New-MailboxImportRequest -Mailbox "NewRoomMailbox" -IncludeFolders "namethefolder" -FilePath \\servername\c$\mailboxexport.pst

 

For Example, the below exports calendar items from one Mailbox to the other

New-MailboxImportRequest -Mailbox "OLDRoomMailbox" -IncludeFolders "#Calendar#" -FilePath \\servername\c$\meetingroomcalendat.pst

New-MailboxExportRequest -Mailbox "NEWRoomMailbox" -IncludeFolders "#Calendar#" -FilePath \\servername\c$\meetingroomcalendat.pst

Sometimes you can face the issue of getting the below when you submit a request

“asn1 bad tag value met”

image

The Solution is simple, do the below

1- Open Up the request in notepad

2- Select File –> Save As

3- Choose ANSI instead of UNICODE

image

Resubmit the request and you should be issued the certificate Smile

Several of my clients always face an issue when they want to renew the exchange certificate from their internal CA which doesn’t have the Web Enrollment installed and configured.

When they try to issue the certificate from the GUI they get the below issue

Denied By Policy Module 0x80094801, The Request does not contain a certificate template extension or the certificate template request attribute.

clip_image002

Now the solution is very easy, once you get a hold of the .req file you need to copy it over to you CA Server and run the below command

certreq -submit -attrib "CertificateTemplate:WebServer" <Cert Request.req>

Then you will be issued the certificate given you have proper permissions.

To determine the Rollup that has been applied to Microsoft Exchange 2010, run the following command in the Exchange Management Shell:

GCM exsetup |%{$_.Fileversioninfo}

To determine the Microsoft Exchange version for all Microsoft Exchange Servers in the organisation:

Get-ExchangeServer | Format-Table Name, *Version*

As you know Exchange 2010 SP2 Came with a requirement to update the schema,

Now quoting Michael’s Blog There are several very interesting items :

  1. The Mail-Recipient class has now gained the Company and Department attributes.
    This means that Groups (both security groups and distribution groups) and Contacts (mail contacts) can now be assigned values to the Company and Department attributes.
    From a technical perspective, the Mail-Recipient class is a system auxiliary class, for both the Group and Contact classes, and all attributes present in Mail-Recipient are available in them.

  2. The ms-Exch-Custom-Attributes class has gained 35 new custom attributes, from ms-Exch-Extension-Attribute-16 to ms-Exch-Extension-Attribute-45, and ms-Exch-Extension-Custom-Attribute-1 through ms-Exch-Extension-Custom-Attribute-5.
    This means that Contacts, Groups, Users, Public Folders, Dynamic Distribution Lists, and Recipient Policies all now have a huge number of new attributes that can be assigned arbitrary values by an organization. This is welcome news to organizations who are using many or most of the current custom attributes and are wary to extend the schema themselves.
    From a technical perspective, the ms-Exch-Custom-Attributes class is an auxiliary class for all the named classes above.

  3. Many new attributes and classes were added to provide support for Address Book Policies and to enhance access to various address lists, global address lists, and offline address lists maintained by Exchange.
    The master class is ms-Exch-Address-Book-Mailbox-Policy.

  4. There are several new attributes and one new class (ms-Exch-Coexistence-Relationship) that are probably designed to support the Hybrid Coexistence Wizard and to overall simplify the process of configuring hybrid coexistence with Exchange Online.

  5. There is a new class (ms-Exch-ActiveSync-Device-Autoblock-Threshold) and a number of new attributes that are within that class that appear to be designed to support automatic throttling of ActiveSync devices.

You can get a lot more detailes from the following link

Exchange Server Active Directory Schema Changes Reference, November 2011

You can use the following tables to determine which Exchange Version You have

 

Exchange Server Release dates

Product name

Build number

Date

Microsoft Exchange Server 2003

6.5.6944

6/30/2003

Microsoft Exchange Server 2003 SP1

6.5.7226

5/25/2004

Microsoft Exchange Server 2003 SP2

6.5.7638

10/19/2005

Microsoft Exchange Server 2007

8.0.685.24

12/9/2006

Microsoft Exchange Server 2007

8.0.685.25

12/9/2006

Microsoft Exchange Server 2007 SP1

8.1.240.6

11/29/2007

Microsoft Exchange Server 2007 SP2

8.2.176.2

8/24/2009

Microsoft Exchange Server 2007 SP3

8.3.083.6

6/20/2010

Microsoft Exchange Server 2010

14.0.639.21

11/9/2009

Microsoft Exchange Server 2010 SP1

14.1.218.15

8/24/2010

Microsoft Exchange Server 2010 SP2

14.2.247.5

12/4/2011

Exchange Server 2007 Service Pack 1

Product name

Build number

Date

KB

Microsoft Exchange Server Exchange 2007 SP1

8.1.240.6

11/29/2007

 

Update Rollup 1 for Exchange Server 2007 Service Pack 1

8.1.263.1

2/28/2008

KB945684 clip_image001

Update Rollup 2 for Exchange Server 2007 Service Pack 1

8.1.278.2

5/8/2008

KB948016 clip_image001[1]

Update Rollup 3 for Exchange Server 2007 Service Pack 1

8.1.291.2

7/8/2008

KB949870 clip_image001[2]

Update Rollup 4 for Exchange Server 2007 Service Pack 1

8.1.311.3

10/7/2008

KB952580 clip_image001[3]

Update Rollup 5 for Exchange Server 2007 Service Pack 1

8.1.336.1

11/20/2008

KB953467 clip_image001[4]

Update Rollup 6 for Exchange Server 2007 Service Pack 1

8.1.340.1

2/10/2009

KB959241 clip_image001[5]

Update Rollup 7 for Exchange Server 2007 Service Pack 1

8.1.359.2

3/18/2009

KB960384 clip_image001[6]

Update Rollup 8 for Exchange Server 2007 Service Pack 1

8.1.375.2

5/19/2009

KB968012 clip_image001[7]

Update Rollup 9 for Exchange Server 2007 Service Pack 1

8.1.393.1

7/17/2009

KB970162 clip_image001[8]

Update Rollup 10 for Exchange Server 2007 Service Pack 1

8.1.436.0

4/9/2010

KB981407 clip_image001[9]


Exchange Server 2007 Service Pack 2

Product name

Build number

Date

KB

Microsoft Exchange Server 2007 SP2

8.2.176.2

8/24/2009

 

Update Rollup 1 for Exchange Server 2007 Service Pack 2

8.2.217.3

11/19/2009

KB971534 clip_image001[10]

Update Rollup 2 for Exchange Server 2007 Service Pack 2

8.2.234.1

1/22/2010

KB972076 clip_image001[11]

Update Rollup 3 for Exchange Server 2007 Service Pack 2

8.2.247.2

3/17/2010

KB979784 clip_image001[12]

Update Rollup 4 for Exchange Server 2007 Service Pack 2

8.2.254.0

4/9/2010

KB981383 clip_image001[13]

Update Rollup 5 for Exchange Server 2007 Service Pack 2

8.2.305.3

12/7/2010

KB2407132 clip_image001[14]

Exchange Server 2007 Service Pack 3

Product name

Build number

Date

KB

Microsoft Exchange Server 2007 SP3

8.3.083.6

6/20/2010

 

Update Rollup 1 for Exchange Server 2007 Service Pack 3

8.3.106.2

9/9/2010

KB2279665 clip_image001[15]

Update Rollup 2 for Exchange Server 2007 Service Pack 3

8.3.137.3

12/10/2010

KB2407025 clip_image001[16]

Update Rollup 3 for Exchange Server 2007 Service Pack 3

8.3.159.0

3/2/2011

KB2492691 clip_image001[17]

Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3

8.3.159.2

3/30/2011

KB2530488 clip_image001[18]

Update Rollup 4 for Exchange Server 2007 Service Pack 3

8.3.192.1

7/7/2011

KB2509911 clip_image001[19]

Update Rollup 5 for Exchange Server 2007 Service Pack 3

8.3.213.1

9/21/2011

KB2602324 clip_image001[20]

Update Rollup 6 for Exchange Server 2007 Service Pack 3

8.3.245.2

1/25/2012

KB2608656 clip_image001[21]


Exchange Server 2010

Product name

Build number

Date

KB

Microsoft Exchange Server 2010 RTM

14.0.639.21

11/9/2009

 

Update Rollup 1 for Exchange Server 2010

14.0.682.1

12/9/2009

KB976573 clip_image001[22]

Update Rollup 2 for Exchange Server 2010

14.0.689.0

3/4/2010

KB979611 clip_image001[23]

Update Rollup 3 for Exchange Server 2010

14.0.694.0

4/9/2010

KB981401 clip_image001[24]

Update Rollup 4 for Exchange Server 2010

14.0.702.1

6/17/2010

KB982639 clip_image001[25]

Update Rollup 5 for Exchange Server 2010

14.0.726.0

12/13/2010

KB2407113 clip_image001[26]


Exchange Server 2010 Service Pack 1

Product name

Build number

Date

KB

Microsoft Exchange Server 2010 SP1

14.1.218.15

8/24/2010

 

Update Rollup 1 for Exchange Server 2010 SP1

14.1.255.2

10/4/2010

KB2407028 clip_image001[27]

Update Rollup 2 for Exchange Server 2010 SP1

14.1.270.1

12/9/2010

KB2425179 clip_image001[28]

 

Update Rollup 3 for Exchange Server 2010 SP1

14.1.289.3

3/7/2011

KB2492690 clip_image001[29]

Update Rollup 3-v3 for Exchange Server 2010 SP1

14.1.289.7

4/1/2011

KB2529939 clip_image001[30]

Update Rollup 4 for Exchange Server 2010 SP1

14.1.323.1

6/22/2011

KB2509910 clip_image001[31]

Update Rollup 4-v2 for Exchange Server 2010 SP1

14.1.323.6

7/27/2011

KB2579150 clip_image001[32]

Update Rollup 5 for Exchange Server 2010 SP1

14.1.339.1

8/23/2011

KB2582113 clip_image001[33]

Update Rollup 6 for Exchange Server 2010 SP1

14.1.355.2

10/27/2011

KB2608646 clip_image001[34]

Exchange Server 2010 Service Pack 2

Product name

Build number

Date

KB

Microsoft Exchange Server 2010 SP2

14.2.247.5

12/4/2011

 

Update Rollup 1 for Exchange Server 2010 SP2

14.2.283.3

2/13/2012

KB2645995 clip_image001[35]

The Exchange Team Blog have released a new tool called “PST Capture” so you can discover and import .pst files across your environment.

PST Capture is used to discover and import Outlook Personal Folder (.pst) File Format files into Exchange Server and Exchange Online. PST Capture helps an organization that wishes to gain more control over their email data repositories by placing them into Exchange. By optionally installing PST Capture Agents on target machines, administrators can determine where .pst files are located and who their file owner is via the PST Capture Console. Administrators can import .pst files via Import Lists to Exchange Server or Exchange Online. Data can be directly imported into the primary mailbox or associated archive mailbox.

Check out this blog article describing the tool: http://blogs.technet.com/b/exchange/archive/2012/01/30/pst-time-to-walk-the-plank.aspx

And the download location: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28767

Even if you don’t plan on importing the .PST files into Exchange, it can be very useful to determine how many .PST files you have and where they are located.

Created By Randy Wintle

http://cid-389bd51b03b1f8f9.office.live.com/embedicon.aspx/Public/UserSetupScriptGeneric.ps1 

You would most likely need to customize it for you specific environment, but it can be used as a good reference.

I was faced with an issue at a client where after the migration of a mailbox from exchange 2003 to exchange 2010 the user can no longer see the To-Do list in Exchange Online mode, it would work for Cached mode though.

In outlook 2010 it would show

image

in outlook 2007 it would show : Could not display folder.

Looking at the move request log I could see errors with SearchFolders, now the problem here is that corrupted items were ignored upon creating the move request.

Luckily we have a tool from Microsoft called MFCMAPI. this tool uses Microsoft’s published APIs to provide access to MAPI stores through a graphical user interface

Now in order to fix this Specific To-do issue, we can use MFCMAPI to delete the To-Do Search folder from under the Root menu as they seem corrupt, which forces outlook to recreate it.

So download MFCMAPI from here 

Open it up and choose Session then Log on and display store table then Double click you mailbox

image

Then Right click and Force Delete The TO-DO Search under the ROOT.

Open up the affected user’s outlook and it will display the to do list Smile.

I have been banging my head with an issue with ActiveSync not working properly.

Running the Exchange Remote Connectivity Analyzer I was constantly getting and error Where it failed to Sync folders due to a server closing the connection

FolderSync Failed: A connection was closed

Well as I always do, the first thing was to check IIS on the CAS.

So opening the Logs under Inetpub\logfiles\W3SVC1 I found this logged

2011-04-27 07:03:00 172.25.25.115 POST /Microsoft-Server-ActiveSync/default.eas Cmd=FolderSync&User=exch2010test&DeviceId=112284038&DeviceType=TestActiveSyncConnectivity 443 – 172.25.25.101 Microsoft-Server-ActiveSync/12.0+(TestExchangeConnectivity.com) 401 2 5 0

Now notice the error code is a 401.2, so checking for the IIS7 http status codes here, I can tell that this an authentication problem due to server configuration.

So next from here, its 1- an authentication problem and 2- Server configuration

So checking on the ActiveSync virtual Directory I found only Basic enabled, and so was the result checking from Exchange shell I found that WindowsAuthentication was disabled.

so I went ahead on the virtual directory and enabled Windows Authentication, restarted IIS. and guess what ??

IT WORKED Open-mouthed smile

I would always recommend you check IIS when anything is related to a service provided through it.