-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patching office online server separately #23
Comments
@brianlala, what's your take on this improvement? I think it is reasonable since OOS is a separate product. It's not kind of SharePoint addin, but independent software that can be used without SP, so it should be probably be installable separately. At least your opinion would be appreciated, so if you don't have time to implement, maybe someone from community will contribute. |
Patching OOS is somewhat of a different beast as it involves actually removing the OOS farm, among other things. I don't personally see a huge interest in incorporating this, but as always others are welcome to tackle it and submit a pull request :) |
Oops sorry I mistakenly thought this was for AutoSPUpdater as you referenced patching OOS as opposed to just downloading patches... |
So what do you think about such AutoSPSourceBuilder feature as preparing the slipstreamed media for OWA and OOS? |
Overall I'm fine with it, but is it even necessary? They are releasing OOS ISOs regularly that are already slipstreamed. |
Well the last slipstreamed is 2017 November AFAIK, so if we talk about some serious installations, it probably makes sense. |
True, there have been several updates since then. |
Is it possible to exploit AutoSPSourceBuilder for slipstreaming only OOS server, without SharePoint.
I've got an OOS image mounted to E drive, then I run
&"C:\Windows\Temp\SPUpgradeSharedFolder\AutoSPSource Builder\AutoSPSourceBuilder.ps1" -WACSourceLocation "E:" -Destination \\unionenspshare.file.core.windows.net\common\inst allmedia\OOSSlipStreamedMedia_sv-se_October_2017 -CumulativeUpdate "October 2017" -Languages "sv-se"
Here is what I get:
The text was updated successfully, but these errors were encountered: