This article is in continuation with the first part, which is available here Publish Exchange 2010 OWA Using Forefront TMG 2010 & Configure OWA Redirection – Part 1 Create Rule for OWA Redirect and Simplify URL Go to the TMG Management Console and in the Firewall Policy list, highlight the OWA publishing rule created, and right click and again click on “Copy”. Select the Exchange 2010 OWA rule again and click on “Paste”, it will create a same copy of rule as shown below Before we Apply the rule, we have to do some changes as shown below, Change the Rule name to Exchange2010 OWA Redirect, and select the tab “Action” and set like below, enter the complete URL of the Web App page e.g. https://mail.fabrikam.com/owa Go to the Listener tab, and click on properties of selected listener and select the Connection tab. Tick the “Enable HTTP connections on port:”…

Many of us are now publishing OWA using the Microsoft Forefront Threat Management Gateway, to ensure maximum protection. In these couple of articles I tried to cover how you can do the following, Publish Outlook Web App using TMG 2010 Configure OWA redirection (implementing URL simplification for users) How HTTP to HTTP redirection can be achieved using TMG 2010 rule My Lab consist of, Exchange Server 2010 Server (all 3 roles combined together) - 1 Forefront Threat Management Gateway(TMG) - 1, with single NIC card. When you use TMG with 2 NIC card, the publishing rules will be created on the External Listener Publish Exchange 2010 OWA on TMG 2010 Before you start creating the publishing rule in TMG, there are some authentication changes needs to be completed on the Exchange Server 2010 which will be used as the internal CAS server in TMG configuration. Set-OwaVirtualDirectory -id <CASServer>\* -BasicAuthentication $true…

I have scripted the Prepare-MoveRequest and New-MoveRequest together to ease the process of cross forest mailbox migration. All you need to provide is the PrimarySMTP address of the user you wish to migrate in the input file. The script itself is self-explanatory.  This script will only work if you have the target user as mail enabled. If you have not done, please read my previous post about preparing the target forest mail usersfor the migration. Cross Forest Migration GAL Preparation - Exchange 2007 to 2010  If you are ready to move, then copy the below script and save it as _PrepareAndMove.ps1 ~~~~~~~~ #------------------------------------#Script for Cross Forest Mailbox Move#------------------------------------Write-Host "Enter the Source Domain Migration Admin Credential"Write-Host "Press any key when ready ..."$x = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")$InputFile = "C:\Migration\Input\MailEnable.csv" #User list file "MailEnable.csv" saved under the folder "C:\Migration\Input"$SourceADServer = "dc01.ex2007forest.local" #Source Forest Domain Controller$RemoteCredentials = Get-Credential #Enter the Source Forest Migration Crendentials Import-Csv $InputFile…

Recently I had an issue when opening my Exchange Management Shell or the Exchange Management Console. The error that you receive when opening Shell or Console would be, Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic. The shell will try to find another server available on the Org and connect to the remote server automatically, where as EMC will show the above error and wait for response. If you have single server, the EMS will fail to connect as well. This happened because, I have enabled “Require SSL” settings on PowerShell virtual directory. Uncheck the Require SSL settings and do an IISRESET /noforce to fix this issue. It uses Kerberos authentication, hence the SSL is not required. If the issue is different, please read…