Ye Olde Something-or-Other

You can use these PowerShell commands in the Exchange Management Shell to find all the Room and Equipment mailboxes for which a particular user is a delegate:

#Assigns the mailbox to a variable called "Mailbox". $Mailbox = Get-Mailbox #Assigns the mailbox name to a variable called MBName $MBName = $Mailbox.Name #Gets a list of all Room and Equipment type mailboxes on the system and assigns the list to a variable called "ResourceMailboxes" $ResourceMailboxes = (Get-Recipient -resultsize Unlimited | Where-Object {$_.ResourceType -eq "Room" -or $_.ResourceType -eq "Equipment"}) #Output a list of resource mailboxes for which the user is a delegate $ResourceMailboxes | ForEach {$ResourceName = $_.Alias;Get-CalendarProcessing $ResourceName | Select -ExpandProperty ResourceDelegates | ForEach-Object {$NameInDelList = $_.Name; if($MBName -eq $NameInDelList) {$ResourceName}}}

 

If you want to assign the list of resource mailboxes to a variable to use later, just modify that last line to something like this:

$ManagedResources = ($ResourceMailboxes | foreach {$resourcename = $_.Alias;Get-CalendarProcessing $resourcename | select -expandproperty resourcedelegates | foreach-object {$NameInDelList = $_.Name; if($MBName -eq $NameInDelList) {$resourcename}}})

Last Updated ( Monday, 30 April 2012 12:50 )

I've migrated users from several Exchange organizations (Exchange 2003 and 2010) into a single organization running Exchange 2010. Each migration has had its own quirks. This one was curious:

Migrating from Exchange 2003 to an existing Exchange 2010 organization. We used Exmerge to export the mailboxes from the 2003 system to pst files, then used New-MailboxImportRequest to import them to the 2010 system. When the end users logged into their 2010 mailboxes, some of them had duplicates of some of the managed folders, specifically Sent Items, Deleted Items, Junk E-mail, Suggested Contacts, and Sync Issues. The folders imported from the pst file kept their original names, while Exchange 2010 created Deleted Items1, Junk E-mail1, etc. with the system-created folders being used as the actual managed folders. So new junk e-mail would go to Junk E-mail1 instead of to Junk E-mail. This was the third 2003 -> 2010 migration I've done, but the first time I've seen this. We had to rename the imported folders if the user needed to preserve the contents, then use MFCMAPI to delete the new ...1 managed folders and let the system recreate them with the correct names.

I've read several sources that say this can happen if the original mailbox and the new mailbox had different language settings. For example, if the Exchange 2003 mailbox was using French and the Exchange 2010 is set to en-US (US English). That was not the case here. All clients and mailboxes are using US English. Right now, it appears that the users who had duplicate folders were using a 64-bit client of Outlook 2010.

The New-MailboxExportRequest (and New-MailboxImportRequest) cmdlet requires a UNC path for the FilePath parameter. In other words, you can't use "New-MailboxExportRequest -Mailbox MailboxName -FilePath C:\output.pst". You have to use "New-MailboxExportRequest -Mailbox MailboxName -FilePath \\servername\sharename\output.pst". However, if the share and NTFS permissions aren't set correctly on the destination path, you could get an error like this one.

 

Last Updated ( Tuesday, 24 April 2012 08:31 )

Read more...

Canadian based BlackBerry maker, Research In Motion, is in serious trouble both financially and technologically. I believe their biggest mistake was compromising user security at the demand of authoritarian governments. If they had held their ground against all the dictators of the world (including those in North America), they wouldn't have lost so much of their cult following over the last few years.