Last updated 17.01.2012

Connecting

In addition to log on the Lync Server and open Lync Server Management Shell you can also access and work with Lync through remote PowerShell which came available in V2. Here is what you need to connect. The url could be your external webservices url as well

$session = New-PSSession -ConnectionUri https://lync-admin.contoso.local/OcsPowershell -Credential (Get-Credential)
Import-PSSession -Session $session

Finding cmdlets

There are several ways to find cmdlets in Lync. If you like the graphical representation like a mind map there is some good ones created by MVP Tom Arbuthnot

• Lync 2010 PowerShell Commandlets by Verb
• Lync 2010 PowerShell Commandlets by Category

In PowerShell there is some cmdlets available as well when finding what is available

#Get all cmdlets for Lync that contains -Cs
Get-Command *-Cs* -CommandType cmdlet -Module Lync
#Get all cmdlets that contains user
Get-Command *user* -CommandType cmdlet -Module Lync

#When you find the cmdlet you want to use find the syntax on how to use it
Get-Help Get-CsUser -Examples
#Use -Online to open the TechNet website for that cmdlet
Get-Help Get-CsUser -Online

#Looking for a specific setting to set and don't know which cmdlet that can modify it use the below code
$params = Get-Command -CommandType Cmdlet *-Cs* | % { $n = $_.Name ; $_.Parameters.Values | % { Add-Member -in $_ noteproperty CmdletName $n; $_ } }
$params | where { $_.Name -like "*meeting*" } | select Name,CmdletName
#This is cool, found the trick over at http://blogs.technet.com/b/csps/archive/2010/06/14/howtofindsetting.aspx

Cmdlets

There are some cmdlets I use more than others and find useful. Let me know what is your most used cmdlets.

#List a lot of the topology information, here you can sort to find URLs, ports and servernames configured
Get-CsService

#List all pools in your topology, useful for finding Front End pool name, when you forget it
Get-CsPool

#The only policy that is not available in Lync Control Panel, lot of nice features can be configured here
Get-CsClientPolicy

#Update the AddressBook files
Update-CsAddressBook

#List the CMS replication status for each Lync Server
Get-CsManagementStoreReplicationStatus

Oneliners

The most used oneliners that I use

#Find what Lync Services are running
Get-CsWindowsService -ExcludeActivityLevel | ft Name, Status
#Start any stopped services
Get-CsWindowsService -ExcludeActivityLevel | where {$_.Status -like "Stopped"} | Start-CsWindowsService

#Find all users that are enabled for Lync and have a LineUri, sort them by LineUri, display displayname and LineUri
Get-CsUser -Filter {LineURI -ne $Null} | sort -Property LineURI | ft DisplayName,LineURI

#Quickly find and open the share folder for the Lync pool
Invoke-Item(Get-CsService -FileStore | Select-Object -ExpandProperty UncPath)

Scripts

There are a lot of scripts that is created and expand on Lync Server PowerShell functionality and and some that simplifies working with Lync as well as monitors the solution. Below are some of my favourite scripts. Please let me know of other epic scripts out there.

Set-Lync2010Features.ps1

A script to install prerequisites on Server 2008 R2 before you start install Lync Server on the OS.  You can download the resource kit tools, Silverlitght and other tools easily. You even have som post deployment options in the script as well. This script is highly recommended and I use it in every deployment.

List-UnusedNumbers.ps1

A scripts that read unassigned numbers and depends on you having put you entire number serie there. It will find all numbers assigned to users, devices and features in Lync and find what numbers are available in any given unassigned numbers series. This is a script that saves you the pain of managing available numbers in an excel sheet.

Set-GlobalVoiceRouting.ps1

This script is for demo or initial deployments only. It is created for norwegian rules and genereates an easy way to dial out through one gateway and has the usual normalization rules for Norway. To edit the script and find the nomralization rules for your country see the Dialing Rule Optimizer.

Reset-UserPolicies.ps1

This script is used in an OCS to Lync migration scenario. It will reset all policies to $Null so that they use Global or Pool level policies for External access, Voice Policy and so on. The reason for this is that all users should use what you define for Lync and not what you inherit from OCS.

Get-CsConnections.ps1

This script lists user connections, client versions and the distribution of users in a load balanced scenario

Monitoring OCS and Lync Peak Call Capacity

Script to monitor how many concurrent calls a particular OCS or Lync Mediation Server is handling. The script grabs the counters for inboud and outbound calls, parses their values, adds them together, and dumps the output into a CSV file. A good tool to find how many concurrent calls you have on your deployment

Update-AdPhoto.ps1

A script that enables you to import AD photos from file and store it in the thumbnailPhoto attribute. It is a central feature in Lync to show a photo of users

New-SipContact.ps1

A script to enable users to search for external contacts and Video Conferencing endpoints from Lync. It creates a contact in AD and adds the SIP address to the msRTCSIP-PrimaryUserAddress so it will be synced to the addressbook in Lync.

Scripting Tips

There is a lot of techniques used for scripting. The best script tips I know of I will list here.

Use Write-Debug

Lets you easilly define debug lines that can test variables and logic in you script that is good to use when developing the script but that not need to be there when it is used in production. When you want to debug the script you change the $DebugPreference from ‘SilentlyContinue’ to ‘Continue’. Then all Write-Debug lines will be displayed.

$DebugPreference = 'Continue'

$var = Read-Host "Enter a computer name"
Write-Debug “’$var’ contains $var“

$DebugPreference = 'SilentlyContinue'

Use Functions

Functions are scripts in scripts. If it is certain things you need to do more than once in you script, make it a function with an input and output. I have also seen functions being used to organize your script in a better way to make it easier and more ordered to view.

Function Do-Something ($computername,$domainname) {
	# function code goes here
}

Resources

The Official Lync PowerShell Blog: http://blogs.technet.com/b/csps/p/categories.aspx
The Official Lync PowerShell Blog Cmdlet Descriptions: http://blogs.technet.com/b/csps/archive/2010/07/16/refallcmdlets.aspx
MVP Pat Richard’s Blog: http://www.ehloworld.com/category/powershell

The reason for creating this script is when migrating customers in Norway most of them want to allow everyone to use side by side calendaring in Outlook and Oulook Web App. In Exchange 2003/2007 we needed to instruct users how to set Default to Reviewer. This script sets it for all users. The script works for both Exchange Online and Exchange Server 2010. For Exchange 2007 check out this post on how to do it: http://exchangeshare.wordpress.com/2008/05/27/faq-give-calendar-read-permission-on-all-mailboxes-pfdavadmin/

Get the script here: http://msunified.net/exchange-downloads/script-set-calendarpermissions-ps1/

What the script does

As the picture shows you get three menu items.

1. Will set the permission on all users and resources
2. Will set the permission on all users and reources created the last 30 days
3. Will give a user you specify Editor access to a mailbox you specify
• This is good for switchboard or secretary functions

How to run the script against an Exchange Online environment

• Connect to Exchange Online through PowerShell Remoting

$cred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection
Import-PSSession $Session

• Set Execution Policy to unrestricted

Set-ExecutionPolicy Unrestricted

• Run the script by copying the script, saving it as a ps1 file, navigate to it in PowerShell and start typing set-Cal and hit TAB to use TAB completion

.\Set-CalendarPremissions.ps1

Resources

Administering Microsoft Office 365 using Windows PowerShell: http://blog.powershell.no/2011/05/09/administering-microsoft-office-365-using-windows-powershell/

With this in mind I have created a script to easily implement appropriate Nomralization Rules, Pstn Usage, Route with Gateway and Voice Policy without any typos. Since all this is intended for global use and the scope is global, all users get access to the Dial Plan and Route. All calls and numbers are routed through a single Gateway.

The script is run at your own risk, tips and feedback is most appreciated

View and download the script here: http://msunified.net/lyncdownloads/script-set-globalvoicerouting-ps1/

Intended Scenario

• One CentralSite
• One PstnGateway
• All Enterprise Voice users will be able to call
• All previous configuration will be removed

To have a clean as possible configuration some existing default configuration is removed

• The “Prefix All” Normalization Rule on the Global Dial Plan
• The Local Route under Routes is removed
• All the default PstnUsage records are removed
• Running the script several times does no harm, all error messages are suppressed

The Script creates the following

• Four Norwegian Nomralization Rules under the Global Dial Plan
  • No need to Grant users with usage
  • Just change and adapt them to your own country/environment before running the script
• Creates PstnUsage named Global
• Edits the Global Voice Policy and adds PstnUsage Global
• Finds the PstnGateway configured in the Topology Builder
  • Only one is added
• Creates a new Route named GlobalRoute and adds Global as PstnUsage and the PstnGateway found earlier
• Creates a VoiceTestConfiguration for one of the normalization rules
• Runs the Test
• Displays the result

Screenshot

Since this is a feature I really want, I have tried to create a PowerShell Script to find out how many numbers are available in any given number range and what they are. First of all I want to declare that I am a PowerShell novice so my syntax may not be that optimized. The script works, though there’s a lot of variables and loops that I am sure could be done better. The script does the following:

• It goes through each entry in Unassigned Phone Numbers that needs to be populated with all numbers series available to the Lync Server
  • See TechNet on how to do it: http://technet.microsoft.com/en-us/library/gg412748.aspx
  • Also see TechNet on how to configure an Announcement required by Unassagnied Numbers: http://technet.microsoft.com/en-us/library/gg412783.aspx
• Then it gets all teluri’s for all the users, dial-in conferencing and Exchange UM contacts
  • I didn’t find the response group command to get the teluri while I was at it, will add this in an update
• Then the string gets “washed” for “tel:+47″ where 47 is the hardcoded region code for Norway
  • The string also get “washed” for any extension numbers
• After that a new string gets created to get rid of property types and so on
• I use Compare-Object to compare the Unassigned Number array with the used numbers
  • Run a check to find what numbers where not used and count them
• Then I find out what the total number of unused numbers are and write the output

I hope this script will come useful to anyone who needs this feature and that others can use this to and adapt it to their needs. Please share any improvements that could be made to the script. Enjoy!

http://msunified.net/lyncdownloads/script-list-unusednumbers-ps1/

NOTE: This article will be updated when more information and requirements become available and necessary. Last update 02.12.2010

Part One – Prerequisites required on all server roles

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature NET-Framework-Core,Telnet-Client
  • This installs the following features
    • [NET-Framework-Core] – .Net Framework 3.5 SP1
    • [Telnet-Client] – Telnet Client (recommended not required)
  • For .Net Framework 3.5 SP1 download the following updates
    • http://go.microsoft.com/fwlink/?linkid=197396, which addresses a set of known application compatibility issues
    • http://go.microsoft.com/fwlink/?linkid=197397, which addresses a file association issue for XPS document
• Install the prerequisites for the specific role as described in Part Three
  • A PowerShell script for installing the prerequisites: SCRIPT: Set-Lync2010Windows2008R2Features.ps1
• Run Windows Update untill everything is updated
• Install the Lync Server 2010 binaries for the role you are installing
• Do post installation tasks as described in Part Two

Part Two – What to install AFTER Lync Server 2010 is installed

I describe it here so it is more accessible rather than in the end of the post

• Download and install the Lync Server 2010 Resource Kit Tools
• Download and install the latest updates for Lync Server 2010 (Link can be found here: http://msunified.net/lyncdownloads/)

Part Three – Commands to install prerequisites for Lync Server 2010 on Windows Server 2008 R2

Front End, Director and Group Chat Server Roles on Windows Server 2008 R2

NOTE: To be able to run schema, forest and domain prep from the Front End Server you need to have the Remote Server Administrative Tools [RSAT-ADDS] installed. It is only required on the first Front End server in you organization. For more information on preparing AD see: http://technet.microsoft.com/en-us/library/gg398607.aspx

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature RSAT-ADDS,Web-Static-Content,Web-Default-Doc,Web-Http-Errors,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Http-Tracing,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Client-Auth,Desktop-Experience

Installs the following components:

• [RSAT-ADDS] – Remote Server Administrative Tools
• [Web-Static-Content] – Static Content
• [Web-Default-Doc] – Default Document
• [Web-Http-Errors] – HTTP Errors
• [Web-Asp-Net] – ASP.NET
• [Web-Net-Ext] – .NET Extensibility
• [Web-ISAPI-Ext] – Internet Server API (ISAPI) Extensions
• [Web-ISAPI-Filter] – ISAPI Filters
• [Web-Http-Logging] – HTTP Logging
• [Web-Log-Libraries] – Logging Tools
• [Web-Http-Tracing] – Tracing
• [Web-Windows-Auth] – Windows Authentication
• [Web-Filtering] – Request Filtering
• [Web-Stat-Compression] – Static Content Compression
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Scripting-Tools] – IIS Management Scripts and Tools
• [Web-Client-Auth] – Client Certificate Mapping Authentication
• Anonymous Authentication (This is installed by default when IIS is installed)
• [Desktop-Experience] – Desktop Experience

NOTE: Installing on Server 2008 R2 SP1, you need to do this step manually. All Front End Servers and Standard Edition servers where conferencing will be deployed must have the Windows Media Format Runtime installed. The Windows Media Format Runtime is required to run the Windows Media Audio (.wma) files that the Call Park, Announcement, and Response Group applications play for announcements and music. Thats why Desktop Experience is installed. If you only want to install the correct runtime run the command below:

• Run using Command Prompt as administrator
• Requires reboot
• %systemroot%\system32\dism.exe /online /add-package
  /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
  /ignorecheck
  

Mediation Server Role on Windows Server 2008 R2

• No additional features required for mediation

EDGE Server Role on Windows Server 2008 R2

• Need one aditional hotfix for Lync EDGE Server Role.
  • Note: This hotfix is included in SP1 for Server 2008 R2
  • Windows Server 2008 R2 update available from Microsoft Knowledge Base article 2028827, “The applications that use the TDI driver for network traffic may stop responding in Windows Server 2008 R2 or in Windows 7,” at http://go.microsoft.com/fwlink/?LinkId=205459

Monitoring and Archiving Server Roles on Windows Server 2008 R2

NOTE: If Monitoring og Archiving is deployed in the topology, all server roles must install the below features, including the Monitoring and Archiving Servers

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature msmq-server,msmq-directory

Installs the following components:

• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration

Software Automatically Installed by Lync Server Setup

References:
For more information see TechNet documentation: http://technet.microsoft.com/en-us/library/gg398686.aspx

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/

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

In the article the author talks about editing the PowerShell Profile. I cant do this for every customer site I am at, so I have edited the syntax to fit my needs. If this is run after you launch PowerShell the file is saved at the root of your C drive.

CD \
$date = get-date -UFormat %y%m%d
Start-Transcript c:\$date.txt -append -noclobber

This will set the working directory to the root of the C drive (gives you more real estate to work with), defines a variable called $date, and specifies that it will get the date in the format of YearMonthDay (i.e. 090706), then tells Powershell to start the transcript, and it uses the variable we defined earlier to automatically create a new text file based on the current date.  Additionally, since the default behavior of start-transcript is to overwrite the previous file, we are telling it to append to an existing file (if present), and the -noclobber tells it to not overwrite the previous file.

Powershell does have some other options here.  The Start-Transcript command includes a -Path parameter that you can define, but it is not used here.

• Create a new internal receive connector in EMC
• Add the servers that need to relay
• When created edit the settings and navigate to Permission Groups
• Select only Anonymous users, deselect other options
• Navigate to the Authentication tab
• Deselect every checkbox so that nothing is selected
• Apply changes
• Open EMS and run the following commandlet
• Get-ReceiveConnector “InternalRelay” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient”
• Relay should now work for the selected servers

This information was based on this blog, http://msexchangeteam.com/archive/2006/12/28/432013.aspx