Justin's Tech Blog

Situation: When we try to modify Dynamic Distribution Group, below message is shown in “Filter” tab: “The Dynamic Distribution Group was created with the Exchange Management Shell. You can use the Exchange Management Shell to modify the filter." Solution: Edit the specific Dynamic Distribution Group in ADSIEdit, change the following value from 1 to 2: Attribute: msExchQueryFilterMetadata Old value: Microsoft.Exchange12.8f91d340bc0c47e4b4058a479602f94c:RecipientFilterType=1 New value: Microsoft.Exchange12.8f91d340bc0c47e4b4058a479602f94c:RecipientFilterType=2 (Note: The attribute after Microsoft.Exchange is variable) Ref: http://blog.craigirvinsworld.com/2010/04/unable-to-modify-exchange-2007-dynamic.html

http://technet.microsoft.com/en-us/library/bb310789(EXCHG.80).aspx http://blogs.technet.com/b/exchange/archive/2007/06/25/3403244.aspx View permissions: Get-PublicFolderClientPermission -Identity "\root folder\sub1\PublicFolder" |format-list Set permissions: Add-PublicFolderClientPermission -Identity "\Rootfolder\sub1\Public folder" -AccessRights PublishingEditor -User "global group" -Confirm –WhatIf Syntaxes [PS] C:\>Get-help Get-PublicFolderClientPermission -examples NAME     Get-PublicFolderClientPermission SYNOPSIS     Use the Get-PublicFolderClientPermission cmdlet to retrieve the user permis     sions for a public folder.       Get-PublicFolderClientPermission "\My Public Folder"     Get-PublicFolderClientPermission -Identity "\My Public Folder" -User Chris     -Server "My Server" | Format-List   Add-PublicFolderClientPermission SYNTAX     Add-PublicF...

[PS] C:\>Get-MailboxCalendarSettings ResourceName |fl AutomateProcessing                  : AutoAccept AllowConflicts                      : False BookingWindowInDays                 : 180 MaximumDurationInMinutes            : 0 AllowRecurringMeetings              : True EnforceSchedulingHorizon            : True ScheduleOnlyDuringWorkHours         : False ConflictPercentageAllowed           : 0 MaximumConflictInstances      ...

Microsoft Outlook lets you configure a delegate for a Microsoft Exchange Server 5.5, Microsoft Exchange 2000 Server, or Microsoft Exchange Server 2003 mailbox. If the delegate that you select is damaged, corrupted, or missing, the following symptoms may occur: Meeting requests are incorrectly sent to previously-removed delegates. You cannot add a user as a delegate if that user was previously a delegate and then had been removed from the list of delegates. A non-delivery report (NDR) is generated when a user sends a meeting request to a mailbox because that mailbox has a delegate whose mailbox has been deleted. The NDR will look similar to the following: Your message did not reach some or all of the intended recipients. The following recipient(s) could not be reached: User D on 4/4/2005 12:10 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the corre...

Get-Mailbox -resultsize unlimited | Where {$_.GrantSendOnBehalfTo -ne $null} | select Name, @{Name='GrantSendOnBehalfTo';Expression={[string]::join(";", ($_.GrantSendOnBehalfTo))}} | Export-CSV C:\SendOnBehalfTo.csv –noTypeInformation Let’s break this command down.  The first portion Get-Mailbox -resultsize unlimited retrieves all user mailboxes and doesn’t limit to 1000 as is default with Exchange 2007.  We pipe this command into the next one with the ‘|’ symbol.  Here we use a conditional Where and select the attribute GrantSendOnBehalfTo returning only mailboxes from the first part of the command where said attribute is NOT null or empty. Next, out of these mailboxes that don’t have the GrantSendOnBehalfTo attribute as empty, we select the Name of the user.  Now we should be able to stop here, however, we’re working with a string attribute here and returning Name will return a Multivalued property instead of the proper DN or user name we’re looking for (so...

  Get-Mailbox | Where {$_.ForwardingAddress -ne $null} | Select Name, ForwardingAddress, DeliverToMailboxAndForward   Ref: http://exchangeshare.wordpress.com/2008/05/26/faq-find-all-users-with-forwarding-address-is-set/

Managing Message Tracking Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2009-06-03 A message tracking log is a detailed log of all message activity as messages are transferred to and from a computer that is running Microsoft Exchange Server 2007 and that has the Hub Transport server role, the Mailbox server role, or the Edge Transport server role installed. Exchange servers that have the Client Access server role or Unified Messaging server role installed don't have message tracking logs. You use message tracking logs for message forensics, mail flow analysis, reporting, and troubleshooting. You can use the Set-TransportServer cmdlet for all message tracking configuration tasks on a Hub Transport server or Edge Transport server. You can use the Set-MailboxServer cmdlet for all message tracking configuration tasks on a Mailbox server. For servers that have the Hub Transport server role and the...