Prerequisite Software for EV Installation on Windows 2003

Transcription

1 Implementation

2 Prerequisite Software for EV Installation on Windows 2003 Windows 2008 Server SP1, including:.net Framework 2.0 Message Queuing (no AD integration) IIS (with Active Server Pages enabled) Windows Installer 3.1 MSXML Microsoft Outlook 2003 (with CDO) Note: Not necessary if server only archives from Lotus Domino, SPS or File Server (new installations only) SQL Server 2000 SP4 or 2005 ready for use (usually separate server to EV server, limited for Vault Reporting)

3 Prerequisite Software for EV Installation on Windows 2008 Windows 2008 Server SP1, including:.net Framework 2.0 Message Queuing (no AD integration) IIS (with Active Server Pages enabled) Windows Installer MSXML Microsoft Outlook 2003 (with CDO) Note: Not necessary if server only archives from Lotus Domino, SPS or File Server (new installations only) SQL Server 2000 SP4 or 2005 ready for use (usually separate server to EV server, limited for Vault Reporting)

4 Message Queuing Enterprise Vault uses MSMQ to pass data between the Tasks and Storage Service Asynchronous messaging Fail-safe By default MSMQ installs into the C:\windows\system32\msmq\storage folder Can be changed in the Computer Management snap-in Ideally the MSMQ files should be on fast disks (heavy I/O) Not on the C: drive or any other heavily used disk Exclude MSMQ folders from anti-virus scanning Refer to Administrators_Guide.pdf for more detail on the message queues created and used by Enterprise Vault

5 SQL Server EnterpriseVaultDirectory database contains configuration information: Server identities and roles Storage locations Policies and configuration information Each Enterprise Vault Store has its own database for metadata (240 bytes per message, file or document archived): Content IDs Permissions Size (before single-instancing and compression) Dates (Content date and Archived date) Note: Enterprise Vault does not use SQL for index or data storage It is common to use an existing SQL server via ODBC Named instances are supported (e.g. SQLSRV01\EV) EV can only use case-insensitive SQL servers

6 Lesson Outline Prerequisite Software Environment Preparation Deployment Scanner Software Installation & Configuration Wizard Building Block Components

7 Environment Preparation Install prerequisite software Create Enterprise Vault service account Add EV service account to local administrators group on EV servers Assign MS Exchange permissions (if archiving from Exchange) Assign temporary SQL Server permissions SQL: Database Creator Windows: Local Administrator to see administrative shares Create permanent DNS aliases for site and each server Create EV service mailboxes on each Exchange Server Disable Strict Name Checking Initialize MAPI by running Outlook when EV account logged in

8 EV Service Account Must reside in an Active Directory domain Should not be a member of Domain Admins It will inherit AD permissions that explicitly Deny access to mailboxes Must be a member of the local Administrators Group on every EV server Does not need to be a member of the local Administrators group on Exchange Servers Should be sole-purpose, not a shared account Other user accounts may be given restricted admin rights later via Roles Based Administration

9 Exchange Permissions Exchange 5.5 Not supported from EV 7.0 onwards Exchange 2000 & 2003 Exchange Full Administrator on each server or higher Double-check to ensure Receive As and Send As are not denied Exchange 2007 Full Control (for Mailbox Role Server)

10 SQL Server Permissions The EV Service Account needs to have DB Creator permissions during the installation, and when creating vault store databases This permission can be removed after setup Configure the data files and the log files on different spindles Setup requires SQL local admin rights to see administrative shares to specify data locations (C$, D$, etc) Run this part of the setup from an account that is a member of the local Administrators group (in Windows) on the SQL server If customer will not allow EV setup wizard to create databases on production SQL server, temporarily point EV to a nonproduction SQL server, then transplant the databases to the production SQL server

11 DNS Aliases Vault Site Alias Vault Site: a group of Enterprise Vault servers with the same settings Vault Site has no dependence on physical sites, Exchange sites, etc Vault Site typically resolves to Directory server, unless there are multiple sites in one Directory Vault Server Alias One alias for every Enterprise Vault server Simplifies failover and future reconfiguration Required even if installing on VCS or MS Cluster Point DNS aliases to virtual cluster server names

12 EV Service Mailbox Every Exchange server being archived needs to have a unique mailbox created on it Used by the Archiving, Journaling, and Public Folder Tasks Need a mailbox to make initial connection to Exchange Service mailboxes cannot be enabled for archiving (keep empty!) Must not be hidden from address lists or disabled Tasks create MAPI profiles on the fly so need to be able to resolve the service mailbox each time EV service mailbox names must be unique to the end names should not be a subset of another name Standard naming convention is EnterpriseVault(exchangeserver) e.g. EnterpriseVault(EXCH1) This avoids a possibly ambiguous name that will not be resolvable by Outlook (and thus by the Archiving tasks)

13 Exchange Organizational Forms Provide icons and retrieval transparency for Outlook users Manually install once per language in each Exchange org, and they are available to all users as needed by Outlook automatically, no need to copy them to each client Forms need to be replicated to all Exchange servers where mailboxes are being archived Use Outlook to install the 4 forms into the Exchange folder using an account that is a folder owner To support multiple languages, customer should have multiple Organizational Form libraries. Copy the appropriate form files into the appropriate libraries, by language. EV 8.0 provides forms in 13 languages

15 Deployment Scanner - Overview Can be run pre-install to check prerequisites Can be run post-install to gather information about the environment for sending to Symantec Technical Support This will be covered in a later lesson Before installation, run Deployment Scanner on the vault server when logged in as Vault Service Account (VSA) Checks that all necessary prerequisite applications are installed on the server it is run from Also checks VSA s permissions to Exchange, SQL, File Servers and Sharepoint if you provide the names of those servers to test Must run Deployment Scanner as VSA for this to be valid test Provides results both on screen as well as in a HTML report file (Passed, Warning, Failed, Info)

16 Running the Deployment Scanner Prior to Installation

17 Specifying Configuration Options for Deployment Scan (1)

18 Specifying Configuration Options for Deployment Scan (2)

19 Deployment Scan Report - Summary Report is an html file can be opened later in browser

20 Deployment Scan Report - Detail Scan can easily be run again once problem has been addressed

22 Enterprise Vault Installation Wizard-driven installer program Installs Admin Service and Web Application, and copies files for other services (which will be created during the Configuration stage) Main Enterprise Vault installer is used to install the following features: Administration Console Enterprise Vault Services OWA & RPC front-end and back-end components Enterprise Vault Reporting Operations Manager Monitoring Web App File Placeholder Service, User Extensions, Compliance and Discovery Accelerators, and ECM connectors are separate installers

23 Enterprise Vault Configuration Separate Configuration Program run after installation Identifies Vault Service Account and DNS aliases Grants local privileges to Vault Service Account Log on as a service Debug programs Act as part of the operating system Replace a process-level token Creates (or connects to) Directory Service and database Creates monitoring database and monitoring agents Creates new Vault Site, or joins existing Vault Site Installs core services (storage, indexing, shopping, task controller)

25 Enterprise Vault Building Blocks Building block is a scalable, repeatable unit of Enterprise Vault functionality, containing: Directory Service Storage Service Indexing Service Shopping Service Task Controller Service Web Access Application Admin Service

26 Directory Service Used to retrieve and update EV configuration information stored in a SQL Server database Only one EV configuration database per directory By default, only the first server in a Directory has a Directory Service Directory Service created on all EV servers when they are converted to Building Blocks This is covered in the High Availability lesson

27 Storage Service Takes care of managing the storage and retrieval of archived data Items are passed to the Storage Service via MSMQ by the various archiving tasks Stores items in a vault store Creates an HTML or Text copy of the archived item Creates a compressed version of the item on a NTFS file system, or through a specific storage API (like a Centera) Stores metadata in the SQL Server database Must have Indexing Service on the same server

28 Indexing Service Uses Alta Vista Enterprise Edition Indexes archived items Created on NTFS partitions only Strongly recommended to store indexes on DAS or SAN Recommended to configure multiple indexing locations in the service properties before creating archives (or enabling mailboxes for archiving) Provides load balancing across disk spindles Makes it easier to move indexes around as they grow Rule of thumb: 1 Index Location per 1000 mailboxes, with a minimum of 4 Index Locations

29 Shopping Service Shopping service used to create and manage users shopping baskets Required by Web Access Application Through the Web Access Application users add items they wish to be restored to a shopping basket Installed on every EV server automatically Shopping service uses a small amount of space to record user shopping basket information These files must be on direct-attached disk

30 Task Controller Service Manages up to 40 Enterprise Vault Tasks Must be installed before tasks can be installed Stopping the Task Controller Service stops all tasks Tasks can be configured for Automatic or Manual startup Automatic tasks start when Task Controller Service starts

31 Web Access Application Not to be confused with Outlook Web Access Installed on every EV server automatically during setup Set of Active Server pages Provides the main search interface to the archived information within EV Also handles requests from Outlook shortcuts By default the URL contains the FQDN of the Directory server. This needs to be removed when multiple servers are used.

32 Anti-Virus Exclusions Do NOT scan: MSMQ folders *.DVS files (Vault Store folders) Index files Temp folder Ideally virus scanning should occur before or as items enter mailboxes At gateway At desktop Exchange database scan Enterprise Vault data should also be scanned on the workstation when a user retrieves and opens an archived item