Fabric Management Fabric Management Host and Guest Installation Fabric Management Guest Sizing To help you properly size fabric management host systems, the following table outlines the virtual machines (and their default configurations) that are deployed to compose the fabric management component architecture. These virtual machines are hosted on a dedicated two- to four-node Hyper-V failover cluster. These virtual machines serve as the basis for fabric management operations. The table summarizes the fabric management virtual machine requirements by the System Center component that supports the product or operating system role. These requirements include CPU, random access memory (RAM) in gigabytes (GB), and virtual hard disk (VHD). Component roles Virtual CPU RAM (GB) Virtual hard disk (GB) Microsoft SQL Server cluster node 1 16 16 60 Microsoft SQL Server cluster node 2 16 16 60 Microsoft System Center Virtual Machine Manager (VMM) management server 4 8 60 Virtual Machine Manager management server 4 8 60 Microsoft System Center App Controller server 4 8 60 Microsoft System Center Operations Manager management server 8 16 60 Microsoft System Center Operations Manager reporting server 8 16 60 Microsoft System Center Orchestrator server (management server, runbook server, and web service) 4 8 60 Microsoft System Center Service Reporting server 4 16 60 Microsoft System Center Service Provider Foundation server 2 4 60
Server cluster. All instances must be configured with Windows Authentication. The following table outlines the options that are required for each instance. Fabric management component Instance name (suggested) Components Collation Storage requirements Virtual Machine Manager Windows Server Update Services SCVMMDB Database Engine Latin1_General_100_CI_AS Two LUNs Operations Manager SCOMDB Database Engine, Full-Text Search Latin1_General_100_CI_AS Two LUNs Operations Manager data warehouse SCOMDW Database Engine, Full-Text Search Latin1_General_100_CI_AS Two LUNs Service Manager SCSMDB Database Engine, Full-Text Search Latin1_General_100_CI_AS Two LUNs Service Manager data warehouse SCSMDW Database Engine, Full-Text Search Latin1_General_100_CI_AS Two LUNs Service Manager data warehouse SCSMAS Analysis Services Latin1_General_100_CI_AS Two LUNs Service Manager web parts and portal (Microsoft SharePoint Foundation) Orchestrator App Controller Service Provider Foundation Service Management Automation SCDB Database Engine Latin1_General_100_CI_AS Two LUNs Windows Azure Pack WAPDB Database Engine Latin1_General_100_CI_AS Two LUNs Table 6 Database instances and requirements
SQL Server instance LOG cluster disk resource Cluster Disk 3 Cluster Disk 5 Cluster Disk 7 Cluster Disk 9 Cluster Disk 11 Cluster Disk 13 Cluster Disk 15 Cluster Disk 17 SQL Server instance installation drive E G I K M O Q S SQL Server instance DATA drive E G I K M O Q S SQL Server instance LOG drive F H J L N P R T SQL Server Instance TEMPDB Drive F H J L N P R T Cluster service name SQL Server (SCSMDB) SQL Server (SCSMDW) SQL Server SQL Server (SCDB) SQL Server SQL Server (SCOMDB) SQL Server (SCOMDW) SQL Server (WAPDB) Clustered SQL Server instance IP address 10.1.1.22 10.1.1.23 10.1.1.24 10.1.1.25 10.1.1.26 10.1.1.27 10.1.1.28 10.1.1.29 Host cluster public network interface subnet mask 255.255.255.0 255.255.255.0 (SCSMAS
Installing the SQL Server Named Instances on the Guest Cluster (Additional Nodes) After you create all required SQL Server instances on Node 1, you can add more nodes to each instance of the cluster. (Node 2 is required, and additional nodes are optional.) Complete the following steps to begin the installation of additional nodes of the cluster. Perform the following steps on each additional fabric management SQL Server node virtual machine. From the SQL Server 2012 SP1 installation media source, setup.exe, and then click Run as administrator to begin setup. The SQL Server Installation Center appears. From the SQL Server Installation Center, click the Add node to a SQL Server failover cluster link. The SQL Server 2012 Setup Wizard appears. On the Setup Support Rules page, verify that each rule shows a Passed status. If any rule requires attention, remediate the issue and rerun the validation check. Click OK to continue. On the Product Updates page, select the Include SQL Server product updates check box, and then click Next to continue. On the Install Setup Files page, click Install and allow the wizard to install the support files.
Click the Permissions tab, and then click Add. Add the following accounts with Full Control permissions for the NTFS file system: Virtual Machine Manager service account Virtual Machine Manager Administrators group Both Virtual Machine Manager computer accounts Virtual Machine Manager cluster name object computer account Virtual Machine Manager virtual computer object (VCO) computer account Click OK to save the changes, and then click Next to continue the wizard. On the Confirm selections page, review the settings, and then click Create. On the View results page, verify that the shared folder was provisioned properly, and then click Close. Perform the following steps on the Virtual Machine Manager virtual machine. In the Virtual Machine Manager console, click the Library node. Click the Home tab, and then click Add Library Server from the ribbon.
On the Select Management Packs from Catalog page, find and add the following management packs (in this order): Windows Server Internet Information Services Library Windows Server Internet Information Services 2003 Windows Server 2008 Internet Information Services 7 Windows Server 2008 Operating System (Discovery) Windows Server Operating System Library SQL Server Core Library Click OK to continue. Note that additional management packs may be required to satisfy dependencies or monitoring requirements for the target infrastructure. On the Select Management Packs page, click Install to import the selected management packs. The management packs are downloaded into Operations Manager. When the process is complete, verify that the imports were successful, and then click Close to exit the Import Management Packs Wizard. In the Operations Manager console, browse to the Administration workspace and verify that the previously selected management packs are installed.
<DOMAIN>\ FT-SCSM-WF Service Manager workflow account Must have permissions to send email and must have a mailbox on the Simple Mail Transfer Protocol (SMTP) server (required for the Email Incident feature) Must be a member of the local Users security group on all Service Manager servers Must be a member of the Service Manager Administrators user role for email Must be a local administrator on all SQL Server nodes <DOMAIN>\ FT-SCSM-SSRS Service Manager reporting account Must be a local administrator on all SQL Server nodes <DOMAIN>\ FT-SCSM-OMCI Service Manager Operations Manager CI connector account Must be a member of the local Users security group on all Service Manager servers Must be an Operations Manager operator <DOMAIN>\ FT-SCSM-ADCI Service Manager Active Directory CI connector account Must be a member of the local Users security group on the Service Manager management server Must have permissions to bind to the domain controller that the connector will read data from Must have generic Read rights on the objects that are being synchronized to the Service Manager database from AD DS <DOMAIN>\ Service Manager Operations Manager alert connector account Must be a member of the local Users security group on the Service Manager management server Must be a member of FT-SCSM-Admins <DOMAIN>\ FT-SCSM-VMMCI Virtual Machine Manager CI connector account Must be a member of the Virtual Machine Manager Administrators domain group and be in the Service Manager Advanced Operator role <DOMAIN>\ FT-SCSM-OCI Orchestrator CI connector account Must be a member of the Orchestrator Operators (Users) domain group and be in the Service Manager Advanced Operator role
administrative rights to all Service Provider Foundation components and web services. <DOMAIN>\ FT-SPF-Provider Service Provider domain group used to provide domain accounts access to the Service Provider Foundation Provider web service. Appropriate domain accounts to be delegated permissions to services <DOMAIN>\ FT-SPF-VMM Service Provider domain group used to provide domain accounts access to the Service Provider Foundation VMM web service. Appropriate domain accounts to be delegated permissions to services <DOMAIN>\ FT-SPF-Usage Service Provider domain group used to provide domain accounts access to the Service Provider Foundation Usage web service. Appropriate domain accounts to be delegated permissions to services <SPF Server>\SPF_Admin Local group created by Service Provider Foundation setup process to provide access to the Admin web service. Domain groups and accounts must be added after setup finishes. <Service Provider Foundation Server>\Local-SPF-SVC <DOMAIN>\FT-SPF-Admins <Service Provider Foundation Server>\SPF_Provider Local group created by Service Provider Foundation setup process to provide access to the Admin web service. Domain groups and accounts must be added after setup finishes. <Service Provider Foundation Server>\Local-SPF-SVC <DOMAIN>\FT-SPF-Admins <DOMAIN>\ FT-SPF-Provider <Service Provider Foundation Server>\SPF_VMM Local group created by Service Provider <Service Provider Foundation Server>\Local-SPF-SVC
Appendix A: SQL Server Cluster Named Instance Worksheet Before you install the SQL Server cluster, we recommend that you compile information to provide a point of reference for the information that is required during the setup steps. You can use the following template for that purpose. Component Service Manager server Service Manager data warehouse server Service Manager analysis server App Controller, Microsoft SharePoint Services farm, and WSUS Virtual Machine Manager Manager Operations Manager data warehouse SQL Server instance name SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW SQL Server instance failover cluster network name SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW SQL Server instance DATA cluster disk resource SQL Server instance LOG cluster disk resource SQL Server Instance installation drive SQL Server instance DATA drive SQL Server instance LOG drive SQL Server instance TEMPDB drive Cluster service name SQL Server (SCSMDB) SQL Server (SCSMDW) SQL Server (SCSMAS) SQL Server (SCDB) SQL Server (SCVMMDB) SQL Server (SCOMDB) SQL Server (SCOMDW)
Appendix B: Example VHD Design VHD name Components Instance name Purpose Size VHDX 1 Service Manager management SCSMDB Instance database 145 GB VHDX 2 Service Manager management SCSMDB Instance logs 70 GB VHDX 3 Service Manager data warehouse SCSMDW Instance database 1 terabyte (TB) VHDX 4 Service Manager data warehouse SCSMDW Instance logs 500 GB VHDX 5 Service Manager Analysis Services SCSMAS Analysis services 8 GB VHDX 6 Service Manager Analysis Services SCSMAS Analysis logs 4 GB VHDX 7 Service Manager SharePoint farm Orchestrator App Controller Service Provider Foundation Service Management Automation SCDB Instance database 10 GB VHDX 8 Service Manager SharePoint farm Orchestrator App Controller Service Provider Foundation Service Management Automation SCDB Instance logs 5 GB VHDX 9 Virtual Machine Manager Windows Server Update Services SCVMMDB Instance database 6 GB VHDX 10 Virtual Machine Manager Windows Server Update Services SCVMMDB Instance logs 3 GB VHDX 11 Operations Manager SCOMDB Instance database 130 GB VHDX 12 Operations Manager SCOMDB Instance logs 65 GB