Dell PowerVault DP600 - Manual (Page 88)

88
Software Requirements
• DPM is designed to run on a dedicated, single-purpose server that cannot be either a domain
controller or an application server.
• To administer multiple DPM servers remotely, install DPM Management Shell on computers
other than the DPM server.
Installing DPM 2007
• You must properly configure Microsoft Windows Server 2003 to support a DPM 2007
installation. For more information about installing Windows Server 2003, see How to Install
Windows Server 2003 ( http://go.microsoft.com/fwlink/?LinkID=100243 ).
• DPM 2007 requires a clean installation of DPM. Before you install DPM 2007, you must first
uninstall System Center Data Protection Manager 2006 (DPM 2006) and its associated
prerequisite software, as well as any previous versions of DPM. Because of the architectural
differences between DPM 2006 and DPM 2007, you cannot directly upgrade a computer
running DPM 2006 to DPM 2007. However, DPM 2007 includes an upgrade tool that enables
you to migrate your DPM 2006 protection group configurations to DPM 2007.
For more information about upgrading from DPM 2006 to DPM 2007, see Upgrading
DPM 2006 to DPM 2007 (http://go.microsoft.com/fwlink/?LinkId=66737).
• If you choose to install DPM or prerequisite software products from a shared folder, DPM
Setup adds the Universal Naming Convention (UNC) path of the shared folder to the Internet
Explorer local intranet security zone for the duration of the installation.
• You cannot install DPM 2007 on the same computer on which your Microsoft Exchange
Server is running.
• You can install DPM only on a local drive, and you cannot install it in read-only folders, in
hidden folders, or directly to local Windows folders such as Documents and Settings or
Program Files. (DPM can, however, be installed to a subfolder of the Program Files folder.)
• After installation is complete, apply all available Windows Server 2003 service packs and
updates. All Windows updates are available from Microsoft Windows Update
(http://go.microsoft.com/fwlink/?LinkID=451).
Use a Remote Instance of SQL Server
• We recommend a clean installation on the remote instance of Microsoft SQL Server or when
installing the dedicated instance of SQL Server for DPM, and that you use the following
settings:
• Default failure audit setting.
• Default Windows Authentication mode.
• Assign a strong password to the sa account.
• Enable password policy checking.
• Install only the SQL Server Database Engine and Reporting Services components.