1. Open cmd
2. Type: nslookup
3. Type: set type=all
4. Type the SRV record to list its content

For OCS 2007 R2

• External
  • _sip._tls.domain.com
    • Usually points to Access EDGE FQDN on port 443 
  • _sipfederationtls._tcp.domain.com
    • Usually points to Access EDGE FQDN on port 5061
• Internal
  • _sipinternaltls._tcp.domain.com
    • Usually points to Pool name with correct sip domain on port 5061

For Exchange 2007/2010

• External autodiscover
  • _autodiscover._tcp.domain.com
    • Usually points to owa FQDN listener with NTLM negotiate on port 443

Problem: Receiving following error on Exchange 2010 server after opening EMC and expending Mailbox tab under organization configuration. An error caused a change in the current set of domain controllers. It was running command ‘Get-FederationTrust”

Possible causes:

To be honest first thing I checked was to make sure Exchange server is able to talk to all domain controllers as its configured on its TCP/IP properties.Also as always check to see anything catches your attention under application logs. Fair enough I was able to locate the event log “2080” MsExchangeADAccess” was showing me one DC only, however the TCP/IP stack was configured to talk to secondary DC.

Make sure Exchange is able to talk to all DC’s within its “Site”. Above example the second DC was not even discovered by MSExchange AD access, due to replication problems existed among the DC’s in the  site where exchange is residing. After fixing the relocation issues and restarting MSExchangeADTopology service took care of the error.

Note:

Some other people who had same error assumed to fix this issue by deleting the local profile ( corrupted profile) for the user account they logged into Exchange server. So if the above solution does not work, try this:

This error is actually a false error, and is caused by GUI caching, more specifically MMC caching. This occurs when a DC (domain controller) that is either unreachable or has changed in some way is still cached by the MMC applet. To fix this issue by removing the cache and basically resetting the MMC applet do this:

 Delete this file: “c:\users\<specific user>\appdata\roaming\microsoft\mmc\Exchange Management Console“

Source: http://trycatch.be/blogs/pdtit/archive/2010/02/04/an-error-caused-a-change-in-the-current-set-of-domain-controllers-exchange-2010.aspx

Here is the main new features in Exchange 2010 SP1 and how to configure them

• Installation of prerequisites made part of SP1 setup process
  • http://www.howexchangeworks.com/2010/06/installing-exchange-2010-pre-requisites.html
• DAG improvements
  • DAC mode support for 2 node DAG’s over two datacenters and in single AD sites
    • http://www.shudnow.net/2010/06/30/exchange-2010-database-activation-coordination-dac/
  • Ability to set static IP and Alternate Witness Server in EMC
    • http://www.howexchangeworks.com/2010/06/more-database-availability-group-dag.html
  • Continuous Replication – Block Mode. Each update to the log file is updated on the copy databases
    • http://blogs.technet.com/b/scottschnoll/archive/2010/04/10/new-high-availability-features-in-exchange-2010-sp1.aspx
• Archiving improvements
  • Archives can be stored in different databases, DAG’s and servers
    • http://www.shudnow.net/2010/04/07/exchange-2010-sp1-personal-archive-mailboxes-on-separate-databases/
  • Create retention policy tags for automating archiving
    • http://www.shudnow.net/2010/04/08/exchange-2010-sp1-retention-policies/
  • Outlook 2007 can access archive mailboxes
• Import and Export of mailboxes can be done directly to pst files without the need for Outlook
  • http://www.nitingupta.in/blogs/index.php/2010/06/16/how-to-import-pst-files-into-personal-archive-mailbox-in-exchange-2010-sp1-beta/
• E-Discovery improvements
  • View preview of search before actually performing the search
  • De-Duplication of emails in the search result sent to the DiscoveryMailbox
  • http://www.howexchangeworks.com/2010/06/mailbox-search-improvements-in-exchange.html
• Support for iCal Calendar Sharing
  • Enables the administrator to publish calendars publicly
  • http://www.stevieg.org/2010/06/calendar-sharing-improvements-coming-in-exchange-2010-sp1/
• Administrator Audit Logging improvements
  • Review Audit Log Entries in the Shell
  • Manually Write Entries to the Audit Log
  • Review Audit Reports in ECP
  • http://www.mikepfeiffer.net/2010/07/whats-new-in-administrator-audit-logging-in-exchange-2010-sp1-beta/
• OWA improvements
  • Ability to choose themes. Branding of OWA can be down with only one theme for the entire organization
    • http://www.howexchangeworks.com/2010/06/themes-are-back-in-exchange-2010-sp1.html
  • Delivery reports improvements
    • http://www.howexchangeworks.com/2010/06/delivery-reports-in-exchange-2010-sp1.html
• ECP, more configuration possibilities available
  • Journar rules
    • http://www.howexchangeworks.com/2010/06/transport-rules-in-exchange-2010-sp1.html
  • Transport rules
  • MailTips
  • Manage Litigation Hold
    • http://www.howexchangeworks.com/2010/06/litigation-hold-exposed-in-exchange.html
• Public Folder permissions added to EMC
  • http://www.howexchangeworks.com/2010/06/public-folder-permissions-added-to.htm

 Some minor changes in how to configure some features

• Change to how static ports are assigned on a CAS server
  • http://blogs.msexchange.org/walther/2010/06/09/exchange-2010-sp1-change-to-how-static-ports-are-assigned-on-a-cas-server/
• Reset virtual directories in EMC
  • http://www.howexchangeworks.com/2010/06/reset-virtual-directory-in-exchange.html
• Change to how to configure OWA integration with OCS 2007 R2
  • http://msunified.net/2010/06/22/exchange-2010-rtm-and-sp1-owa-integration-with-ocs-2007-r2/

You can find a longer list of new features here: http://exchangepedia.com/2010/06/released-exchange-sever-2010-sp1-beta.html
TechEd 2010 Interviews with folks from the Exchange Product group about SP1: http://blogs.msexchange.org/walther/2010/06/16/teched-2010-interviews-with-folks-from-the-exchange-product-group/

Prerequisites

1. Download and install OCS 2007 R2 Web Trust Tool on the Exchange 2010 server
   1. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ca107ab1-63c8-4c6a-816d-17961393d2b8 
   2. Locate and install the following files in elevated mode by running cmd.exe as administrator
      • vc_redistx64
      • UCMAredist.msi
      • CWAOWASSP.msi
2. If the Exchange 2010 server is running on Server 2008 R2 you also need to install the latest cumulative hotfix update for OCS 2007 R2 on the Exchange server
   1. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4
   2. Download and run ServerUpdateInstaller.exe
   3. Also download the latest update for UCMAredist that is not included in CU5
      • http://support.microsoft.com/?kbid=982614
   4. Reboot the server

Configuring Exchange 2010 RTM

NOTE: The below steps need to be done on all Exchange 2010 CAS servers in you deployment

1. Download and run the PowerShell Script found in the below link
   1. http://msunified.net/exchange-downloads/script-imexintegration-ps1/
   2. The script will not configure anything
   3. It takes backup of web.conf and  generates the configuration you manually need to add the web.conf file
   4. The script makes it easy to generate the correct syntax for populating the below keys 
2. Navigate to the web.conf file
   1. C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\web.conf
   2. Edit the file and search for the string IMPoolName
   3. Replace the three “add key” strings with the ones provided with the script
3. In Exchange Management Shell run the following command to configure OWA Virtual Directory

   • Get-OwaVirtualDirectory -Server "CasServer" | Set-OwaVirtualDirectory -InstantMessagingType 1

     • NOTE: The RTM documentation states OCS, but that don’t work. Use 1 as InstantMessagingType
4. Run IISreset in PowerShell

Configuring Exchange 2010 SP1

The Exchange 2010 SP1 guide is based on this great post written by Martin Sundström: http://msundis.wordpress.com/2010/06/21/integrate-ocs-2007-r2-with-exchange-server-2010-sp1-owa/ The configuration on Exchange is now moved from web.conf to the per server OWA Virtual Directory. I will definitely create a script automating the below process when I get more hands on :)

NOTE: The below steps need to be done on all Exchange 2010 CAS servers in you deployment 

1. Get the active Exchange 2010 certificate using this command in Exchange Management Shell 

   • Get-ExchangeCertificate | Where-Object {$_.Services -match "IIS"} | Get-ExchangeCertificate | fl thumbprint,subject

     • This command gets the active certificate on the local server, because only one certificate can have IIS as service at a time
2. Use the thumbprint and OCS pool FQDN in the command below

   • Get-OwaVirtualDirectory -Server "CasServer" | Set-OwaVirtualDirectory -InstantMessagingCertificateThumbprint 4DC1EE3506E06E971FF82AC8DD60015EAC11B21E -InstantMessagingServerName ocspool01.domain.local -InstantMessagingType OCS -InstantMessagingEnabled $true

     • NOTE: This time we use OCS as InstantMessagingType
3. Run iisreset

Configuring OCS 2007 R2

In order to allow the Exchange 2010 server to communicate with OCS using SIP containing presence and chat you need to add every Exchange 2010 CAS servers as authorized hosts on OCS.

1. On your OCS R2 Pool server configure authorized host
   • NOTE: Your user needs to be member of the RTCUniversalServerAdmins group
2. Open Office Communications Server R2 under Administrative Tool
3. Expand forest and Enterprise pool or Standard Edition Servers depending on you deployment
4. Right click your pool and choose properties->Front End Properties
5. On the Hosts Authorization tab
6. You need to add the Client Access server FQDN and configure as the below image 
   • NOTE: This is the FQDN of your subject name (CN) on the certificate used on the CAS server

• On OCS Front End you need to install the same cumulative update as we installed on the Exchange server if you have not already done it
  1. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4
  2. Download and run ServerUpdateInstaller.exe
  3. NOTE: It is good practice to have all OCS servers on the same hotfix level
  4. Reboot the server

Troubleshooting the Installation (RTM)

Next are a few troubleshooting steps that can assist with some of the more common problems encountered with Exchange/OCS integration. I found these valid troubleshooting steps on Rand Morimoto’s post: http://www.networkworld.com/community/node/47348

Configuring the Firewall on the CAS Server

If the Client Access Server has the Windows Firewall enabled, it might need an exception to enable OCS 2007 R2 to communicate with it. To create the exception, perform the following steps:

1. From the Control Panel, open Windows Firewall 
2. On the left side of the Windows Firewall window, click .“Allow a Program Through Windows Firewall.
3. Click Add Program; then click Browse.
4. Browse to C:\Windows\System32\inetsrv and select w3wp.exe.
5. Click Open and then click OK twice to apply changes and close the window. Be sure to perform this step on all CAS servers with IM integration enabled.

User Configuration

• Before the user community can utilize the IM features, they must be “provisioned” for Office Communications Server R2 and must be enabled for Enhance Presence. When the user is initially enabled on OCS 2007 R2, he will automatically be enabled for Enhanced Presence.
• Users must also have a valid SIP proxy address for the OWA IM integration component to enable the IM Integration UI.
• When attempting to view the Instant Messaging contact list, a user might receive a notification that states
  • Instant Messaging Isn’t Available Right Now. The Contact List Will Appear When the Service Becomes Available.
• If this occurs, perform the following steps:
  1. Using the same user account, confirm that you can access the IM services using the Office Communicator 2007 R2 client.
  2. If functional, confirm that the OCS Server name is properly entered in the Web.Config file of the CAS server.
  3. Also confirm the configuration of the Authorized Hosts option on the OCS pool contains all IM Integrated Client Access Servers.

OWA Certificate Error

If OWA cannot locate the certificate, an error stating The Local Certificate Specified Was Not Found in the Store for the Local Computer appears.

In this case, confirm that the value of the OCSCertificateIssuer and OCSCertificateSerialNumber fields in the Web.Config file are correct. Also ensure that there are blank spaces between every two characters in the serial number to separate octets in the string.

References

TechNet: http://technet.microsoft.com/en-us/library/ee633458%28EXCHG.140%29.aspx
Chris and Robin’s Technology blog: http://chrislehr.com/2009/11/implementing-integrated-ocs-in-owa-2010.htm
Martin Sundström: http://msundis.wordpress.com/2010/06/21/integrate-ocs-2007-r2-with-exchange-server-2010-sp1-owa/
Rand Morimoto: http://www.networkworld.com/community/node/47348

This script may come in handy in the following scenarios:

• Initial configuration, avoid typos
• Expansion in the infrastructure with load balanced CAS
• Change in internal FQDN if you change certificate name
• When you have a total disaster on site 1 and need to fail over to a second site with a passive DAG server that holds all server roles

Please keep in mind:

• The Script is developed for Exchange 2003 coexistence and migration scenarios
• The script must not be run in an Exchange 2007 coexistence and migration scenario
• For InternalURL the script will look for a CASArray (It is recommended to create a CASArray in any scenario)
• The script assumes there is only one ADsite

About the script:

• First you will be presented with som choices on what to do
• InternalURL will autoconfigure based on CASArray
• ExternalURL will prompt for public FQDN and assume one external address
  • Will use same FQDN for OWA, ActiveSync, Autodiscover and so on
• Will prompt for Exchange 2003 URL
• All configuration will output the changes made

Update 27.05.2010:

• Added support for Exchange 2007 and Exchange 2007/2010 coexistence scenarios.
• The script will check for Exchange version before applying any settings.
• When applying Exchange 2010 Internal URL the script will match the CAS servers to the correct CASarray in the correct ADsite

Update 28.05.2010

• Added option for checking current configuration
• Corrected some errors on the Exchange 2007 configuration and listing of URLs
• Tested in Exchange 2007 only deployments and Exchange 2010 and 2007 coexistence deployments

 The Script can be viewed and downloaded here: http://msunified.net/exchange-downloads/script-internalexternalurls-ps1/

Session 1: Exchange 2010 Installation and Migration. Talks about:

• Some new features in Exchange 2010
• How to prepare before an installation
• How to Migrate to Exchange 2010
• How Client Access coexistence works
• Gotchas during the first Exchange 2010 migrations
• Download PDF

Session 2: Exchange 2010 Performance and Scalability. Talks about:

• Memory and Processor requirements
• Virtualization
• Planning for Scalability
• Some new High Availability features
• Walks through some new HA scenarios for Exchange 2010
• Download PDF

General guidelines for installing Update Rollups in Exchange Server 2007/2010:

1. Use elevated Administrator-privileges when running the installation either from Windows Update or by manually downloading the installation file.
2. Verify that all Execution Policies are set to “Undefined”.
3. Uninstall any interim Exchange hotfixes installed since the last Update Rollup.
4. Verify that the ExchangeSetupLogs directory are present on the system-drive. The installer uses this directory for saving service-state information.

PowerShell Script: Bhargav Shukla has created a PowerShell sctipt to check for current Exchange 2007/2010 patchlevel: http://msunified.net/exchange-downloads/script-exchangeupdaterollups-ps1/

Here are some facts:

• You need to activate the thumbnailPhoto attribute in schema to replicate to Global Catalog
• The attribute is limited to 10K in size
• The recommended thumbnail size is 96*96 pixels
• In Exchange PowerShell use the cmdlet Import-RecipientDataProperty
  • Import-RecipientDataProperty -Identity ”Bharat Suneja” -Picture -FileData ([Byte[]]$(Get-Content -Path ”C:\pictures\BharatSuneja.jpg” -Encoding Byte -ReadCount 0))
• After the thumbnails are uploaded you need to update OAB, so that it will point to AD for the images
  • Update-OfflineAddressBook “Default Offline Address Book”
• For true offline use, you could modify the ConfiguredAttributes of an OAB to make thumbnailPhoto a Value attribute
  • This will increase the size of the OAB so it need to be tested before deployed

Anderson Patricio, MVP has created a script to automate this pocess: http://msunified.net/exchange-downloads/script-uploadphoto-ps1/
GAL Photos: Frequently Asked Questions: http://msexchangeteam.com/archive/2010/06/01/455005.aspx
See this article for the full story: http://msexchangeteam.com/archive/2010/03/10/454223.aspx

The below guide is not written by me. I found it so useful that I want to repost it here on my blog for later reference. This guide is written by Elie Bou Issa and the original article can be found here:  http://blog.elieb.info/2010/03/06/exchange-2010-with-ur2-installation-in-unattended-mode.aspx

 

UPDATE: This script has been updated and revamped 07.05.2010 and described in this post: http://msunified.net/2010/05/07/script-for-configuring-exchange-2010-internal-and-external-urls/

In Exchange 2010 you need to set the internal URL for various services on the Client Access Server. Outlook 2007 uses autodiscover internally to connect to the exchange server. If internal URL is configured wrong you could get certificate errors when logging on to Outlook as well as errors when using other services internally.

This script may come in handy in the following scenarios

• Initial configuration
• Expansion in the infrastructure with load balanced CAS
• Change in internal FQDN if you change certificate name
• Change from https to http
• When you have a total disaster on site 1 and need to fail over to a second site with a passive DAG server that holds all server roles

 It is a very simple script, if you have some advice to make the script better I would be happy if you let me know. The script does the following:

• The server path is specified with a prompt
• The script is set up with “-identity *” if you have more than one instance you need to specify wich instance you want to configure
• The url is generated using the variable and the default location of the services
• After configuring the URL’s the scritp lists all changes so its easy to doublecheck the configuration
• The UM role is excluded because it is not supported to be hosted on the same server as CAS

To run the script do the following:

• Copy this into a txt file and rename it to a ps1 file
• Open powershell and navigate to the location where the file is saved
• Use tab in powershell to get the correct run syntax
• Run it and type the correct FQDN like this when prompted: https://yourcasserver.domain.local

#InternalURL.ps1
$urlpath = Read-Host "Type internal Client Access FQDN starting with http:// or https://"
Set-AutodiscoverVirtualDirectory -Identity * –internalurl “$urlpath/autodiscover/autodiscover.xml”
Set-ClientAccessServer –Identity * –AutodiscoverServiceInternalUri “$urlpath/autodiscover/autodiscover.xml”
Set-webservicesvirtualdirectory –Identity * –internalurl “$urlpath/ews/exchange.asmx”
Set-oabvirtualdirectory –Identity * –internalurl “$urlpath/oab”
Set-owavirtualdirectory –Identity * –internalurl “$urlpath/owa”
Set-ecpvirtualdirectory –Identity * –internalurl “$urlpath/ecp”
Set-ActiveSyncVirtualDirectory -Identity * -InternalUrl "$urlpath/Microsoft-Server-ActiveSync"
#get commands to  to doublecheck the config
get-AutodiscoverVirtualDirectory | ft identity,internalurl
get-ClientAccessServer | ft identity,AutodiscoverServiceInternalUri
get-webservicesvirtualdirectory | ft identity,internalurl
get-oabvirtualdirectory | ft identity,internalurl
get-owavirtualdirectory | ft identity,internalurl
get-ecpvirtualdirectory | ft identity,internalurl
get-ActiveSyncVirtualDirectory | ft identity,internalurl