Install Windows Server 2008 R2 or Windows Server 2008 on each server machine. For basic instructions in the context of the example in this documentation, see Install Windows Server 2008 R2. For Microsoft's guidance, see Installing Windows Server 2008 R2 or Install and Deploy Windows Server.
For the purposes of the examples in this documentation, the application server machine will be the domain controller and a DNS server. The Active Directory Domain Services Installation Wizard recommends assigning IP addresses for physical network adapters statically. For basic instructions about how to assign static IP addresses to physical network adapters, see Assign Static IP Addresses to Physical Network Adapters. For basic instructions in the context of the example, see Make the Application Server the Domain Controller. For Microsoft's guidance, see Installing an Additional Domain Controller.
Also, in these examples, roles are added to the application server to support its function as an Active Directory server and a DHCP server. For basic instructions in the context of the example, see Add AD and DHCP Roles to the Server. For Microsoft's guidance, see AD DS Installation and Removal Step-by-Step Guide and Dynamic Host Configuration Protocol.
For basic instructions about how to add the other servers to the domain, see Add a Machine to the Domain.
A number of other role services on the application server are prerequisites for Blackbaud CRM and Blackbaud Internet Solutions installation. You can set these up before you install Blackbaud CRM and Blackbaud Internet Solutions. But in these examples, the role services will be added as necessary. These examples include screenshots of the error messages that occur if role services are not added along with links to basic instructions. Here are the basic instructions for each of those role services:
Add Indexing Service Role Service
Add IIS Management Scripts and Tools Role Service
Add IIS 6 WMI Compatibility Role Service
Add ISS 6 Scripting Tools Role Service
For Micorosft's guidance about installing these role services, see Installing IIS 7 on Windows Server 2008 or Windows Server 2008 R2 and Available Web Server (IIS) Role Services in IIS 7.5.
.NET framework 3.5 should be installed prior to the installation of .NET framework 4.0 on each of the server machines. Installing SQL Server 2008 R2 on the database machine handles this. In the example, configuring the application server with a role for Active Directory Domain Services includes an installation of .NET 3.5. However, the safest approach is to install .NET 3.5 early to avoid accidentally installing .NET 4.0 first. There is potential to corrupt the functionality of .NET 4.0 in IIS otherwise which may require re-registering .NET 4.0 with IIS.
Note: If you encounter this issue with .NET 4.0 and IIS, the registration executable is located at a location such as C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_iisreg.exe.
For more information about installing .NET 3.5 see, Install .NET Framework 3.5. The Blackbaud CRM installer prompts for installation of .NET 4.0, which requires access to the Internet or installation media. But, you can install .NET 4.0 prior to installation of Blackbaud CRM. For more information, see Install .NET Framework 4.0. The downloads page for .NET 3.5 is located at Microsoft .NET Framework 3.5. A downloads page for .NET 4.0 is located at Microsoft .NET Framework 4 (Web Installer). Microsoft discusses .NET 4.0 and its relationship to earlier editions in What's New in the .NET Framework 4.
Install SQL Server 2008 or SQL Server 2008 R2 on each machine to host the Infinity database and each machine to host reporting services. For basic instructions in the context of this documentation's example, see Install SQL Server 2008 R2. For Microsoft's guidance, see How to: Install SQL Server 2008 (Setup), How to: Install SQL Server 2008 R2 (Setup), Install SQL Server 2012 from the Installation Wizard (Setup).
For the SQL Server installations, enable Named Pipes and TCP/IP Connections. For basic instructions in the context of this documentation's example, see Enable Named Pipes and TCP/IP Connections. For Microsoft's guidance about network protocols, see Choosing a Network Protocol.