'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Configure IIS After Adding a SharePoint 2016 Farm Server
Question details
The user needs to know which specific IIS and farm settings must be manually verified or configured after adding a new server to an existing SharePoint 2016 farm.
- Product
- SharePoint 2016
- Device & OS
- not provided
- Scenario
- Expanding a SharePoint 2016 farm architecture by introducing new servers and ensuring proper web application delivery.
- Observed behavior
- Ensure that IIS websites, application pools, service instances, SSL certificates, and load balancing configurations seamlessly integrate the new server into the farm.
Ensure that the SharePoint Configuration Wizard has successfully finished running on the newly added server before applying any manual IIS configurations.
Verify and Configure IIS Settings for the New Farm Server
Use this checklist to ensure all essential IIS configurations, bindings, and custom modules are properly set up on the new SharePoint server.
While the SharePoint Configuration Wizard automates many baseline provisions, manual verification is critical for custom environments, SSL configurations, and third-party integrations.
Your exact steps will vary depending on your specific farm design, MinRole topology, and server load balancing mechanisms.
Open IIS Manager on the new server and confirm that the required SharePoint IIS websites and application pools have been successfully provisioned by the farm.
If the newly added server is intended to host entirely new web applications, manually create the corresponding IIS websites and application pools as required by your architecture.
Check the site bindings in IIS Manager. Ensure that host headers and ports are correct, and manually import and bind your SSL certificates to the HTTPS endpoints.
If your farm utilizes a network load balancer or reverse proxy, access your load balancer's admin console and add the new server's IP address to the appropriate server pool.
Open Central Administration or use PowerShell (Get-SPServiceInstance) to verify that all required SharePoint services are started and running correctly on the new server.
Manually install and configure any third-party IIS modules, ISAPI filters, or URL rewrite rules that are utilized by other servers in the farm to ensure consistency.
Document Your SharePoint Farm Architecture with WPS Office
While server deployments require dedicated Microsoft admin tools, documenting your complex farm topology, IP addresses, and IIS configurations is crucial. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for maintaining your IT infrastructure guides.
- 1. Download and install WPS Office: Get the free installer from the official WPS website and quickly set it up on your administrative workstation.
- 2. Create server documentation: Open WPS Writer to draft your IIS configuration steps, or use WPS Spreadsheet to manage your server IP addresses and load balancer routing tables.
- 3. Save in standard formats: Save your documents as .docx or .xlsx to share seamlessly with other system administrators on your team.
Frequently Asked Questions
Do I need to manually create the Central Administration site in IIS on the new server?
No. If you selected a server role that hosts Central Administration during the configuration phase, the SharePoint Configuration Wizard will automatically provision the site in IIS.
Why are my custom IIS settings missing on the new SharePoint server?
SharePoint only replicates settings configured through Central Administration or SharePoint PowerShell. Manual IIS modifications, such as custom ISAPI filters or manual web.config edits, do not replicate automatically and must be recreated.
Do I need to re-import SSL certificates on the newly added farm server?
Yes. SSL certificates must be manually imported into the local machine's certificate store and then bound to the appropriate IIS websites on every new server added to the farm.
