SharePoint Server 2019 Preview

SharePoint Server 2019 Preview

Microsoft has just released the public preview of SharePoint server 2019, with the final RTM version expected before the end of 2018.

I thought I would spin up a quick single server farm in Azure to take a quick look-see, few thoughts below with some reference blog posts also linked.

Features to Note

  • Modern SharePoint – Communications Sites, Team News and Sites
  • OneDrive Modern Sync, On-demand file and push notifications for SharePoint
  • Large File Support, Character Restrictions, and File/Folder Names
  • Hybrid Configuration enhancements
  • PowerApps and Flow have deeper hooks through a gateway
  • Smaller backend footprint and resource efficiencies
  • Upgrade from 2016 using Content Database Attach (not direct SP2013 upgrade)
  • My Quick Thoughts

    • Great to see on-going investments in SharePoint Server, on-premises deployments will still seeing the growth I predict
    • The modern interface will need some adjusting to for an on-premises business to are used to the same interface and customisation options of the previous few versions
    • It certainly feels weird with SharePoint Designer 2013 still being the official tool for management of the 2019 version
    • Deprecation of feature generally falling in line with what has occurred in Office 365

    Blogs to Check out

    SharePoint 2016 Farm Build in Azure with PowerShell

    • SSL deployment for Central Administration, Web Application and Services
    • Scripted Deployment with a supporting configuration file
    • Examples of Remote Script Running

    I’ve taken inspiration and examples of this package from many of the awesome talents who share their expertise in the industry, to name a few

    • SharePoint 2016 Book
    • Microsoft Documents – SharePoint 2016 / PowerShell

    Desired State Configuration (PowerShell DSC) is a step to far for some organisations, with the maintenance of additional servers and the monitoring, so I wanted the benefits of a standard and known deployment from a central configuration file, demonstrating remote script running in places.

    This was a great learning experience in many PowerShell functions, and Windows Server and SharePoint Server 2016 deployments, i hope you get some value out of these scripts and potentially expand upon and share your knowledge back with the industry. Please share a link in the comments if you do.

    Hass.io – Starting with a Locally Controlled Smart Home

    After my first step into a smart home concept with home monitoring and automation with a custom web page in azure which integrated with various online services I though it was time to play with a setup that would be useful long term with simpler integrations. Hass.io and dockerised and componentised version of Home Assistant looked the good, and with a great community for support and ideas.

    I like the idea of a cloud hosted solution which my initial setup used, though it does bring challenges integrating with local network devices. Hass.io running locally and exposed externally works, though isn’t my preferred option.

    I’m slowly building up the device I have to integrate, components and services utilised, and the automation I have configured to in the end have a reliable and easy to understand smart home.

    Starting Setup
    – Hass.io (Docker version) running on a Raspberry Pi 3+
    – Broadlink RM Pro for RF and IR control and integrations (Roller Shutters, Ceiling Fans)
    – Xiaomi Gateway Hub, Temperature Sensor, Window Door Sensor, Switches, Yeelights Blubs

    Starting Automation
    – Ceiling Fans will turn on automatically when temperature in the room reaches certain levels
    – Roller shutters will auto close and open in the mornings and evenings (also controlled via voice)
    – Lights will dim in the evening

    Early learnings from getting started with Hass.io
    – Yaml is a stickler for standards (watch for spaces, capitalisation, naming, placement)
    – I found using packages simplified the understanding and reading of how a device or service is used
    – Backup and push configuration (not including secrets.yaml) to GitHub to share with others
    – Makes small changes, check config, reboot and test
    – Debugging is a process of elimination, delete until is works to narrow down where error is
    – I found most help from the Home Assistant form, Youtube for bigger concepts

    Future expansions on the list
    – Node-Red for automation flow
    – HADashboard(or similar) for a wall panel interface (this is the big end goal)
    – Google Home/Assistant integration

    View my Hass.io Configuration in my GitHub

    Check out my Home Automation link farm for a ton of useful sites