SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

SharePoint 2016

How to install OOS and SharePoint 2016 on the same PC

NOTE – IIS configuration is reset by WAC every time you reboot or restart the WAC service.

For this reason, the install bypass below would still experience the issue of SharePoint IIS websites being lost after reboot. Better to run a second VHD. I wanted to try a workaround, but there doesn’t appear to be any.

http://www.wictorwilen.se/office-web-apps-2013-why-you-can%E2%80%99t-and-shouldn%E2%80%99t-install-sharepoint-2013-on-the-same-machine


I wanted to create a new AIO (all-in-one) demo machine for SharePoint 2016.   However, Excel Web Services features have moved out to Office Online Server (OOS) and the guidance is to install OOS on a dedicated IIS machine.   This appears related to the HTTP default bindings and a need for OOS to capture all inbound HTTP traffic.

For demo purposes, I want a single VHD running all services I need:

  • Active Directory Domain Controller
  • SQL Server
  • SharePoint Server
  • Office Online Server
  • Workflow Manager

 

With SysInternals PROCMON, I was able to monitor the launch of SETUP.EXE and see the local Registry keys queried.   37 total keys were referenced to trigger the error

  • The install in progress conflicts with a previously installed Microsoft Office 2016 Server product

 

Renaming these 37 registry keys makes OOS effectively disappear to the detection run by SharePoint Server 2016 SETUP.EXE.   From there, we can install normally.

After install completes, we rename the 37 registry keys back to their original names.  Voila!  We are now running both products on a single machine.  Cheers! 

shades_smile

 

NOTE – OOS has a smaller install footprint than SharePoint Server so the most reliable approach is to install OOS, rename a minimal number of regkeys, and then install SharePoint Server 2016.   The reverse would be precarious given the much larger install footprint of SharePoint and higher number of registry keys.   I thought about both and OOS before SharePoint seems to be the only reliable way.

NOTE – Approach is meant for DEV/DEMO only and is not supported.   It is entirely possible that OOS, SharePoint, or both may behave in unexpected ways given this configuration.   Use at your own risk.

 

 

Download PowerShell

https://github.com/spjeff/spadmin/blob/master/Run-OOS-with-SP2016.ps1

 

 

Screenshots

SharePoint 2016 install error when it detect OOS has been installed

 

image

 

Run PowerShell to rename 37 registry keys for OOS.  Now SETUP.EXE for SharePoint runs normally.

image

.

 

Run PowerShell again with “-disable” to toggle the rename back to OOS original names after SETUP.EXE for SharePoint completes.  All done.

image

How to install Office Online Server for SharePoint 2016 (OOS)

Recently I wanted to create a SharePoint 2016 lab environment.   With Excel Services moving out of the SharePoint 2016 product, we now need to plan for an instance of OOS.   Below are the steps I followed and screenshots of the process. 

Cheers! 

shades_smile

 

Steps

  1. Install Windows Server 2012 R2 (en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso)
    1. NOTE – Windows Server 2016 seems to be missing Ink and Handwriting Support.
  2. Run PowerShell to install IIS
    1. import-module servermanager
    2. add-windowsfeature web-server –includeallsubfeature
  3. Install Windows Identity Foundation
  4. Install Ink and Hand Writing Services
  5. Get latest Windows Updates
  6. Generate Self Signed Certificate
    1. INETMGR > generate > export PFX file
    2. MMC > add Local Machine certificates > import PFX to “Personal” folder
  7. Create new OOS farm
    1. New-OfficeWebAppsFarm –InternalURL http://sp16 –CertificateName OOS
  8. Install Office Online Server (en_office_online_server_may_2016_x64_dvd_8484396.iso)
 

Screenshots

image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image

 

References

I Wanna Patch FAST

Want to patch your SharePoint farms faster?  Try running https://github.com/spjeff/sppatchify

 

The latest version (0.42) includes new PowerShell code for parallel execution of “Upgrade-SPContentDatabase.”  This was implemented with “Get-Job” and PowerShell job management to remote sessions. 

The more user content databases you have, the greater the time savings.  Below are summary statistics from patching a 9 server SharePoint 2013 farm with 200 SQL content databases in just 4 hours.  Each of the 9 servers will spawn 4 PowerShell remoting runspaces for “Upgrade-SPContentDatabase.”  With 36 concurrent worker threads, the queue of 200 content databases now becomes only 6 deep.  

Instead of waiting 200 units of time to process content databases serially, we now only wait 6 units of time for the upgrade database phase.

Larger farms with more user content (and databases) will see significant overall time savings considering how a majority of the traditional patching timeline is processing all content databases.    The binary EXE phase runs with all content databases  removed (Dismount-SPContentDatabase ) so PSCONFIG can complete sooner.    After that is done, content is introduced again (Mount-SPContentDatabase) and upgraded (Upgrade-SPContentDatabase).

 

Amazing speed!!!    Cheers 

 

 

Charts

 

image

 

image

 

image

 

Image result for i wanna go fast

 

 

SPPatchify

Open source hosted on GitHub

 

image

Ready for SharePoint 2016?

As we get closer to the August release of SharePoint 2016 Preview I wanted to create a local virtual machine and try things out.   Below are steps with dozens of screenshots.   Now I’m ready for the big day to install.

Ideally matching the latest generation of all Microsoft products will give a more integrated experience.    Often in the past I’ve seen where features are disabled or less than optimal if another software layer is older.  For example,  SharePoint 2013 Business Intelligence has many features which only work with SQL 2012.   Yes, you can run older SQL 2008R2 but some features will be missing.

Here’s counting down to the SP2013 release … cheers! 

shades_smile

 

References

 

Prepare ISO and VHD

image
image
image
image
image

Windows Server – Technical Preview

image
image
image
image
image
image
image
image
image
image
image

Rename PC

image
image

 

Server Manager – AD and GUI

image
image
image
image
image
image
image
image
image

Promote Domain

image
image
image
image
image
image
image
image

Create Service Accounts

image

 

image

 

image

Install SQL 2016

image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image

 

Ready for SharePoint 2016

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲