Exchange and Invalid Mailboxes

#Exchange #Exchange2010 #Powershell

You know when you run Get-Mailbox using the Exchange Management Shell, and if your unlucky like me you have a shed load of mailboxes that are “invalid” for various reasons.   .. and when you run Get-Maibox you get red text that says the mailbox has an error, but you don’t know which mailbox.

So I knocked this up .. Enjoy .. as you may have guessed the result is InvalidMBX.html.  Not the most glamorous but does the trick

$allMailboxes = get-mailbox -ResultSize unlimited
$invalid = $allMailboxes | where {$_.IsValid -eq $False}

$InvalidMBX = @()
ForEach ($MBX in $Invalid){
  $tmpTable = “” | Select Name, Email, PropertyName,Description, InvalidData

  $mbxvalid = $MBX.Validate()
  $mbxValid | ForEach{
    $tmpTable.Name = $MBX.name
    $tmpTable.Email = $MBX.PrimarySmtpAddress.ToString()
    $tmpTable.PropertyName  = $_.PropertyName
    $tmpTable.Description   = $_.Description
    $tmpTable.InvalidData   = $_.InvalidData
  $InvalidMBX += $tmpTable
  }
}

$InvalidMBX | ConvertTo-Html | Out-File InvalidMBX.html

A Month in #Exchange and #OCS: November 2010: To Read

#Exchange2010 #Lync

#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#* Technical White Papers for Exchange Server 2007
http://technet.microsoft.com/en-us/library/cc164340.aspx

Nothing new

#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#* Technical White Papers for Exchange Server 2010
http://technet.microsoft.com/en-us/library/dd795096(EXCHG.140).aspx

Nothing new

#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#* Exchange 2007 Documentation Updates
http://technet.microsoft.com/en-us/library/cc164372.aspx

New:

Updated:

#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#* Office Communication Server Documentation Updates
http://technet.microsoft.com/en-us/library/bb676082.aspx

Communications Server 2010
http://technet.microsoft.com/en-us/library/ff770144.aspx -and- http://technet.microsoft.com/en-us/lync/default.aspx

** Full Lync Server 2010 Documentation coming in November, 2010. **

#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#* New KBs from Last Month
New means they appear in KB as Revision 1.0! (well apart from the ones that look interesting too)
Exchange 5.5:  http://kbalertz.com/Technology_55.aspx
Exchange 2000: http://kbalertz.com/Technology_53.aspx
Exchange 2003: http://kbalertz.com/Technology_313.aspx
Exchange 2007: http://kbalertz.com/Technology_515.aspx
Exchange 2010: http://kbalertz.com/Technology_1282.aspx
Exchange 2010 Coexistence: http://kbalertz.com/Technology_1281.aspx
Forefront For Exchange: http://kbalertz.com/Technology_523.aspx
Communications Server 2007: http://kbalertz.com/Technology_557.aspx
Communicator 2007: http://kbalertz.com/Technology_558.aspx
Outlook 2007: http://kbalertz.com/Technology_506.aspx
Outlook 2010: http://kbalertz.com/technology_1543.aspx
Lync 2010: http://kbalertz.com/Technology_1859.aspx
Lync Server: http://kbalertz.com/Technology_1860.aspx

Found this too: http://blogs.technet.com/b/hot/archive/tags/Messaging+Server/

October 29, 2010
2259044How to troubleshoot issues that prevent you from viewing other clients’ free/busy information in Office Outlook 2007 and in Outlook 2010

October 28, 2010
2455134Cross-Forest Availability for Exchange 2003 and/or 2007
2405793Description of the Outlook 2010 hotfix package (outlook-x-none.msp)October 26, 2010
2405799Description of the Office 2010 hotfix package (proof-hr-hr.msp)October 26, 2010

October 27, 2010
2431942Lync 2010 client cannot place calls to the Exchange Unified Messaging Auto Attendant
2436196Description of the Office Outlook 2007 hotfix package (wordconv-x-none.msp, word-x-none.msp, outlook-x-none.msp)October 26, 2010
2412273Description of the Office Outlook 2007 hotfix package (Outlook-x-none.msp)October 26, 2010
2449183Office 2010 Cumulative Update for October 2010

October 21, 2010
2431925Office Communicator cannot place calls to the Exchange Unified Messaging Auto Attendant

October 20, 2010
2445711Outlook Hotmail Connector send/receive error 4403 or 1133 and prompt to repair synchronization configuration
2447034You may receive e-mail messages from blocked senders in Outlook 2010

October 18, 2010
2447520Forward or Reply may Fail on a message with an attachment from a 3rd Party MAPI/CDO client in Exchange 2010

October 13, 2010
2444590Microsoft Office Communicator 2007 R2 Basic Diagnostics Package
2444588Microsoft Office Communicator 2007 R2 Basic Diagnostics Package

October 12, 2010
2400041Unable to view attachments in Owa 2003, when sent from Owa 2010
2410707Description of the Office Outlook 2003 Junk Email Filter updateOctober 12, 2010

October 8, 2010
2407028Description of Update Rollup 1 for Exchange Server 2010 Service Pack 1
2420644Description of Hotfix Rollup 3 for Forefront Security for Exchange Service Pack 2

October 6, 2010
2403513You receive error 1034 when you try to create a new us
er by using the Live Meeting Service Portal

October 4, 2010
2413248Notes in an Archive mailbox cannot be viewed in Outlook Web App (OWA)

2407028: Description of Update Rollup 1 for #Exchange Server 2010 Service Pack 1

#Exchange2010

Yeah yeah I know it’s old, but I just wanted a place to track the changes to this KB

http://support.microsoft.com/kb/2407028
Last Review: October 8, 2010 – Revision: 2.0

  • 2028967 Event ID 3022 is logged and you still cannot replicate a public folder from one Exchange Server 2010 server to another
    • You still cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another Exchange Server 2010 server even after you apply the update that is described in knowledge Base (KB) article 979921….

      This problem occurs because the size of a certain property, which belongs to the public folder, exceeds the size limit.

  • 2251610 The email address of a user is updated unexpectedly after you run the Update-Recipient cmdlet on an Exchange Server 2010 server

    • In this scenario, the msExchPoliciesIncluded property of the user is incorrectly set to the GUID of the default email address policy. Therefore, the email address of the user is updated unexpectedly.

  • 978292 (http://support.microsoft.com/kb/978292/ ) An IMAP4 client cannot send an email message that has a large attachment in a mixed Exchange Server 2010 and Exchange Server 2003 environment

    • In a mixed Microsoft Exchange Server 2010 and Microsoft Exchange Server 2003 environment, an Exchange Server 2010 Client Access server handles the proxy requests for Exchange Server 2003 servers. A user accesses a mailbox which is hosted on an Exchange Server 2003 server by using an IMAP4 client. In this situation, the Exchange Server 2010 Client Access server advertises the “Literal+” support during the “capabilities” broadcast. However, the IMAP4 client may encounter certain issues. For example, the IMAP4 client cannot send an email message that has a large attachment.

  • 982004 (http://support.microsoft.com/kb/982004/ ) Exchange Server 2010 users cannot access the public folder

    • This problem occurs because a deadlock in the Store.exe process occurs when there are two or more users who are trying to access the same public folder. 

  • 983549 (http://support.microsoft.com/kb/983549/ ) Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

  • 983492 (http://support.microsoft.com/kb/983492/ ) You cannot view updated content of an Exchange Server 2010 public folder