Skip to content

Instantly share code, notes, and snippets.

@testanull
Last active April 3, 2025 09:23
Show Gist options
  • Save testanull/e1573437f91ec3726ab5041389c6f28d to your computer and use it in GitHub Desktop.
Save testanull/e1573437f91ec3726ab5041389c6f28d to your computer and use it in GitHub Desktop.
Microsoft SharePoint setup guide

Follow by MS guide:

Server setup check list

  • Server OS: Windows Server 2022 Datacenter Evaluation
  • Update windows
  • Rename computer
  • Config DNS before join Domain
    • Domain DNS server, example: 192.168.133.134
    • Public DNS server, example: 8.8.8.8

Domain Controller setup

SQL Server setup

SQL Server version: SQL Server 2019 Express (https://www.microsoft.com/en-us/download/details.aspx?id=101064)

  • Join domain
  • Use local administrator account to setup SQL Server
  • SQL Server Setup
    • Firewall open port 1433
      • netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT
    • In Feature Selection: uncheck "Machine Learning Services ..."
    • In Server Configuration > Service Accounts: with "SQL Server Database Engine" section, use a domain user instead of local account
  • SQL Server Management Studio (https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?redirectedfrom=MSDN&view=sql-server-ver16)
    • In Security > Logins: Add new entry with login name is the farm admin account with Server Roles: securityadmin and dbcreator
    • Right click on current SQL Server instance > Properties > Advanced, change Max Degree of Parallelism to 1
  • SQL Server 2019 Configuration Manager:
    • SQL Server Network Configuration > Protocols for <instance> > TCP/IP: change Enabled to Yes. Switch to tab IP Addresses, in IPAll > TCP Dynamic Ports: remove 0 value, change TCP Port to 1433.
    • Restart service

Microsoft Sharepoint setup

SharePoint version: 2019 (https://www.microsoft.com/en-us/download/details.aspx?id=57462)

  • Join domain
  • Login as farm admin to begin setup
  • Run "Computer Management" as local admin, add farm admin to local administrators group
  • Run PrerequisiteInstaller.exe
  • Run setup.exe The exploit works for both Standard and Enterprise editions of SharePoint, but we prefer the Enterprise edition for the demonstration. Please setup the target SharePoint server with Single-Server Farm role.
    • Key:
      • Enterprise trial product key: M692G-8N2JP-GG8B2-2W2P7-YY7J6
      • Standard trial product key: F2DPD-HPNPV-WHKMK-G7C38-2G22J
    • After setting up, reboot server
  • Run SharePoint Products Configuration Wizard
    • Create a new server farm
    • In Specify Configuration Database Settings:
      • Database server: the sqlserver address
      • Username: use the farm service account
    • In Specify Server Role: use Single Server Farm
  • Initial Farm Configuration Wizard

After setting up with SharePoint Products Configuration Wizard, use the Initial Farm Configuration Wizard to continue setting up the target SharePoint server.

  • For the Service Applications and Services setup page:

    • In Service Account section, you can either use an existing managed account, or create a new one if you want.
    • In Service Applications and Services section, make sure the User Profile Service is selected for installing.
  • For the Create Site Collection step:

    • Enter title and description for new site.
    • In Web Site Address section: choose the root "/" path for the URL (default).

After the Initial Farm Configuration Wizard has completed the setup, a new SharePoint site will be created. To check that the SharePoint server has been configured correctly:

  • Visit the SharePoint site URL,
  • Login to SharePoint site, if the home page is shown, then the setup is done.

Apply latest security patch for target sharepoint server

Note:

  • After setting up, at least one SharePoint user needs to be logged in to initialize the User Profile Database.
  • Take snapshot of both SQL Server and SharePoint Server after the setup is done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment