请求协助：为SharePoint 2013场添加应用服务器

Got it, let's walk through how to add an application server to your SharePoint 2013 farm to take the load off that overworked WFE/App server. I've tackled similar setups for dev/test environments before, so here's a practical, step-by-step breakdown tailored to your scenario:

• First, make sure your new server meets SharePoint 2013's requirements: Windows Server 2012 R2 (or compatible), .NET Framework 4.5.2, and all required Windows Server roles/features (even for an app server, you'll need things like IIS components under the Web Server role).
• Join the new server to the same domain as your existing farm servers, and confirm DNS can resolve both the SQL server and existing WFE/App server names.
• Back up your farm's configuration database and all content databases—better safe than sorry. You can do this via Central Admin, or run the PowerShell command:

  Backup-SPFarm -Directory "C:\BackupLocation" -BackupMethod Full -ConfigurationOnly
  

• Grab your SharePoint 2013 installation media and product key (must match what's used in your current farm).

1. On the new server, run the PrerequisiteInstaller.exe from your SharePoint media. It'll automatically download and install all required dependencies—let this run fully (it might restart the server a few times).
2. Install the SharePoint 2013 server software, selecting the Complete installation type (avoid "Standalone" since we're joining an existing farm).
3. Launch the SharePoint Products Configuration Wizard, choose Connect to an existing server farm, then enter your existing SQL server name and the farm's configuration database name (you can find this in Central Admin on your WFE/App server, or run Get-SPFarm in PowerShell there to check).
4. Follow the wizard through to completion—once done, your new server will be part of the farm.

This is the key step to reduce load on your original server. We'll move non-WFE services to the new app server:

• Open Central Admin > System Settings > Manage services on server.
• First, on the new server, stop the Microsoft SharePoint Foundation Web Application service—we want this to be a dedicated application server, not a WFE.
• Now, switch to your original WFE/App server in the "Server" dropdown, stop resource-heavy services like these, then switch back to the new server and start them:
  • Search Service Application-related services (Search Query and Site Settings Service, Search Host Controller Service)
  • Managed Metadata Web Service
  • User Profile Service
  • Business Data Connectivity Service
  • Secure Store Service
• For your DEV/QAS web application pools: Go to Central Admin > Application Management > Manage web applications, select your DEV or QAS web app, click Application Pools > Change application pool, and assign the pool to run on the new application server. This lets the new server handle the backend processing for those apps.

• Since you need separate web apps for DEV and QAS, consider splitting their backend load: keep QAS-related services/app pools on the original server, and move DEV ones entirely to the new app server (or vice versa) to isolate environments.
• Use PowerShell to verify service assignments on the new server:

  Get-SPServiceInstance | Where-Object {$_.Server.Name -eq "YourNewAppServerName"}
  

• Monitor performance with Task Manager or Performance Monitor (track CPU, memory, and disk IO) for a few days, and adjust service/app pool assignments if you still see bottlenecks.

• Check Central Admin to confirm all services are running on the correct servers without errors.
• Test your DEV and QAS web apps thoroughly—make sure search works, metadata updates, and all custom components function as expected.
• Scan the SharePoint ULS logs (usually in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS) to catch any silent issues.

内容的提问来源于stack exchange，提问作者Kevin