Discover E2003 Relay IP

Situation

Faced with discovery and documenting “hundreds” of potential IP’s in the relay lists spread across 14 e2003 servers, I went looking for a more programmatic methodology.

Potential Solution

Found this:  http://support.microsoft.com/kb/935635

While the output is a little clunky, it works way better than me writing them down manually, or screen shots. The reference KB would have you do this from an Exchange server. I am using a domain workstation with good results.  With a little excel work, I will be able to combine all this into one PS script to create receive connectors in E2010.

This is probably old info to some of you. YMMV.

OCS 2007 R2 updates

Nice to know that even after the release of Lync, the Microsoft OCS team is still keeping things updated…

New today

Servers

http://www.microsoft.com/download/en/details.aspx?id=19178

communicator

http://www.microsoft.com/download/en/details.aspx?id=21547

and the ever popular GC…

http://www.microsoft.com/download/en/details.aspx?id=12180

UCMA redistributable (for those doing ExUM you may need this)

http://www.microsoft.com/download/en/details.aspx?id=7557

Enjoy!  YMMV.

Who can Federate tool

Situation

You want to demonstrate to a potential client who their users would want to federate with for business processes.

Possible Solution

MVP Matt Landis has written a nifty little utility…. http://gallery.technet.microsoft.com/Who-Can-Federate-Tool-a9e00d23

The WCF Tool (who can federate tool) will scan through your Outlook contacts and give you a "heads up" on which of your business partners have public Microsoft Lync or OCS federation enabled. This is a great tool to run for people who do or don't have Microsoft Lync to show them who they could connect with in their own contact list.

Useful, eh?  This worked nicely for me – found several on my contact list that I had not thought about.

YMMV