Steve Goodman's Exchange Blog
4Sep/114

New Release – Exchange 2010 Virtual Load Balancer

An extra added cost to Exchange 2010 deployments is often a hardware load balancer, or even virtual load balancer appliances. These start at over £1000 for some of the cheaper ones and can cost tens of thousands, however there’s open source software out there that can do the same thing, just as well.

I’ve wrapped up some of this software together and built a web-based management interface, the end result being a free, easy to setup and use Virtual Load Balancer appliance that runs in both VMware vSphere and Hyper-V environments.

This is version 0.1 – the very first version, so I don’t recommend it in your production environment just yet; the base Load Balancer, HAProxy, should be rock-solid but overall it just needs a few more features, feedback and bug reports on the management interface.

Read more and download from the Exchange 2010 HAProxy Virtual Load Balancer page…

17Aug/110

Reader’s Problems: Can’t send a Calendar sharing message

Sometimes an error message doesn’t get you very far, especially when you think you’ve covered the basics. This is one of those cases where a reader was part way through implementing Federated Free/Busy and Calendar Sharing between Exchange On-Premises and Live@EDU using the instructions in my guide, and when trying to share a calendar from an on-premises mailbox to a Live@EDU mailbox:

Hi Steve

Sorry - I'm stuck with this. Do you mind me bothering you some more?

I've set it all up, and sent my colleague (who has a 2010 mailbox) a calendar sharing offer and request from my admin@live.contoso.edu mailbox.

I've set his external email address on Live to in1150@exch.contoso.edu.

The invitation is delivered fine. If he opens the calendar of admin@live.contoso.edu from the message, he can see it, and it gets updated dynamically. However, when he tries to share his calendar with admin@live.contoso.edu (using the request in the message), he gets an error message:

image

This is very odd, because sharing is definitely set up with our domain…

That error again, for the benefit of anyone else experiencing this – “Your organization is not set up for secure sharing with this recipient”.

The first thing we did was check the basics for sharing were setup correctly which they were, but on further inspection and investigation into the Exchange On-Premises environment, the solution was pretty simple. For sharing to work you need to set the ExternalURL for the Exchange Web Services (EWS) virtual directory.

To set the ExternalURL attribute on the EWS Virtual Directory, use the following command against each of the Client Access Servers providing the facility to Internet clients, replacing servername and mail.contoso.edu with appropriate values for your organization:


GeSHi Error: GeSHi could not find the language powershell (using path /home/content/03/9366303/html/wp-content/plugins/codecolorer/lib/geshi/) (code 2)

Steve

17Aug/1135

Exchange Environment Report v1.5.4

It’s been a few weeks since my last update to the Environment report, but since last time I’ve been incrementally fixing a few bugs reported and added a couple of new requested features.

New Features

  • Initial support for /hosting mode installations
  • Support for multiple email recipients with the MailTo parameter, e.g -MailTo "person1@org.com",person2@org.com
  • Support for filtering by server name using a new parameter –ServerFilter. Use this to limit the report to servers with certain characters in the name, e.g. –ServerFilter “NL-*”
  • Support to change whether or not the entire forest is examined with the –ViewEntireForest flag.
  • When sending the report by mail, the report is also shown as the message content, for easy viewing on mobiles.

Bug Fixes

  • Large deleted item total sizes caused an error due to not setting the variable type to long.
  • In Exchange 2003 environments, Back End and Front End roles are not highlighted in the overview section.
  • In some circumstances the formatting of the report is not spaced correctly in the overview section.
  • Shortened the command used as input to schtasks.exe due to it’s maximum character limitations.
  • Non-DAG databases header showed even if no non-DAG databases were present.
  • Archive Mailbox information was no longer showing.

In the next release I’m hoping to add a few more features that have been requested, including integrating some new features written and sent in by readers. In the meantime, as always if you have any problems give me a shout at steve@goodman.net or in the comments.

Download the new version from the original article here…

24Jul/1120

Exchange Environment Report 1.5.3 released

I’ve had a couple of bugs reported in version 1.5 that needed some quick attention, so I’m pleased to release version 1.5.3.

Fixes in this version

  • Per-Server Mailbox count could show incorrectly in certain cases. This appears to be due to a known bug in Get-Mailbox where the ServerName is not always valid. A workaround has been implemented in the script.
  • Exchange 2003 and earlier server information would not show more than one server. Due to a last minute change in the way the script stores information about pre-Exchange 2007 servers this bug got through testing. A fix has been implemented.

No new features this time around, but if you missed the 1.5 release post, check it out here. As always comments and suggestions are welcome either in the comments or via email.

Download the new version from the original article here…