November 2012 - Posts
 | How can I clean up my File Server Public folder directory on an interval basis using PowerShell?
If your company uses a Public folder and your policy is to clean up every X days you can use PowerShell to do the work for you. Let’s create a folder on the C: root called Operations and save the command line below in a file called PF-clean.ps1. Make sure to change the path for your public folder.
Remove-Item -Path F:\Public\* -Recurse
Now it comes the easy part, just create new Windows Task and make sure to fill out these following fields when they show up: - Program/Script field
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe - Add arguments (optional) field
-NoLogo -NonInteractive -File C:\Operations\PF-clean.ps1 Finally, during the general tab you can configure the service to run when your user is not logged on by configuring the settings shown in the figure below: 
Note: Depending of your environment you may have to run Set-ExecutionPolicy –ExecutionPolicy Unrestricted if your scripts are not signed. |
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Good morning folks!
In Today’s post we will summarize all our posts around Office Web Apps Server that were created in the last few days. Office Web Apps Server will help organizations to centralize all the load related to office web viewers in a single location and it provides fault tolerance, resilience and Load Balance support to all collaborative Microsoft products (UC), such as: Exchange Server 2013, Lync 2013, and SharePoint 2013.
In the following list we will find step-by-step how to deploy, manage certificates, configure the server and finally integrate with Exchange Server 2013.
Remem
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Buenos tardes hermanos (Yeah, we are all sad that Brazil won the game last night playing at the Bombonera!)
In Today’s post we going over the last step of the Office Web Apps Server which is the integration with Exchange Server 2013 (we will work on the integration with other products down the road as well).
Integrating with Exchange Server 2013
It’s a piece of cake and we configure the integration using the same URL that we used yesterday to test the Office Web Apps Server. The following cmdlet can be used (where <server-name> should be the same name assigned to the certificate).
Set-OrganizationalConfig –WACDiscoveryEndPoint /hosting/Discovery">https://<server-name>/hosting/Discovery
Configuring OWA
We need to enable OWA WebReady and we can do that using either PowerShell or EAC. In this post we are going to use EAC and it all depends if you have a single Outlook Web App Policy or a bunch of them. If you have just one just double click on the Default one and change it however if you have several you can go on each one of them and change as you want to.
In order to configure the Outlook Web Policy, open EAC, then click on Permissions and then on the last item on the right side which is Outlook Web App Policies and edit the desired entry. Click on File Access item on the left and you can enable WebReady for either Public or Private computer. We can also force the users to use WebReady before downloading the file by clicking on Force WebReady Document Viewing when a converter is available. Click on Save.
Now on any message that has a Microsoft Office file supported by Office Web Apps Server, click on Preview
Here you go, the file will be displayed in the new Microsoft World Web App, as shown in the figure below.
It’s that simple!
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hola Hermanos! strike is over and the life goes on in the heart of Argentina’s capital)
In Today’s post we are going over the steps to configure the Office Web Apps Server and the configuration has no GUI, everything is done at PowerShell level however the configuration is really simple, just a few cmdlets and you will be all set to configure the integration on your favorite products: Exchange 2013, Lync 2013 and SharePoint 2013.
It is possible to configure HTTP however for the sake of security let’s configure the certificates that we installed yesterday.
Our first step is to create the farm and we can do that using the New-OfficeWebAppsFarm and in this cmdlet we can define the internal (-InternalURL parameter) and/or external (-ExternalURL parameter) URL and another key parameter is the –CertificateName which must match the name that we defined yesterday. Bear in mind that is the Friendly Name of the certificate installed on the server not the common name of the certificate.
In this example we are going to define just the internal name. The result of that cmdlet is shown in the Figure below as well.
New-OfficeWebAppsFarm –InternalURL https://POAWebApp.apatricio.local –CertificateName “POAWebApp – Internal CA”
The cmdlet is nice but we should look at the IIS level to see what is really going on. A 809 binding will be created for intercommunication among nodes, and also 810 using https and our certificate will be created. The figure below show the changes on IIS.
Testing the new server..
The best way to test it is using /hosting/Discovery">https://<name-of-the-server>/hosting/Discovery and the result should be similar to the figure below.
Configuring some Server’s settings..
Now that our server is configured, we can configure additional features. A good one is to enable users to edit documents on Office Web Apps Server (There is a license required for that). If you want to enable we show you how to do it in the image below.
Also, you may want to add new servers to your farm and it can be done easily using the following cmdlet:
New-OfficeWebAppsMachine -MachineToJoin "POASRV02"
How about to enable the users to open from URL and/or UNC? You can use the same Set-officeWebAppsFarm and the following parameters using $true or $false to manage the settings: OpenFromURLEnabled and OpenFromUNCEnabled
In order to get a list of all parameters that you can play with, just run Get-OfficeWebAppsFarm and voilà!
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
 | Sometimes you need to add the legacy .NET Framework on Windows Server 2012 and if you follow the regular steps as shown in the figure below.  You will find the following error where the Windows Server 2012 media will be required. 
In order to install any Features that require the media, you can use either the GUI or the command line. Using the GUI you can click on Specify Alternate Source Path and then use the path (if you are using the DVD on the D: drive, you can use D:\sources\sxs) 
If you prefer PowerShell, not a problem, just add the –Source <path> to your existent cmdlet and you will be able to install such feature. 
|
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Buenos días hermanos (Live from Buenos Aires Today even with the Transit Public strike over here 
)
In Today’s post we are going to continue our journey to configure Office Web Apps Server towards the integration with Lync and Exchange Server 2013. Last post we installed the server and its language packs, you can check it out here:
A few key points about the digital certificates and Office Web Apps, as follows:
- If using an internal CA download the certificate in base-64 format
- If using an internal CA use the advanced option to request the certificate and select web server as certificate template
- If you want to request a certificate with several names (different names for internal and external) you can use Certificates (Computer Store) using MMC (it also applies to Windows Server 2012)
- The SAN name of the certificate cannot be a wildcard (*)
- The certificate must be exportable and the same on all servers from the balance (if you are terminating SSL on each one of the hosts)
- Office Web Apps supports Hardware Load Balance and you can offload SSL from the servers using those devices. If that is your case you need to plan to move the certificate to the hardware load balancer
- The certificate must be valid in an internal CA or Public CA, if you are going to use in a large scale a Public CA may be a good option
All Office Web Apps Server is configured through PowerShell however before going there we will need to have a certificate in place and there are a couple of ways to do that, let’s start with a simple one using IIS for a single name, as follows:
First, open IIS Manager, expand the server name, and on the right side click on Server certificates, then click on Create Certificate Request... located on the right side in the Toolbox Actions.
In the new page (figure below) fill out all the information and set it up the name that will be used by this Office Web Apps Server in the Common name field
In the Cryptographic Service Providers Properties page. Let’s change to 2048 the bit length and then click Next.
![clip_image002[4]](http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/andersonpatricio.metablogapi/1122.clip_5F00_image0024_5F00_thumb_5F00_5C878E96.jpg "clip_image002[4]")
In the File name page. Let’s choose a place for the request file and we are going to use that file with our local CA or Public CA (depending of your design).
![clip_image002[6]](http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/andersonpatricio.metablogapi/0435.clip_5F00_image0026_5F00_thumb_5F00_11D0A0FC.jpg "clip_image002[6]")
Time to move the request to your CA and get the certificate ready for our next step.
Deploying the certificate..
Time to go back to IIS and complete the request by clicking on Complete Certificate Request and in the new page, let’s select the certificate that we got from our Certification Authority, and let’s assign a Friendly name for this certificate (we are going to use the same name during the Office Web Apps Server configuration). Click on OK.
![clip_image002[8]](http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/andersonpatricio.metablogapi/4135.clip_5F00_image0028_5F00_thumb_5F00_47F2194B.jpg "clip_image002[8]")
Now we should be able to see the certificate on the list as shown in the figure below.
![clip_image002[10]](http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/andersonpatricio.metablogapi/2352.clip_5F00_image00210_5F00_thumb_5F00_338C53C0.jpg "clip_image002[10]")
In tomorrow (perhaps Tonight ) post we are going to configure the server and then we will be ready to integrate with Lync and Office 2013 products.
One last thing for our series, is to configure the DNS using the same name that we defined in the certificate for the server and that name will be used in our integration down the road.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hola che hermanos!
In Today’s post we will go over the process to monitor the Microsoft Directory Synchronization Tool using SCOM. This post is a small part of one of my upcoming articles about the transition process from on-premises Exchanges to FOPE that will be published in MSExchange.org.
Before performing the monitoring wizard below, you should have at least:
- Agent installed on the FOPE Server
- A Group created for the FOPE Server (in this case FOPE-Group)
- A Management Pack to store all FOPE monitoring and groups (in this case FOPE Management Pack)
Now that we have all that in place, let’s open the SCOM Console, click on Authoring, expand
Monitoring Type. Let’s click on Windows Service and then hit Next.
General Page. Type in the name and choose the Template that was created before, and hit Next.
Service Details. In the first field click on … and on the new page (figure below) connect on the DST Server and select the service Microsoft Directory Synchronization and then click OK.
Back to Service Details, we need to use the group that we created previously, and let’s uncheck the last option and then click Next.
That’s it! Now in order to perform a simple test we can stop the service in the FOPE server and we will receive an alert on the SCOM.
As part of the Monitoring wizard, there is also a task that the operator can use to start the service, by clickin on Start NT service in the new FOPE – Directory Synchronization Tool Service tasks.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hola hermanos,
Scott Schnoll (@schnoll) has just tweeted about new updates for Exchange Server 2007 and 2010. Here are the updates:
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
 | How can manage agent proxy in a SCOM agent using PowerShell?
PowerShell makes everything easier, right?  To list all agents using names with wildcards we can use the following cmdlet where in this post all my locations share the site code on their names:
Get-SCOMAgent *POA*
If the previous cmdlet brought the servers that you were expecting, then we can go ahead and enable the agent proxy for all those servers using the following cmdlet:
Get-SCOMAgent *POA* | Enable-SCOmAgentProxy
If you want to disable based on the initial cmdlet, just run the following cmdlet: Get-SCOMAgent *POA* | Disable-SCOmAgentProxy |
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hola che Hermanos (live from Argentina this week)
This week we are going to go over the new kid on the block which is the Office Web Apps on Windows Server 2012. Using this server on-premises we can have browser-based view of Office documents, such as Excel, Word, PowerPoint and One Note and it works with Lync 2013, Exchange 2013 and SharePoint 2013.
By default we can read documents and if you have license you can also edit documents using the same component. Isn’t that cool?
First things first, let’s download the software and also the language packs. Here are the links:
Installing the pre-requisites..
The key information here is.. you should not have anything installed on the machine (please do not install office on that server).
Okay, from the Windows Feature/Role side we can run the following cmdlet and it will install all pre-requisites. After that, please restart the server.
Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices
Now that we have the features installed, let’s right-click on the img file that we downloaded and then click on Mount (great feature of Windows Server 2012!)
In the License Agreement page. After reading the document and if you are okay with the terms, please click on I accept… and click Continue
File location page. Let’s leave default settings and click on Install now.
Final page of the deployment, just click on Close and we are golden!
Installing a Language Pack…
It’s easier than the installation process (no kidding!) you just need to execute the software that you download on the desired language and accept the license and voilà (in my case French language) will be ready to go. The final installation is already on the language that you installed.
Note: If you want to install a language pack afterwards you need to remove the Office Web App Server from the farm, install the language pack and then add it back gain.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hi folks,
This week topic was the Import/Export of PST files using Exchange Admin Center (EAC) in Exchange Server 2013. Our series has 4 posts where on the first one we cover the required permissions, then we create a shared folder to support EAC common operations and finally in the last 2 (two) posts we demonstrate how you can Import and Export PST data in Exchange Server 2013.
Here are all posts that we created during within these last few days:
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
 | How to manage basic computer tasks in Windows Server 2012, such as logoff, restart and shutdown from the PowerShell?
I do share the same feeling, I really enjoy the new interface but when you are in a RDP session and you want to be fast, there is nothing better than open PowerShell, cmdlet and hit enter and see ya!, right? So here we have a list of common tasks where we can use Powershell and a couple of commands to get stuff done.
Restarting your computer..
Restart-Computer
Logging off your session.. Logoff
Shutdown your computer… Stop-Computer Before doing all that is always good to check the computer name, so the command below will help you out  hostname |
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hi folks,
So far this week we assign the required permissions to manage the Import/Export process using Exchange Server 2013 and we also created a file share to support the operations, and finally we export data. Now, it’s time to bring it back and import data into a mailbox using Exchange Admin Center.
We are going to use the same ExUtil$ folder that we created (my next post will be a summary with all posts related to this topic) and we are going to have a couple of PST files with some content, as shown in the figure below.
In order to start the process, let’s log on EAC, and then click on recipients item on the left, and then mailboxes tab. In the list of mailboxes, select the one that is going to receive a PST and click on … (more) and then click on Import PST
In the first page of the wizard, let’s specify our sharing work folder and also the file (in our case \\servername\ExUtil$\anderson2.pst) and click Next.
In the second page, we still have a chance to change the mailbox by clicking on browse however let’s keep the mailbox that we selected in the main page and we can choose if we want to import the PST data into the regular mailbox or archive, the default settings is regular mailbox. Click on Next.
The final page of the wizard allows us to choose an user (by default who started the operation) and send a message when the process is finished. Click on Finish.
As part of the process when it completes a notification will be displayed if you are still using Exchange Admin Center.
Also a message will be sent to you informing you that the process is over, how long it took, the mailbox, time which started, which file was used and finally who was the user who started the process.
That’s all, simple as that to import a PST into any mailbox using Exchange Server 2013! 
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hi folks,
Today we are going over the process of assigning permissions to any given user to allow export/import to and from PST using Exchange Server 2013 EAC (Exchange Admin Center). The process is similar to Exchange Server 2010 however since EAC is sort of a different interface the location of the settings is in a different place.
Logged with organization management credentials, let’s click on permissions item on the left, and then admin roles tab. If you are using default settings on the RBAC, you may just change the Recipient Management however if the user that you want to use the Import/Export feature has a different management role, then double click on that one. In our case let’s go straight to Recipient Management.
In the properties of the management role, let’s click on Add (+ icon) under Roles section.
Select Mailbox Import/Export from the list and click Add, as shown in the figure below. Then click OK and Save.
Make sure that you logoff and logon the user affected by the role that we just updated and the user will be golden to perform the import and export process. Bear in mind that yesterday we cover the export process and my next post is going to be about the import one. Here is the link for export process:
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
 | I was asked Today how to create a list of all users from a specific OU with their Display Names and their logon names using PowerShell?
There are several ways to get the results, a simple one when you know the location of the OU (in our example here is apatricio.local/Argentina) is to run the following cmdlet. Make sure that you are logged on a Domain Controller or at least a server with AD tools installed.
Import-Module ActiveDirectory
Get-ADUser -SearchBase "OU=Argentina,dc=apatricio,dc=local" -Filter * -ResultSetSize 5000 | Select Name,SamAccountName That will give you a list of the users, if you want to export that, just add | export-csv C:\Argentina-users.csv to the end of the previous cmdlet and open the file afterwards and the same can be open in Excel as well. |
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hola amigos! (Live from Santiago/Chile)
In Today’s post we are going over the process to export Mailboxes using EAC. We are not going to cover the permissions requirements to perform such task on this post but it will be the content of the following post, so stay tuned!
In order to export a mailbox to PST in EAC is a piece of cake, let’s open EAC, then click on recipient, mailboxes, select the desired user and click Export to a PST file
In the new page, the mailbox selected previously will be already selected, we have a chance to change by clicking on browse. Also, we can decide which mailbox we are going to export to a PST (the mailbox or the archive one). Click on Next.
In the following page we need to specify a folder and the name of the PST file. In Today’s morning post we went over the process to create the shared folder (ExUtil$):
Final page of the wizard, we can configure to send a message when the process is finished. Let’s leave default settings and click Finish.
The alert will pop-up in our EAC saying that the process has started. Now it’s time for a coffee and bring your cell phone (I hope a Windows 8 device 
) with you so you can keep your social skills in the cafeteria and you will still be able to know when the process is done.
Here we go.. the message that you are going to receive when the export process is over. Easy, isn’t it? Exchange has done all the hard work, now you can forward the message to your boss/user saying that it’s all good and keep the conversation in the cafeteria!!
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Buenos días mis amigos (live from Santiago/Chile)
In Today’s post (actually we are going to have two) I would like to go over the simple process to create a shared folder to support EAC. You may find that useful when playing with certificates and PST Import/Export process (that is the topic of Today’s second post).
Before getting to the technical side and creating the share I would like to point out a couple of recommendations, as follows:
- The Shared folder can be created on any server however I would recommend to create it on an Exchange Server for the sake of simplicity and also you guarantee that your Exchange administrator has all its requirements in the same set of servers where he works.
- Bear in mind the size of the disk where you are creating the folder, especially if you are going to work with several PSTs, in that case a separate disk could be helpful.
First step is to create a folder and I’m going to call it ExUtil on the desired drive and then click on properties of this new folder and go to the Sharing tab. Let’s hide this folder by adding $ at the end of its name, so the Share name will be ExUtil$, make sure that you check the option Share this folder.
Let’s click on Permissions and here it’s up to you and your company policy. You can be very restrictive and make sure that you match all permissions that we are going to add on the NTFS (next sentence) or you can go and configure Everyone with Full Control. Since I’m going to secure my lab on the NTFS side I went to the second strategy.
Let’s click on OK, and then let’s click on Security tab.
Let’s click on Advanced button, and then on the new Block inheritance dialog box, let’s click on the first option which is Convert inherited permissions into explicit permissions on this object and then click OK.
Now that the inheritance was broken, we can click on Edit (we continue on the Security tab), and let’s remove Users and let’s add Exchange Trusted Subystem with Full Control permissions assigned to it. You may want to add any other group that is responsible to import/export PSTs in case they are not administrators, but you got the idea, right?
Done deal! Now, you can always use \\servername\ExUtil$ to manage your certificates, PSTs and so forth.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hi Friday Lovers!!! It’s finally here, eh?
In Today’s post we are going to disable EAC and that can be done easily through Exchange Management Shell and the Set-ECPVirtualDirectory cmdlet.
Why you should do that? Well, depends of your security requirements. You may have a policy that does not allow any management outside of your network or something like that.
Anyways, here is the two cmdlets, in the first one I find the current value and afterwards I change it. Also a IISReset is a good thing to force the refresh.
How about the results? If any admin that used to have the full admin console tries to log on using ECP he will have the same logon page, no surprises here.
However after logging then he will have a surprise where he will be able to manage just his personal mailbox settings not the organization.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio
Hi folks,
Mail flow was completely redesigned in Exchange Server 2013 and by default all outbound connections through Send Connectors go through our Mailbox Servers (being specific through the Transport Service on the Mailbox Service). I understand the change but it’s always good to check and run a couple of scenarios and that helps to understand better the feature, so in this post we are going through the steps to describe how the feature Proxy through client access server in a Send Connector really works in Exchange Server 2013.
In order to understand better this feature I would like to show you my environment, as follows:
- POAEX01 (CAS) and IP 10.60.99.52
- POAEX02 (CAS) and IP 10.60.99.53
- POAEX10 (Mailbox) and IP 10.60.99.56
- POAEX11 (Mailbox) and IP is 10.60.99.57
- My domain in my lab is AndersonPatricio.ca
- Our Internet Send Connector (POA-Internet) using default settings
- The reference XX.XX.XX.XX is my Public IP that is the reason that I added that information.
Awesome now that we are on the same page I’m going to send a message from my regular user to my Office365 mailbox which is anderson@andersonpatricio.org and here you go with the results:
Received: from POAEX10.apatricio.local (XX.XX.XX.XX) by CO1EHSMHS031.bigfish.com (10.243.66.41) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 2 Nov 2012 00:33:57 +0000
Received: from POAEX10.apatricio.local (10.60.99.56) by POAEX10.apatricio.local (10.60.99.56) with Microsoft SMTP Server (TLS) id 15.0.516.32; Thu, 1 Nov 2012 20:44:24 -0400
Received: from POAEX10.apatricio.local ([fe80::d9e1:7e76:27ee:1189]) by POAEX10.apatricio.local ([fe80::b13b:f91d:f64e:2813%29]) with mapi id 15.00.0516.029; Thu, 1 Nov 2012 20:44:24 -0400
From: Anderson Patricio <Anderson@AndersonPatricio.ca>
To: "anderson@andersonpatricio.org" <anderson@andersonpatricio.org>
Subject: Test #02: FrontendProxyEnabled $false (default)
Okay, test completed and by default who connects on the external host is the Mailbox Server. Now, let’s change the configuration by logging on EAC, mail flow and then send connectors. Double click on the Send connector to the internet.
Another way to change it is using PowerShell, as follows:
Time to send another message and check the results on the Internet Headers of the message and the results now are clear the server that connected was the CAS instead of the Mailbox.
Received: from POAEX01.apatricio.local (XX.XX.XX.XX) by CH1EHSMHS028.bigfish.com (10.43.70.28) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 2 Nov 2012 00:23:58 +0000
Received: from POAEX10.apatricio.local (10.60.99.56) by POAEX10.apatricio.local (10.60.99.56) with Microsoft SMTP Server (TLS) id 15.0.516.32; Thu, 1 Nov 2012 20:33:35 -0400
Received: from POAEX10.apatricio.local ([fe80::d9e1:7e76:27ee:1189]) by POAEX10.apatricio.local ([fe80::b13b:f91d:f64e:2813%29]) with mapi id 15.00.0516.029; Thu, 1 Nov 2012 20:33:35 -0400
From: Anderson Patricio <Anderson@AndersonPatricio.ca>
To: "anderson@andersonpatricio.org" <anderson@andersonpatricio.org>
Subject: Test #01: Using FrontEndProxyEnabled $true
Since it’s a new product and it’s time for testing, I resolved to play around, so I kept the FrontEndProxyEnabled $true and I went to the CAS servers and I removed the default gateway of those boxes, to see what would happen and as expected the message didn’t go through and if I look at the Queue Viewer and as expected the message didn’t go through and I we have an error being displayed on the Last Error column.
The error message was the one below and it seems harder at the first glance to find out the issue but in the messages you can identify the communications between Mailbox and CAS where the last error is coming from the CAS server.
451 4.4.0 Primary outbound frontend IP address responded with “450 4.7.0 Proxy session setup failed on Frontend with ‘451 4.4.0 Error encountered while communications with primary target IP address: “4.2.1 Unable to Connect.” Attempted failover to alter
Tomorrow I hope to get done the post about how to create a simple connector in Exchange Server 2013.
Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio