SharePoint geek, dev, admin – Chicago IL
SharePoint geek, dev, admin – Chicago IL

Blog

What’s in that patch? November 2016

NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.

 

Ever wondered what fixes are inside of a given CU?   Please see attached PDF with full detail. I wanted a new format for easy reading.   Show management and make the business case for why downtime should be taken to apply CUs.  Also posted at http://sharepointupdates.com/

If you found this helpful, please leave a comment.   

shades_smile_thumb_thumb_thumb_thumb[2]

 

Download

What’s in that patch – Nov 2016.PDF

PowerShell – Create SharePoint Alert remotely (CSOM)

I want to migrate user alerts to Office 365 from SharePoint 2013 on-prem and was surprised to learn there is no client side API for creating Alerts.   Not SOAP, not REST, nothing but the web browser ASPX web form GUI.

So I took Fiddler and inspected the HTTP POST traffic when you click “OK” on the SharePoint “SubNew.aspx” page in the browser.   Lots of great detail!    You can see all the ASPX web form controls and internal values.   Clicking the “OK” button posts that event back to the server side Dot Net for processing with Request Digest, ViewState, and lots of cool stuff.

So …. could we simulate sending that same HTTP traffic?   From somewhere else?    Like PowerShell??    That’d be awesome!

 

Below is the working concept. PowerShell function with a handful of sample calls. Immediate alert, Daily, Weekly scheduled, etc. With various recipients and filters. Enjoy! 

shades_smile

 

Screenshots

image
image
image
image
image
image

 

Code  (CreateSPAlert.ps1)

 

 

References

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

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲