To force full edge subscription synchronization from hub transport server Hub01 to the Edge server Edge03:

Start-EdgeSynchronization -Server Hub01 -TargetServer Edge03 -ForceFullSync

This is a Group Policy that allows you to control Internet Explorer site zones list is called “Site to Zone Assignment List”. Keep in mind once you set these the user will be unable to modify the list of sites themselves.

Computer Configuration – Administrative Templates – Windows Components – Internet Explorer – Internet Control Panel – Security Page – Site to Zone Assignment List – Enabled

Internet Explorer has 4 security zones, numbered 1-4. (1) Intranet Zone, (2) Trusted Sites, (3) Internet Zone, (4) Restricted sites. Enable this setting, add the sites and whichever zone they need to be in.

Change ownership of one VM:

Get-VM -Name "NAME-OF-VM" | Set-VM -Owner "DOMAIN\Username"

Change ownership of all VMs belonging to “UserOne” to “UserTwo”:

Get-VM -VMMServer "SCVMM-SERVER-NAME" | where {$_.Owner -eq "DOMAIN\UserOne"} | Set-VM -Owner "DOMAIN\UserTwo"

When attempting to upgrade Exchange 2010 RTM to Exchange 2010 SP1 setup would fail on upgrading the mailbox role. The error given was:

Mailbox Role 
Failed

Error: 
The following error was generated when "$error.Clear(); 
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; 
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; 
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1; 
          if( $dismbx -ne $null) 
          { 
            $srvname = $dismbx.ServerName; 
            if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" ) 
            { 
              Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission."; 
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; 
              if( $mountedMdb -eq $null ) 
              { 
                Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission..."; 
                mount-database $dismbx.Database; 
              }

              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; 
              if( $mountedMdb -ne $null ) 
              { 
                $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagementWkGuid; 
                $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue; 
                if( $dmRoleGroup -ne $null ) 
                { 
                  Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue; 
                } 
              } 
            } 
          } 
        " was run: "Couldn't resolve the user or group "domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.".

Couldn't resolve the user or group "domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.

The trust relationship between the primary domain and the trusted domain failed.

This is caused by the existing Discovery Mailbox account. The solution is to delete the existing Discovery Mailbox user account and run Exchange setup again.

1. Delete the Discovery Search Mailbox, and remove the account from AD. In my case it was “DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}”, the GUID on your setup will be different.
2. Remove the “action” and “Watermark” registry keys from: <pre>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole</pre>

Otherwise you may receive a &#8220;BuildToBuildUpgrade&#8221; error when you try attempt the next step.</li> 

  * Prepare active directory for Exchange to re-create a new Discovery Search Mailbox: 
    <pre>setup.com /preparead</pre>

  * Run Setup again and it should work without issue.</ol>

Howto increase the maximum accepted content length in Exchange Web Services.

1. Open Explorer
2. Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
3. Open the file Web.Config in with notepad
4. Go to the end of the file
5. Insert the following XML tags before the </configuration> tag, note that 104857600 indicates 100mb. <pre><system.webServer> <security> <requestFiltering> <requestLimits maxAllowedContentLength=”104857600” /> </requestFiltering> </security> </system.webServer>

</pre>

1. Restart IIS:
   <pre>iisreset</pre>

Exchange 2010 has a much lower throttling limit than previous versions of Exchange. You may find it necessary to disable throttling on a specific account for administrative purposes.

To do this we will create a new throttling policy, set properties on it, and set the policy on the mailbox. The example below creates a policy and assigns it to the UberMail user.

New-ThrottlingPolicy UberMailPolicy

Set-ThrottlingPolicy UberMailPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null

Set-Mailbox "UberMail" -ThrottlingPolicy UberMailPolicy

There are three places message size limits can be set. At the organizational level, on send connectors, and on receive connectors.

Determine the current message size limits:

1. Open the Exchange Management Shell
2. Run the following commands:

   • Get organizational settings: <pre class="brush: powershell; title: ; notranslate" title="">Get-TransportConfig

     Format-List -Property MaxReceiveSize, MaxSendSize

</pre>

  * Send connector settings: <pre class="brush: powershell; title: ; notranslate" title="">Get-SendConnector | Format-List -Property Identity, MaxMessageSize

</pre>

  * Receive connector settings: <pre class="brush: powershell; title: ; notranslate" title="">Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize

</pre>

Change the message size limits:

1. Open the Exchange Management Shell
2. Run the following commands, these examples up the limits to 100mb
   • Setting at the organizational level: <pre class="brush: powershell; title: ; notranslate" title="">Set-TransportConfig -MaxReceiveSize 100MB -MaxSendSize 100MB

</pre>

      * Setting at the send connector: <pre class="brush: powershell; title: ; notranslate" title="">Set-SendConnector -Identity "send connector name" -MaxMessageSize 100MB

</pre>

      * Setting at the receive connector: <pre class="brush: powershell; title: ; notranslate" title="">Set-ReceiveConnector -Identity "receive connector name" -MaxMessageSize 100MB

</pre></ul> </ol>

If you receive the following error in Exchange 2010 it can be resolved by upping the MAPI session limit in the registry.

MapiExceptionSessionLimit: Unable to open message store. (hr=0x80040112, ec=1246)

To set the Maximum Allowed Sessions Per User:

1. Start Registry Editor.

2. Locate, and then click to select the following registry subkey: <pre>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem</pre>

3. If the Maximum Allowed Sessions Per User does not exist, do the following:
   1. On the Edit menu, point to New, and then select DWORD Value.
   2. Type Maximum Allowed Sessions Per User as the entry names, and then press Enter
4. Right-click Maximum Allowed Sessions Per User , and then click Modify.
5. Click Decimal, type the value that you want to set in the Value data box, and then click OK.
6. Close the Registry Editor.

Restart the Information Store Service:

sc stop MSExchangeIS
sc start MSExchangeIS

After creating a new mailbox database in Exchange 2010, the database creation was successful, however it failed when trying to mount it. I was presented with the following error:

MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)

Apparently, this can happen if the value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. – http://bit.ly/nGe7zf

To resolve this you can set the preferred Active Directory server in the Exchange Management Shell:

Set-ADServerSettings –PreferredServer <DC FQDN>

Enable OWA access on an Exchange 2003 server without SSL. For those times it just has to work and self-signed certs aren’t an option.

• Enable forms based authentication: http://bit.ly/j64QNi
• Disable SSL requirement for FBA: http://bit.ly/moUv31
• Restart IIS

  • Make logon page customizations (so users can input username rather than DOMAIN\Username): http://bit.ly/jfHwxg</li>

  • Configure redirection to point default website to /exchange, create c:\inetpub\wwwroot\index.htm

    <html>
    <head>
    <META 
     HTTP-EQUIV="Refresh"
     CONTENT="1; URL=http://yourserver.domain.com/exchange/">
    </head>
    <body>
    Redirecting to Outlook Web Access...
    </body>
    </html>
    

</pre>