Publishing Office Web App Server using Forefront TMG.

This is not a post on how to install Office Web App Server in your environment. For a walkthrough of the installation process, check out this blog post by Terence Luk: http://terenceluk.blogspot.no/2012/11/deploying-office-web-apps-server-for.html

So, Publishing Office Web Apps using Forefront TMG:
If you would like to securely publish Office Web Apps to the internet in a Lync environment, you can use a number of solutions. A widely used method is to do this with Microsoft Forefront TMG server, as this solution often is used in connection with Lync web services.

The procedure is to generate a new web publishing rule pointing towards the Office Web App server internal web URL(recommend using the same URL internally as for public publishing eq. https://OfficeWebApps.domain.com in public and internal DNS). The listener would be the same as for Lync web services, and the Office Web Apps URL should be registered with the public IP address of the Forefront TMG server used by the Lync listener.

You would also have to update the excisting SAN certificate used by Lync or create a New Public SSL certificate containing the SAN for the Office Web Apps server(eq. officewebapps.domain.com) and install this certificate on the Office Web Apps Server and the reverse proxy used for internet publishing(the TMG Server).

To test the publishing of the Office Web App server, go to the published URL from an external client and verify that the page displays the XML-output.

TMG_RuleTest_OfficeWebApp
Error Message when testing Office Web Apps Publishing rule.

If you try testing the Web Publishing Rule from the TMG server, you might experience a “test failed” as shown in this picture.
Even though it seems like the rule won’t work, if you try testing from the internet with the published URL and are able to get the XML-output, you’re good to go.

The test from the TMG server fails because there are no content present in the Virtual web Directory of the Web App server.

Advertisements

Lync 2010 Enterprise upgrade to 2013, SQL requirements.

SQL_error
Topology Builder will display the following message to inform you of this issue: “The SQL server [FQDN of the server] already contains a SQL instance hosting role ‘User Store’.”
I recently discovered a small bump in the road when it comes to upgrading an excisting Lync 2010 Enterprise pool to Lync 2013 Enterprise.

The SQL server instance not only has to be unique to the Lync 2013 Enterprise Pool, but it also has to be on a dedicated SQL server not already in use by the Lync 2010 Pool.

This means, when upgrading from Lync 2010 Enterprise to Lync 2013 Enterprise, take into concideration that you would need a new SQL server as well.
The Microsoft documentation on the subject is not very easy to find(unless you search specifically for SQL migration scenarios), and even in this article http://technet.microsoft.com/en-us/library/gg425764.aspx it’s not clear that the requirement for a new SQL server is only for an Enterprise scenario.

A possible workaround(in a small organization) could be to install Lync 2013 Standard Edition, migrate users and move the CMS, then reinstall Lync 2010 Enterprise server as Lync 2013 Enterprise pointing towards the old SQL server and then move everything back…

Your Call 🙂

Lync 2013 for iOS

This post is in Norwegian and covers Lync 2013 mobility from iOS Devices. Screenshots are universal and gives a nice view of available features. Check out this post from MVP Matt Landis for more mobile stuff http://windowspbx.blogspot.no/2013/02/microsoft-lync-mobile-2013-everything.html

LyncAtea.no

IMG_2955I starten av mars slapp Microsoft de første mobilklientene for Lync 2013. Vi har tidligere skrevet om Windows Phone 8, i denne artikkelen skal vi ta for oss Lync 2013 Mobile for iOS.

View original post 107 more words