Setup Wizard: Collection Database page
Applies To: Forefront Client Security
Use this wizard page to specify details about the collection database. This page will appear when you install the collection database and when you install other components that need to know the location of the collection database. Some controls appear only when you install the collection database.
Important
It is highly recommended that you read the Client Security Deployment Guide. The Deployment Guide covers the system requirements, prerequisite software, and the order of installation, all of which are critical for successfully installing Client Security.
| Control | Description |
|---|---|
Collection database |
Specifies the name of the computer on which the collection database is located. If the collection database is not a default instance of a SQL Server database, you must also enter the instance name. For example: computer name\instance name If you are installing the collection server on the current computer, the default value should be correct. Important If you are installing other Client Security components and not installing the collection database on the current computer, then the default value will be incorrect. Make sure to update this value before continuing. In the standard topologies, the collection server and database are installed on the same computer. For more information about the collection database, see "Server components" in the Client Security Planning and Architecture Guide. |
Database size |
Determines the size of the collection database. Important Make sure the size you enter does not exceed the available space on your server. The database will be installed in the location you specified when installing SQL Server. For more information about choosing the size of the collection database, see "Performance and scalability considerations" in the Client Security Planning and Architecture Guide. |
Reporting account |
Specifies the reporting account. The reporting server uses the reporting account to access the reporting database and the collection database. When you enter the reporting account in the wizard, it must be a domain user account. Client Security automatically grants the reporting account the appropriate permissions as part of set up. This control appears only when you install the collection database. For more information about service accounts, including the reporting account, see "Service and installation accounts" in the Client Security Planning and Architecture Guide. |
Re-use the DAS account |
Select this check box if you want to use the DAS account user name and password for the reporting account as well. |
Client Security uses Microsoft Operations Manager (MOM) 2005 to collect and report about malware and vulnerabilities on the client computers. To learn about the MOM components in Client Security, see "Client Security and Microsoft Operations Manager" in the Client Security Planning and Architecture Guide.