This project has moved. For the latest updates, please go here.

Office Web Apps - bind to URL

Topics: Feature Requests
Apr 10, 2014 at 5:56 PM
Edited Apr 10, 2014 at 5:57 PM
How about adding 1 new XML element and 1 more PowerShell command for OWA binding? That would enable the new SP2013 farm to come online and be connected to OWA all ready to go for users.

New-SPWOPIBinding -ServerName [SERVER_HERE]

somewhere to hold "SERVER_HERE"? maybe
               <OfficeWebApps Install="false"
Apr 10, 2014 at 6:13 PM
Not a bad idea Jeff, have considered it already but I gotta keep in mind the can of worms something like this opens up :) I still keep WAC install/config separate from AutoSPInstaller myself, with a separate set of scripts/commands that I run through after the farm's all built (note the order: SP first, then WAC)

Let me give it some more thought...

Apr 10, 2014 at 6:17 PM
Cool stuff. Thanks Brian!

I thought this probably has come up before with good reasons behind, but just wanted to suggest since I sometimes forget to run that last command. With 2013 and shared WAC farm I guess things are different and in my case WAC is online already for Lync/Exchange before I begin SP.

Either way is all good. Easy command to process manually. I'm just super lazy. =)