<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>FreeDriverSiteBlog - Exchange 2007</title>
    <link>http://blog.freedriversite.com/</link>
    <description>Discussions for current technology topics.</description>
    <language>en-us</language>
    <copyright>FREEDRIVERSITE 2009</copyright>
    <lastBuildDate>Tue, 23 Mar 2010 05:03:40 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>freedriversite@gmail.com</managingEditor>
    <webMaster>freedriversite@gmail.com</webMaster>
    <item>
      <trackback:ping>http://blog.freedriversite.com/Trackback.aspx?guid=36b4fb10-b15b-4882-bfdc-3dff1ecc96e8</trackback:ping>
      <pingback:server>http://blog.freedriversite.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.freedriversite.com/PermaLink,guid,36b4fb10-b15b-4882-bfdc-3dff1ecc96e8.aspx</pingback:target>
      <dc:creator>FreeDriverSiteAdmin</dc:creator>
      <wfw:comment>http://blog.freedriversite.com/CommentView,guid,36b4fb10-b15b-4882-bfdc-3dff1ecc96e8.aspx</wfw:comment>
      <wfw:commentRss>http://blog.freedriversite.com/SyndicationService.asmx/GetEntryCommentsRss?guid=36b4fb10-b15b-4882-bfdc-3dff1ecc96e8</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
          <span style="TEXT-ALIGN: left; LINE-HEIGHT: 16px; FONT-FAMILY: Verdana, Arial, Helvetica; FONT-SIZE: 11px" class="Apple-style-span">
            <p>
              <strong>
                <font color="#000000">There are times when you need to allow applications
to relay through your Exchange 2007 or 2010 Server.  These steps give two options
for allowing this.</font>
              </strong>
            </p>
            <p>
              <strong>
                <font color="#0000ff">Allow all computers which successfully authenticate
to relay, regardless of the list above</font>
              </strong>
            </p>
            <p>
Like its predecessor, Exchange 2007 is configured to accept and relay email from hosts
that authenticate by default. Both the "Default" and "Client" receive connectors are
configured this way out of the box. Authenticating is the simplest method to submit
messages, and preferred in many cases.
</p>
            <p>
The Permissions Group that allows authenticated users to submit and relay is the "ExchangeUsers"
group. The permissions that are granted with this permissions group are:
</p>
            <blockquote>
              <p>
                <font face="Courier New">NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Submit}<br />
NT AUTHORITY\Authenticated Users {ms-Exch-Accept-Headers-Routing}<br />
NT AUTHORITY\Authenticated Users {ms-Exch-Bypass-Anti-Spam}<br />
NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Accept-Any-Recipient}</font>
              </p>
            </blockquote>
            <p>
The specific ACL that controls relay is the ms-Exch-SMTP-Accept-Any-Recipient.
</p>
            <p>
              <strong>
                <font color="#0000ff">Only the list below (specify IP address)</font>
              </strong>
            </p>
            <p>
This option is for those who cannot authenticate with Exchange. The most common example
of this is an application server that needs to be able to relay messages through Exchange.
</p>
            <p>
First, start with a new custom receive connector. You can think of receive connectors
as protocol listeners. The closest equivalent to Exchange 2003 is an SMTP Virtual
Server. You must create a new one because you will want to scope the remote IP Address(es)
that you will allow.
</p>
            <p>
              <a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432008/original.aspx">
                <img src="http://msexchangeteam.com/photos/postpictures2/images/432008/original.aspx" />
              </a>
            </p>
            <p>
The next screen you must pay particular attention to is the "Remote Network settings".
This is where you will specify the IP ranges of servers that will be allowed to submit
mail. You definitely want to restrict this range down as much as you can. In this
case, I want my two web servers, 192.168.2.55 &amp; 192.168.2.56 to be allowed to
relay.
</p>
            <p>
              <a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432009/original.aspx">
                <img src="http://msexchangeteam.com/photos/postpictures2/images/432009/original.aspx" />
              </a>
            </p>
            <p>
The next step is to create the connector, and open the properties. Now you have two
options, which I will present. The first option will probably be the most common.
</p>
            <p>
              <strong>
                <em>Option 1: Make your new scoped connector an Externally Secured connector</em>
              </strong>
            </p>
            <p>
This option is the most common option, and preferred in most situations where the
application that is submitting will be submitting email to your internal users as
well as relaying to the outside world.
</p>
            <p>
Before you can perform this step, it is required that you enable the Exchange Servers
permission group. Once in the properties, go to the Permissions Groups tab and select
Exchange servers.
</p>
            <p>
              <a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432010/original.aspx">
                <img src="http://msexchangeteam.com/photos/postpictures2/images/432010/original.aspx" />
              </a>
            </p>
            <p>
Next, continue to the authentication mechanisms page and add the "Externally secured"
mechanism. What this means is that you have complete trust that the previously designated
IP addresses will be trusted by your organization.
</p>
            <p>
              <a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432011/original.aspx">
                <img src="http://msexchangeteam.com/photos/postpictures2/images/432011/original.aspx" />
              </a>
            </p>
            <p>
Caveat: If you do not perform these two steps in order, the GUI blocks you from continuing.
</p>
            <p>
Do not use this setting lightly. You will be granting several rights including the
ability to send on behalf of users in your organization, the ability to ResolveP2
(that is, make it so that the messages appear to be sent from within the organization
rather than anonymously), bypass anti-spam, and bypass size limits. The default "Externally
Secured" permissions are as follows:
</p>
            <blockquote>
              <p>
                <font face="Courier New">MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authoritative-Domain}<br />
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Anti-Spam}<br />
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Message-Size-Limit}<br />
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Exch50}<br />
MS Exchange\Externally Secured Servers {ms-Exch-Accept-Headers-Routing}<br />
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Submit}<br />
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Recipient}<br />
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authentication-Flag}<br />
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Sender}</font>
              </p>
            </blockquote>
            <p>
Basically you are telling Exchange to ignore internal security checks because you
trust these servers. The nice thing about this option is that it is simple and grants
the common rights that most people probably want.
</p>
            <p>
              <strong>
                <em>Option 2: Grant the relay permission to Anonymous on your new scoped connector</em>
              </strong>
            </p>
            <p>
This option grants the minimum amount of required privileges to the submitting application.
</p>
            <p>
Taking the new scoped connector that you created, you have another option. You can
simply grant the ms-Exch-SMTP-Accept-Any-Recipient permission to the anonymous account.
Do this by first adding the Anonymous Permissions Group to the connector.
</p>
            <p>
              <a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432012/original.aspx">
                <img src="http://msexchangeteam.com/photos/postpictures2/images/432012/original.aspx" />
              </a>
            </p>
            <p>
This grants the most common permissions to the anonymous account, but it does not
grant the relay permission. This step must be done through the Exchange shell:
</p>
            <blockquote>
              <p>
                <font face="Courier New">Get-ReceiveConnector "CRM Application" | Add-ADPermission
-User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"</font>
              </p>
            </blockquote>
            <p>
In addition to being more difficult to complete, this step does not allow the anonymous
account to bypass anti-spam, or ResolveP2.
</p>
            <p>
Although it is completely different from the Exchange 2003 way of doing things, hopefully
you find the new SMTP permissions model to be sensible.
</p>
            <p>
Source: <a href="http://msexchangeteam.com/archive/2006/12/28/432013.aspx">http://msexchangeteam.com/archive/2006/12/28/432013.aspx</a></p>
            <p>
Applies to: Exchange 2007, Exchange 2010, Exchange Server 2007, Exchange Server 2010,
Backup Exec, Symantec Backup Exec, Symantec Backup Exec 12.5
</p>
          </span>
        </span>
        <img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=36b4fb10-b15b-4882-bfdc-3dff1ecc96e8" />
      </body>
      <title>Allow applications, such as Backup Exec 12.5, to relay alert notifications through Exchange 2007</title>
      <guid isPermaLink="false">http://blog.freedriversite.com/PermaLink,guid,36b4fb10-b15b-4882-bfdc-3dff1ecc96e8.aspx</guid>
      <link>http://blog.freedriversite.com/2010/03/23/AllowApplicationsSuchAsBackupExec125ToRelayAlertNotificationsThroughExchange2007.aspx</link>
      <pubDate>Tue, 23 Mar 2010 05:03:40 GMT</pubDate>
      <description>&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="TEXT-ALIGN: left; LINE-HEIGHT: 16px; FONT-FAMILY: Verdana, Arial, Helvetica; FONT-SIZE: 11px" class=Apple-style-span&gt; 
&lt;p&gt;
&lt;strong&gt;&lt;font color=#000000&gt;There are times when you need to allow applications to
relay through your Exchange 2007 or 2010 Server.&amp;nbsp; These steps give two options
for allowing this.&lt;/font&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&lt;font color=#0000ff&gt;Allow all computers which successfully authenticate to
relay, regardless of the list above&lt;/font&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
Like its predecessor, Exchange 2007 is configured to accept and relay email from hosts
that authenticate by default. Both the "Default" and "Client" receive connectors are
configured this way out of the box. Authenticating is the simplest method to submit
messages, and preferred in many cases.
&lt;/p&gt;
&lt;p&gt;
The Permissions Group that allows authenticated users to submit and relay is the "ExchangeUsers"
group. The permissions that are granted with this permissions group are:
&lt;/p&gt;
&lt;blockquote&gt; 
&lt;p&gt;
&lt;font face="Courier New"&gt;NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Submit}&lt;br&gt;
NT AUTHORITY\Authenticated Users {ms-Exch-Accept-Headers-Routing}&lt;br&gt;
NT AUTHORITY\Authenticated Users {ms-Exch-Bypass-Anti-Spam}&lt;br&gt;
NT AUTHORITY\Authenticated Users {ms-Exch-SMTP-Accept-Any-Recipient}&lt;/font&gt;
&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;
The specific ACL that controls relay is the ms-Exch-SMTP-Accept-Any-Recipient.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&lt;font color=#0000ff&gt;Only the list below (specify IP address)&lt;/font&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
This option is for those who cannot authenticate with Exchange. The most common example
of this is an application server that needs to be able to relay messages through Exchange.
&lt;/p&gt;
&lt;p&gt;
First, start with a new custom receive connector. You can think of receive connectors
as protocol listeners. The closest equivalent to Exchange 2003 is an SMTP Virtual
Server. You must create a new one because you will want to scope the remote IP Address(es)
that you will allow.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432008/original.aspx"&gt;&lt;img src="http://msexchangeteam.com/photos/postpictures2/images/432008/original.aspx"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The next screen you must pay particular attention to is the "Remote Network settings".
This is where you will specify the IP ranges of servers that will be allowed to submit
mail. You definitely want to restrict this range down as much as you can. In this
case, I want my two web servers, 192.168.2.55 &amp;amp; 192.168.2.56 to be allowed to
relay.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432009/original.aspx"&gt;&lt;img src="http://msexchangeteam.com/photos/postpictures2/images/432009/original.aspx"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The next step is to create the connector, and open the properties. Now you have two
options, which I will present. The first option will probably be the most common.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&lt;em&gt;Option 1: Make your new scoped connector an Externally Secured connector&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
This option is the most common option, and preferred in most situations where the
application that is submitting will be submitting email to your internal users as
well as relaying to the outside world.
&lt;/p&gt;
&lt;p&gt;
Before you can perform this step, it is required that you enable the Exchange Servers
permission group. Once in the properties, go to the Permissions Groups tab and select
Exchange servers.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432010/original.aspx"&gt;&lt;img src="http://msexchangeteam.com/photos/postpictures2/images/432010/original.aspx"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Next, continue to the authentication mechanisms page and add the "Externally secured"
mechanism. What this means is that you have complete trust that the previously designated
IP addresses will be trusted by your organization.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432011/original.aspx"&gt;&lt;img src="http://msexchangeteam.com/photos/postpictures2/images/432011/original.aspx"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Caveat: If you do not perform these two steps in order, the GUI blocks you from continuing.
&lt;/p&gt;
&lt;p&gt;
Do not use this setting lightly. You will be granting several rights including the
ability to send on behalf of users in your organization, the ability to ResolveP2
(that is, make it so that the messages appear to be sent from within the organization
rather than anonymously), bypass anti-spam, and bypass size limits. The default "Externally
Secured" permissions are as follows:
&lt;/p&gt;
&lt;blockquote&gt; 
&lt;p&gt;
&lt;font face="Courier New"&gt;MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authoritative-Domain}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Anti-Spam}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-Bypass-Message-Size-Limit}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Exch50}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-Accept-Headers-Routing}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Submit}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Recipient}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Authentication-Flag}&lt;br&gt;
MS Exchange\Externally Secured Servers {ms-Exch-SMTP-Accept-Any-Sender}&lt;/font&gt;
&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;
Basically you are telling Exchange to ignore internal security checks because you
trust these servers. The nice thing about this option is that it is simple and grants
the common rights that most people probably want.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;&lt;em&gt;Option 2: Grant the relay permission to Anonymous on your new scoped connector&lt;/em&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
This option grants the minimum amount of required privileges to the submitting application.
&lt;/p&gt;
&lt;p&gt;
Taking the new scoped connector that you created, you have another option. You can
simply grant the ms-Exch-SMTP-Accept-Any-Recipient permission to the anonymous account.
Do this by first adding the Anonymous Permissions Group to the connector.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="COLOR: rgb(39,84,160)" href="http://msexchangeteam.com/photos/postpictures2/images/432012/original.aspx"&gt;&lt;img src="http://msexchangeteam.com/photos/postpictures2/images/432012/original.aspx"&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This grants the most common permissions to the anonymous account, but it does not
grant the relay permission. This step must be done through the Exchange shell:
&lt;/p&gt;
&lt;blockquote&gt; 
&lt;p&gt;
&lt;font face="Courier New"&gt;Get-ReceiveConnector "CRM Application" | Add-ADPermission
-User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"&lt;/font&gt;
&lt;/p&gt;
&lt;/blockquote&gt; 
&lt;p&gt;
In addition to being more difficult to complete, this step does not allow the anonymous
account to bypass anti-spam, or ResolveP2.
&lt;/p&gt;
&lt;p&gt;
Although it is completely different from the Exchange 2003 way of doing things, hopefully
you find the new SMTP permissions model to be sensible.
&lt;/p&gt;
&lt;p&gt;
Source: &lt;a href="http://msexchangeteam.com/archive/2006/12/28/432013.aspx"&gt;http://msexchangeteam.com/archive/2006/12/28/432013.aspx&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Applies to: Exchange 2007, Exchange 2010, Exchange Server 2007, Exchange Server 2010,
Backup Exec, Symantec Backup Exec, Symantec Backup Exec 12.5
&lt;/p&gt;
&lt;/span&gt;&lt;/span&gt;&lt;img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=36b4fb10-b15b-4882-bfdc-3dff1ecc96e8" /&gt;</description>
      <comments>http://blog.freedriversite.com/CommentView,guid,36b4fb10-b15b-4882-bfdc-3dff1ecc96e8.aspx</comments>
      <category>Exchange 2007</category>
      <category>Exchange 2010</category>
      <category>Symantec Backup Exec</category>
    </item>
    <item>
      <trackback:ping>http://blog.freedriversite.com/Trackback.aspx?guid=975d4e5d-7e01-4872-8168-b35175084b0d</trackback:ping>
      <pingback:server>http://blog.freedriversite.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.freedriversite.com/PermaLink,guid,975d4e5d-7e01-4872-8168-b35175084b0d.aspx</pingback:target>
      <dc:creator>FreeDriverSiteAdmin</dc:creator>
      <wfw:comment>http://blog.freedriversite.com/CommentView,guid,975d4e5d-7e01-4872-8168-b35175084b0d.aspx</wfw:comment>
      <wfw:commentRss>http://blog.freedriversite.com/SyndicationService.asmx/GetEntryCommentsRss?guid=975d4e5d-7e01-4872-8168-b35175084b0d</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
I had an issue with a Small Business Server SBS 2003 to SBS 2008 migration where once
everything was up and running, I had problems with Outlook 2007 Clients giving certificate
errors.  Also, OWA Outlook Web Access would redirect to <a href="http://sites/owa">http://sites/owa</a>. 
The problem was the internal and external URL settings on the various transports in
Exchange 2007.  This powershell script helped to fix the problem.  Note,
some errors occurred for me but I was able to just step through the code and issue
the commands to the Exchange Shell manually to get the job finished.  The main
problem was the AutoDiscover Internal URI - once that was fixed the rest fell into
place.
</p>
        <p>
 
</p>
        <p>
          <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
            <span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class="Apple-style-span">#
Script to allow you to set all virtual directories to a common name like mail.company.com<br /><br />
Start-Transcript<br /><br />
# Variables<br /><br />
[string]$UMExtend = "/UnifiedMessaging/Service.asmx"<br />
[string]$OABExtend = "/OAB"<br />
[string]$SCPExtend = "/Autodiscover/Autodiscover.xml"<br />
[string]$EWSExtend = "/EWS/Exchange.asmx"<br />
[string]$ConfirmPrompt = "Set this Value? (Y/N)"<br />
[string]$NoChangeForeground = "white"<br />
[string]$NoChangeBackground = "red"<br /><br />
Write-host "This will allow you to set the virtual directories associated with Autodiscover
provided services to the name you provide."<br />
Write-host ""<br />
[string]$base = Read-host "Base name of virtual directory (e.g. mail.company.com)"<br />
write-host ""<br />
# =======================================================<br />
# Validate if a third party trusted certificate is being used<br />
# because BITS won't use untrusted certificates<br />
[string]$set = Read-host "Is the certificate being used an internally generated certificate?
(Y/N)"<br />
Write-host ""<br /><br />
if ($set -eq "Y")    {<br />
    [string]$OABprefix = "http://"<br />
}    else    {<br />
    [string]$OABprefix = "https://"<br />
}<br /><br />
# =======================================================<br />
# Build the Autodiscover URL and set the SCP Value<br /><br />
Write-host "Setting Autodiscover Service Connection Point" -foregroundcolor Yellow<br />
write-host ""<br /><br />
$SCPURL = "https://" + $base + $SCPExtend<br /><br />
[array]$SCPCurrent = Get-ClientAccessServer<br /><br />
Foreach ($value in $SCPCurrent) {<br />
    Write-host "Looking at Server: " $value.name<br />
    Write-host "Current SCP value: " $value.AutoDiscoverServiceInternalUri.absoluteuri<br />
    Write-host "New SCP Value:     " $SCPURL<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br />
    <br />
    if ($set -eq "Y")    {<br />
         Set-ClientAccessServer -id $value.identity
-AutoDiscoverServiceInternalUri $SCPURL<br />
    }    else {<br />
        write-host "Autodiscover Service Connection
Point internal value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground<br />
    }<br />
}<br /><br />
# =======================================================<br />
# Build the EWS URL and set the internal Value<br /><br />
Write-host "Setting Exchange Web Services Virtual Directories" -foregroundcolor Yellow<br />
write-host ""<br /><br />
$EWSURL = "https://" + $base + $EWSExtend<br /><br />
[array]$EWSCurrent = Get-WebServicesVirtualDirectory<br /><br />
Foreach ($value in $EWSCurrent) {<br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current Internal Value: " $value.internalURL<br />
    Write-host "New Internal Value:     " $EWSUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y")    {<br />
        Set-WebServicesVirtualDirectory -id $value.identity
-InternalURL $EWSURL<br />
     } else {<br />
        write-host "Exchange Web Services Virtual Directory
internal value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground<br />
     }<br /><br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current External Value: " $value.externalURL<br />
    Write-host "New External Value:     " $EWSUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y")    {<br />
        Set-WebServicesVirtualDirectory -id $value.identity
-ExternalURL $EWSURL<br />
    } else {<br />
        write-host "Exchange Web Services Virtual Directory
external value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground<br />
    }<br />
}<br /><br />
# ======================================================<br />
# Build the OAB URL and set the internal Value<br /><br />
Write-host "Setting OAB Virtual Directories" -foregroundcolor Yellow<br />
write-host ""<br /><br />
$OABURL = $OABprefix + $base + $OABExtend<br /><br />
[array]$OABCurrent = Get-OABVirtualDirectory<br /><br />
Foreach ($value in $OABcurrent) {<br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current Internal Value: " $value.internalURL<br />
    Write-host "New Internal Value:     " $OABUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y")    {<br />
        Set-OABVirtualDirectory -id $value.identity
-InternalURL $OABURL<br />
    } else {<br />
        write-host "OAB Virtual Directory internal value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground<br />
    }<br /><br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current External Value: " $value.externalURL<br />
    Write-host "New External Value:     " $OABUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y") {<br />
        Set-OABVirtualDirectory -id $value.identity
-ExternalURL $OABURL<br />
    } else {<br />
        write-host "OAB Virtual Directory external value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground<br />
    }<br />
}<br /><br />
# =======================================================<br />
# Build the UM URL and set the internal Value<br /><br />
Write-host "Setting UM Virtual Directories" -foregroundcolor Yellow<br />
write-host ""<br /><br />
$UMURL = "https://" + $base + $UMExtend<br /><br />
[array]$UMCurrent = Get-UMVirtualDirectory<br /><br />
foreach ($value in $UMCurrent) {<br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current Internal Value: " $value.internalURL<br />
    Write-host "New Internal Value:     " $UMUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y") {<br />
        Set-UMVirtualDirectory -id $value.identity -InternalURL
$UMURL<br />
    } else {<br />
        write-host "UM Virtual Directory internal value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground<br />
    }<br /><br />
    Write-host "Looking at Server: " $value.server<br />
    Write-host "Current External Value: " $value.externalURL<br />
    Write-host "New External Value:     " $UMUrl<br />
    [string]$set = Read-host $ConfirmPrompt<br />
    write-host ""<br /><br />
    if ($set -eq "Y") {<br />
        Set-UMVirtualDirectory -id $value.identity -ExternalURL
$UMURL<br />
    } else {<br />
        write-host "UM Virtual Directory external value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground<br />
    }<br />
}<br />
Stop-Transcript</span>
          </span>
        </p>
        <p>
          <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
            <span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class="Apple-style-span">
            </span>
          </span> 
</p>
        <p>
          <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
            <span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class="Apple-style-span">(<a href="http://www.exchangeninjas.com/set-allvdirs">http://www.exchangeninjas.com/set-allvdirs</a>)</span>
          </span>
        </p>
        <img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=975d4e5d-7e01-4872-8168-b35175084b0d" />
      </body>
      <title>Outlook 2007 and Exchange 2007 - Outlook gets certificate error when opening - trying to resolve to "sites" which is not on the UCC</title>
      <guid isPermaLink="false">http://blog.freedriversite.com/PermaLink,guid,975d4e5d-7e01-4872-8168-b35175084b0d.aspx</guid>
      <link>http://blog.freedriversite.com/2010/02/22/Outlook2007AndExchange2007OutlookGetsCertificateErrorWhenOpeningTryingToResolveToSitesWhichIsNotOnTheUCC.aspx</link>
      <pubDate>Mon, 22 Feb 2010 18:50:27 GMT</pubDate>
      <description>&lt;p&gt;
I had an issue with a Small Business Server SBS 2003 to SBS 2008 migration where once
everything was up and running, I had problems with Outlook 2007 Clients giving certificate
errors.&amp;nbsp; Also, OWA Outlook Web Access would redirect to &lt;a href="http://sites/owa"&gt;http://sites/owa&lt;/a&gt;.&amp;nbsp;
The problem was the internal and external URL settings on the various transports in
Exchange 2007.&amp;nbsp; This powershell script helped to fix the problem.&amp;nbsp; Note,
some errors occurred for me but I was able to just step through the code and issue
the commands to the Exchange Shell manually to get the job finished.&amp;nbsp; The main
problem was the AutoDiscover Internal URI - once that was fixed the rest fell into
place.
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;
&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class=Apple-style-span&gt;#
Script to allow you to set all virtual directories to a common name like mail.company.com&lt;br&gt;
&lt;br&gt;
Start-Transcript&lt;br&gt;
&lt;br&gt;
# Variables&lt;br&gt;
&lt;br&gt;
[string]$UMExtend = "/UnifiedMessaging/Service.asmx"&lt;br&gt;
[string]$OABExtend = "/OAB"&lt;br&gt;
[string]$SCPExtend = "/Autodiscover/Autodiscover.xml"&lt;br&gt;
[string]$EWSExtend = "/EWS/Exchange.asmx"&lt;br&gt;
[string]$ConfirmPrompt = "Set this Value? (Y/N)"&lt;br&gt;
[string]$NoChangeForeground = "white"&lt;br&gt;
[string]$NoChangeBackground = "red"&lt;br&gt;
&lt;br&gt;
Write-host "This will allow you to set the virtual directories associated with Autodiscover
provided services to the name you provide."&lt;br&gt;
Write-host ""&lt;br&gt;
[string]$base = Read-host "Base name of virtual directory (e.g. mail.company.com)"&lt;br&gt;
write-host ""&lt;br&gt;
# =======================================================&lt;br&gt;
# Validate if a third party trusted certificate is being used&lt;br&gt;
# because BITS won't use untrusted certificates&lt;br&gt;
[string]$set = Read-host "Is the certificate being used an internally generated certificate?
(Y/N)"&lt;br&gt;
Write-host ""&lt;br&gt;
&lt;br&gt;
if ($set -eq "Y")&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$OABprefix = "http://"&lt;br&gt;
}&amp;nbsp;&amp;nbsp; &amp;nbsp;else&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$OABprefix = "https://"&lt;br&gt;
}&lt;br&gt;
&lt;br&gt;
# =======================================================&lt;br&gt;
# Build the Autodiscover URL and set the SCP Value&lt;br&gt;
&lt;br&gt;
Write-host "Setting Autodiscover Service Connection Point" -foregroundcolor Yellow&lt;br&gt;
write-host ""&lt;br&gt;
&lt;br&gt;
$SCPURL = "https://" + $base + $SCPExtend&lt;br&gt;
&lt;br&gt;
[array]$SCPCurrent = Get-ClientAccessServer&lt;br&gt;
&lt;br&gt;
Foreach ($value in $SCPCurrent) {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.name&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current SCP value: " $value.AutoDiscoverServiceInternalUri.absoluteuri&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New SCP Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $SCPURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y")&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp;Set-ClientAccessServer -id $value.identity
-AutoDiscoverServiceInternalUri $SCPURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&amp;nbsp;&amp;nbsp; &amp;nbsp;else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "Autodiscover Service Connection
Point internal value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
}&lt;br&gt;
&lt;br&gt;
# =======================================================&lt;br&gt;
# Build the EWS URL and set the internal Value&lt;br&gt;
&lt;br&gt;
Write-host "Setting Exchange Web Services Virtual Directories" -foregroundcolor Yellow&lt;br&gt;
write-host ""&lt;br&gt;
&lt;br&gt;
$EWSURL = "https://" + $base + $EWSExtend&lt;br&gt;
&lt;br&gt;
[array]$EWSCurrent = Get-WebServicesVirtualDirectory&lt;br&gt;
&lt;br&gt;
Foreach ($value in $EWSCurrent) {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current Internal Value: " $value.internalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New Internal Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $EWSUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y")&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-WebServicesVirtualDirectory -id $value.identity
-InternalURL $EWSURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp; } else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "Exchange Web Services Virtual Directory
internal value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp; }&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current External Value: " $value.externalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New External Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $EWSUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y")&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-WebServicesVirtualDirectory -id $value.identity
-ExternalURL $EWSURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;} else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "Exchange Web Services Virtual Directory
external value NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor
$NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
}&lt;br&gt;
&lt;br&gt;
# ======================================================&lt;br&gt;
# Build the OAB URL and set the internal Value&lt;br&gt;
&lt;br&gt;
Write-host "Setting OAB Virtual Directories" -foregroundcolor Yellow&lt;br&gt;
write-host ""&lt;br&gt;
&lt;br&gt;
$OABURL = $OABprefix + $base + $OABExtend&lt;br&gt;
&lt;br&gt;
[array]$OABCurrent = Get-OABVirtualDirectory&lt;br&gt;
&lt;br&gt;
Foreach ($value in $OABcurrent) {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current Internal Value: " $value.internalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New Internal Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $OABUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y")&amp;nbsp;&amp;nbsp; &amp;nbsp;{&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-OABVirtualDirectory -id $value.identity
-InternalURL $OABURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;} else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "OAB Virtual Directory internal value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current External Value: " $value.externalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New External Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $OABUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y") {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-OABVirtualDirectory -id $value.identity
-ExternalURL $OABURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;} else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "OAB Virtual Directory external value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
}&lt;br&gt;
&lt;br&gt;
# =======================================================&lt;br&gt;
# Build the UM URL and set the internal Value&lt;br&gt;
&lt;br&gt;
Write-host "Setting UM Virtual Directories" -foregroundcolor Yellow&lt;br&gt;
write-host ""&lt;br&gt;
&lt;br&gt;
$UMURL = "https://" + $base + $UMExtend&lt;br&gt;
&lt;br&gt;
[array]$UMCurrent = Get-UMVirtualDirectory&lt;br&gt;
&lt;br&gt;
foreach ($value in $UMCurrent) {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current Internal Value: " $value.internalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New Internal Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $UMUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y") {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-UMVirtualDirectory -id $value.identity -InternalURL
$UMURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;} else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "UM Virtual Directory internal value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Looking at Server: " $value.server&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "Current External Value: " $value.externalURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;Write-host "New External Value:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; " $UMUrl&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;[string]$set = Read-host $ConfirmPrompt&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host ""&lt;br&gt;
&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;if ($set -eq "Y") {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Set-UMVirtualDirectory -id $value.identity -ExternalURL
$UMURL&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;} else {&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;write-host "UM Virtual Directory external value
NOT changed" -foregroundcolor $NoChangeForeground -backgroundcolor $NoChangeBackground&lt;br&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;}&lt;br&gt;
}&lt;br&gt;
Stop-Transcript&lt;/span&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class=Apple-style-span&gt;&lt;/span&gt;&lt;/span&gt;&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;
&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: medium 'Times New Roman'; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="TEXT-ALIGN: left; FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: rgb(0,153,204); FONT-SIZE: 14px" class=Apple-style-span&gt;(&lt;a href="http://www.exchangeninjas.com/set-allvdirs"&gt;http://www.exchangeninjas.com/set-allvdirs&lt;/a&gt;)&lt;/span&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=975d4e5d-7e01-4872-8168-b35175084b0d" /&gt;</description>
      <comments>http://blog.freedriversite.com/CommentView,guid,975d4e5d-7e01-4872-8168-b35175084b0d.aspx</comments>
      <category>Exchange 2007</category>
      <category>SBS 2008</category>
    </item>
    <item>
      <trackback:ping>http://blog.freedriversite.com/Trackback.aspx?guid=0f4bb55f-2cec-47a2-99f1-43dc5918b9a3</trackback:ping>
      <pingback:server>http://blog.freedriversite.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.freedriversite.com/PermaLink,guid,0f4bb55f-2cec-47a2-99f1-43dc5918b9a3.aspx</pingback:target>
      <dc:creator>FreeDriverSiteAdmin</dc:creator>
      <wfw:comment>http://blog.freedriversite.com/CommentView,guid,0f4bb55f-2cec-47a2-99f1-43dc5918b9a3.aspx</wfw:comment>
      <wfw:commentRss>http://blog.freedriversite.com/SyndicationService.asmx/GetEntryCommentsRss?guid=0f4bb55f-2cec-47a2-99f1-43dc5918b9a3</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
As you probably knew, or do now since you are searching for this information, Exchange
2007 requires a UCC Multi-Domain SSL Certificate to properly function.  Here
are some tips for setting it up.
</p>
        <p>
-Pick your favorite vendor to purchase the UCC SSL from and make the purchase
</p>
        <p>
-Generate the request from the Exchange 2007 Server.  To do this, open the Management
Shell and issue the New-ExchangeCertificate command.  A great tool is provided
here: <a href="https://www.digicert.com/easy-csr/exchange2007.htm">https://www.digicert.com/easy-csr/exchange2007.htm</a>. 
You can use this tool to generate the request and it will save the information to
a file in the path you can specify or leave default
</p>
        <p>
   For Example:  Lets say we have an Exchange 2007 Server whos
Internet Address is mail.rockabilly.com and its local domain address is exch07.rockabilly.local. 
I would also include <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span"><span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span"><font face="Verdana"><font size="2">remote.rockabilly.com,
rockaserver.rockabilly.local, autodiscover.rockabilly.com, autodiscover.rockabilly.local
in the list of requested names.  Feeding this into the tool yields the following
request:  "<span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span"><span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span"><font size="2" face="Verdana">New-ExchangeCertificate
-GenerateRequest -Path c:\mail_rockabilly_com.csr -KeySize 2048 -SubjectName "c=US,
s=Utah, l=YourTown, o=RockABillyDoodles, ou=IT, cn=mail.rockabilly.com" -DomainName
remote.rockabilly.com, pcrserver.rockabilly.local, autodiscover.rockabilly.com, autodiscover.rockabilly.local
-PrivateKeyExportable $True"  Copy and paste this request into your Exchange
Server Management Shell and it will spit out the request to c:\mail_rockabilly_com.csr. 
Open this in Notepad and copy and paste the request into the request fields at the
site where you purchased the SSL cert.</font>  </span></span></font></font></span></span></p>
        <p>
          <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
            <span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span">
              <font face="Verdana">
                <font size="2">
                  <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
                    <span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span">-Once
the request is received by the registering entity, an email will be generated to approve
this request.  The email will go to the contacts on the WHOIS record for the
domain.  Ensure you have access to those email accounts so you can approve the
request.</span>
                  </span>
                </font>
              </font>
            </span>
          </span>
        </p>
        <p>
          <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
            <span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span">
              <font face="Verdana">
                <font size="2">
                  <span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class="Apple-style-span">
                    <span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class="Apple-style-span">-Once
the request is approved and you are able to download the certificate, the next step
is to install it into the Exchange 2007 server.</span>
                  </span>
                </font>
              </font>
            </span>
          </span>
        </p>
        <img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=0f4bb55f-2cec-47a2-99f1-43dc5918b9a3" />
      </body>
      <title>Setting up Unified Communications SSL Certificate (UCC) in Exchange 2007</title>
      <guid isPermaLink="false">http://blog.freedriversite.com/PermaLink,guid,0f4bb55f-2cec-47a2-99f1-43dc5918b9a3.aspx</guid>
      <link>http://blog.freedriversite.com/2010/02/12/SettingUpUnifiedCommunicationsSSLCertificateUCCInExchange2007.aspx</link>
      <pubDate>Fri, 12 Feb 2010 22:13:21 GMT</pubDate>
      <description>&lt;p&gt;
As you probably knew, or do now since you are searching for this information, Exchange
2007 requires a UCC Multi-Domain SSL Certificate to properly function.&amp;nbsp; Here
are some tips for setting it up.
&lt;/p&gt;
&lt;p&gt;
-Pick your favorite vendor to purchase the UCC SSL from and make the purchase
&lt;/p&gt;
&lt;p&gt;
-Generate the request from the Exchange 2007 Server.&amp;nbsp; To do this, open the Management
Shell and issue the New-ExchangeCertificate command.&amp;nbsp; A great tool is provided
here: &lt;a href="https://www.digicert.com/easy-csr/exchange2007.htm"&gt;https://www.digicert.com/easy-csr/exchange2007.htm&lt;/a&gt;.&amp;nbsp;
You can use this tool to generate the request and it will save the information to
a file in the path you can specify or leave default
&lt;/p&gt;
&lt;p&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;For Example:&amp;nbsp; Lets say we have an Exchange 2007 Server whos
Internet Address is mail.rockabilly.com and its local domain address is exch07.rockabilly.local.&amp;nbsp;
I would also include &lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;&lt;font face=Verdana&gt;&lt;font size=2&gt;remote.rockabilly.com,
rockaserver.rockabilly.local, autodiscover.rockabilly.com, autodiscover.rockabilly.local
in the list of requested names.&amp;nbsp; Feeding this into the tool yields the following
request:&amp;nbsp; "&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;&lt;font size=2 face=Verdana&gt;New-ExchangeCertificate
-GenerateRequest -Path c:\mail_rockabilly_com.csr -KeySize 2048 -SubjectName "c=US,
s=Utah, l=YourTown, o=RockABillyDoodles, ou=IT, cn=mail.rockabilly.com" -DomainName
remote.rockabilly.com, pcrserver.rockabilly.local, autodiscover.rockabilly.com, autodiscover.rockabilly.local
-PrivateKeyExportable $True"&amp;nbsp; Copy and paste this request into your Exchange
Server Management Shell and it will spit out the request to c:\mail_rockabilly_com.csr.&amp;nbsp;
Open this in Notepad and copy and paste the request into the request fields at the
site where you purchased the SSL cert.&lt;/font&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;&lt;font face=Verdana&gt;&lt;font size=2&gt;&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;-Once
the request is received by the registering entity, an email will be generated to approve
this request.&amp;nbsp; The email will go to the contacts on the WHOIS record for the
domain.&amp;nbsp; Ensure you have access to those email accounts so you can approve the
request.&lt;/span&gt;&lt;/span&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;&lt;font face=Verdana&gt;&lt;font size=2&gt;&lt;span style="WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; BORDER-COLLAPSE: separate; FONT: 12px Verdana, Arial, Helvetica, sans-serif; WHITE-SPACE: normal; ORPHANS: 2; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px" class=Apple-style-span&gt;&lt;span style="FONT-FAMILY: tahoma, arial, helvetica, sans-serif; WHITE-SPACE: pre-wrap" class=Apple-style-span&gt;-Once
the request is approved and you are able to download the certificate, the next step
is to install it into the Exchange 2007 server.&lt;/span&gt;&lt;/span&gt;&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=0f4bb55f-2cec-47a2-99f1-43dc5918b9a3" /&gt;</description>
      <comments>http://blog.freedriversite.com/CommentView,guid,0f4bb55f-2cec-47a2-99f1-43dc5918b9a3.aspx</comments>
      <category>Exchange 2007</category>
      <category>Exchange 2010</category>
    </item>
    <item>
      <trackback:ping>http://blog.freedriversite.com/Trackback.aspx?guid=79b10737-a49d-40bb-a3cd-edf6eda3c2f2</trackback:ping>
      <pingback:server>http://blog.freedriversite.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.freedriversite.com/PermaLink,guid,79b10737-a49d-40bb-a3cd-edf6eda3c2f2.aspx</pingback:target>
      <dc:creator>FreeDriverSiteAdmin</dc:creator>
      <wfw:comment>http://blog.freedriversite.com/CommentView,guid,79b10737-a49d-40bb-a3cd-edf6eda3c2f2.aspx</wfw:comment>
      <wfw:commentRss>http://blog.freedriversite.com/SyndicationService.asmx/GetEntryCommentsRss?guid=79b10737-a49d-40bb-a3cd-edf6eda3c2f2</wfw:commentRss>
      <slash:comments>1</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">To enable protocol logging on Receive Connectors,
use the following command:<p class="code">
Set-ReceiveConnector "Connector Name" -ProtocolLoggingLevel verbose
</p>
In case you're wondering if there are any choices for the logging level - there aren't.
It's either verbose or none.<br /><br />
To enable protocol logging from the Exchange console, go to <span class="bold">Server
Configuration</span> | <span class="bold">Hub Transport</span> | select the Hub Transport
server you want to configure | select the <span class="bold">Receive Connector</span> -&gt; <span class="bold">properties</span> | <span class="bold">General</span> tab
| change <span class="bold">Protcol logging level</span> to <span class="bold">Verbose</span>,
as shown in the screenshot below.<br /><br /><img alt="Screenshot: Enabling SMTP protocol logging on a Receive Connector in Exchange 2007" src="http://exchangepedia.com/blog/images/ReceiveConn-Logging.gif" /><br /><span class="caption"><span class="bold">Figure 1:</span> Enabling SMTP logging on
a Receive Connector</span><br /><br />
Unlike Exchange Server 2003/2000, you have to enable logging separately for Send Connectors
(equivalent of SMTP Connectors), using the following command:<p class="code">
Set-SendConnector "Send Connector Name" -ProtocolLoggingLevel verbose
</p>
To do this using the Exchange console, go to <span style="font-weight: bold;">Organization
Configuration</span> | <span style="font-weight: bold;">Hub Transport</span> | <span style="font-weight: bold;">Send
Connectors</span> tab | select the <span style="font-weight: bold;">Send Connector</span> -&gt; <span style="font-weight: bold;">properties</span> | <span style="font-weight: bold;">General</span> tab
| change <span style="font-weight: bold;">Protocol logging level</span> to <span style="font-weight: bold;">verbose</span>.<br /><br />
Besides the visible Receive and Send connectors, <span class="highlightyellow">an
invisible Send Connector lurks under the hood - used to transport messages within
the organization</span>, between Hub Transport servers, Edge Transport servers, and
Exchange Server 2003/2000 servers. It's the Intra-Organization Send Connector. You
won't see it in the console, or in the shell if you use the <span class="command">get-SendConnector</span> command.
To configure protocol logging for this Intra-Organization Send Connector:<p class="code">
Set-TransportServer "TRANSPORT SERVER NAME" -IntraOrgConnectorProtocolLoggingLevel
verbose
</p><br /><span class="sectionhead2">Where do protocol logs reside?</span><br />
- Unlike Exchange Server 2003/2000, which maintain separate protocol logs for each
instance of a SMTP Virtual Server, all Receive Connectors share "SmtpReceive" logs.
Similarly, Send Connectors share "SmtpSend" logs.<br />
- Receive Connector logs are located in 
<br /><span class="command highlightyellow">\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive</span><br />
- Send Connector logs are located in 
<br /><span class="command highlightyellow">\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend</span><br /><span style="font-weight: bold;"><br />
How do you change the path of SMTP logs?</span><br /><br />
To change the path of SmtpReceive logs:<p class="code">
Set-TransportServer "TRANSPORT SERVER NAME" -ReceiveProtocolLogPath "C:\New SmtpReceive
Log File Directory"
</p>
To change the path of SmtpSend logs:<p class="code">
Set-TransportServer "TRANSPORT SERVER NAME" -SendProtocolLogPath "C:\New SmtpSend
Log File Directory"
</p>
If you do decide to change the path, ensure the new directories/folders exist with
appropriate permissions, as outlined in "<a class="external-link" title="Go to 'How to Configure Protocol Logging' in Exchange 2007 online documentation on microsoft.com" href="http://technet.microsoft.com/en-us/library/bb124531.aspx">How
to Configure Protocol Logging</a>" in the product documentation. In addition to the
above, you can also <span class="highlightyellow">control the maximum log file size,
the maximum directory size, and the maximum age of log files</span>. This ensures
you don't have to worry about purging the logs manually over time, or scheduling a
script to do this periodically.<br /><br />
SMTP logs are an important troubleshooting tool - enabling SMTP logging after the
fact isn't any help when troubleshooting SMTP mail flow.<p></p><img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=79b10737-a49d-40bb-a3cd-edf6eda3c2f2" /></body>
      <title>Setup SMTP Logging in Exchange Server 2007</title>
      <guid isPermaLink="false">http://blog.freedriversite.com/PermaLink,guid,79b10737-a49d-40bb-a3cd-edf6eda3c2f2.aspx</guid>
      <link>http://blog.freedriversite.com/2009/06/18/SetupSMTPLoggingInExchangeServer2007.aspx</link>
      <pubDate>Thu, 18 Jun 2009 18:45:20 GMT</pubDate>
      <description>To enable protocol logging on Receive Connectors, use the following command:&lt;p class="code"&gt;
Set-ReceiveConnector "Connector Name" -ProtocolLoggingLevel verbose
&lt;/p&gt;
In case you're wondering if there are any choices for the logging level - there aren't.
It's either verbose or none.&lt;br&gt;
&lt;br&gt;
To enable protocol logging from the Exchange console, go to &lt;span class="bold"&gt;Server
Configuration&lt;/span&gt; | &lt;span class="bold"&gt;Hub Transport&lt;/span&gt; | select the Hub Transport
server you want to configure | select the &lt;span class="bold"&gt;Receive Connector&lt;/span&gt; -&amp;gt; &lt;span class="bold"&gt;properties&lt;/span&gt; | &lt;span class="bold"&gt;General&lt;/span&gt; tab
| change &lt;span class="bold"&gt;Protcol logging level&lt;/span&gt; to &lt;span class="bold"&gt;Verbose&lt;/span&gt;,
as shown in the screenshot below.&lt;br&gt;
&lt;br&gt;
&lt;img alt="Screenshot: Enabling SMTP protocol logging on a Receive Connector in Exchange 2007" src="http://exchangepedia.com/blog/images/ReceiveConn-Logging.gif"&gt;
&lt;br&gt;
&lt;span class="caption"&gt;&lt;span class="bold"&gt;Figure 1:&lt;/span&gt; Enabling SMTP logging on
a Receive Connector&lt;/span&gt;
&lt;br&gt;
&lt;br&gt;
Unlike Exchange Server 2003/2000, you have to enable logging separately for Send Connectors
(equivalent of SMTP Connectors), using the following command:&lt;p class="code"&gt;
Set-SendConnector "Send Connector Name" -ProtocolLoggingLevel verbose
&lt;/p&gt;
To do this using the Exchange console, go to &lt;span style="font-weight: bold;"&gt;Organization
Configuration&lt;/span&gt; | &lt;span style="font-weight: bold;"&gt;Hub Transport&lt;/span&gt; | &lt;span style="font-weight: bold;"&gt;Send
Connectors&lt;/span&gt; tab | select the &lt;span style="font-weight: bold;"&gt;Send Connector&lt;/span&gt; -&amp;gt; &lt;span style="font-weight: bold;"&gt;properties&lt;/span&gt; | &lt;span style="font-weight: bold;"&gt;General&lt;/span&gt; tab
| change &lt;span style="font-weight: bold;"&gt;Protocol logging level&lt;/span&gt; to &lt;span style="font-weight: bold;"&gt;verbose&lt;/span&gt;.&lt;br&gt;
&lt;br&gt;
Besides the visible Receive and Send connectors, &lt;span class="highlightyellow"&gt;an
invisible Send Connector lurks under the hood - used to transport messages within
the organization&lt;/span&gt;, between Hub Transport servers, Edge Transport servers, and
Exchange Server 2003/2000 servers. It's the Intra-Organization Send Connector. You
won't see it in the console, or in the shell if you use the &lt;span class="command"&gt;get-SendConnector&lt;/span&gt; command.
To configure protocol logging for this Intra-Organization Send Connector:&lt;p class="code"&gt;
Set-TransportServer "TRANSPORT SERVER NAME" -IntraOrgConnectorProtocolLoggingLevel
verbose
&lt;/p&gt;
&lt;br&gt;
&lt;span class="sectionhead2"&gt;Where do protocol logs reside?&lt;/span&gt;
&lt;br&gt;
- Unlike Exchange Server 2003/2000, which maintain separate protocol logs for each
instance of a SMTP Virtual Server, all Receive Connectors share "SmtpReceive" logs.
Similarly, Send Connectors share "SmtpSend" logs.&lt;br&gt;
- Receive Connector logs are located in 
&lt;br&gt;
&lt;span class="command highlightyellow"&gt;\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive&lt;/span&gt;
&lt;br&gt;
- Send Connector logs are located in 
&lt;br&gt;
&lt;span class="command highlightyellow"&gt;\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend&lt;/span&gt;
&lt;br&gt;
&lt;span style="font-weight: bold;"&gt;
&lt;br&gt;
How do you change the path of SMTP logs?&lt;/span&gt;
&lt;br&gt;
&lt;br&gt;
To change the path of SmtpReceive logs:&lt;p class="code"&gt;
Set-TransportServer "TRANSPORT SERVER NAME" -ReceiveProtocolLogPath "C:\New SmtpReceive
Log File Directory"
&lt;/p&gt;
To change the path of SmtpSend logs:&lt;p class="code"&gt;
Set-TransportServer "TRANSPORT SERVER NAME" -SendProtocolLogPath "C:\New SmtpSend
Log File Directory"
&lt;/p&gt;
If you do decide to change the path, ensure the new directories/folders exist with
appropriate permissions, as outlined in "&lt;a class="external-link" title="Go to 'How to Configure Protocol Logging' in Exchange 2007 online documentation on microsoft.com" href="http://technet.microsoft.com/en-us/library/bb124531.aspx"&gt;How
to Configure Protocol Logging&lt;/a&gt;" in the product documentation. In addition to the
above, you can also &lt;span class="highlightyellow"&gt;control the maximum log file size,
the maximum directory size, and the maximum age of log files&lt;/span&gt;. This ensures
you don't have to worry about purging the logs manually over time, or scheduling a
script to do this periodically.&lt;br&gt;
&lt;br&gt;
SMTP logs are an important troubleshooting tool - enabling SMTP logging after the
fact isn't any help when troubleshooting SMTP mail flow.&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=79b10737-a49d-40bb-a3cd-edf6eda3c2f2" /&gt;</description>
      <comments>http://blog.freedriversite.com/CommentView,guid,79b10737-a49d-40bb-a3cd-edf6eda3c2f2.aspx</comments>
      <category>Exchange 2007</category>
      <category>KnowledgeBaseArticles</category>
    </item>
    <item>
      <trackback:ping>http://blog.freedriversite.com/Trackback.aspx?guid=1c688246-212c-4253-beaf-18c3341cf601</trackback:ping>
      <pingback:server>http://blog.freedriversite.com/pingback.aspx</pingback:server>
      <pingback:target>http://blog.freedriversite.com/PermaLink,guid,1c688246-212c-4253-beaf-18c3341cf601.aspx</pingback:target>
      <dc:creator>FreeDriverSiteAdmin</dc:creator>
      <wfw:comment>http://blog.freedriversite.com/CommentView,guid,1c688246-212c-4253-beaf-18c3341cf601.aspx</wfw:comment>
      <wfw:commentRss>http://blog.freedriversite.com/SyndicationService.asmx/GetEntryCommentsRss?guid=1c688246-212c-4253-beaf-18c3341cf601</wfw:commentRss>
      <slash:comments>2</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">Here are some great notes on setting the
content filter parameters in Exchange 2007:<br /><br /><p>
Open the <strong>Exchange Management Shell</strong>:
</p><p><strong># To check the Content Filter configuration</strong>, type in:
</p><p><em> Get-ContentFilterConfig</em></p><p><strong># To set the Bypassed Senders </strong>(example):
</p><p><em>Set-ContentFilterConfig -BypassedSenders donotspamme@calazan.com, jdoe@abc.com</em></p><p><strong># To set the Bypassed Sender Domains</strong> (example):
</p><p><em>Set-ContentFilterConfig -BypassedSenderDomains calazan.com, *.xyz.com</em></p><p><strong>Important Note:</strong> BypassedSenders and BypassedSenderDomains are multivalued
properties. When you use the <strong>Set-ContentFilterConfig</strong> cmdlet, it will
overwrite the values of those properties. If you just need to add more senders or
domains, please follow the example below.
</p><p><strong># To add Bypassed Senders:</strong></p><p><em>$x = Get-ContentFilterConfig</em></p><p><em>$x.BypassedSenders += “jsmith@google.com”, “bhope@yahoo.com”</em></p><p><strong># To remove Bypassed Senders (can only be done one at a time):</strong></p><p><em>$x = Get-ContentFilterConfig</em></p><p><em>$x.BypassedSenders -= “jsmith@google.com”</em></p><p><strong># To empty the list:</strong></p><p><em>Set-ContentFilterConfig -BypassedSenders $null</em></p><br /><p></p><img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=1c688246-212c-4253-beaf-18c3341cf601" /></body>
      <title>Exchange 2007 SP1: Message rejected as spam by Content Filtering</title>
      <guid isPermaLink="false">http://blog.freedriversite.com/PermaLink,guid,1c688246-212c-4253-beaf-18c3341cf601.aspx</guid>
      <link>http://blog.freedriversite.com/2009/06/18/Exchange2007SP1MessageRejectedAsSpamByContentFiltering.aspx</link>
      <pubDate>Thu, 18 Jun 2009 18:43:13 GMT</pubDate>
      <description>Here are some great notes on setting the content filter parameters in Exchange 2007:&lt;br&gt;
&lt;br&gt;
&lt;p&gt;
Open the &lt;strong&gt;Exchange Management Shell&lt;/strong&gt;:
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To check the Content Filter configuration&lt;/strong&gt;, type in:
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt; Get-ContentFilterConfig&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To set the Bypassed Senders &lt;/strong&gt;(example):
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Set-ContentFilterConfig -BypassedSenders donotspamme@calazan.com, jdoe@abc.com&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To set the Bypassed Sender Domains&lt;/strong&gt; (example):
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Set-ContentFilterConfig -BypassedSenderDomains calazan.com, *.xyz.com&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Important Note:&lt;/strong&gt; BypassedSenders and BypassedSenderDomains are multivalued
properties. When you use the &lt;strong&gt;Set-ContentFilterConfig&lt;/strong&gt; cmdlet, it will
overwrite the values of those properties. If you just need to add more senders or
domains, please follow the example below.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To add Bypassed Senders:&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;$x = Get-ContentFilterConfig&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;$x.BypassedSenders += “jsmith@google.com”, “bhope@yahoo.com”&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To remove Bypassed Senders (can only be done one at a time):&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;$x = Get-ContentFilterConfig&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;$x.BypassedSenders -= “jsmith@google.com”&lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;# To empty the list:&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Set-ContentFilterConfig -BypassedSenders $null&lt;/em&gt;
&lt;/p&gt;
&lt;br&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.freedriversite.com/aggbug.ashx?id=1c688246-212c-4253-beaf-18c3341cf601" /&gt;</description>
      <comments>http://blog.freedriversite.com/CommentView,guid,1c688246-212c-4253-beaf-18c3341cf601.aspx</comments>
      <category>KnowledgeBaseArticles</category>
      <category>Exchange 2007</category>
    </item>
  </channel>
</rss>