((Alias -ne $null -and RecipientType -ne 'MailUser') -and ((((ObjectClass -eq 'user' -or ObjectClass
-eq 'Contact' -or ObjectClass -eq 'msExchSystemMailbox') -or ObjectClass -eq 'msExchDynamicDistributi
onList') -or ObjectClass -eq 'group') -or ObjectClass -eq 'publicFolder'))

You can see that the following object classes are included:

• User
• Contact
• System Mailbox
• Dynamic Distribution Group
• Group
• Public Folder

In some environments it may be desirable to exclude Mail Users.  Mail Users are similar to Contacts in that they do not have a mailbox in the local Exchange organization, however unlike Contacts they do have a user account in Active Directory.

In other words, Mail Users are mail-enabled user objects that use an external email service.

Mail Users are displayed in the same area of the Exchange Management Console as regular Contacts, which may lead you to think that excluding them from the Global Address List is as simple as removing this part of the recipient filter:

-or ObjectClass -eq ‘Contact’

However that is not correct, and will not remove Mail Users from the Global Address List.  To understand how to actually do this take a closer look at the attributes of a Mailbox User and a Mail User.

[PS] C:\>get-mailbox "John Smith" | fl objectclass, recipienttype

ObjectClass   : {top, person, organizationalPerson, user}
RecipientType : UserMailbox

[PS] C:\>get-mailuser "Peter Banes" | fl objectclass, recipienttype

ObjectClass   : {top, person, organizationalPerson, user}
RecipientType : MailUser

Notice that both are the same ObjectClass of ‘user’, which would still be included in the recipient filter if you were to simply remove the ‘Contact’ object class.

Instead, to remove Mail Users from the Global Address List you should exclude them by Recipient Type. You can do this by including the following condition in your recipient filter:

RecipientType -ne ‘MailUser’

For example:

Set-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and RecipientType -ne 'MailUser' -and (ObjectClass -eq 'user' -or ObjectClass -eq 'Contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}

If you’re making this change to the default Global Address List see my previous post with the solution to the error that occurs when modifying the default Global Address List.

Related posts:

• Unable to Modify Default Global Address List
• How to Enter the Exchange Server 2010 Product Key for Multiple Servers
• How to Use a Specific Domain Controller in Exchange 2010 Management Shell
• Exchange 2010 Certificate Revocation Checks and Proxy Settings
• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal

This article How to Remove Mail Users from the Global Address List is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

You can’t peform this operation on default global address list “Default Global Address List”.

The recipient filter of the default Global Address List can be modified once during conversion from Exchange 2003 but not after that.  If you want to change the default Global Address List recipient filter after that you must either:

• Create a new Global Address List with the desired recipient filter
• Temporarily modify the Global Address List so that it isn’t the default

For the second option you can refer back to my earlier post on fixing  the issue where there is no default Global Address List in the organization.  This is determined by the msExchRecipientFilterFlags attribute of the object.

Simply use ADSIEdit.msc to modify the attribute from 3 to 0, apply the change to the Global Address List recipient filter, then return to ADSIEdit.msc and set the flag back to 3.  For more detailed instructions check out my previous post.

Related posts:

• How to Remove Mail Users from the Global Address List
• How to Enter the Exchange Server 2010 Product Key for Multiple Servers
• How to Use a Specific Domain Controller in Exchange 2010 Management Shell
• Exchange 2010 Certificate Revocation Checks and Proxy Settings
• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal

This article Unable to Modify Default Global Address List is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

The error message tells you that the “Object is read only because it was created by a future version of Exchange”.

[PS] C:\>Remove-PublicFolderDatabase "EXCH07\Public Folder Database"

Confirm
Are you sure you want to perform this action?
Removing Public Folder Database "EXCH07\Public Folder Database".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help
(default is "Y"):y
Remove-PublicFolderDatabase : Object is read only because it was created by a f
uture version of Exchange: 0.10 (14.0.100.0). Current supported version is 0.1
(8.0.535.0).
At line:1 char:28
+ Remove-PublicFolderDatabase  <<<< "EXCH07\Public Folder Database"

The solution is to use the Exchange Server 2010 Management Shell to remove the Public Folder Database. From an Exchange Server 2010 server run the following command to retrieve the identity of the Public Folder Database you wish to remove.

[PS] C:\>Get-PublicFolderDatabase -Server EXCH07 | fl name, identity

Name     : Public Folder Database
Identity : EXCH07\Second Storage Group\Public Folder Database

Then run this command to remove the Public Folder Database, using the Identity that was retrieved in the previous command.

[PS] C:\>Remove-PublicFolderDatabase "EXCH07\Second Storage Group\Public Folder Database"

Confirm
Are you sure you want to perform this action?
Removing public folder database "EXCH07\Second Storage Group\Public Folder Database".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y
WARNING: The specified database has been removed. You must remove the database file located in E:\Data\SG2\Public
Folder Database.edb from your computer manually if it exists. Specified database: Public Folder Database

The Public Folder Database is now removed from the Exchange 2007 server.

Related posts:

• Public Folders Not Replicating Between Exchange 2007 and 2010
• Causes of MapiExceptionNotAuthorized Error Sending to Public Folders
• Which Version of Exchange Am I Running?
• Browsing Mailbox Databases in Exchange 2007 and 2010
• Managing Diagnostic Logging with Exchange Server 2007

This article Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

For multiple servers in the organization this can be achieved using the Exchange Management Shell.  First identify which servers are currently in trial mode.

[PS] C:\>Get-ExchangeServer | where {$_.IsExchange2007TrialEdition -eq "True"}

Name                Site                 ServerRole  Edition     AdminDisplayVersion
----                ----                 ----------  -------     -------------------
EX1                 exchangeserverpro... Mailbox,... Standard... Version 14.0 (Bu...

To enter the product key use the Set-ExchangeServer cmdlet with the -ProductKey switch.

[PS] C:\>$trialservers = Get-ExchangeServer | where {$_.IsExchange2007TrialEdition -eq "True"}

[PS] C:\>$trialservers | Set-ExchangeServer -ProductKey 12345-12345-12345-12345-12345
WARNING: The product key has been validated and the product ID has been successfully created. This change won't take effect until the Information Store service has been restarted.

Restart the Information Store on the servers and they are no longer in trial mode.

[PS] C:\>Get-ExchangeServer | fl name,*trial*

Name                              : EX1
IsExchange2007TrialEdition        : False
IsExpiredExchange2007TrialEdition : False
RemainingTrialPeriod              : 00:00:00

Related posts:

• How to Use a Specific Domain Controller in Exchange 2010 Management Shell
• Exchange 2010 Certificate Revocation Checks and Proxy Settings
• How to Remove Mail Users from the Global Address List
• Unable to Modify Default Global Address List
• Browsing Mailbox Databases in Exchange 2007 and 2010

This article How to Enter the Exchange Server 2010 Product Key for Multiple Servers is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Any Exchange Management Shell cmdlet will permit you to specify a domain controller using the -DomainController switch.  But you can also set a preferred domain controller for your entire session.

Note the cmdlet to use here – Set-AdServerSettings. This cmdlet configures the session settings such as the preferred Domain Controller and other settings such as the recipient scope.  Check out the full list of Set-AdServerSettings parameters here.

First take a look at the current session settings. In this example dc1.exchangeserverpro.local has been automatically selected.

[PS] C:\>Get-ADServerSettings | fl

RunspaceId                                 : 15e4d968-032b-4cd8-bc66-bf0b665c4161
DefaultGlobalCatalog                       : DC1.exchangeserverpro.local
PreferredDomainControllerForDomain         : {}
DefaultConfigurationDomainController       : DC1.exchangeserverpro.local
DefaultPreferredDomainControllers          : {DC1.exchangeserverpro.local}
UserPreferredGlobalCatalog                 :
UserPreferredConfigurationDomainController :
UserPreferredDomainControllers             : {}
RecipientViewRoot                          : exchangeserverpro.local
ViewEntireForest                           : False
Identity                                   :
IsValid                                    : True

Using Set-ADServerSettings we can specify the preferred server for the current session with the -PreferredServer switch.

[PS] C:\>Set-ADServerSettings -PreferredServer dc2.exchangeserverpro.local

Now Get-ADServerSettings shows this change has occurred.

[PS] C:\>Get-ADServerSettings | fl

RunspaceId                                 : b15cbfd9-5144-442e-bc74-c00a3216b864
DefaultGlobalCatalog                       : dc2.exchangeserverpro.local
PreferredDomainControllerForDomain         : {}
DefaultConfigurationDomainController       : dc2.exchangeserverpro.local
DefaultPreferredDomainControllers          : {DC1.exchangeserverpro.local}
UserPreferredGlobalCatalog                 : dc2.exchangeserverpro.local
UserPreferredConfigurationDomainController : dc2.exchangeserverpro.local
UserPreferredDomainControllers             : {dc2.exchangeserverpro.local}
RecipientViewRoot                          : exchangeserverpro.local
ViewEntireForest                           : False
Identity                                   :
IsValid                                    : True

Related posts:

• How to Enter the Exchange Server 2010 Product Key for Multiple Servers
• Exchange 2010 Certificate Revocation Checks and Proxy Settings
• How to Remove Mail Users from the Global Address List
• Unable to Modify Default Global Address List
• Browsing Mailbox Databases in Exchange 2007 and 2010

This article How to Use a Specific Domain Controller in Exchange 2010 Management Shell is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Jim notes that the shell will generally choose the closest domain controller, which is not always the most appropriate one depending on the administrative tasks you are planning to execute.

Jim points out that you can add the -DomainController argument to any EMS cmdlet, which will resolve the issue for that specific command.  However there are two other ways to address this issue.

One way is to modify the $AdminSessionADSettings settings, which can be seen from the shell.

[PS] C:\>$AdminSessionADSettings

ViewEntireForest              : False
DefaultScope                  : contoso.com
PreferredGlobalCatalog        :
ConfigurationDomainController : exch2007.contoso.com
PreferredDomainControllers    : {}

Note these two settings:

• ConfigurationDomainController – lets you hard code a DC to use for shell cmdlets
• PreferredDomainControllers – lets you specify one or more preferred DC’s for shell cmdlets to use. If a domain is specified that is not served by one of these preferred DC’s one will be chosen automatically.

Modifying the settings is simple.

[PS] C:\>$AdminSessionADSettings.ConfigurationDomainController = 'dc1.contoso.com'
[PS] C:\>$AdminSessionADSettings.PreferredDomainControllers = 'dc1.contoso.com','dc2.contoso.com'

Any DC that you specify here must be valid or an error will appear and the change rejected.

Modifying $AdminSessionADSettings applies to the current session only. To make these changes apply to all EMC sessions that the administrator launches you must edit the Bin\Exchange.ps1 file in the Exchange Server installation folder. Look for this line in the file:

$global:AdminSessionADSettings.ViewEntireForest = $false

Then simply append any additional settings after it.

$global:AdminSessionADSettings.ViewEntireForest = $false
$global:AdminSessionADSettings.ConfigurationDomainController = 'dc1.contoso.com'

This change will then take affect for all future Exchange Management Shell sessions on that server.

Related posts:

• Exchange 2010 Certificate Revocation Checks and Proxy Settings
• How to Remove Mail Users from the Global Address List
• Unable to Modify Default Global Address List
• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal
• Browsing Mailbox Databases in Exchange 2007 and 2010

This article How to Use a Specific Domain Controller in the Exchange 2007 Management Shell is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

First of all the two shell cmdlets we are going to use are Get-EventLogLevel and Set-EventLogLevel.  Each does what the name suggests, and can be combined to manage multiple diagnostic logging items quickly and easily. The -Level parameter of each cmdlet determines what level of diagnostic logging is displayed. The levels you can choose are 0 (Lowest), 1 (Low), 3 (Medium), 5 (High), and 7 (Expert). Usually level 5 (High) is adequate but sometimes you will want level 7 (Expert). The default level is 0 (Lowest) and should always be reset once your troubleshooting is complete.

Running Get-EventLogLevel on its own will output a long list of diagnostic logging items.

[PS] C:\>Get-EventLogLevel

Identity                                                             EventLevel
--------                                                             ----------
MSExchange ActiveSync\Requests                                       Lowest
MSExchange ActiveSync\Configuration                                  Lowest
MSExchange Antispam\General                                          Lowest
MSExchange Autodiscover\Core                                         Lowest
MSExchange Autodiscover\Web                                          Lowest
...

To change the diagnostic logging level for one of these items we use Set-EventLogLevel.

[PS] C:\>Set-EventLogLevel "MSExchange ActiveSync\Requests" -Level 5

You can see the outcome of this by running Get-EventLogLevel again.

[PS] C:\>Get-EventLogLevel

Identity                                                             EventLevel
--------                                                             ----------
MSExchange ActiveSync\Requests                                       High
MSExchange ActiveSync\Configuration                                  Lowest
MSExchange Antispam\General                                          Lowest
MSExchange Autodiscover\Core                                         Lowest
...

Changing the level back is the same command with a different -Level value used.

[PS] C:\>Set-EventLogLevel "MSExchange ActiveSync\Requests" -Level 0

Now lets say you are troubleshooting a Public Folder issue and want to turn up all of the diagnostic logging items for Public Folders. You could run the Set-EventLogLevel cmdlet for each of the Public Folder logging items but that would be quite tedious as there are quite a few.

MSExchangeIS\9001 Public\Transport General                           Lowest
MSExchangeIS\9001 Public\General                                     Lowest
MSExchangeIS\9001 Public\Replication DS Updates                      Lowest
MSExchangeIS\9001 Public\Replication Incoming Messages               Lowest
MSExchangeIS\9001 Public\Replication Outgoing Messages               Lowest
MSExchangeIS\9001 Public\Replication NDRs                            Lowest
MSExchangeIS\9001 Public\Transport Sending                           Lowest
MSExchangeIS\9001 Public\Transport Delivering                        Lowest
MSExchangeIS\9001 Public\MTA Connections                             Lowest
MSExchangeIS\9001 Public\Logons                                      Lowest
MSExchangeIS\9001 Public\Access Control                              Lowest
MSExchangeIS\9001 Public\Send On Behalf Of                           Lowest
MSExchangeIS\9001 Public\Send As                                     Lowest
MSExchangeIS\9001 Public\Rules                                       Lowest
MSExchangeIS\9001 Public\Storage Limits                              Lowest
MSExchangeIS\9001 Public\Replication Site Folders                    Lowest
MSExchangeIS\9001 Public\Replication Expiry                          Lowest
MSExchangeIS\9001 Public\Replication Conflicts                       Lowest
MSExchangeIS\9001 Public\Replication Backfill                        Lowest
MSExchangeIS\9001 Public\Background Cleanup                          Lowest
MSExchangeIS\9001 Public\Replication Errors                          Lowest
MSExchangeIS\9001 Public\DS Synchronization                          Lowest
MSExchangeIS\9001 Public\Views                                       Lowest
MSExchangeIS\9001 Public\Replication General                         Lowest
MSExchangeIS\9001 Public\Download                                    Lowest
MSExchangeIS\9001 Public\Local Replication                           Lowest

With a little PowerShell syntax we can set the logging level of all of these items in a single command.

[PS] C:\>Get-EventLogLevel | where {$_.identity -like "MSExchangeIS\9001 Public\*"} | Set-EventLogLevel -Level 5

Get-EventLogLevel will show us the outcome of this.

[PS] C:\>Get-EventLogLevel | where {$_.identity -like "MSExchangeIS\9001 Public\*"}

Identity                                                             EventLevel
--------                                                             ----------
MSExchangeIS\9001 Public\Transport General                           High
MSExchangeIS\9001 Public\General                                     High
MSExchangeIS\9001 Public\Replication DS Updates                      High
MSExchangeIS\9001 Public\Replication Incoming Messages               High
MSExchangeIS\9001 Public\Replication Outgoing Messages               High
MSExchangeIS\9001 Public\Replication NDRs                            High
MSExchangeIS\9001 Public\Transport Sending                           High
MSExchangeIS\9001 Public\Transport Delivering                        High
MSExchangeIS\9001 Public\MTA Connections                             High
MSExchangeIS\9001 Public\Logons                                      High
MSExchangeIS\9001 Public\Access Control                              High
MSExchangeIS\9001 Public\Send On Behalf Of                           High
MSExchangeIS\9001 Public\Send As                                     High
MSExchangeIS\9001 Public\Rules                                       High
MSExchangeIS\9001 Public\Storage Limits                              High
MSExchangeIS\9001 Public\Replication Site Folders                    High
MSExchangeIS\9001 Public\Replication Expiry                          High
MSExchangeIS\9001 Public\Replication Conflicts                       High
MSExchangeIS\9001 Public\Replication Backfill                        High
MSExchangeIS\9001 Public\Background Cleanup                          High
MSExchangeIS\9001 Public\Replication Errors                          High
MSExchangeIS\9001 Public\DS Synchronization                          High
MSExchangeIS\9001 Public\Views                                       High
MSExchangeIS\9001 Public\Replication General                         High
MSExchangeIS\9001 Public\Download                                    High
MSExchangeIS\9001 Public\Local Replication                           High

To reset the logging levels when we are finished troubleshooting just use the same command string with the value for Lowest.

[PS] C:\>Get-EventLogLevel | where {$_.identity -like "MSExchangeIS\9001 Public\*"} | Set-EventLogLevel -Level 0

Now lets say you have a server with several different diagnostic logging items set to High, filling up your Application event log with entries. Some are Public Folder related, some are Transport related, and resetting them all would mean several individual commands. You also don’t want to touch any of the items set to other levels such as Low.

[PS] C:\>Get-EventLogLevel | where {$_.EventLevel -ne "Lowest" -and $_.EventLevel -ne "Low"}

By piping that command to the Set-EventLogLevel cmdlet you can reset any logging item that is now already set to Lowest or Low.

[PS] C:\>Get-EventLogLevel | where {$_.EventLevel -ne "Lowest" -and $_.EventLevel -ne "Low"} | Set-EventLogLevel -Level 0

Now all of the various items that were set to Medium, High, or Expert levels have been reset to Lowest.

I hope that helps demystify Exchange Server 2007 diagnostic logging commands and helps you make use of this feature when troubleshooting any servers issues you are having.

Related posts:

• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal
• EMS – Creating Email Address Policies for branch offices
• Which Version of Exchange Am I Running?
• Browsing Mailbox Databases in Exchange 2007 and 2010
• How to Enable AutoAccept on Multiple Exchange 2007 Room Mailboxes

This article Managing Diagnostic Logging with Exchange Server 2007 is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

First we must make sure each of the domains is included as an Accepted Domain, using the New-AcceptedDomain cmdlet.

[PS] C:\>New-AcceptedDomain -Name 'Sydney' -DomainName 'sydney.company.com'

Name                           DomainName                     DomainTy Default
                                                              pe
----                           ----------                     -------- -------
Sydney                         sydney.company.com             Autho... False

[PS] C:\>New-AcceptedDomain -Name 'Brisbane' -DomainName 'brisbane.company.com'
-DomainType Authoritative

Name                           DomainName                     DomainTy Default
                                                              pe
----                           ----------                     -------- -------
Brisbane                       brisbane.company.com           Autho... False

[PS] C:\>New-AcceptedDomain -Name 'Melbourne' -DomainName 'melbourne.company.com
' -DomainType Authoritative

Name                           DomainName                     DomainTy Default
                                                              pe
----                           ----------                     -------- -------
Melbourne                      melbourne.company.com          Autho... False

[PS] C:\>New-AcceptedDomain 'Company.com' -DomainName 'company.com' -DomainType
Authoritative

Name                           DomainName                     DomainTy Default
                                                              pe
----                           ----------                     -------- -------
Company.com                    company.com                    Autho... False

Then we can configure the Email Address Policies using the New-EmailAddressPolicy cmdlet.  In this example I am using the “Office” user attribute to filter recipients.

[PS] C:\>New-EmailAddressPolicy -Name 'Sydney' -RecipientFilter {(Office -eq 'Sy
dney')} -EnabledEmailAddressTemplates 'SMTP:%g.%s@sydney.company.com','smtp:%g.%
s@company.com'

Name                       Priority                   RecipientFilter
----                       --------                   ---------------
Sydney                     1                          Office -eq 'Sydney'

[PS] C:\>New-EmailAddressPolicy -Name 'Brisbane' -RecipientFilter {(Office -eq '
Brisbane')} -EnabledEmailAddressTemplates 'SMTP:%g.%s@brisbane.company.com','smt
p:%g.%s@company.com'

Name                       Priority                   RecipientFilter
----                       --------                   ---------------
Brisbane                   2                          Office -eq 'Brisbane'

[PS] C:\>New-EmailAddressPolicy -Name 'Melbourne' -RecipientFilter {(Office -eq
'Melbourne')} -EnabledEmailAddressTemplates 'SMTP:%g.%s@melbourne.company.com','
smtp:%g.%s@company.com'

Name                       Priority                   RecipientFilter
----                       --------                   ---------------
Melbourne                  3                          Office -eq 'Melbourne'

Here is the result for a recipient who matches the filter for the Sydney policy.

[PS] C:\>Get-Recipient 'Peter Grover' | fl Office,Emailaddresses

Office         : Sydney
EmailAddresses : {smtp:Peter.Grover@company.com, SMTP:Peter.Grover@sydney.company.com}

Related posts:

• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal
• Managing Diagnostic Logging with Exchange Server 2007
• Which Version of Exchange Am I Running?
• Browsing Mailbox Databases in Exchange 2007 and 2010
• How to Enable AutoAccept on Multiple Exchange 2007 Room Mailboxes

This article EMS – Creating Email Address Policies for branch offices is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

When an Exchange Server 2007 mailbox user attempts to open a public folder they may see the following information in the OWA window.

This will appear if the public folder database configured for use by mailboxes on the Exchange Server 2007 mailbox database does not contain any content. If the user clicks the “click here” link they are taken to the Exchange Server 2003 web-view of the public folder.

When Outlook Web Access accesses public folders from an Exchange 2007 SP1 mailbox, Outlook Web Access first tries to connect to an Exchange 2007 SP1 public folder store. If no Exchange 2007 SP1 public folder database is available, the Outlook Web Access server next tries to connect to an Exchange 2003 public folder store. When it connects, the user will see the public folder by using the Outlook Web Access 2003 UI.

Source (Microsoft Technet)

This behaviour will occur if the public folder store on the Exchange Server 2007 server has not been configured as a replica for that public folder. Although a public folder store on an Exchange Server 2007 server will hold the public folder hierarchy information, it will only perform public folder referrals to another server if it does not hold a local replica of the data. If that public folder referral results in the user being directed to an Exchange Server 2003 server, they will receive the prompt shown above.

To resolve this issue configure your Exchange Server 2007 public folder store to be a replica for the public folder content. You can view the current list of replicas for a public folder with the Get-PublicFolder cmdlet.

[PS] C:\>Get-Publicfolder "\NameOfFolder" | fl name,replicas

Name     : NameOfFolder
Replicas : {Public Folders}

To see all public folders you can do a recursive search.

[PS] C:\>Get-Publicfolder \ -Recurse | fl name,replicas

Name     : IPM_SUBTREE
Replicas : {}

Name     : NameOfFolder
Replicas : {Public Folders}

Name     : NameOfNextFolder
Replicas : {Public Folders}

Public folder replicas can be managed with the Set-Publicfolder cmdlet. The “replicas” attribute is multi-valued, and the Set-Publicfolder cmdlet will set it but not append to it, so you must include any existing replicas that you want to retain in the list.

[PS] C:\>Get-PublicFolder -recurse | Set-PublicFolder -Replicas "SERVER1\Public
 Folders","SERVER2\Public Folders","SERVER3\Public Folders"

The public folder content will replicate to the new replicas using the configured public folder replication interval. If you wish to do an update manually to speed things up you can use the Update-Publicfolder cmdlet.

Once the public folder store is listed as a replica and the content has replicated the Exchange Server 2007 SP1 mailbox users will be able to access the content in Outlook Web Access.

See also How to configure public folder replication.

Related posts:

• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal
• Public Folders Not Replicating Between Exchange 2007 and 2010
• Causes of MapiExceptionNotAuthorized Error Sending to Public Folders
• How to Migrate Public Folders from Exchange 2003 to Exchange 2007
• Moving the Public Folder Hierarchy During an Exchange 2007 Migration

This article Exchange Server 2007 SP1 Public Folders and Outlook Web Access is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Since you’ve pre-planned your Exchange system before installing it (right?) you can also take the time to whip up a script that will create your storage groups and mailbox databases for you while you do something more enjoyable. The script will make use of the New-StorageGroup, New-MailboxDatabase, and optionally the Mount-Database cmdlets.

I’ve uploaded a sample script here:
PowerShell Script

How to run the script:

1. Download the script file from the link above and save it to your computer
2. Rename the file extension to .ps1
3. Launch the Exchange Management Shell
4. Execute the script by entering the name of the file (eg C:\Script\createmailstores.ps1)

The script will output the name of each Storage Group as it is created, and then the name and all of the details of each of the Mailbox Databases as they are created. A 300 second (5 minute) sleep is inserted at the end to try to avoid errors that can appear if you try to mount a database too soon after it has been created.

If any of the databases fail to mount you can wait a few more minutes before trying again. One way of mounting several dismounted databases all together is to pipe the Get-MailboxDatabase cmdlet into the Mount-Database cmdlet like so:

Get-MailboxDatabase | Mount-Database

Because all of the databases are created with the MountAtStartup attribute set to True you can also mount all of the databases by restarting the Microsoft Exchange Information Store service like so:

[PS] C:\>Restart-Service MSExchangeIS
WARNING: Waiting for service 'Microsoft Exchange Information Store
(MSExchangeIS)' to finish stopping...
WARNING: Waiting for service 'Microsoft Exchange Information Store
(MSExchangeIS)' to finish starting...

You should not use the Restart-Service method if you already have production databases running on the server.

Related posts:

• Error “Object is Read Only” During Exchange Server 2007 Public Folder Database Removal
• Managing Diagnostic Logging with Exchange Server 2007
• EMS – Creating Email Address Policies for branch offices
• Exchange Server 2007 SP1 Public Folders and Outlook Web Access
• EMS – Check your Exchange Server 2007 services

This article EMS – Script your Exchange Server 2007 Storage Groups and Mailbox Databases is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com