Skip to content
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

Open
shurick81 opened this issue Nov 29, 2017 · 7 comments
Open

Patching office online server separately #23

shurick81 opened this issue Nov 29, 2017 · 7 comments

Comments

@shurick81
Copy link
Contributor

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:

 -- AutoSPSourceBuilder SharePoint Update Slipstreaming Utility --
 - Checking for D:\Setup.exe and D:\PrerequisiteInstaller.exe...
 - Checking for E:\Setup.exe and E:\PrerequisiteInstaller.exe...
 - Checking for F:\Setup.exe and F:\PrerequisiteInstaller.exe...
 - Checking for G:\Setup.exe and G:\PrerequisiteInstaller.exe...
 - Checking for H:\Setup.exe and H:\PrerequisiteInstaller.exe...
 - Checking for I:\Setup.exe and I:\PrerequisiteInstaller.exe...
 - Checking for J:\Setup.exe and J:\PrerequisiteInstaller.exe...
 - Checking for K:\Setup.exe and K:\PrerequisiteInstaller.exe...
 - Checking for L:\Setup.exe and L:\PrerequisiteInstaller.exe...
 - Checking for M:\Setup.exe and M:\PrerequisiteInstaller.exe...
 - Checking for N:\Setup.exe and N:\PrerequisiteInstaller.exe...
 - Checking for O:\Setup.exe and O:\PrerequisiteInstaller.exe...
 - Checking for P:\Setup.exe and P:\PrerequisiteInstaller.exe...
 - Checking for Q:\Setup.exe and Q:\PrerequisiteInstaller.exe...
 - Checking for R:\Setup.exe and R:\PrerequisiteInstaller.exe...
 - Checking for S:\Setup.exe and S:\PrerequisiteInstaller.exe...
 - Checking for T:\Setup.exe and T:\PrerequisiteInstaller.exe...
 - Checking for U:\Setup.exe and U:\PrerequisiteInstaller.exe...
 - Checking for V:\Setup.exe and V:\PrerequisiteInstaller.exe...
 - Checking for W:\Setup.exe and W:\PrerequisiteInstaller.exe...
 - Checking for X:\Setup.exe and X:\PrerequisiteInstaller.exe...
 - Checking for Y:\Setup.exe and Y:\PrerequisiteInstaller.exe...
 - Checking for Z:\Setup.exe and Z:\PrerequisiteInstaller.exe...
WARNING:  - The correct SharePoint source files/media were not found!
WARNING:  - Please insert/mount the correct media, or specify a valid path.
@shurick81
Copy link
Contributor Author

@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.

@brianlala
Copy link
Owner

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 :)

@brianlala
Copy link
Owner

Oops sorry I mistakenly thought this was for AutoSPUpdater as you referenced patching OOS as opposed to just downloading patches...

@shurick81
Copy link
Contributor Author

So what do you think about such AutoSPSourceBuilder feature as preparing the slipstreamed media for OWA and OOS?

@brianlala
Copy link
Owner

Overall I'm fine with it, but is it even necessary? They are releasing OOS ISOs regularly that are already slipstreamed.

@shurick81
Copy link
Contributor Author

Well the last slipstreamed is 2017 November AFAIK, so if we talk about some serious installations, it probably makes sense.

@brianlala
Copy link
Owner

True, there have been several updates since then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants