SharePoint 2013 Platform Options – On-premises

What BDMs and architects need to know about an on-premises deployment.

On Premises

  • You own everything.
  • Capacity planning and sizing.
  • Server acquisition and setup.
  • Deployment.
  • Scaling out, patching, and operations.
  • Backing up data.
  • Maintaining a disaster recovery environment.
  • Customizations are not limited.

Best for

  • In-country farms (when data is required to reside within a jurisdiction).
  • Complex BI solutions that must reside close to BI data.
  • Private cloud solutions.
  • Highly customized solutions.
  • Legacy solutions with third- party components that depend on hardware and software that are not supported on Microsoft Azure Infrastructure Services.
  • Privacy restrictions that prevent synchronization of Active Directory accounts with Microsoft Azure Active Directory (a requirement for Office 365).
  • Organizations that desire control of the entire platform and solution.

License requirements

  • Server Operating System
  • SQL Server
  • SharePoint 2013 Server License
  • SharePoint 2013 Client Access License

Architecture tasks

Design the SharePoint environment in an existing on-premises environment:

  • SharePoint farm topology and logical architecture.
  • Server hardware.
  • Virtual environment, if used.
  • Load balancing.
  • Integration with Active Directory and DNS.
  • Design the disaster recovery environment.

IT Pro responsibilities

Deploy and manage the SharePoint on premises environment:

  • Provision servers.
  • Deploy the SharePoint environment.
  • Update SharePoint farm servers.
  • Add or remove farm servers as needed based on farm utilization.
  • Backup the SharePoint environment.
  • Implement the disaster recovery environment and protocol.

Leave a Reply