Plesk 9.5 Win Advanced Administration Guide

8/9/2019 Plesk 9.5 Win Advanced Administration Guide

http://slidepdf.com/reader/full/plesk-95-win-advanced-administration-guide 1/206

Revision 1.1

Parallels®

Plesk Panel

Parallels Plesk Panel 9.5 for Windows

Advanced Administration Guide



Copyright Notice

ISBN: N/A

Parallels

660 SW 39th Street

Suite 205

Renton, Washington 98057

USA

Phone: +1 (425) 282 6400

Fax: +1 (425) 282 6444

© Copyright 1999-2010,

Parallels, Inc.

All rights reserved

Distribution of this work or derivative of this work in any form is prohibited unless prior writtenpermission is obtained from the copyright holder.

Patented technology protected by U.S.Patents 7,328,225; 7,325,017; 7,293,033; 7,099,948;7,076,633.

Patents pending in the U.S.Product and service names mentioned herein are the trademarks of their respective owners.



Contents

Preface 6

Documentation Conventions ......................................................................................................... 6

Typographical Conventions ........................................................................................................... 6

Feedback .......................................................................................................................................7

About This Guide ...........................................................................................................................8

Who Should Read This Guide ....................................................................................................... 9

How This Guide Is Organized ..................................................................................................... 10

Introduction 12

When to Use Parallels Plesk Panel Advanced Features 13

Administering Securi ty Sett ings on Windows Objects 14

Parallels Plesk Panel Security Policies ....................................................................................... 15

Windows Accounts Used by Parallels Plesk Panel to Manage Windows Objects ...................... 15

Default User Permissions for Disks .................................................................................. 15

Windows Accounts Used by Parallels Plesk Panel to Manage Hosted Windows Objects ......... 18

Administering Windows Objects Security on Parallels Plesk Panel Server ................................ 20

Initial Windows Security Configuration During Parallels Plesk Panel Installation or Hosting Account Creation ...............................................................................................................21

Browsing Object Security Settings Through Parallels Plesk Panel GUI ........................... 22

Customizing Object Security Settings in Parallels Plesk Panel ........................................ 23

General Security Metadata Structure ................................................................................ 38

Achieving Compl iance with Payment Card Industry Data Securi ty Standard 43

Programming Event Handlers to Execute Custom Scripts on Parallels Plesk Panel Server 45

Parallels Plesk Panel Events .......................................................................................................46

Creating Event Handlers .............................................................................................................51

Removing Event Handlers ...........................................................................................................51

Composing Event Handler Command ......................................................................................... 52

Event Handler Command Syntax ...................................................................................... 52

Environment Variables in Event Handler Commands ....................................................... 52

Event Handler Command Example ................................................................................... 53

Event Parameters Passed by Event Handlers .................................................................. 54

Script Writing Rules .....................................................................................................................88

Installing and Upgrading Parallels Plesk Panel Components 89

Parallels Plesk Panel Component Installation and Upgrade Overview ....................................... 90

Third-Party Application Installation as Parallels Plesk Panel Component ........................ 90

Parallels Plesk Panel Component Upgrade ...................................................................... 93 Third-Party Applications Supported by Parallels Plesk Panel ..................................................... 94

Third-Party Applications not Supported by Parallels Plesk Panel ............................................... 96



Preface 4

Installing and Upgrading Parallels Plesk Panel Components ..................................................... 97

General Integration Procedure .......................................................................................... 98

Installing and Upgrading Mail Components ...................................................................... 99

Installing and Upgrading Antivirus Components ............................................................. 111

Installing and Upgrading DNS Servers ........................................................................... 118

Installing and Upgrading FTP Servers ............................................................................ 122 Installing and Upgrading Server-Side Web Scripting Engines ........................................ 132

Installing and Upgrading Web Administration Tools ....................................................... 147

Installing and Upgrading Database Servers ................................................................... 152

Installing and Upgrading Web Mail Solutions ................................................................. 156

Installing SpamAssassin Spam Filter .............................................................................. 162

Installing stunnel .............................................................................................................163

Using Parallels Plesk Billing ............................................................................................ 164

Using Parallels Plesk Panel Reconfigurator 165

Getting Started With Parallels Plesk Panel Reconfigurator ...................................................... 166

Changing IP Addresses on Parallels Plesk Panel Server ......................................................... 167

Changing Virtual Hosts Location ............................................................................................... 168

Changing Parallels Plesk Panel Backup Data Location ............................................................ 169

Changing Parallels Plesk Panel Mail Data Location ................................................................. 169

Repairing Parallels Plesk Panel Installation .............................................................................. 170

Restoring Disk User Permissions .............................................................................................. 173

Switching Parallels Plesk Panel Database Server Engine ........................................................ 174

Using GUI to Switch Between Database Servers ........................................................... 175

Using Command-Line Interface to Switch Between Database Servers ... ...................... 176

Checking Component and Folder Permissions ......................................................................... 179

Changing Web Server Used for Accessing Parallels Plesk Panel ............................................ 180

Managing Tomcat Service 181

Changing Tomcat Java Connector Ports .................................................................................. 181

Monito ring Server Status with Parallels Plesk Panel Services Monitor 182

Changing Your Server's Host Name 183

Customizing Parallels Plesk Panel Title Bar Text 184

Customizing Link to Parallels Plesk Panel Support 185

Creating Link to Support Form on Your Site ............................................................................. 187

Creating Link to Compose E-mail Message .............................................................................. 189

Changing DNS Zone Serial Number Format 190

Restoring Mail Configuration 191

Automating Parallels Plesk Panel Management Tasks by Using Command-Line Interface 193



Preface 5

Configuring MSDE Network Access 194

Parallels Plesk Panel Autoupdates by vztmplupsvc Service Using Virtuozzo Update Templates195

Rules for User Names and Passwords of Parallels Plesk Panel Users 197

Customizing Statistics Calculation 198

Configuring APS Applications Catalog 200

Switch ing PHP Handler Type to FastCGI 203

Using Open Relay Option for Your Mail Server 205

Glossary 206



6 Preface

In this section:

Documentation Conventions ............................................................................... 6 Typographical Conventions ................................................................................. 6 Feedback ............................................................................................................. 7 About This Guide ................................................................................................. 8

Who Should Read This Guide ............................................................................. 9 How This Guide Is Organized ............................................................................. 10

Documentation Conventions

Before you start using this guide, it is important to understand the documentationconventions used in it.

Typographical Conventions

The following kinds of formatting in the text identify special information.

Formatting convention Type of Information Example

Special Bold Items you must select, such asmenu options, commandbuttons, or items in a list.

Go to the QoS tab.

Titles of chapters, sections,and subsections.

Read the Basic Administration chapter.

Italics Used to emphasize theimportance of a point, tointroduce a term or todesignate a command lineplaceholder, which is to bereplaced with a real name orvalue.

The system supports the socalled wildcard character search.

Monospace The names of style sheetselectors, files and directories,and CSS fragments.

The license file is calledl i cense. key.

Preface



Preface 7

Preformatted Bold What you type, contrasted withon-screen computer output.

Unix/Linux:

# cd /root/rpms/php

Windows:

>cd %myfolder%Pref ormat t ed On-screen computer output in

your command-line sessions;source code in XML, C++, orother programming languages.

Unix/Linux:

# ls –al /filest otal 14470

Windows:

>ping localhostRepl y f r om 127. 0. 0. 1:byt es=32 t i me<1ms TTL=128

Feedback

If you have found an error in this guide, or if you have suggestions or ideas on how toimprove this guide, please send your feedback using the online form athttp://www.parallels.com/en/support/usersdoc/. Please include in your report the guide's title,chapter and section titles, and the fragment of text in which you have found an error.

http://www.parallels.com/en/support/usersdoc/

http://www.parallels.com/en/support/usersdoc/



8 Preface

About This Guide

The Parallels Plesk Panel for Windows Advanced Features Administrator's Guide is acompanion guide for Parallels Plesk Panel for Windows Administrator's guide. The guideprovides step-by-step instructions to perform Parallels Plesk Panel management tasks thatrequire use of Parallels Plesk Panel functionality other than the GUI and GUI-only tasks thatParallels Plesk Panel administrators may need to perform only in rear specific situations. Theneed to perform these tasks is likely to arise only when Parallels Plesk Panel server isrunning in a non-standard configuration.



Preface 9

Who Should Read This Guide

This book is intended for Parallels Plesk Panel server administrators whose responsibilitiesinclude maintaining Parallels Plesk Panel servers and troubleshooting server softwareproblems. The administrators who use Parallels Plesk Panel in a non-standard configuration,that is, configuration that includes components other than those provided in original ParallelsPlesk Panel distribution package, are encouraged to familiarize themselves with the contentsof this guide.



10 Preface

How This Guide Is Organized

The following table describes the chapters in this guide:

Chapter Name Chapter Description

Chapter 2, Introduction (onpage 12)

Briefly describes the user tasks that can be accomplished byusing the Parallels Plesk Panel advanced features.

Chapter 3, When to UseParallels Plesk Panel Advanced Features (on page13)

Describes user cases when use of the Parallels Plesk Paneladvanced features rather than features implemented throughthe GUI is warranted.

Chapter 4, Administering

Security Settings onWindows Objects (on page14)

Describes the process of applying Parallels Plesk Panel

security rules to Windows objects and provides step-by-stepinstructions for customizing both disk and hosting security onParallels Plesk Panel servers. Presents examples of commonlyused security rules with explanations.

Chapter 5, ProgrammingEvent Handlers to ExecuteCustom Scripts on ParallelsPlesk Panel Server (on page45)

Describes the event handler procedure, event handlercommand syntax, rules for writing custom scripts to be used inthe event handler commands.

Chapter 6, Installing andUpgrading Third-PartyParallels Plesk PanelComponents (on page 97)

Describes supported third-party software application (ParallelsPlesk Panel component) installation and upgrade proceduresemphasizing the extra steps that must be taken to successfullyinstall or upgrade each supported application.

Chapter 7, Using ParallelsPlesk Panel Reconfigurator(on page 165)

Describes the use of the application to reconfigure ParallelsPlesk Panel server IP addresses, moving large volumes ofhosted Web or mail content hosted on Parallels Plesk Panelserver to another location on a file system.

Chapter 8, ManagingTomcat Service (on page181)

Describes changing Tomcat connector port numbers by usingSQL queries to the Parallels Plesk Panel database.

Chapter 9, Monitoring ServerStatus with Parallels PleskPanel Services Monitor (on

page 182)

Describes monitoring services' statuses of Parallels PleskPanel server without logging in to Parallels Plesk Panel (byaccessing the server operating system).

Chapter 10, Changing YourServer's Host Name (onpage 183)

Describes changing Parallels Plesk Panel server's host name.

Chapter 11, CustomizingParallels Plesk Panel TitleBar Text (on page 184)

Describes setting or changing Parallels Plesk Panel Title bartext by using SQL queries to the Parallels Plesk Paneldatabase.

Chapter 12, CustomizingLink to Parallels Plesk PanelSupport (see page 185)

Describes setting the link to Parallels Plesk Panel support sothat it leads to your support team instead of Parallels support.



Preface 11

Chapter Name Chapter Description

Chapter 13, Changing DNSZone Serial Number Format(on page 190)

Describes changing changing DNS zone serial number formatby using SQL queries to the Parallels Plesk Panel database.

Chapter 14, Restoring MailServer Configuration (onpage 191)

Describes restoring mail server configuration and synchronizingthe configuration with the Parallels Plesk Panel database.

Chapter 15, AutomatingParallels Plesk PanelManagement Tasks byUsing Parallels Plesk PanelCommand-Line Interface (onpage 193)

Introduces the Parallels Plesk Panel command-line utilities andprovides information about accessing the command-line utilitiesuser documentation.

Chapter 16, ConfiguringMSDE Network Access (on

page 194)

Describes the network transport protocol requirements foraccess MSDE from network.

Chapter 17, Parallels PleskPanel Autoupdates byvztmplupsvc Service UsingVirtuozzo Update Templates(on page 195)

Provides information about Parallels Plesk Panel autoupdatesimplementation for Parallels Plesk Panels installed on VPSs byusing Virtuozzo application templates.

Chapter 18, Rules for UserNames and Passwords ofParallels Plesk Panel Users(see page 197)

Describes the symbol usage rules for creating user names andpasswords in Parallels Plesk Panel.

Chapter 19, Customizing

Statistics Calculation (seepage 198)

Describes how you can vary which statistics data to count

instead of collecting the whole statistics, thus making the taskwork faster.

Chapter 20, Switching PHPHandler Type to FastCGI(see page 203)

Describes how to switch the PHP handler type in IIS to FastCGIfor better performance.



Although Parallels Plesk Panel's GUI affords the administrators complete control of theroutine server hosting configuration needs, the hosting management capabilitiesprovided by Parallels Plesk Panel are not limited to Parallels Plesk Panel functionalityavailable to users through its GUI. Parallels Plesk Panel administrators can use severaladditional tools that are supplied in the standard Parallels Plesk Panel distributionpackage to add customized automation tasks, optimize Parallels Plesk Panel serverperformance, and repair Parallels Plesk Panel components and system settings. Thetools include a number of standalone Windows applications, Parallels Plesk Panelpublic API, utility programs, and the ability to integrate custom scripting with ParallelsPlesk Panel. (To learn about additional Parallels Plesk Panel capabilities afforded bypublic API and creation utilities, Parallels Plesk Panel administrators are advised toconsult Parallels Plesk Panel SDK documentation.) The tools together with theParallels Plesk Panel's ability to manage various third-party components allowadministrators to customize their Parallels Plesk Panel installations in an unlimitednumber of ways. However, the more complex a system becomes, the more potential isthere for incongruities and conflicts between its components. Parallels Plesk Panel GUIcannot possibly provide means to address all potential problems arising because ofthis. But that does not mean that the problems are not solvable. The Parallels PleskPanel tools provide effective means to diagnose and troubleshoot problems onParallels Plesk Panel servers.

The purpose of this guide is not to describe all possible uses of the tools, but ratherdescribe advanced tasks that administrators may need to perform whentroubleshooting problems on Parallels Plesk Panel servers running in a non-standardconfiguration.

C H A P T E R 1

Introduction



Parallels Plesk Panel advanced features should only be used when GUI-basedremedies have been attempted but have not achieved your objective. Before usingadvanced administration features, you should first diagnose the problem correctly. Youmay need to use Parallels Plesk Panel advanced features to correct the followingproblems:

A third-party component integration with Parallels Plesk Panel fails repeatedly afterinstallation or upgrade;

A new custom event handler needs to be created in Parallels Plesk Panel;

Parallels Plesk Panel server or one or more of its components or servicesmalfunction due to misconfigurations.

C H A P T E R 2

When to Use Parallels Plesk Panel

Advanced Features



Parallels Plesk Panel has a built-in mechanism for customizing security settings forWindows objects on the server disks. You can specify security rules and then haveParallels Plesk Panel automatically apply the rules to Windows object security settings.The security files are easily accessible, and once you understand the logic of their use,you will be able to customize security settings on any folder or file found on a ParallelsPlesk Panel server.

Incorrect security settings on Windows objects found on Parallels Plesk Panel serversmay result in a number of server problems including but not limited to unavailability ofsite application and services. We recommend that you become acquainted with thissection before attempting to modify security settings on folders and files found onParallels Plesk Panel server.

Parallels Plesk Panel creates different Windows user accounts to manage servers andto serve Internet requests by IIS. Parallels Plesk Panel has to assign the user accountsnecessary permissions to access and manage Windows objects on managed servers.When assigning user account permissions, Parallels Plesk Panel exercises twodifferent security policies towards Windows objects - Disk security and Hosting

security. Security settings for all Windows objects on a Parallels Plesk Panel server areinitially configured according to the policies during Parallels Plesk Panel installation.Server compliance with the policies ensures the maximum security of the ParallelsPlesk Panel server without compromising server performance. The Windows objectssecurity settings can be further customized. To manage object security settings,Parallels Plesk Panel has implemented a flexible system based on Parallels PleskPanel's own security metadata files and the DACL inheritance mechanismsimplemented in Windows. Security settings can be customized by using the ParallelsPlesk Panel security metadata files and Parallels Plesk Panel creation utilities that aredistributed with Parallels Plesk Panel.

Warning: Before making any changes to the security metadata, make a backup copyof the metadata file that you want to modify. For information why backing up securitymetadata files before modifying them is a good idea, see "Customizing Disk Security"(on page 27) and "Customizing Hosting Security" (on page 29) sections.

In this chapter:

Parallels Plesk Panel Security Policies ............................................................... 15 Windows Accounts Used by Parallels Plesk Panel to Manage Windows Objects 15 Windows Accounts Used by Parallels Plesk Panel to Manage Hosted WindowsObjects ................................................................................................................ 18 Administering Windows Objects Security on Parallels Plesk Panel Server ........ 20

C H A P T E R 3

Administering Security Settings on

Windows Objects



Administering Security Set tings on Windows Objects 15

Parallels Plesk Panel Security Policies

Parallels Plesk Panel exercises two different security policies towards Windows objects: disksecurity and hosting security. The difference between the policies is dictated by the differentsecurity requirements for hosted content as opposed to the rest of the server disks. Bothpolicies are defined by security rules specified in corresponding Parallels Plesk Panelsecurity metadata files. The disk security policy is defined by the disk security metadata fileand is applied to all Parallels Plesk Panel server disks except for the contents of the%pl esk_vhost s%directory, where all hosted content is located. For more information aboutthe disk security metadata file, see "Disk Security Metadata File" (on page 24). All hostingdirectories are governed by security policies defined by corresponding hosting securitymetadata files. Hosting security metadata files are automatically generated from hostingsecurity metadata file templates. For more information about security metadata file

templates, see "Hosting Security Metadata File Templates" (on page 25).

Windows Accounts Used by Parallels PleskPanel to Manage Windows Objects

The following table describes Windows user accounts and groups used by Parallels PleskPanel to manage Windows objects on server disks.

Account Descript ion

psaadm Used by Parallels Plesk Panel to log on to the system andaccess files and folders.

psacln All users created by Parallels Plesk Panel are members of thisgroup.

psaserv Some auxiliary Internet users are members of this group.

In this section:

Default User Permissions for Disks ..................................................................... 15

Default User Permissions for Disks

Path Account Default Permissions * Comment

Disk root Everyone Read & Execute for this

object onlypsaadm Deny Full Control



16 Administering Security Settings on Windows Objects

Path Account Default Permissions * Comment

psacln

Progr am

Fi l es

psacln Deny Full Control except

Read Attributes

Progr amFi l es\ Common Fi l es

psaadm Read & Execute

psacln

psaserv

NETWORKSERVICE

Document sandSet t i ngs

Windows defaultpermissions.

Default user permissions areleft intact because it isnecessary to allow users to logon to the system.

RECYCLER psaadm Deny Read & Executefor this object only

psacln

Wi ndows Windows defaultpermissions.

Default user permissions areleft intact because it isnecessary to allow users toaccess system components.

Wi ndows\ TEMP

psaadm Read & Execute forfolders; Read for files

psacln

psaserv

NETWORKSERVICE

%pl esk_di r % psaadm Read & Execute Permissions are not inheritedfrom parent

psacln Deny Full Control

psaserv

NETWORKSERVICE

%pl esk_bi n%

psaadm Read & Execute

psacln Read Attributes for this

object only; Read &Execute for files

%pl esk_vhost s%

psacln Deny Full Control exceptRead Attributes for thisobject only

psaadm Deny Full Control for thisobject only

psaserv

NETWORKSERVICE




* Actual permissions set on Windows objects may differ from the default permissions listed inthis table because some of them may result from a combination of several security rules. For

more information about security rules, see "Customizing Object Security Settings in ParallelsPlesk Panel" (on page 23).




Windows Accounts Used by Parallels Plesk

Panel to Manage Hosted Windows ObjectsParallels Plesk Panel administers the server on which it is installed by using a number ofWindows user accounts. The user accounts are used by Parallels Plesk Panel or remoteusers logging in to the Parallels Plesk Panel server. The following table lists severalWindows user accounts and groups that are used by Parallels Plesk Panel or remote usersspecifically to access and manage content hosted on domains, subdomains, and Web useraccounts. The default permissions on a domain's \ ht t pdocs folder for each account arealso described.

Account Descript ion Default Permissions for\httpdocs folder

ftp_subaccounts A Windows user group. Additional ftpuser accounts created on domains orsubdomains are assigned membershipin this user group.

Deny Delete for this object.

<Domain FTPuser>

A Windows user account. It is createdfor domain content managementpurposes at the time of domaincreation. For each domain, a separateDomain FTP user account is created.Remote users can access domain

content by logging in to the server byusing the domain FTP user credentials.The account is also used by ParallelsPlesk Panel to manage hosted domaincontent.

FileNonRemovable (on page40) for this object and FullControl for subfolders andfiles.

<IIS user> A Windows user account. It is used forserving incoming HTTP requests. Theaccount is automatically created duringdomain creation. For each domain aseparate account is created. Forsecurity reasons, the user accountshould not be granted full accessrights.

Read for files, Read &Execute for folders.

<Parent domainFTP user>

A Windows user account. It is createdduring domain creation for managingcontent hosted on subdomains or Webuser folders that belong to the domain.The account is used by Parallels PleskPanel when the subdomain's or Webuser's content is managed by ParallelsPlesk Panel users who are logged in toParallels Plesk Panel as domainowners. Note that a separate domainFTP user account can be enabled for asubdomain to manage its content.

FileNonRemovable (on page40) for this object and FullControl for subfolders andfiles.




Account Descript ion Default Permissions for\httpdocs folder

<Parent domain IISuser>

A Windows user account. It is createdduring domain creation for servingHTTP requests for subdomains andsubdomain Web users. The account isused when the content is requested aspart of the domain hosting structure.

Read for files, Read &

Execute for folders.

<IIS ApplicationPool user>

A Windows user account createdspecifically to use IIS Application Pool.The use of separate user accountscorresponding to dedicated IIS Application Pools ensures themaximum degree of domain isolation.For each domain a separate accountcan be created. For security reasons,

the user account should not be grantedfull access rights.

Read for files, Read &Execute for folders.




Administering Windows Objects Security on

Parallels Plesk Panel ServerThe initial security configuration of all disks on a Parallels Plesk Panel server is performedduring Parallels Plesk Panel installation. Parallels Plesk Panel applies its own securitysettings to all existing Windows objects on the server according to the disk and hostingsecurity policies.

Once security has been configured, you have several options to manage security settings forWindows objects. We recommend that you use Parallels Plesk Panel security metadata filesto set and edit security settings for Windows objects on Parallels Plesk Panel servers. Thechanges made in the files can be then applied to Windows objects by running the

Appl ySecur i t y. exe and Host i ngSecur i t y. exe command line utilities.

You can also modify the security settings for each object individually either through ParallelsPlesk Panel GUI or directly by going to Security tab in the object's Properties. However, neitherof these options is recommended. The main reason is that the changes made in the securitysettings by using these options may be overwritten by security settings applied byAppl ySecur i t y. exe, Host i ngSecur i t y. exe, or Reconf i gur at or . exe command lineutilities .

The following advantages are afforded by using the security metadata files to configuresecurity settings for Windows objects:

The ability to apply security rules to multiple objects at once. Easy track of security settings changes.

Easy portability of customized security settings between domains and servers.

In this section:

Initial Windows Security Configuration During Parallels Plesk Panel Installation orHosting Account Creation .................................................................................... 21 Browsing Object Security Settings Through Parallels Plesk Panel GUI .............. 22

Customizing Object Security Settings in Parallels Plesk Panel ........................... 23 General Security Metadata Structure .................................................................. 38




Initial Windows Security Configuration During ParallelsPlesk Panel Installation or Hosting Account Creation

The initial security configuration of Windows objects is performed automatically by ParallelsPlesk Panel during Parallels Plesk Panel installation. Parallels Plesk Panel creates a numberof default accounts and sets user permissions on all Windows objects found on the freshlyinstalled Parallels Plesk Panel server. All pre-existing security settings are erased and newsecurity settings are applied according to the security rules found in the default disk securitymetadata file (on page 24).

Subsequently, each time a new hosting account is created, the created default hostedobjects are assigned user account permissions based on the security rules found in thecorresponding hosting security metadata file (on page 26) instantiated from a current hostingsecurity metadata file template (on page 25).

If a folder or a file is created, for which no security rule is set in the security metadata, theobject will automatically inherit security settings of their respective parent containers.




Browsing Object Security Settings Through Parallels PleskPanel GUI

Parallels Plesk Panel provides GUI access to the current security settings of Windowsobjects that it manages. You can browse and modify hosted objects security settings throughParallels Plesk Panel GUI. User account permissions on hosted objects can be viewed andedited by any Parallels Plesk Panel user authorized to access hosted objects throughParallels Plesk Panel.

Note: Security settings for some critical folders on hosting accounts are not allowed to bechanged through Parallels Plesk Panel GUI to prevent potential security problems or Website malfunction that may be caused by inadvertant user interference with the securitysettings.

For example, to browse the user permissions for the / ht t pdocs directory on domainexampl e. com, follow these steps:

1. Log in to Parallels Plesk Panel as the client who owns domain exampl e. com.

2. Click the Domains link under General in the Navigation pane. The list of domains on theclient account is displayed.

3. Click the exampl e. comentry in the domain list. The domain management windowopens.

4. Click File Manager under Hosting. The list of files and directories located in the domain root

directory is displayed.5. Click on the Lock icon corresponding to the / ht t pdocs directory. The list of Windows

user accounts is displayed on the left under Group or user names. By default, the upperentry in the user account list is highlighted. On the right, the access permissions for thehighlighted user account are displayed.

6. Click on the user account or user group name in the list to view the assignedpermissions.

Note: To view the advanced security settings, click Advanced .




Figure 1: Browsing User Account Access Permissions for Windows Objects Managed byParallels Plesk Panel

Customizing Object Security Settings in Parallels PleskPanel

The preferred way to customize Windows object security settings is by adding new ormodifying existing Ent r y elements in a disk security metadata file (for disk security) or in ahosting security metadata file instance corresponding to the hosting account that isauthorized to access and manage the hosted objects (for hosting security). To learn whyother customization options are not recommended, see "Administering Object Security onParallels Plesk Panel Server" (on page 20). For detailed description of the Ent r y elementcontents, see "General Security Metadata Structure" (on page 38). For step-by-stepinstructions on modifying the disk security metadata file, see "Customizing Disk Security" (onpage 27). For step-by-step instructions on modifying the hosting security metadata files, see"Customizing Hosting Security" (on page 29).

Warning: Before making any changes to the security metadata, make a backup copy of themetadata file that you want to modify. For information why backing up security metadata filesbefore modifying them is a good idea, see "Customizing Disk Security" (on page 27) and"Customizing Hosting Security" (on page 29) sections.

In this section:

Security Metadata Files and Templates .............................................................. 24 Customizing Disk Security ................................................................................... 27 Customizing Hosting Security ............................................................................. 29




Secur ity Metadata Files and Templates

Parallels Plesk Panel security rules for managed objects on hosted domains, subdomains,

and web user folders are stored in security metadata files. Because Parallels Plesk Panelhas two different security policies applied to Windows objects, it uses two different types ofsecurity metadata files: disk security metadata file (on page 24) and hosting securitymetadata files (on page 26).

The disk security metadata file defines security rules for Windows objects on Parallels PleskPanel server disks except for the contents of the %pl esk_vhost s%directory, whichcontains hosted content for Parallels Plesk Panel hosting accounts and is governed by adifferent security policy.

Security rules for Windows objects in the %pl esk_vhost s%directory are defined by hostingsecurity metadata files. Separate instances of hosting security metadata files are

automatically created for each hosting account (domain, subdomain, or Web user) from thecorresponding template files during hosting account creation in Parallels Plesk Panel.

You can manually modify security rules by editing corresponding security metadata files ortemplates. For detailed information about modifying Parallels Plesk Panel security rules, see"Customizing Disk Security" (on page 27) and "Customizing Hosting Security" (on page 29)sections.

In this section:

Disk Security Metadata File ................................................................................. 24

Hosting Security Metadata File Templates .......................................................... 25 Hosting Security Metadata Files .......................................................................... 26

Disk Security Metadata File

The disk security metadata file is named Di skSecur i t y. xml . The file defines security rulesfor all disks on a Parallels Plesk Panel server except for the %pl esk_vhost s%folder wherehosted domain folders are located. The file is located in the%pl esk_di r %\ et c\ Di skSecur i t y directory, where %pl esk_di r %is the Windowsenvironment variable designating the Parallels Plesk Panel installation directory.

Warning: Exercise caution when changing disk security rules by editing theDi skSecur i t y. xml file. Follow recommendations in the "Customizing Disk Security" (onpage 27) section to avoid potential problems in administering disk security policy in ParallelsPlesk Panel.




Hosting Security Metadata File Templates

Parallels Plesk Panel hosting security metadata template files are XML files that contain

default security rules to be included in separate instances of security metadata files (on page26) for each Parallels Plesk Panel hosting account. Separate security template files exist forthe following types of Parallels Plesk Panel hosting accounts - domains, subdomains, andWeb users. When a new hosting account is created, the security metadata file templatecorresponding to the account's type is used to create a separate instance of a securitymetadata file for the account. At the time of account creation, the metadata file contains thedefault security configuration for all hosted objects manageable by the account. The file isstored in the root folder of the file system segment that the account is authorized to accessand manage. For example, the security metadata file for domain exampl e. comwill belocated in the %pl esk_vhost s%/ exampl e. comdirectory.

The following Parallels Plesk Panel security settings template files are used to createsecurity metadata files when instantiating new hosting accounts:

%pl esk_di r %\ et c\ host i ng_t empl ate. xml (for domain administrator accounts)

%pl esk_di r %\ et c\ subdomai n_t empl at e. xml (subdomain user accounts)

%pl esk_di r %\ etc\ webuser _t empl ate. xml (web user accounts)

Note: Other hosting security metadata template files, for examplehost i ng_wr i t e_t empl ate. xml , are also located in the directory and can be used tocreate or modify instances of hosting security metadata files. The additional templates are

used when corresponding options are selected in the Parallels Plesk Panel GUI. You canalso define your own templates and use them to apply security rules by using theHost i ngSecur i t y. exe utility.




Hosting Security Metadata Files

Separate instances of security metadata files exist for all hosting accounts created in

Parallels Plesk Panel - domain, subdomain, and Web user hosting accounts. The files arelocated in the root folders of corresponding hosting accounts and contain security rules for allobjects manageable by the authorized hosting account.

The following security metadata files are used by Parallels Plesk Panel to administer securityof hosted content for different Parallels Plesk Panel hosting accounts:

%pl esk_vhost s%\ <domai n r oot path>\ . secur i t y (domains)

%pl esk_vhost s%\ <subdomai n r oot path>\ . secur i t y (subdomains)

%pl esk_vhost s%\ <domai n r oot path>\ . Web. <Web user name>. secur i t y (Web users)

Warning: Exercise caution when changing hosting security rules by editing securitymetadata files. Follow recommendations in the "Customizing Hosting Security" (on page 29)section to avoid potential problems in administering hosting security policy in Parallels PleskPanel.




Customizing Disk Security

Custom changes to disk security metadata should not be applied to the

Di skSecur i t y. xml file itself. The disk security metadata can be contained in multiple files. All disk security metadata do not have to be contained only in the Di skSecur i t y. xml file.You can create any number of additional disk security metadata files. To customize disksecurity, you should create an additional file with the xml extension in the%pl esk_di r %\ et c\ Di skSecur i t y directory and specify additional security rules in thefile. This will enable you to track changes and manipulate sets of security metadata easily.

To customize disk security rules in Parallels Plesk Panel, follow these steps:

1. Log in to a Parallels Plesk Panel-managed Windows-based server as administrator.

2. Determine what Windows objects you would like to set new security rules for.

3. Open the %pl esk_di r %\ et c\ Di skSecur i t y folder.4. In the folder, create a new file with the xml extension.

You can name this file anything you want.

5. Open and edit the file by using your favorite XML file editor to create security rule entries.

Disk security rule entries have the same format as hosting security rule entries. For helpin completing this step, see "Adding New Security Rule to Hosting Security Metadata FileTemplate" (on page 30). See also an explanatory example of a security rule entryfollowing this procedure. For entry attribute descriptions and possible values, see"General Security Metadata Structure" (on page 38).

6. Save and close the file.

Once you have made necessary modifications to the security metadata file, run theAppl ySecur i t y. exe utility to apply the security rules to Windows objects. For informationabout using the Appl ySecur i t y. exe utility, consult Parallels Plesk Panel for Windows

Creation Utilities Administrator's Guide.

This is an example of a security rule that sets access rights to the disk root folder for theParallels Plesk Panel administrator account.

Example:

<Ent r y AccounType="1" Account ="Psaadm" Pat h="/ "AceFl ags="Thi sFol der Subf ol dersAndFi l es" AccessMask="Ful l Access"Entr yFl ags="0x9" / >

Explanation:




Because name Psaadmis not a standard Windows system account, it has to be resolved inthe system (hence, AccounType="1" ). Pat h="/ " specifies that the security rule will beapplied to the disk root folder. AceFl ags="Thi sFol der Subf ol der sAndFi l es" specifiesthat, according to this rule, an ACE with permission defined by

AccessMask="Ful l Access" will be created for the disk root folder and all of its subfoldersand files. Ent r yFl ags="0x9" (derived by combining 0x1 and 0x8 entry flags) set the ACE's type to Deny and enables Parallels Plesk Panel to proceed with applying othersecurity rules to other objects even if an error occurs while applying the security rule definedby this rule.




Customizing Hosting Security

Custom changes in hosting security rules can be made both at the level of the security

metadata template files and at the level of the security metadata file instances on individualhosting accounts. However, direct modification of security metadata file instances is notrecommended. The preferred way of customizing hosting security is through creation ofadditional security metadata template files.

Note: If you do decide to modify a security metadata file instance directly, be sure to make abackup copy of the file before modifying it.

Once a template file with additional security rules is created, the security rules can be addedinto or removed from hosting security metadata files by using the Host i ngSecur i t y. exe utility. For information about using the Host i ngSecur i t y. exe utility to modify securityrules in security metadata files, consult Parallels Plesk Panel for Windows Creation Utilities

Administrator's Guide.

To customize hosting security rules for Windows objects in Parallels Plesk Panel, followthese steps:

1. Log in to a Parallels Plesk Panel-managed Windows-based server as administrator.

2. Determine what Windows objects you would like to set new security rules for.

3. Create a new hosting security metadata template file or open an existing one by usingyour favorite XML file editor.

For information about locating the appropriate template file, see "Hosting SecurityMetadata File Templates" (on page 25).

4. Add or modify security rule entries in the file as needed.

For help in completing this step, see the "Adding New Security Rule to Security MetadataFile Template" (on page 30) section. For entry attribute descriptions and possible values,see "General Security Metadata Structure" (on page 38). For entry examples withexplanations, see "Common Security Rule Entry Examples" (on page 32).

5. Save and close the file.

6. Apply the changes to hosting accounts that you want to change object security rules forby running the Host i ngSecur i t y. exe utility.

In this section:

Adding New Security Rule to Hosting Security Metadata File Template ............. 30 Common Security Rule Examples ....................................................................... 32




Adding New Security Rule to Hosting Security Metadata File Template

A security rule is an access permission for a Windows user account or group that will be

added to a Windows object once the rule is applied to it. A single rule may be applied tomore than one object depending on the attribute values specified. To add a new securityrule, you need to create a new Ent r y element in a security metadata file template andinclude in it the necessary information by using the available declaration options for theelement's attributes. For detailed description of the attributes and information about valuesthat can be assigned to the attributes, see "General Security Metadata Structure" (on page38).

To add a new security rule, follow these steps:

1. Identify the Windows object that you want to create a new security rule for.

The example used here assumes that you want to add a new security rule for theerror_docs folder located in the domain root folder directory.

2. Identify the Windows object to which the rule is to apply by specifying the Pat h and, ifapplicable, the SubPat h attribute in the new Ent r y element.

Consult "General Security Metadata Structure" (on page 38) for applicable declarationoptions.

For example,

<Ent r y AccounType="" Account ="" Pat h=" [HTTPD_VHOSTS_D]"SubPat h="error_docs" AceFl ags="" AccessMask="" Ent r yFl ags="" Tag=""

Tag2="" / >

3. Specify the Windows user account that you want to assign the security rule for.For example, to specify a domain FTP user account, make the following declarations:

<Ent r y AccounType="0" Account ="Null" Pat h="" SubPat h="" AceFl ags=""AccessMask="" Ent r yFl ags="" Tag="DomainUser " Tag2="" / >

Note: The name Nul l will be replaced by an actual domain FTP user account name inmetadata security files instantiated from the the template file. You can also include aSi dSt r attribute if a SID for a particular Windows account is known. For moreinformation about the Si dSt r attribute, see "General Security Metadata Structure" (onpage 38).

4. Define the type of the rule (Al l ow or Deny, just like you would for an ACE) and how therule is to be propagated to child objects by specifying the Ent r yFl ags element.

For help in completing this step, see "Possible EntryFlags Attribute Values" (on page 40).For example, to enable application of the security rule only to files contained in thespecified error_docs folder, but not to the folder itself you need to use the 0x80 flag.The rule is set to the Al l ow type by default (the 0x0 flag) unless the 0x1 flag (Deny) isincluded.

<Ent r y AccounType="" Account="" Path="" SubPat h="er r or _docs\ *.*"AceFl ags="" AccessMask="" Ent r yFl ags="0x80" Tag="" Tag2="" / >

Note: When you use the 0x80 flag, a file mask must be included in the Pat h or SubPat h

attribute, whichever is applicable. In this example the *.* mask must be used. You canuse other entry flags to further fine-tune the application of the rule to Windows objects.




5. Set the permissions for the user account on Windows objects to which the rule is going toapply by specifying the AccessMask attribute. For help in completing this step, see"Possible AccessMask Attribute Values" (on page 40).

For example, to grant the Read and Write permissions for the Windows user account,

specify ReadWr i t e:<Ent r y AccounType="" Account="" Path="" SubPat h="" AceFl ags=""AccessMask="ReadWrite" Ent r yFl ags="" Tag="" Tag2="" / >

6. Define if ACEs must be created for the Windows object and its child objects based on thissecurity rule by specifying the AceFl ags attribute. For help in completing this step, see"Possible AceFlags Attribute Values" (on page 39). For example, to create ACEs only forthe error_docs folder and all files contained within that folder useAceFl ags="Fi l esOnl y" .

This is the resulting security rule entry:<Ent r y AccounType="0" Account="Nul l " Pat h="[ HTTPD_VHOSTS_D] "SubPat h="err or_docs\ *. *" AceFl ags="Fi l esOnl y" AccessMask="ReadWr i t e"Ent r yFl ags="0x80" Tag="Domai nUser " Tag2="" / >

Rule Description

Because the name Nul l is a standard system account name, it does not have to be resolvedin the system (hence, AccounType="0" ).(The name Nul l will be replaced by an actualdomain FTP user account name in metadata security files instantiated from the the templatefile). The optional Domai n and Si dSt r attributes do not need to be defined for the samereason. The HTTPD_VHOSTS_D component path in the Pat h attribute specifies the path to

the domain root folder where the error_docs folder is located. The SubPat h attribute setsthe mask for all files in the error_docs folder to which the rule will be applied.AceFl ags="Fi l esOnl y" specifies that, according to this rule, an ACE with permissiondefined by AccessMask="ReadWr i t e" will be created only for the error_docs folder andall files contained within that folder. However, Ent r yFl ags="0x80" further restricts the ACE creation only to the files within the folder, excluding the error_docs folder from thisrule. Tag="Domai nUser " designates the security rule as pertaining to a Parallels PleskPanel domain hosting account and is used by Parallels Plesk Panel to properly organize theprocessing of security metadata.

Note: When entry flag 0x80 is included in a security rule entry, the path to the objects

defined by the Pat h and SubPat h attributes must include a file mask. This example uses filemask *. * .




Common Security Rule Examples

This section describes several security rule entry examples commonly found in security

metadata files and templates.

In this section:

Example of Security Rule Entry in Security Metadata File .................................. 32 Setting File Access Rights Different From Parent Container's ............................ 33 Prohibiting Container Deletion When Deletion of its Parent Container Contents IsDisabled .............................................................................................................. 34 Prohibiting Container Deletion When Deletion of its Parent Container Contents Is Allowed................................................................................................................ 36

Example of Securi ty Rule Entry in Security Metadata File

The following security rule sets access rights to objects that belong to domain exampl e. comfor the Windows user account named domai nuser 1.

Security rule entry

<Ent r y AccounType="1" Account ="domai nuser 1" Si dSt r ="S- 1- 5- 21- 821798554-1223697094- 3523996037- 1043" Pat h="[ HTTPD_VHOSTS_D] " SubPat h="exampl e. com"AceFl ags="Fi l esOnl y" AccessMask="Read" Ent r yFl ags="0x140" Tag="Domai nUser " Tag2="" / >

Explanation

Because the name domai nuser 1 is not a standard system account name, it has to beresolved in the system (hence, AccounType="1" ). The optional Si dSt r attribute is definedto improve Parallels Plesk Panel stability. The HTTPD_VHOSTS_D component path in thePat h attribute specifies the common part of the path to the domain root folder where theexampl e. comfolder is located. The SubPat h attribute sets the specific domain root folderto which the rule will be applied. AceFl ags="Fi l esOnl y" specifies that, according to thisrule, an ACE with permission defined by AccessMask="Read" will be created and addedonly to the exampl e. comfolder and all files contained within that folder.Ent r yFl ags="0x140" enables (i) creation of the domain root folder (which is necessaryduring domain creation) and (ii) strict enforcement of the access permissions defined by theAccessMask="Read" permission mask. Tag="Domai nUser " designates the security ruleas pertaining to a Parallels Plesk Panel domain hosting account and is used by ParallelsPlesk Panel to properly organize the processing of security metadata.




Setting File Access Rights Dif ferent From Parent Container's

The following rule sets access rights to files in the error_docs folder on domain

exampl e. comfor the Windows user account named domai nuser 1.

Security rule entry

<Ent r y AccounType="1" Account ="domai nuser 1" Si dSt r ="S- 1- 5- 21- 821798554-1223697094- 3523996037- 1043" Pat h="[ HTTPD_VHOSTS_D] "SubPat h="exampl e. com\ err or_docs\ *. *" AceFl ags="Fi l esOnl y"AccessMask="ReadWr i t e" Ent r yFl ags="0x80" Tag="Domai nUser " Tag2="" / >

Note: When entry flag 0x80 is included in a security rule entry, the path to the objectsdefined by the SubPat h attribute must include a file mask. This example uses file mask *. * .

Explanation

Because the name domai nuser 1 is not a standard system account name, it has to beresolved in the system (hence, AccounType="1" ). The optional Si dSt r attribute is definedto improve Parallels Plesk Panel stability. The HTTPD_VHOSTS_D component path in thePat h attribute specifies the common part of the path to the domain root folder where theexampl e. comfolder is located. The SubPat h attribute completes the path to theerror_docs folder to which the rule will be applied. AceFl ags="Fi l esOnl y" specifiesthat, according to this rule, an ACE with permission defined by AccessMask="ReadWr i t e" will be created and added only to the error_docs folder and all files contained within thatfolder. However, Ent r yFl ags="0x80" further restricts the ACE creation only to the fileswithin the folder, excluding the error_docs folder from this rule. Tag="Domai nUser " designates the security rule as pertaining to a Parallels Plesk Panel domain hosting accountand is used by Parallels Plesk Panel to properly organize the processing of securitymetadata.






Because the name domai nuser 1 is not a standard system account name, it has to beresolved in the system (hence, AccounType="1" ). The optional Si dSt r attribute is defined toimprove Parallels Plesk Panel stability. The HTTPD_VHOSTS_D component path in the Pat h attribute specifies the common part of the path to the domain root folder where the

exampl e. comfolder is located. The SubPat h attribute completes the path to the ht t pdocs folder to which the rule will be applied. AceFl ags="Subf ol dersAndFi l esOnl y" specifiesthat, according to this rule, an ACE with permission defined by AccessMask="Ful l Access" will be created and added to the ht t pdocs folder and all of its subfolders and files on domainexampl e. com. Ent r yFl ags="0x140" enables (i) creation of the folder (which is necessaryduring domain creation) and (ii) strict enforcement of the access permissions defined by theAccessMask="Ful l Access" permission mask. Tag="Domai nUser " designates the securityrule as pertaining to a Parallels Plesk Panel domain hosting account and is used by ParallelsPlesk Panel to properly organize the processing of security metadata.




Prohibi ting Container Deletion When Deletion of its Parent Container Contents Is Al lowed

The following two security rules set different sets of access rights for a parent object (in thisexample, the pi cture_ l i brary folder on domain exampl e. com) and its child objects -subfolders and files contained in the folder. The resulting security configuration will prohibitdeletion of the parent container by a domain user but will allow the user full control for filesand folders contained in the pi cture_ l i brary folder.

Security rule entry 1

The following rule sets access rights to files in the ht t pdocs\ pi ctur e_l i br ar y folder ondomain exampl e. comfor the Windows user account named domai nuser 1, prohibitingdeletion of the folder.

<Ent r y AccounType="1" Account ="domai nuser 1" Si dSt r ="S- 1- 5- 21- 821798554-1223697094- 3523996037- 1043" Pat h="[ HTTPD_VHOSTS_D] "SubPat h="exampl e. com\ ht t pdocs\ pi ct ur e_l i br ar y" AceFl ags="Thi sObj ect Onl y"AccessMask="Fi l eRemovabl e" Ent r yFl ags="0x141" Tag="Domai nUser " Tag2="" / >

Explanation

Because the name domai nuser 1 is not a standard system account name, it has to beresolved in the system (hence, AccounType="1" ). The optional Si dSt r attribute is defined toimprove Parallels Plesk Panel stability. The HTTPD_VHOSTS_D component path in the Pat h attribute specifies the common part of the path to the domain root folder where theexampl e. comfolder is located. The SubPat h attribute completes the path to the

ht t pdocs\ pi ctur e_l i br ar y folder to which the rule will be applied.AceFl ags="Thi sObj ectOnl y" specifies that, according to this rule, an ACE with permissiondefined by AccessMask="Fi l eRemovabl e" will be created and added only to theht t pdocs\ pi ctur e_l i br ar y folder on domain exampl e. com. Ent r yFl ags="0x141" enables (i) creation of the folder (which is necessary during domain creation), (ii) strictenforcement of the access permissions defined by the AccessMask="Fi l eRemovabl e" permission mask, and (iii) sets the ACE type to Deny Access. Tag="Domai nUser " designates the security rule as pertaining to a Parallels Plesk Panel domain hosting accountand is used by Parallels Plesk Panel to properly organize the processing of securitymetadata.

Security rule entry 2

The rule sets full control rights to the ht t pdocs\ pi ctur e_l i br ar y folder, its subfolders andfiles on domain exampl e. comfor the Windows user account named domai nuser 1.

<Ent r y AccounType="1" Account ="domai nuser 1" Si dSt r ="S- 1- 5- 21- 821798554-1223697094- 3523996037- 1043" Pat h="[ HTTPD_VHOSTS_D] "SubPat h="exampl e. com\ ht t pdocs\ pi ct ur e_l i br ar y"AceFl ags="Thi sFol der Subf ol dersAndFi l es" AccessMask="Ful l Access"Ent r yFl ags="0x140" Tag="Domai nUser " Tag2="" / >




Explanation

Because the name domai nuser 1 is not a standard system account name, it has to beresolved in the system (hence, AccounType="1" ). The optional Si dSt r attribute is defined to

improve Parallels Plesk Panel stability. The HTTPD_VHOSTS_D component path in the Pat h attribute specifies the common part of the path to the domain root folder where theexampl e. comfolder is located. The SubPat h attribute completes the path to theht t pdocs\ pi ctur e_l i br ar y folder to which the rule will be applied.AceFl ags="Thi sFol der Subf ol dersAndFi l es" specifies that, according to this rule, an ACEwith permission defined by AccessMask="Ful l Access" will be created and added to theht t pdocs\ pi ctur e_l i br ar y folder and all of its subfolders and files on domainexampl e. com. Ent r yFl ags="0x140" enables (i) creation of the folder (which is necessaryduring domain creation) and (ii) strict enforcement of the access permissions defined by theAccessMask="Ful l Access" permission mask. Tag="Domai nUser " designates the securityrule as pertaining to a Parallels Plesk Panel domain hosting account and is used by Parallels

Plesk Panel to properly organize the processing of security metadata.




General Security Metadata Structure

A security metadata template or file contains security rule entries for Windows objects. Each

such entry consist of a single Ent r y element that has multiple attributes specifying a securityrule and the identity of one or more Windows objects to which the rule applies. In addition,each Ent r y element declares entry flags specifying how existing DACL security settingsassociated with Windows objects and Parallels Plesk Panel security rules are combined andinherited by Windows objects. The element can also have optional tags that are used byParallels Plesk Panel to organize processing of security metadata.

Parallels Plesk Panel follows Windows security processing rules when translating thesecurity rule entries stored in the metadata files into ACEs.

The following security rule entry definition format is adopted for the files:

<Entry AccounType="" Account="" Path="" AceFlags="" AccessMask="" EntryFlags=""Tag="" Tag2="" />

When applying security rules listed in the metadata files to Windows objects, Parallels PleskPanel can write new, modify old, or erase existing ACEs in object DACLs, depending onwhat entry tags are specified by the corresponding Ent r y element.

The following table describes the attributes that are used in the Ent r y element and providesmappings to DACL's ACEs components where applicable.

At tr ibutes and Their Mapping to ACE Components

Attr ibute ACE component Requi red Comment

Account Name (the userpart)

Yes Symbolic Windows user account name forwhich the security rule is created.

Domai n Name (thedomain part)

No Symbolic Windows domain name to which theWindows user account belongs.

Si dSt r Name's SID No Windows user account SID corresponding tothe Windows user account name specified bythe Account attribute.

AceFl ags Apply to flags Yes ACE control flag symbolic name or actual flagbits setting ACE inheritance rules that areapplied to ACEs in object DACLs. See also"Possible AceFlags Attribute Values" (on page39).

AccessMask Permission Yes Access mask that defines specific permissionsfor ACEs created from the security rule. Seealso "Possible AccessMask Attribute Values"(on page 40).




Attr ibu te ACE component Requi red Comment

Ent r yFl ags Type Yes ACE type and other flags that define rules forcombining DACL security settings with the

security rule defined by the Entry element.Several flags can be combined together. Seealso "Possible EntryFlags Attribute Values" (onpage 40).

AccounType none Yes Windows user account type. This attributespecifies if the account has a well-known SID(Account Type=0) or must be resolved in thesystem (Account Type=1) by using thesymbolic name specified by the Account attribute.

Pat h none Yes A Parallels Plesk Panel component path orenvironment variable that sets a standard path

for standard hosted objects. The list ofParallels Plesk Panel component paths isinvoked by the packagemng. exe utility. Seealso "Possible Path Attribute Values". Forinformation about the packagemng. exe utility,consult Parallels Plesk Panel for WindowsCreation Utilities Administrator's Guide.

SubPat h none No Remaining part of the object path if the path isnot fully defined by the Pat h attribute.

Tag none Yes The Tag attributes are used by Parallels PleskPanel for processing the security rules defined

in a security metadata template file. The tagattributes are required for security metadatatemplates, but are optional for the securitymetadata file . Secur i t y. See also "PossibleTag Attribute Values" (on page 41).

Tag2 none No

In this section:

Possible AceFlags Values ................................................................................... 39 Possible AccessMask Values .............................................................................. 40

Possible EntryFlag Attribute Values .................................................................... 40 Possible Path Attribute Values ............................................................................ 41 Possible Tag Attribute Values ............................................................................. 41

Possible AceFlags Values

AceFlags Valu e Descript ion

Thi sObj ect Onl y The ACE created based on this rule will be assigned to this objectonly.

Thi sFol derAndFil es

The ACE created based on this rule will be assigned to this folderand files contained in the folder.




AceFlags Valu e Descript ion

Fi l esOnl y The ACE created based on this rule will be assigned only to files inthe specified folder and the folder itself.

Thi sFol derAndSubf ol der s

The ACE created based on this rule will be assigned to thespecified folder and its subfolders only.

Thi sFol derSubf ol der sAndFi l es

The ACE created based on this rule will be assigned to thespecified folder and its subfolders and files only.

Subf ol der sAndFil esOnl y

The ACE created based on this rule will be assigned only tosubfolders and files of the specified folder.

Possible AccessMask Values

AccessMask Value Corresponding Permissions

NoAccess None

Read Generic read

ReadAndExecut e Generic execute

ReadAndDel et e Generic delete

ReadWr i t e Generic write

Modi f y Generic write, execute, and delete

Ful l Access Full control

Fi l eRemovabl e Write extended attributes, delete and write to DACL, write owner ,delete subfolders and files.

Fi l eNonRemovabl e Full control excluding write attributes for files, write extendedattributes for files, delete and write to DACL, write owner , anddelete subfolders and files.

Ft pSubaccount sNonRemovabl e

Write extended attributes, add file, create directory, writeattributes, and delete subfolders and files.

Possible EntryFlag Attr ibute Values

Note: several flags can be combined together.

EntryFlags value Description

0x0 Allow access for the user account. This is the default value.

0x1 Deny access for the user account.

0x2 Applies the security rule to all parent containers in the object's path.




EntryFlags value Description

0x4 Breaks DACL inheritance from parent containers, erases existing ACEs, and creates new ACEs in the object's DACL based on thesecurity rules found in the security metadata files.

0x8 Enables Parallels Plesk Panel to proceed with applying othersecurity rules to other objects even if an error occurs while applyinga security rule carrying this flag.

0x10 Blocks propagation of the security rule to child objects of thespecified folder.

0x20 Instructs Parallels Plesk Panel to cancel applying any ParallelsPlesk Panel security rules to the specified folder.

0x40 Enables creation of absent folders.

0x80 Enables application of the security rule only to files contained in thespecified folder, but not to the folder itself. Supported starting withParallels Plesk Panel for Windows version 8.2. Requires that anobject path specified by the Pat h attribute includes a file mask.

0x100 Enables strict enforcing of access masks specified by the securityrule. If the flag is not included in the rule, extra access permissionsthat already exist are left intact. Supported starting with ParallelsPlesk Panel for Windows version 8.1.1.

Possible Path Attribute Values

Path value Description

/ Disk's root folder

* Any path

<number > A well-known path. Consult MSDN for Windows' well-knownpaths.

any st r i ng i sencl osed i n squarebr acket s

Parallels Plesk Panel component path

<pat h> The path to the Windows file or folder

Possible Tag Attr ibute Values

Tag Value Description

Ft pSubaccounts The tag is used for processing security rules forftp_subaccounts user group.

PsaAdmi n The tag is used for processing security rules for the psaadm user account.

psaServer The tag is used for processing security rules for the psaserv user group.




Tag Value Description

Domai nUser The tag is used for processing security rules for FTP useraccounts (domain FTP user, subdomain FTP user, or an FTPuser associated with a Web user account).

AnonymousDomai nUser The tag is used for processing security rules for anonymousInternet user accounts (IIS users).

Par ent User The tag is used for processing security rules for domain FTPuser accounts created to access subdomains or Web userfolders.

AnonymousPar entUser The tag is used for processing security rules for anonymousInternet user accounts (IIS users) created to access files onsubdomains or Web user folders.



To reduce the risk of compromising sensitive data hosted on your server, you mightwant to implement special security measures that comply with the Payment CardIndustry Data Security Standard (PCI DSS). The standard is intended to helporganizations protect customer account data. For detailed information about thestandard, refer tohttps://www.pcisecuritystandards.org/security_standards/pci_dss.shtml.

This chapter describes the steps that you should perform if you want to secure yourserver and achieve compliance with PCI DSS on a Microsoft Windows-based server.

To prohibit access to MySQL database server from external addresses,use the firewall that comes with your Parallels Plesk Panel for Windows:

1. Log in to the Panel as administrator.

2. Click the Settings link in the navigation pane.

3. Click Manage Firewall Rules.

4. Click Switch On.

To switch off weak SSL ciphers for Web server in Parallels Panel for

Microsoft Windows Server 2003 and 2008:

1. Copy the following text to the clipboard:

REGEDIT4[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0\Server]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0][HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers][HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\DES 56/56]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\NULL]"Enabled"=dword:00000000

C H A P T E R 4

Achieving Compliance with Payment

Card Industry Data Security Standard

https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml

https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml



44 Achieving Compliance with Payment Card Industry Data Security Standard

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 128/128]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 40/128]

"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC2 56/128]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128]"Enabled"=dword:00000000[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128]"Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes][HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\MD5]"Enabled"=dword:00000000

2. Log in to the server over a Remote Desktop connection.

3. When in the server's operating system, open Notepad or any other texteditor, and create a file with the r eg extension.

4. Paste the text from the clipboard into this file.

5. Save the file.

6. Double-click the file to open it.

7. When prompted, confirm addition of new keys to the registry.

8. Restart the operating system.

Note: Some applications on the server that use weak SSL ciphers and protocols maystop working.

To conceal the version of PHP installed on the server:

1. Open for editing the following files:

c: \ Pr ogr amFi l es\ Par al l el s\ Pl esk\ Addi t i onal \ Pl eskPHP5\ php. i ni .

c: \ wi ndows\ php. i ni .

c: \ I net pub\ vhost s\ webmai l \ hor de\ php. i ni .

2. Locate the lines expose_php = On.

3. Change On to Of f .

4. Save the files.

5. Restart the IIS Web server.



Parallels Plesk Panel administrators can assign handlers to certain events in ParallelsPlesk Panel and configure the event handlers to execute commands, for examplecustom scripts.

Parallels Plesk Panel administrators have the ability to monitor Parallels Plesk Paneluser actions by programming Parallels Plesk Panel to automatically executecommands in response to specific control panel events. A control panel event is asuccessfully completed operation performed on a Parallels Plesk Panel object. For thelist of Parallels Plesk Panel events that can trigger event handlers, see "Parallels PleskPanel Events" (on page 46).

To create an event handler and configure it to execute a command, for example acustom script, use Event Manager in Parallels Plesk Panel. For each event type,Parallels Plesk Panel can pass a set of environmental variables. You have the ability tospecify the specific environmental variables to be passed on to event handlercommands each time an event handler is activated. For more information on thespecific sets of environment variables passed on to event handler commands fordifferent event types, see "Event Parameters Passed by Event Handlers" (on page 54).

This section provides background information about and complete instructions oncreating and configuring Parallels Plesk Panel event handlers by Parallels Plesk Paneladministrators.

In this chapter:

Parallels Plesk Panel Events .............................................................................. 46 Creating Event Handlers ..................................................................................... 51 Removing Event Handlers .................................................................................. 51 Composing Event Handler Command ................................................................. 52 Script Writing Rules ............................................................................................. 88

C H A P T E R 5

Programming Event Handlers to Execute

Custom Scripts on Parallels Plesk PanelServer



46 Programming Event Handlers to Execute Custom Scripts on Parallels Plesk Panel Server

Parallels Plesk Panel Events

The following table describes the Parallels Plesk Panel events for which event handlerscan be created.

Event (action) name Description

admi n_update (on page 56) Administrator information updated

servi ce_st op ( on page 56) Service stopped

ser vi ce_st ar t ( on page 56) Service started

ser vi ce_r est ar t ( on page 56) Service restarted

dl _user _updat e (on page 57) Domain administrator account updated

i p_addr ess_cr eate ( on page 57) IP address created

i p_addr ess_update ( on page 57) IP address updated

i p_addr ess_del ete ( on page 57) IP address deleted

sessi on_pref erences_update (onpage 58)

Login settings updated

cl i ent _cr eat e ( on page 59) Client account created

cl i ent _update (on page 59) Client account updated

cl i ent _del et e ( on page 59) Client account deleted

cl i ent _st at us_updat e ( on page59)

Client account status updated

cl i ent _gui d ( on page 60) Client GUID updated

cl i ent _l i mi t s_updat e ( on page60)

Client limits updated

cl i ent _ l i mi t _tr af f i c_r eached( on page 61)

Traffic limit for client account reached

cl i ent _l i mi t _si ze_r eached ( onpage 62)

Disk space limit for client reached

cl i ent _per mi ssi ons_updat e ( on

page 62) Client permissions updated

cl i ent _pref er ences_updat e ( onpage 62)

Client interface preferences updated

cl i ent _i p_pool _updat e (on page63)

Client IP pool updated

cl i ent _si t eapp_added ( on page63)

Client application package added

cl i ent _s i t eapp_r emoved ( on page63)

Client application package removed

dashboar d_preset _cr eat e ( on

page 64) Desktop preset created







phys_host i ng_cr eat e ( on page73)

Physical hosting created

phys_host i ng_updat e ( on page73)

Physical hosting account updated, domainperformance or log rotation settingschanged

phys_host i ng_del ete ( on page73)

Physical hosting account deleted

f orwar di ng_cr eate ( on page 74) Standard or frame forwarding created

f orwardi ng_update ( on page 74) Standard or frame forwarding updated

f orwar di ng_del ete ( on page 74) Standard or frame forwarding deleted

webuser_cr eat e ( on page 75) Web user created

webuser _updat e ( on page 75)Web user properties updated

webuser_del et e ( on page 75) Web user account deleted

si t eapp_i nst al l ( on page 76) Site application installed

si t eapp_r econf i gur e ( on page76)

Site application reconfigured

si t eapp_uni nst al l ( on page 76) Site application uninstalled

si t eapppkg_i nst al l ( on page 77) Site application package installed

si t eapppkg_update (see page 77) Site application package updated

si t eapppkg_uni nst al l ( on page

77)

Site application package uninstalled

l i cense_updat e ( on page 77) License key updated

l i cense_expi r ed ( on page 77) Parallels Plesk Panel license has expired

database_server _cr eat e (on page78)

Connection to database server created

dat abase_ser ver_updat e ( on page78)

Connection to database server updated

database_server _del ete ( on page78)

Connection to database server deleted

dat abase_cr eat e ( on page 78) Database created

dat abase_del et e ( on page 78) Database deleted

database_user _cr eat e ( on page79)

Database user account created

dat abase_user _updat e ( on page79)

Database user account preferencesupdated

database_user _del ete ( on page79)

Database user account deleted

r emot e_dns_st atus_update ( onpage 79)

Remote DNS status updated

f t puser_cr eat e ( on page 80) FTP account createdf t puser _updat e (on page 80) FTP account updated





f t puser _del et e (on page 80) FTP account deleted

pl esk_component _upgrade (on page

81) Parallels Plesk Panel component upgraded

t empl at e_cl i ent _cr eat ed ( seepage 81)

Client template created

t empl at e_cl i ent _updated ( seepage 81)

Client template updated

t empl at e_cl i ent _del et ed ( seepage 81)

Client template removed

t empl ate_admi n_cr eat ed ( seepage 81)

Domain template created by administrator

t empl at e_admi n_updat ed ( see

page 81) Domain template updated by administrator

t empl ate_admi n_del eted ( seepage 81)

Domain template removed by administrator

t empl at e_domai n_cr eat ed ( seepage 82)

Domain template created by client

t empl at e_domai n_updat ed ( seepage 82)

Domain template updated by client

t empl ate_domai n_del eted (see page82)

Domain template removed by client

r esel l er _cr eat e ( see page 82) Reseller account created

r esel l er_ update ( see page 82) Reseller account updated

r esel l er _del et e ( see page 82) Reseller account deleted

r esel l er _st at us_updat e (seepage 83) Reseller account status updated

r esel l er _l i mi t _si ze_r eached( see page 83)

Disk space limit for reseller reached

resel l er_ l i mi t _tr af f i c_r eached( see page 84)

Traffic limit for reseller account reached

r esel l er _l i mi t s_updat e ( seepage 84)

Reseller limits updated

r esel l er _per mi ssi ons_updat e( see page 85)

Reseller permissions updated

r esel l er _pr ef er ences_updat e (seepage 86)

Reseller interface preferences updated

r esel l er_ gui d_update ( see page86) Reseller GUID updated

t empl at e_r esel l er _cr eat e ( seepage 87)

Reseller template created

t empl at e_r esel l er _updat e ( seepage 87)

Reseller template updated






Creating Event Handlers

This section describes the procedure for creating a new event handler in ParallelsPlesk Panel.

To add an event handler, follow these steps:

1. Click the Server shortcut in the navigation pane.

2. Click Event Manager under Control Panel.

3. Click Add New Event Handler . The event handler setup page appears:

4. Select the event you want to assign a handler to in the Event drop-down box.

5. Select a preset priority value for the execution of the handler, or specify a customvalue by using the Priority field.

When assigning several handlers to a single event you can specify the handlerexecution sequence, setting different priorities (higher value corresponds to ahigher priority).

6. Select the system user, on whose behalf the handler will be executed.

7. In the Command text box, type a command to be executed.

For exampl e, command

"c:\program files\parallels\plesk\scripts\test-handler.bat"<new_contact_name> <new_login_name>

will start script t est - handl er . bat located in the c: \ pr ogr amf i l es\ paral l el s\ pl esk\ scr i pts \ directory and pass thenew_cont act _name and new_l ogi n_name command line parameters on to thescript.

See "Composing Event Handler Command" for help in completing this step.

Note: Paths that contains spaces must be enclosed in quotes.

8. Click OK.

The list of current event handlers is displayed. The newly created event handlerappears in the list.

Removing Event Handlers

To remove one or more event handlers, follow these steps:


2. Click Event Manager under Control Panel.

3. Select one or more event handlers by using check boxes and click Remove selected.

The selected event handlers disappear from the list of available handlers.




Composing Event Handler Command

Each event handler must have a command assigned to it that will be executed uponthe event occurrence.To specify an event handler command you need to type in theCommand text box. A command must include a full path to an executable file or scriptfile. If one or more environment variables must be passed on to the script by ParallelsPlesk Panel, the variables names must be included in the command line, too.

This section describes the command syntax and relevant background on usingenvironment variables in event handler commands.

In this section:

Event Handler Command Syntax ........................................................................ 52 Environment Variables in Event Handler Commands ......................................... 52 Event Handler Command Example ..................................................................... 53 Event Parameters Passed by Event Handlers .................................................... 54

Event Handler Command Syntax

An event handler command has the following syntax:

<command> [<parameter 1> <parameter 2> ... <parameter N>]

The parameters in the command line shown in the angle brackets are environmentvariables that will be passed on to the command when it is executed. For moreinformation about using environment variables in event handler commands, see"Environment Variables in Event Handler Commands (on page 52)".

Environment Variables in Event Handler Commands

For each Parallels Plesk Panel event, there is a specific set of environment variablesthat can be passed on to a script. For the list of Parallels Plesk Panel events, see"Parallels Plesk Panel Events" (on page 46). For descriptions of environment variables

corresponding to specific Parallels Plesk Panel events, see "Event Parameters Passedby Event Handlers" (on page 54). Only variables listed for the particular event type maybe used in event handler command. In the command line,the environment variablesmust be listed in the order corresponding to the numbering order of the variablesplaceholders in the script body (the placeholders have the %<number >format; for moreinformation on placeholders, see "Script Writing Rules" (on page 88)). The placeholdernumber parts must form an uninterrupted sequence of consecutive whole numbersstarting with 1 - %1, %2, %3 and so on.




Event Handler Command Example

The following is the example of a valid command for a client creation event handler and

the body of a script file called by it that writes information about a new client creationevent in to a log file. The example includes declaration of parameters to be passedonto the script file.

Command line:

"c:\program files\parallels\plesk\scripts\test-handler.bat"<new_contact_name> <new_login_name>

The body of the test-handler.bat script file:

echo "- - - - - - - - - - - - - - " >> c: \ wi ndows\ t emp\ event _handl er . l ogr em i nf ormat i on on t he event dat e and t i me

date / T >> c: \ wi ndows\ t emp\ event _handl er . l ogr em i nf ormat i on on t he cr eat ed cl i ent accountecho "cl i ent cr eated" >> c: \ wi ndows\ t emp\ event _handl er . l ogr em cl i ent ' s nameecho " name: %1" >> c: \ wi ndows\ t emp\ event _handl er . l ogrem cl i ent ' s l ogi necho "l ogi n: %2" >> c: \ wi ndows\ t emp\ event _handl er . l ogecho "- - - - - - - - - - - - - - " >> c: \ wi ndows\ t emp\ event _handl er . l og

Explanation:

.

Placeholders %1 and %2 in the body of the script will be replaced with values of the new_cont act _name and new_l ogi n_name environment variables, respectively,because the new_cont act _name variable is listed first and the new_l ogi n_name variable is listed second in the command. The script will write the following chunk oftext into the c: \ wi ndows\ t emp\ event _handl er . l og file:

Sat J un 26 21: 46: 34 NOVT 2004

cl i ent creat ed

name: <new_cont act _name>

l ogi n: <new_l ogi n_name>

Note: For object removal events, environment variables starting with "new_ " containempty strings. For object creation events, environment variables starting with "ol d_ "contain empty strings.






In this section:

admin event......................................................................................................... 56 service event ....................................................................................................... 56 dl_user event....................................................................................................... 57 ip_address events ............................................................................................... 57 session_preferences event ................................................................................. 58 client events ........................................................................................................ 59 client_status event .............................................................................................. 59 client_guid event ................................................................................................. 60 client_limits event ................................................................................................ 60 client_limit_traffic event ....................................................................................... 61 client_limit_size event ......................................................................................... 62 client_permissions event ..................................................................................... 62 client_preferences event ..................................................................................... 62

client_ip_pool event ............................................................................................ 63 client_siteapp events ........................................................................................... 63 dashboard_preset events .................................................................................... 64 domain events ..................................................................................................... 64 domain_status event ........................................................................................... 65 domain guid event ............................................................................................... 65 domain_dns event ............................................................................................... 66 subdomain events ............................................................................................... 66 domain_alias events ........................................................................................... 67 domain_alias_dns event ..................................................................................... 68 admin_alias events ............................................................................................. 68 domain_limits event ............................................................................................ 69

domain_limit_traffic event ................................................................................... 70 domain_limit_size event ...................................................................................... 70 cp_user events .................................................................................................... 71 mailname events ................................................................................................. 71 maillist events...................................................................................................... 72 phosting events ................................................................................................... 73 forwarding events ................................................................................................ 74 webuser events ................................................................................................... 75 siteapp events ..................................................................................................... 76 siteapppkg events ............................................................................................... 77 license events ..................................................................................................... 77 db_server event .................................................................................................. 78

db event .............................................................................................................. 78 db_user events.................................................................................................... 79 remote_dns_status event .................................................................................... 79 ftpuser events...................................................................................................... 80 component event ................................................................................................. 81 template_client event .......................................................................................... 81 template_admin event ......................................................................................... 81 template_domain event ....................................................................................... 82 reseller events ..................................................................................................... 82 reseller_status event ........................................................................................... 83 reseller_limit_size event ...................................................................................... 83 reseller_limit_trafic event .................................................................................... 84 reseller_limits event ............................................................................................ 84 reseller_permissions event ................................................................................. 85 reseller_preferences event .................................................................................. 86 reseller_guid event .............................................................................................. 86 template_reseller events ..................................................................................... 87 reseller_ip_pool event ......................................................................................... 87 reseller_siteapp events ....................................................................................... 87 domain _owner_chan e event ............................................................................. 88




admin event

Parameters for event:

Event

Administrator information updated

Componentname/description

Command line parameter

Notes

Old component value New component value

Login Name ol d_l ogi n_name new_l ogi n_name required

Contact Nameol d_cont act _name new_cont act _name

requiredCompany Name ol d_company_name new_company_ name

Phone ol d_phone new_phone

Fax ol d_f ax new_f ax

E-mail ol d_emai l new_emai l

Address ol d_address new_addr ess

City ol d_ci t y new_ci t y

State/Province ol d_st at e_provi nce new_st at e_pr ovi nce

Postal/ZIP Code ol d_post al _zi p_code new_post al _zi p_code

Country ol d_count r y new_count r y

service event

Parameters for events:

Event

Service started

Service stopped

Service restarted



Notes


Service name ol d_servi ce new_servi ce required




dl_user event


Event

Domain administrator propertiesupdated



Notes


Allow domain user

access

ol d_al l ow_domai n_us

er _access

new_al l ow_domai n_us

er_ access


Password ol d_passwor d new_passwor d required

Domain name ol d_domai n_name new_domai n_name required

Contact Name ol d_cont act _name new_cont act _name

Company Name ol d_company_name new_company_name




Address ol d_addr ess ol d_addr ess

City ol d_ci t y ol d_ci t y

Sate/Province ol d_st at e_pr ovi nce ol d_st at e_pr ovi nce

Postal/ZIP code ol d_post al _zi p_code ol d_post al _zi p_code


ip_address events


Event

IP address created

IP address updated




Component

name/description


Notes


IP address ol d_i p_addr ess new_i p_addr ess required

Network mask ol d_i p_mask new_i p_mask

Network interface ol d_i nt er f ace new_i nt er f ace

IP address type ol d_i p_t ype new_i p_t ype


Event

IP address deleted



Notes



session_preferences event


Event

Login settings updated



Notes


Session idle timeol d_sessi on_i dl e_t ime

new_sessi on_i dl e_t ime




client events


Event

Client account created

Client accountupdated

Client accountremoved


Command line parameter Notes



Password ol d_passwor d new_password

Contact Name ol d_cont act _name new_cont act _name required

Company Name ol d_company_name new_company_ name






State/Province ol d_st at e_provi nce new_st at e_provi nce

Postal/ZIP Code ol d_post al _zi p_code new_postal _zi p_code


client_status eventParameters for event:

Event

Client account status updated

Component

name/description


Notes







Notes


Contact Name ol d_cont act _name new_cont act _name requiredLogin Name ol d_l ogi n_name new_l ogi n_name required

Status ol d_st at us new_st at us

client_guid event


Event

Client GUID updated



Notes


Client login name ol d_ login_name new_ login_name required

Client GUID ol d_ guid new_ guid

client_limits event


Event

Client limits updated



Notes


Client Login Name ol d_l ogi n_name new_l ogi n_name required

Maximum Number ofDomains

ol d_maxi mum_domai ns new_maxi mum_domai ns

Maximum Amount ofDisk Space

ol d_maxi mum_di sk_ space

new_maxi mum_di sk_space

Maximum Amount of

Traffic ol d_maxi mum_t r af f i c new_maxi mum_t r af f i c






client_limit_size event


Event

Disk space limit for client accountreached



Notes

Old component value New compon ent value

Contact name ol d_cont act _name new_cont act _name required

Disk space limitol d_maxi mum_di sk_ space


required

client_permissions event


Event

Client permissions updated



Notes


Client login name ol d_l ogi n_name new_l ogi n_name required

client_preferences event


Event

Client interface preferencesupdated




Component

name/description


Notes




Allow multiplesessions

ol d_al l ow_mul t i pl e_ sessi ons

new_al l ow_mul t i pl e_ sessi ons

Interface languageol d_i nt er f ace_l anguage

new_i nt er f ace_l anguage

Interface skin ol d_i nt er f ace_ski n new_i nt er f ace_ski n

client_ip_pool event


Event

Client IP pool updated



Notes


Login name ol d_l ogi n_name new_l ogi n_name required


Status ol d_st at us new_s t at us

client_siteapp events


Event

Client application package added

Client application package removed




Component

name/description


Notes



Package name ol d_package_name new_package_name required

dashboard_preset events


Event

Desktop preset created

Desktop preset deleted

Desktop preset updated



NotesOld component value New component value

Desktop preset IDol d_deskt op_preset _ i d

new_deskt op_pr eset _ i d

required

Desktop preset typeol d_deskt op_preset _ t ype

new_deskt op_pr eset _ t ype

Desktop presetname

ol d_deskt op_preset _ name

new_deskt op_pr eset _ name

domain events


Event

Domain created

Domain updated

Domain deleted




Component

name/description


Notes


Domain Name ol d_domai n_name new_domai n_name required

domain_status event

Event

Domain statusupdated



Notes



Domain status ol d_st at us new_st at us

domain guid event


Event

Domain GUID updated



Notes


Domain name ol d_ domain_name new_ domain_name required

Domain GUID ol d_ guid new_ guid




domain_dns event


Event

Domain DNS zoneupdated



Notes



subdomain events


Event

Subdomain created

Subdomain updated

Subdomain deleted



Notes


Subdomain Name ol d_subdomai n_name new_subdomai n_name required

Parent DomainName

ol d_domai n_name new_domai n_name required

FTP account loginol d_syst em_user _t ype

new_syst em_user_t ype

Subdomain owner'slogin

ol d_syst em_user new_syst em_user

FTP accountpassword

ol d_syst em_user _passwor d

new_syst em_user _passwor d

Hard disk quota ol d_har d_di sk_quota new_har d_di sk_quota

SSI support ol d_ssi _support new_ssi _suppor t

PHP support ol d_php_suppor t new_php_suppor t

CGI support ol d_cgi _support new_cgi _suppor t

Perl support ol d_per l _suppor t new_per l _support






Notes


Python support ol d_pyt hon_suppor t new_pyt hon_suppor t

ColdFusion supportol d_col df usi on_support

new_col df usi on_support

ASP support ol d_asp_suppor t new_asp_suppor t

domain_alias events


Event

Domain alias created

Domain alias updated

Domain alias deleted



Notes


Domain alias nameol d_domai n_al i as_name

new_domai n_al i as_name

required

Domain ID# inParallels PleskPanel database

ol d_domai n_i d new_domai n_i d

Domain status ol d_st at us new_st at us

Status of DNS zonesynchronization with

primary domain

ol d_dns new_dns

Mail service status ol d_mai l new_mai l

Web service status ol d_web new_web




domain_alias_dns event


Event

DNS zone of domain aliasupdated



Notes


Domain alias name

ol d_domai n_al i as_na

me

new_domai n_al i as_na

me required

admin_alias events


Event

Additional administrator account created

Additional administrator accountupdated



Notes





Account status ol d_st at us new_st at us



Event

Additional administrator accountdeleted




Component

name/description


Notes





Account status ol d_st at us new_st at us


domain_limits event


Event

Domain limits updated



Notes



Maximum Amount ofDisk Space



Maximum Amount ofTraffic

ol d_maxi mum_t r af f i c new_maxi mum_t r af f i c

Maximum Number ofWeb Users

ol d_maxi mum_webusers

new_maxi mum_webusers

Maximum Number ofDatabases

ol d_maxi mum_dat abases

new_maxi mum_dat abases

Maximum Number ofMailboxes

ol d_maxi mum_mai l boxes

new_maxi mum_mai l boxes

Mailbox Quotaol d_maxi mum_mai l box _quota

new_maxi mum_mai l box _quot a

Maximum Number ofMail Redirects

ol d_maxi mum_mai l _r edi r ects

new_maxi mum_mai l _r edi r ects

Maximum Number ofMail Groups

ol d_maxi mum_mai l _groups

new_maxi mum_mai l _groups






Notes


Maximum Number ofMail Autoresponders ol d_maxi mum_mai l _aut oresponder s new_maxi mum_mai l _aut oresponder s

Maximum Number ofMailing Lists

ol d_maxi mum_mai l _l is ts

new_maxi mum_mai l _l is ts

Maximum Number ofWeb Applications

ol d_maxi mum_t omcat _ web_appl i cat i ons

new_maxi mum_t omcat _ web_appl i cat i ons

Domain ExpirationDate

ol d_expi r at i on_dat e new_expi r at i on_dat e

domain_limit_traffic eventParameters for events:

Event

Traffic limit for domainreached



Notes



Maximum amount oftraffic limit



required

domain_limit_size eventParameters for events:

Event

Disk space limit for domainreached



NotesOld component value New component value







Event

Mail account updated



Notes


Mail account ol d_mai l name new_mai l name

required(in theformat

mai l name@domai

n)

Mailbox ol d_mai l box new_mai l box


Mailbox Quota ol d_mai l box_quot a new_mai l box_quot a

Redirect ol d_r edi r ect new_r edi r ect

Redirect Addressol d_r edi r ect _addr ess

new_r edi r ect _addr ess

Mail Group ol d_mai l _gr oup new_mai l _gr oup

Autoresponders ol d_autoresponder s new_aut oresponders

maillist events


Event

Mailing list created

Mailing list updated

Mailing list deleted



Notes



Mailing list name ol d_mai l _l i st _name new_mai l _l i st _name required






Notes


Mailing list switchedon ol d_mai l _l i st _enabled new_mai l _l i st _enabled

phosting events


Event

Physical hosting created

Physical hosting updated, domain performance or log rotation settingschanged



Notes



IP Address ol d_i p_addr ess new_i p_addr ess

IP Type ol d_i p_t ype new_i p_t ype

Domain Administrator login


Domain Administratorpassword

ol d_syst em_user _passwor d

new_syst em_user _passwor d

Access to system ol d_syst em_shel l new_syst em_shel l

MS FrontPageSupport

ol d_f p_support new_f p_support

MS FrontPage overSSL Support ol d_f pssl _suppor t new_f pssl _suppor t

MS FrontPage Authoring

ol d_f p_aut hor i ng new_f p_aut hori ng

MS FrontPage Admin Login

ol d_f p_admi n_l ogi n new_f p_admi n_l ogi n

MS FrontPage Admin Password

ol d_f p_admi n_passwor d

new_f p_admi n_passwor d

SSI Support ol d_ssi _support new_ssi _suppor t

PHP Support ol d_php_suppor t new_php_suppor t

CGI Support ol d_cgi _support new_cgi _suppor t

Perl Support ol d_per l _suppor t new_per l _support






Notes


Python support ol d_pyt hon_suppor t new_pyt hon_suppor t



ASP Support ol d_asp_suppor t new_asp_suppor t

SSL Support ol d_ssl _support new_ssl _suppor t

Custom ErrorDocuments

ol d_cust om_er r or_document s

new_cust om_err or _document s

Web Statistics ol d_web_st at i st i cs new_web_st at i st i cs

Hard Disk Quota ol d_har d_di sk_quota new_har d_di sk_quota


Event

Physical hostingdeleted



Notes


Domain Administrator login



forwarding events


Event

Standard or frame forwarding hostingcreated

Standard or frame forwarding hostingupdated



Notes







Notes


Domain name ol d_domai n_name new_domai n_name requiredIP address ol d_i p_addr ess new_i p_addr ess

Forwarding type ol d_f orwardi ng_t ype new_f orwar di ng_t ype

URL ol d_ur l new_ur l


Event

Standard or frame forwarding hostingdeleted



Notes



Forwarding type ol d_f orwardi ng_t ype new_f orwar di ng_t ype

webuser events


Event

Web user created

Web user updated



Notes



Web User Name ol d_webuser _name new_webuser _name required

Web User Passwordol d_webuser _password

new_webuser _password

SSI Support ol d_ssi _support new_ssi _suppor t

PHP Support ol d_php_suppor t new_php_suppor t






Notes


CGI Support ol d_cgi _support new_cgi _suppor tPerl Support ol d_per l _suppor t new_per l _support

Python Support ol d_pyt hon_suppor t new_pyt hon_suppor t



ASP Support ol d_asp_suppor t new_asp_suppor t

Hard Disk Quota ol d_har d_di sk_quota new_har d_di sk_quota


Event

Web user deleted



Notes



Web User Name ol d_webuser _name new_webuser _name required

siteapp events


Event

Site application installedSite application reconfigured

Site application uninstalled



Notes


Site application name ol d_package_name new_package_name required

Domain type (domainor subdomain)

ol d_domai n_t ype new_domai n_t ype required






Notes


Installation directory ol d_di r ect or y new_di r ect or y required

Installation prefixol d_i nstal l at i on_pref i x

new_i nst al l at i on_pref i x

required

siteapppkg events


Event

Site application package installed

Site application package updated

Site application package uninstalled



Notes


Site applicationpackage name

ol d_s i t e_appl i cat i on_package_name

new_si t e_appl i cat i on_package_name required

license events


Event

License key updated



Notes


License ol d_ license new_ license required

License type ol d_ license_type new_ license_type required

License name ol d_ license_name new_ license_name required





Event

Parallels Plesk Panel licensehas expired



Notes


License ol d_ license new_ license required

db_server event


Event

Connection to database server created

Connection to database serverupdated

Connection to database server deleted



Notes


Database server ol d_database_server new_database_server required

db event


Event

Database created

Database removed




Component

name/description


Notes



Database ol d_dat abase_name new_dat abase_name required

db_user events


Event

Database user account created

Database user account preferencesupdated

Database user account removed



Notes



Database ID ol d_database_i d new_database_i d required

Database user nameol d_database_user_name

new_dat abase_user _name

required

remote_dns_status event


Event

Remote DNS status updated



Notes


Remote DNS status ol d_r emote_dns_s t atus new_r emot e_dns_st atus required






component event


Event

Parallels Plesk Panelcomponent upgraded



Notes


Parallels Plesk Panel

component name

ol d_pl esk_component_

name

new_pl esk_component

_name required

template_client event


Event

Template for clients created

Template for clients updated

Template for clients removed



Notes


Client template ID ol d_t empl at e_i d new_t empl ate_i d required

template_admin event


Event

Template for domains created by administrator

Administrator's template for domains updated

Administrator's template for domains removed




Component

name/description


Notes


Domain template ID ol d_t empl at e_i d new_t empl ate_i d required

template_domain event


Event

Template for domains created by client

Client's template for domains updated

Client's template for domains removed



Notes


Domain template ID ol d_t empl at e_i d new_t empl ate_i d required

reseller events


Event

Reseller account created

Reseller account updated

Reseller account removed



Notes





Company Name ol d_company_name new_company_ name






Notes


Phone ol d_phone new_phoneFax ol d_f ax new_f ax




State/Province ol d_st at e_provi nce new_st at e_provi nce

Postal/ZIP Code ol d_post al _zi p_code new_postal _zi p_code


reseller_status event


Event

Reseller account status updated



Notes




Status ol d_st at us new_st at us

reseller_limit_size eventParameters for events:

Event

Disk space limit for reseller account reached



Notes








Notes


Disk space limit ol d_maxi mum_di sk_ space new_maxi mum_di sk_space required

reseller_limit_trafic event


Event

Traffic limit for reseller account

reached



Notes



Maximum amount oftraffic limit

ol d_maxi mum_t r af f i c new_maxi mum_t r af f i c required

reseller_limits event


Event

Reseller limits updated



Notes


Reseller login name ol d_l ogi n_name new_l ogi n_name required

Maximum number ofdomains

ol d_maxi mum_domai ns new_maxi mum_domai ns

Maximum amount ofdisk space



Maximum amount oftraffic ol d_maxi mum_t r af f i c new_maxi mum_t r af f i c






Notes


Maximum number ofweb users ol d_maxi mum_webusers new_maxi mum_webusers

Maximum number ofdatabases

ol d_maxi mum_dat abases

new_maxi mum_dat abases

Maximum number ofmailboxes

ol d_maxi mum_mai l boxes

new_maxi mum_mai l boxes

Mailbox quotaol d_maxi mum_mai l box _quota

new_maxi mum_mai l box _quot a

Maximum number ofmail redirects

ol d_maxi mum_mai l _r edi r ects

new_maxi mum_mai l _r edi r ects

Maximum number ofmail groups ol d_maxi mum_mai l _groups new_maxi mum_mai l _groups

Maximum number ofmail autoresponders

ol d_maxi mum_mai l _aut orespon ders

new_maxi mum_mai l _aut orespon ders

Maximum number ofmailing lists

ol d_maxi mum_mai l _l is ts

new_maxi mum_mai l _l is ts

Maximum number ofweb applications

ol d_maxi mum_t omcat _ web_appl i cat i ons

new_maxi mum_t omcat _ web_appl i cat i ons

Expiration date ol d_expi r at i on_dat e new_expi r at i on_dat e

reseller_permissions event


Event

Reseller permissions updated


Command line parameterNotes


Reseller login name ol d_l ogi n_name new_l ogi n_name required




reseller_preferences event


Event

Reseller interface preferencesupdated



Notes




Allow multiplesessions

ol d_al l ow_mul t i pl e_ sessi ons

new_al l ow_mul t i pl e_ sessi ons

Interface languageol d_i nt er f ace_l anguage

new_i nt er f ace_l anguage

Interface skin ol d_i nt er f ace_ski n new_i nt er f ace_ski n

reseller_guid event


Event

Reseller GUIDupdated



Notes


Reseller login name ol d_ login_name new_ login_name required

Reseller GUID ol d_ guid new_ guid




template_reseller events


Event

Template for resellers created

Template for resellers updated

Template for resellers removed



Notes

Old component value New component valueReseller template ID ol d_t empl at e_i d new_t empl ate_i d required

reseller_ip_pool event


Event

Reseller IP pool updated



Notes




Status ol d_st at us new_s t at us

reseller_siteapp events


Event

Reseller application package added

Reseller application packageremoved




Component

name/description


Notes



Package name ol d_package_name new_package_name required

domain_owner_change event


Event

Domain owner changed



Notes


Domain Name ol d_domai n_name new_domai n_name

Login name ol d_l ogi n_name new_l ogi n_name

Script Writing Rules

When writing executable scripts that will be assigned to Parallels Plesk Panel eventhandlers, you should follow the rules for designating environment variable placeholdersin the body of a script file. The placeholder has the %<number >format. The numberparts of the placeholders used in a particular script file must form an uninterrupted

sequence of consecutive whole numbers starting with 1 - %1, %2, %3 and so on. Thenumbering scheme is important because the numbers refer to the positions of theenvironment variables listed in command line. In the command line, the environmentvariables must be listed in the order corresponding to the numbering order of thevariables placeholders in the script body. For an example of a valid event handlercommand and script body, see "Event Handler Command Syntax" (on page 52).



To enable basic hosting services and functions on a Parallels Plesk Panel server,Parallels Plesk Panel distribution package includes several third-party softwareapplications, also referred to as third-party Parallels Plesk Panel components (ParallelsPlesk Panel components), that need to be installed along with Parallels Plesk Panel.

Parallels Plesk Panel components are ultimately responsible for providing varioushosting services such as DNS, e-mail, FTP, and others.

Hosting providers can also install and manage through Parallels Plesk Panel manyother third-party applications that are not included in the Parallels Plesk Paneldistribution package. For the complete list of third-party applications currentlysupported by Parallels Plesk Panel, see "Third-Party Applications Supported byParallels Plesk Panel" (on page 94).

Parallels Plesk Panel supports management of Parallels Plesk Panel components bythe control panel administrators by integrating with the applications and providing GUItools to perform routine application management tasks. A Parallels Plesk Panel-

supported third-party application installed on a Parallels Plesk Panel server is said tobe integrated with Parallels Plesk Panel if Parallels Plesk Panel can access andmanage the application.

This chapter provides necessary background information and complete instructions forinstalling and upgrading Parallels Plesk Panel components.

In this chapter:

Parallels Plesk Panel Component Installation and Upgrade Overview ............... 90 Third-Party Applications Supported by Parallels Plesk Panel ............................. 94

Third-Party Applications not Supported by Parallels Plesk Panel ....................... 96 Installing and Upgrading Parallels Plesk Panel Components ............................. 97

C H A P T E R 6

Installing and Upgrading Parallels Plesk

Panel Components



90 Installing and Upgrading Parallels Plesk Panel Components

Parallels Plesk Panel Component

Installation and Upgrade OverviewThis section describes possible ways of installing and upgrading Parallels Plesk Panelcomponents.

In this section:

Third-Party Application Installation as Parallels Plesk Panel Component .......... 90 Parallels Plesk Panel Component Upgrade ........................................................ 93

Third-Party Application Installation as Parallels PleskPanel Component

To work as a Parallels Plesk Panel component, an installed third-party application mustmeet the following conditions:

it must be supported by Parallels Plesk Panel

it must be installed on the Parallels Plesk Panel server

an installed application must be integrated with Parallels Plesk Panel

For a list of third-party applications supported by Parallels Plesk Panel, see "Third-Party Software Supported by Parallels Plesk Panel" (on page 94).

If a supported third-party application has already been installed on a server prior toParallels Plesk Panel installation, during Parallels Plesk Panel installation on the serverit will be automatically detected by the Parallels Plesk Panel installer program andintegrated with Parallels Plesk Panel. For more information, see "Automatic Integrationof Pre-Installed Third-Party Applications as Parallels Plesk Panel Components" (onpage 92).

Supported third-party application installed or upgraded manually on an existingParallels Plesk Panel server must be integrated with Parallels Plesk Panel to work asParallels Plesk Panel component.

In this section:

Automatic Installation of Parallels Plesk Panel Components .............................. 91 Automatic Integration of Pre-Installed Third-Party Applications as Parallels PleskPanel Components .............................................................................................. 92 Manual Installation of Parallels Plesk Panel Components on Existing Parallels Plesk

Panel Servers...................................................................................................... 92






myLittleAdmin 2000 2.7 r.126, 2005 3.2

phpMyAdmin 2.11.6

AWStats 6.6

Webalizer V2.01-10-RB02 (Windows NT 5.2 ) English

stunnel 4.07

Horde IMP H3 (4.1.6)

Automatic Integration of Pre-Installed Third-Party Appl icationsas Parallels Plesk Panel Components

Supported third-party applications that have already been installed on a server prior toParallels Plesk Panel installation will be automatically detected during Parallels PleskPanel installation by the Parallels Plesk Panel autoinstaller program and integrated asParallels Plesk Panel components.

Note: Third-party applications that require additional Parallels Plesk Panelconfiguration to complete installation as Parallels Plesk Panel components will not beactivated upon automatic integration until required application information is entered inParallels Plesk Panel. To activate such a component, you will need to enter therequired application information in Parallels Plesk Panel.

Manual Installation of Parallels Plesk Panel Components on

Existing Parallels Plesk Panel Servers

Parallels Plesk Panel component can be installed manually by using a manufacturer-supplied application package.

To install a Parallels Plesk Panel component on a Parallels Plesk Panel server byusing a manufacturer-supplied software package, follow these steps:

1. Upload the package to the Parallels Plesk Panel server and then run the packageinstallation program or, when applicable, follow the manufacturer's installationinstructions.

2. Complete Parallels Plesk Panel component installation by integrating the newlyinstalled third-party application instance with Parallels Plesk Panel by following thegeneral integration procedure (on page 98).

Note: For some applications, you will need to additionally configure system or theapplication for Parallels Plesk Panel component installation to be successful. Fordetailed instructions on installing individual Parallels Plesk Panel components, see thecorresponding subsections in the "Installing Parallels Plesk Panel Components" (onpage 97) section.




Parallels Plesk Panel Component Upgrade

Installed Parallels Plesk Panel components can be upgraded in one of the following

ways:

By applying a Parallels Plesk Panel component upgrade included in the ParallelsPlesk Panel distribution package.

Parallels Plesk Panel components installed by using Parallels Plesk Paneldistribution package can be upgraded automatically by using a Parallels PleskPanel installation package that includes a newer version of a third-party applicationalready installed as a Parallels Plesk Panel component. For this, run the ParallelsPlesk Panel autoinstaller program selecting the Upgrade option and then selectingone or more components that you want to upgrade.

By applying an application upgrade package supplied by the application

manufacturer.Parallels Plesk Panel components can be upgraded manually by usingmanufacturer-supplied upgrade packages. Manually upgraded Parallels PleskPanel components must be re-integrated with Parallels Plesk Panel by following thegeneral integration procedure (on page 98).

Note: Generally it is not a good idea to manually upgrade a Parallels Plesk Panelcomponent that has been installed automatically. The main reason for this is that theapplication builds included in a Parallels Plesk Panel distribution package are oftencustom-tailored to work specifically with the Parallels Plesk Panel version. Upgradingsuch applications by using manufacturer-supplied upgrade packages may haveunpredictable consequences with regard to the upgraded application performance and

also may impact performance of other Parallels Plesk Panel components and ParallelsPlesk Panel itself.




Third-Party Applications Supported by

Parallels Plesk PanelThe following third-party software is supported by Parallels Plesk Panel for Windows. Theup-to-date list of supported software for each Parallels Plesk Panel version is available in theRelease Notes for that version distribution package.

Mail servers

MailEnable Standard 1.986

MailEnable Professional 3.14

MailEnable Enterprise 3.14

Merak 9.2.1

SmarterMail 5.1

MDaemon 9.6.6

hMailServer 4.4.1

CommuniGate Pro 5.2.3

Antivi ruses

Parallels Premium Antivirus by Dr. Web

Kaspersky AV 5.0.0.49

ClamWin 0.92

Merak Antivirus

DNS servers

Microsoft DNS Server 5.2

BIND DNS Server 9.4.2-P1

Simple DNS Plus 5.0

FTP servers

Microsoft FTP 6.0

Microsoft FTP 7.0

Gene6 FTP Server 3.10

Serv-U FTP Server 6.4

Web Statistics

Webalizer V2.01-10-RB02

AWStats 6.6

SmarterStats 3.3

Urchin 5.7

Web Scripting ASP 6.0.3790.0




ASP.NET 1.1.4322

ASP.NET 2.0.50727 (.Net Framework 2.0/3.0/3.5)

Miva Empresa 5.0.6

Perl 5.8.8

PHP 4.4.7

PHP 5.2.6

Python 2.5.0.0

SSI 6.0.3790

Apache Tomcat 5.5.4

ColdFusion 5.0

ColdFusion MX 6.1

ColdFusion MX 7.0

ColdFusion 8.0 (x86 only)

Microsoft FrontPage 5.0.2.5012

FastCGI Support 7.0.6001.18000

Web Administration Tools

phpMyAdmin 2.11.6

ASP.NET Enterprise Manager 0.1.3

myLittleAdmin 2000 2.7 r.126, 2005 3.2

Database servers Microsoft SQL Server 2000

Microsoft SQL Server 2005

MySQL 5.0.45

Web Mail Solutions

Horde IMP H3 (4.1.6)

MailEnable Web Client

IceWarp Web Mail

SmarterMail Web Client CommuniGate Pro Web Client

Spam Filters

SpamAssassin 3.2.3

Merak

SmarterMail SpamAssassin

Other

stunnel 4.07






Installing and Upgrading Parallels Plesk

Panel ComponentsParallels Plesk Panel components can be installed either automatically or manually.

Only third-party applications included in the Parallels Plesk Panel distribution package canbe installed automatically. For overview of installation methods, see "Third-Party ApplicationInstallation as Parallels Plesk Panel Component" (on page 90).

Supported third-party applications not included in Parallels Plesk Panel distribution can beinstalled as Parallels Plesk Panel component manually by using manufacturer-suppliedinstallation packages. After running an installer program, the newly installed third-party

application must be integrated with Parallels Plesk Panel by following the integrationprocedure (on page 98).

For some third-party applications installed by using manufacturer-supplied applicationpackages, you need to additionally configure the application or system for the integrationprocedure to be successful.

Because many Parallels Plesk Panel components are run by Windows as services, beforeswitching Parallels Plesk Panel to a new component, you may need to stop the currentlyrunning Parallels Plesk Panel service to ensure that the component registers itself correctlyin the system during installation. You can stop the old service by using the Parallels PleskPanel Services monitor (on page 182). However, if you do install your new component and

switch Parallels Plesk Panel to it with the service running in the background, potentialintegration problems can be solved by simply restarting the newly installed service.

This section describes installation procedures for third-party applications supported byParallels Plesk Panel.

In this section:

General Integration Procedure ............................................................................ 98 Installing and Upgrading Mail Components ......................................................... 99 Installing and Upgrading Antivirus Components ................................................. 111

Installing and Upgrading DNS Servers ................................................................ 118 Installing and Upgrading FTP Servers ................................................................ 122 Installing and Upgrading Server-Side Web Scripting Engines ............................ 132 Installing and Upgrading Web Administration Tools ............................................ 147 Installing and Upgrading Database Servers ........................................................ 152 Installing and Upgrading Web Mail Solutions ...................................................... 156 Installing SpamAssassin Spam Filter .................................................................. 162 Installing stunnel .................................................................................................. 163 Using Parallels Plesk Billing ................................................................................ 164








Installing and Upgrading MailEnable Mail Server

MailEnable Standard is included in the Parallels Plesk Panel distribution package and can be

automatically installed or upgraded by one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported application configurations

MailEnable Standard

MailEnable Professional

MailEnable Enterprise

Supported versions

For the latest supported MailEnable application version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manual Installation

To install MailEnable mail server manually as Parallels Plesk Panel component, follow thesesteps:

1. Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.

2. Stop the old Parallels Plesk Panel mail service.

This is necessary for the MailEnable mail server that is being installed to properly registeritself in the system.

3. Obtain a MailEnable mail server distribution package and install the application on theParallels Plesk Panel server by running the package installer.

Note: No additional configuration steps are required after running a manufacturer-supplied application installation package.

4. Complete the installation of MailEnable server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The MailEnable mail serverentry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade MailEnable mail component manually as Parallels Plesk Panel component,follow these steps:


2. Obtain a MailEnable mail server upgrade package and apply the upgrade to the existinginstallation.




3. Complete the upgrade of MailEnable mail component by following the general integrationprocedure (on page 98). The upgraded MailEnable mail component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading Merak Mail Server

Merak mail server is not included in the Parallels Plesk Panel distribution package and

cannot be automatically installed.

Supported versions

For the latest supported Merak version, see your Parallels Plesk Panel version release notesor the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide. Merak v. 9.0 is not supported.

Manual Installation

To install Merak mail server manually as Parallels Plesk Panel component, follow thesesteps:



This is necessary for the Merak mail server that is being installed to properly register itselfin the system.

3. Obtain a Merak mail server distribution package and install the application on theParallels Plesk Panel server by running the package installer.


4. Complete the installation of Merak server as Parallels Plesk Panel component by

following the general integration procedure (on page 98). The Merak mail server entryappears in the Parallels Plesk Panel components list.

Note: Merak distribution package includes the Avast antivirus software, which is installedalong with the mail server. When the Merak application is started for the first time, it launchesthe avast . set up process, which consumes most of the processor's computing power. If aninstalled Merak server has never been started before integration, Parallels Plesk Panel willstart the server during the integration procedure. You will not be able to switch from thelegacy mail server to the Merak server until the avast . set up process finishes work.

Manual Upgrade

To upgrade Merak mail component manually as Parallels Plesk Panel component, followthese steps:


2. Obtain a Merak mail server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Merak mail component by following the general integrationprocedure (on page 98). The upgraded Merak mail component entry appears in the

Parallels Plesk Panel components list.






Note: When Parallels Plesk Panel uses SmarterMail mail server, the mailing lists strategydepends on the current mail server settings. View the mail server documentation for details.

Manual Upgrade

To upgrade SmarterMail mail component manually as Parallels Plesk Panel component,follow these steps:


2. Obtain a SmarterMail mail server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of SmarterMail mail component by following the generalintegration procedure (on page 98). The upgraded SmarterMail mail component entryappears in the Parallels Plesk Panel components list.




Installing and Upgrading MDaemon Mail Server

MDaemon mail server is not included in the Parallels Plesk Panel distribution package and


Warning: MDaemon mail server is not compatible with the Windows' Data ExecutionPrevention (DEP) feature.

Warning: Parallels Plesk Panel can work only with MDaemon started as a system service onall supported Windows platforms. Please do not start also MDaemon GUI (by clicking Al lPrograms -> Start MDaemon shortcut), it may lead to the crash of both MDaemon systemservice and MDaemon GUI.

Note: When MDaemon is started as a system service on Windows Server 2008, theMDaemon management icon would not appear in the system tray. Please use MDaemon

Web Admin to manage MDaemon with Parallels Plesk Panel on Windows Server 2008.

Supported versions

For the latest supported MDaemon version, see your Parallels Plesk Panel release notes orthe "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide.

Manual Installation

To install MDaemon mail server manually as Parallels Plesk Panel component, follow thesesteps:



This is necessary for the MDaemon mail server that is being installed to properly registeritself in the system.

3. Obtain a MDaemon mail server distribution package and install it on the Parallels PleskPanel server by running the package installer.

MDaemon must be configured to run as a system service to be installed as a ParallelsPlesk Panel component. By default, MDaemon is registered in the system as a service.

Tip: If MDaemon was installed as an application, configure it to run as a system service:1. Open the MDaemon interface.2. Click the Setup menu at the top.3. Select System Service.4. Click the Install Service button.

4. Complete the installation of MDaemon server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The MDaemon mail serverentry appears in the Par allels Plesk Panel components list.

Manual Upgrade




To upgrade MDaemon mail component manually as Parallels Plesk Panel component, followthese steps:


2. Obtain a MDaemon mail server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of MDaemon mail component by following the general integrationprocedure (on page 98). The upgraded MDaemon mail component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading hMailServer Mail Server

hMailServer mail server is not included in the Parallels Plesk Panel distribution package and


Supported versions

For the latest supported hMailServer version, see your Parallels Plesk Panel version releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Note: The use of hMailServer with Windows Server 2008 is not recommended, whileWindows Server 2008 is not in the list of operating systems supported by hMailServer(http://www.hmailserver.com/documentation/?page=system_requirements).

Note: Parallels Plesk Panel does not support traffic calculation by the stat i s t i cs . exe utility on the hMail mail server.

Manual Installation

To install hMailServer mail server manually as Parallels Plesk Panel component, follow thesesteps:



This is necessary for the hMailServer mail server that is being installed to properly

register itself in the system.3. Obtain a hMailServer mail server distribution package and install the application on the

Parallels Plesk Panel server by running the package installer.


4. Complete the installation of hMailServer server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The hMailServer mail serverentry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade hMailServer mail component manually as Parallels Plesk Panel component,follow these steps:


2. Obtain a hMailServer mail server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of hMailServer mail component by following the generalintegration procedure (on page 98). The upgraded hMailServer mail component entryappears in the Parallels Plesk Panel components list.

http://www.hmailserver.com/documentation/?page=system_requirements

http://www.hmailserver.com/documentation/?page=system_requirements




Installing and Upgrading CommuniGate Pro Mail Server

CommuniGate Pro mail server is not included in the Parallels Plesk Panel distribution

package and cannot be automatically installed.

Supported versions

For the latest supported CommuniGate Pro version, see your Parallels Plesk Panel releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Note: Parallels Plesk Panel does not support traffic calculation by the stat i s t i cs . exe utility on the CommuniGate Pro mail server.

Manual Installation

To install CommuniGate Pro mail server manually as Parallels Plesk Panel component,follow these steps:



This is necessary for the CommuniGate Pro mail server that is being installed to properlyregister itself in the system.

3. Obtain a CommuniGate Pro mail server distribution package and install the application onthe Parallels Plesk Panel server by running the package installer.

4. Start the newly installed CommuniGate Pro mail server application.5. Log in to the mail server by using the server's own Web interface and configure the mail

server's port number and administrator login credentials.

6. Complete the installation of CommuniGate Pro server as Parallels Plesk Panelcomponent by following the general integration procedure (on page 98). The newlyinstalled CommuniGate Pro component entry appears inactive in the Parallels PleskPanel components list.

7. Activate CommuniGate Pro mail component by clicking the entry and entering the portnumber, administrator login name, and administrator password for the CommuniGate Proserver specified at the previous step.

The CommuniGate Pro mail server entry appears in the Parallels Plesk Panel componentslist.






Installing and Upgrading AtMail Mail Server

AtMail Webmail Light is included in the Parallels Plesk Panel distribution package and can be

automatically installed or upgraded by one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Note: AtMail Webmail Light supports only IMAP. To have both IMAP and POP3 support, usethe commercial version of AtMail Webmail.

Supported application configurations

AtMail Webmail Lite (free)

AtMail Webmail (commercial)

Supported versions

For the latest supported AtMail Webmail application version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manual Installation

To install AtMail Webmail server manually as Parallels Plesk Panel component, follow these

steps:

1. Obtain an AtMail Webmail license and additional Parallels Plesk Panel license with AtMail Webmail support.

2. Install the additional license with AtMail Webmail support in your Parallels Plesk Panel.Upon installation of the additional license, AtMail Webmail is automatically downloaded toParallels Plesk Panel application catalogue as an application packaged according to the APS standard.

3. Go to Home > Server Components. Click Refresh. The AtMail Webmail component appears

in the list with the icon.

4. Click the icon to enable the AtMail Webmail component. The AtMail Webmail isinstalled on an auxiliary site which redirects the requests to URL of an applicationinstalled on a specific domain.

5. To use AtMail Webmail instance on a specific domain, go to Domains > domain name > Mailgroup titl e menu > Mail Settings.

6. Select the Atmai l Webmai l component check box.

7. Specify the Destination URL to the AtMail Webmail instance on the domain.

8. Click OK.

Manual Upgrade






Installing and Upgrading Parallels Premium Antivirus

Parallels Premium Antivirus is included in the Parallels Plesk Panel distribution package and

can be automatically installed by one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 92). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported version of Parallels Premium Antivirus by Dr. Web, see yourParallels Plesk Panel version release notes or the "Third-Party Software Supported byParallels Plesk Panel" (on page 94) section in this guide.

Manual Installation

To install Parallels Premium Antivirus manually as Parallels Plesk Panel component, followthese steps:


2. Obtain an antivirus distribution package and install it on the Parallels Plesk Panel serverby running the package installer.

3. Complete the installation of antivirus as Parallels Plesk Panel component by following thegeneral integration procedure (on page 98). The Parallels Premium Antivirus entryappears in the list of Parallels Plesk Panel components.

Manual Upgrade

To upgrade antivirus manually, follow these steps:


2. Obtain an antivirus upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of antivirus component by following the general integrationprocedure (on page 98). The upgraded Parallels Premium Antivirus entry appears in thelist of Parallels Plesk Panel components.




Installing and Upgrading Kaspersky Antivi rus

Kaspersky antivirus is included in the Parallels Plesk Panel distribution package and can be

automatically installed by one of the automatic installation methods. For more informationabout the automatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 91). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported Kaspersky antivirus version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manual Installation

To install Kaspersky antivirus manually as Parallels Plesk Panel component, follow thesesteps:


2. Obtain a Kaspersky antivirus distribution package and install the application on theParallels Plesk Panel server by running the package installer.


3. Complete the installation of Kaspersky antivirus as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The Kaspersky antivirus entryappears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Kaspersky antivirus component manually, follow these steps:


2. Obtain a Kaspersky antivirus upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Kaspersky antivirus component by following the generalintegration procedure (on page 98). The upgraded Kaspersky antivirus component entryappears in the Parallels Plesk Panel components list.




Installing and Upgrading ClamWin Antivirus

ClamWin antivirus is included in the Parallels Plesk Panel distribution package and can be

automatically installed by one of the automatic installation methods. For more informationabout the automatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 91). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade (on page 93)".

Supported versions

For the latest supported ClamWin antivirus version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manual Installation

To install ClamWin antivirus manually as Parallels Plesk Panel component, follow thesesteps:


2. Obtain a ClamWin antivirus distribution package and install the application on theParallels Plesk Panel server by running the package installer.


3. Complete the installation of the ClamWin antivirus component by following the generalintegration procedure (on page 98). The ClamWin antivirus entry appears in the ParallelsPlesk Panel components list.

Manual Upgrade

To upgrade the ClamWin antivirus component manually, follow these steps:


2. Obtain a ClamWin antivirus upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of ClamWin antivirus component by following the generalintegration procedure (on page 98). The upgraded ClamWin antivirus component entryappears in the Parallels Plesk Panel components list.




Installing and Upgrading ClamAV Antivirus

The ClamAV antivirus is not included in the Parallels Plesk Panel distribution package and

cannot be installed automatically.

Supported versions

For the latest supported ClamAV version, see your Parallels Plesk Panel release notes or the"Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in this guide.

Manual Installation

To install ClamAV antivirus manually as Parallels Plesk Panel component, follow thesesteps:


2. Obtain a ClamAV antivirus distribution package and install the application on the ParallelsPlesk Panel server by running the package installer.

3. Check and, if necessary, correct the path records for ClamAV folders and files found inthe following configuration files:

<Cl amAV i nst al l f ol der >\ conf \ f r eshcl am. conf

<Cl amAV i nst al l f ol der >\ conf \ cl amd. conf

where <Cl amAV i nst al l f ol der >is the path to the ClamAV installation folder.Note: In recent ClamAV for Windows versions, upon installation the configuration filesmay contain incorrect path references to ClamAV files and folders, which preventsParallels Plesk Panel from integrating with the installed antivirus.

You can perform the general integration procedure (on page 98) at this point. If theintegration is successful, the ClamAV antivirus entry will appear in the components list.However, you likely also need to perform the next step before ClamAV componentinstallation can be completed.

4. Check and, if necessary, correct the following registry key to contain the proper ClamAVinstallation folder path:

HKEY_LOCAL_MACHI NE\ SOFTWARE\ Wow6432Node\ PLESK\ PSAConf i g\ Conf i g\ Cl amAVPat h (for 64bit Windows)

or

HKEY_LOCAL_MACHI NE\ SOFTWARE\ PLESK\ PSA Conf i g\ Conf i g\ Cl amAVPat h (for 32bit Windows)

4. Wait for at least two minutes for the cache to automatically renew and then complete the

component installation by performing the general integration procedure (on page 98).




If you do not want to wait for the automatic cache renewal, you can force the cacherenewal by restarting the Parallels Plesk Panel Management service by using theParallels Plesk Panel Services Monitor. For information about using Parallels Plesk PanelServices Monitor, see "Monitoring Server Status with Parallels Plesk Panel ServicesMonitor" (on page 182).

Manual Upgrade

To upgrade the ClamAV antivirus component manually, follow these steps:


2. Obtain a ClamAV antivirus upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of ClamAV antivirus component by following the generalintegration procedure (on page 98). The upgraded ClamAV antivirus component entryappears in the Parallels Plesk Panel components list.




Installing and Upgrading Merak Antivirus

Parallels Plesk Panel supports Merak antivirus that is installed as part of the Merak mail

server. The Merak antivirus component cannot be installed or upgraded apart from the Merakmail component. For information about installing and upgrading the Merak mail component,see "Installing and Upgrading Merak Mail Server" (on page 102).

You can switch Parallels Plesk Panel to the Merak antivirus only if the Merak mail server isselected as the current Parallels Plesk Panel mail component. When the Merak mail server isinstalled as a Parallels Plesk Panel component, the Merak antivirus option is displayed in thelist of antivirus components at Home > Server Components > Antivi rus under Antivi rus. Theoption is available only if the Merak mail server is selected as the current Parallels PleskPanel mail component. The option becomes unavailable when mail component other thanMerak is selected.

Note: The antivirus will be automatically disabled when Parallels Plesk Panel is switchedfrom Merak mail server to other supported mail component and no antivirus component willbe automatically enabled in its place. You need to enable another antivirus component toperform antivirus surveillance tasks on your Parallels Plesk Panel server.

Supported versions

For the latest supported Merak antivirus version, see your Parallels Plesk Panel releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

To enable Merak antivirus component on a Parallels Plesk Panel server, follow these steps:

1. Login to Parallels Plesk Panel as the administrator.

2. Go to Home > Server Components. The list of available Parallels Plesk Panel components isdisplayed.

3. Make sure that the Merak mail component is enabled.

4. Click Antivi rus. The list of available antivirus components is displayed.

5. Select the Merak antivirus option and click OK. The list of available Parallels Plesk Panelcomponents is displayed. The Merak antivirus entry is displayed as the currently activecomponent (accompanied by the Running icon).




Installing and Upgrading DNS Servers

BIND DNS server is included in the Parallels Plesk Panel distribution package.

Other supported DNS servers can be installed as Parallels Plesk Panel components by usingmanufacturer-supplied installation packages. After running an installer program, the newlyinstalled DNS server must be integrated with Parallels Plesk Panel by following theintegration procedure (on page 98).

For some DNS server applications, you need to additionally configure the application orsystem for the integration procedure to be successful.

Make sure that during installation and integration of a new DNS server application the currentParallels Plesk Panel DNS service is stopped. You can stop it by using the Parallels PleskPanel Services monitor (on page 182). This is necessary to ensure that the newly installedDNS component registers itself correctly in the system during installation.

However, if you do install your new DNS component and switch Parallels Plesk Panel to itwith the old DNS service running in the background, potential integration problems can besolved by restarting the newly installed DNS service.

This section describes installation and upgrade procedures for DNS servers supported byParallels Plesk Panel.

In this section:

Installing and Upgrading BIND DNS Server ........................................................ 119 Installing and Upgrading Microsoft DNS Server .................................................. 120 Installing and Upgrading Simple DNS Plus Server ............................................. 121




Installing and Upgrading BIND DNS Server

The BIND DNS server is included in the Parallels Plesk Panel distribution package and can

be automatically installed by one of the automatic installation methods. For more informationabout the automatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 91). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported BIND DNS server version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Installing or upgrading the BIND DNS server manually is not recommended. The build

included in the Parallels Plesk Panel distribution package is made by Parallels and isthoroughly tested for functional performance and compatibility with Parallels Plesk Panel. Ifyou install BIND from an installation package produced by others or apply an upgradepackage produced by others to BIND that has been installed automatically by Parallels PleskPanel, the BIND server performance or its integration with Parallels Plesk Panel may becompromised.

If you want to upgrade to a later BIND version, do it by applying a Parallels Plesk Panelupgrade package that includes the newer version of BIND.






Installing and Upgrading Simple DNS Plus Server

The Simple DNS Plus server is not included in the Parallels Plesk Panel distribution package

and cannot be installed automatically.

Supported versions

For the latest supported Simple DNS Plus server application version, see your ParallelsPlesk Panel version release notes or the "Third-Party Software Supported by Parallels PleskPanel" (on page 94) section in this guide.

Manual Installation

To install Simple DNS Plus manually as Parallels Plesk Panel component, follow thesesteps:


2. Stop the old Parallels Plesk Panel DNS service.

This is necessary for the Simple DNS Plus server that is being installed to properlyregister itself in the system.

3. Obtain a Simple DNS Plus server distribution package and install the application on theParallels Plesk Panel server by running the package installer.

4. Select the HTTP API option of the Simple DNS Plus server, set the server address to127. 0. 0. 1, specify the connection parameters (port and administrator password).

5. Complete the installation of Simple DNS Plus server as Parallels Plesk Panel component

by following the general integration procedure (on page 98). The Simple DNS Plus serverentry appears in the Parallels Plesk Panel components list.

6. In the Parallels Plesk Panel, go to Home > Server Components > DNS Server > Simple DNSPlus and specify the same connection parameters (port and password) as you did on theSimple DNS Plus server.

Important: When you have installed Simple DNS Plus 5.0, make sure to enter the validlicense key prior to using the server. Otherwise (with an outdated trial key or a key fromanother server) some operations cannot be performed and the server cannot work properly.

Manual Upgrade

To upgrade the Simple DNS Plus component manually, follow these steps:


2. Obtain a Simple DNS Plus upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Simple DNS Plus component by following the generalintegration procedure (on page 98). The upgraded Simple DNS Plus component entryappears in the Parallels Plesk Panel components list.




Installing and Upgrading FTP Servers

No FTP server is included in the Parallels Plesk Panel distribution package.

All supported FTP servers can be installed as Parallels Plesk Panel components by usingmanufacturer-supplied installation packages. After running an installer program, the newlyinstalled FTP server application must be integrated with Parallels Plesk Panel by followingthe integration procedure (on page 98).

For some FTP server applications, you need to additionally configure the application orsystem for the integration procedure to be successful.

Make sure that during installation and integration of the new FTP server application thecurrent Parallels Plesk Panel FTP service is stopped. You can stop it by using the ParallelsPlesk Panel Services monitor (on page 182). This is necessary to ensure that the newlyinstalled FTP component registers itself correctly in the system.

However, if you do install your new FTP component and switch Parallels Plesk Panel to itwith the old FTP service running in the background, potential integration problems can besolved by restarting the newly installed FTP service.

This section describes installation and upgrade procedures for FTP servers supported byParallels Plesk Panel.

In this section:

Installing and Upgrading Microsoft FTP Publishing Service 6.0 .......................... 123 Installing and Upgrading Microsoft FTP Service 7.0 for Windows 2008 ............. 124 Installing and Upgrading Gene6 FTP Server ...................................................... 126 Installing and Upgrading Serv-U FTP Server ...................................................... 127 Installing and Upgrading Web Statistics Applications ......................................... 128




Installing and Upgrading Microsoft FTP Publishing Service 6.0

Microsoft FTP Publishing service is a Windows component and cannot be installed

automatically.

Supported versions

For the latest supported Microsoft FTP Publishing service application version, see yourParallels Plesk Panel version release notes or the "Third-Party Software Supported byParallels Plesk Panel" (on page 94) section in this guide.

Manual Installation

To install Microsoft FTP manually as Parallels Plesk Panel component, follow these steps:


2. Stop the old Parallels Plesk Panel FTP service.

This is necessary for the Microsoft FTP Publishing service that is being installed toproperly register itself in the system.

3. Obtain a Microsoft FTP Publishing service distribution package and install the applicationon the Parallels Plesk Panel server by running the package installer.


4. Complete the installation of Microsoft FTP Publishing service as Parallels Plesk Panelcomponent by following the general integration procedure (on page 98). The Microsoft

FTP Publishing service entry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Microsoft FTP component manually, follow these steps:


2. Obtain a Microsoft FTP Publishing service upgrade package and apply the upgrade tothe existing installation.

3. Complete the upgrade of Microsoft FTP Publishing service component by following thegeneral integration procedure (on page 98). The upgraded component entry appears inthe Parallels Plesk Panel components list.




Installing and Upgrading Microsoft FTP Service 7.0 for Windows2008

Two different versions of Microsoft FTP Service 7.0 exist. The default one is included in theWindows Server 2008 distribution package. It is essentially the older Microsoft FTPPublishing Service 6.0 that has been adapted to Windows 2008. The other Microsoft FTPService 7.0 is not included in the Windows Server 2008 distribution. You need to downloadthe FTP server distribution package from the Microsoft site in order to install it. Thisdownloadable Microsoft FTP Service 7.0 has many new features that you may want to useon your server.

If you feel confused about the differences between the default and downloadable versions,do not be. Microsoft has an excellent explanatory article about Microsoft FTP Service 7.0.Follow this link to read the article.

Microsoft FTP Service is a Windows component and cannot be installed automatically.

Supported versions

For the latest supported Microsoft FTP service application version, see your Parallels PleskPanel version release notes or the "Third-Party Software Supported by Parallels Plesk Panel"(on page 94) section in this guide.

Manual Installation

To manually install the default version of Microsoft FTP Service 7.0 that is included in theWindows 2008 distribution package follow the instructions on installing Microsoft FTP server6.0 (on page 123).

To manually install the downloadable Microsoft FTP service as Parallels Plesk Panelcomponent, follow these steps:


2. Make sure that the default Microsoft FTP service is not installed on the Parallels PleskPanel server.

If the default Microsoft FTP service is installed, uninstall it by using the Role ServicesManager of IIS 7.0. This is necessary for the Microsoft FTP service to be able to install.

3. Obtain a Microsoft FTP service 7.0 distribution package and install the application on theParallels Plesk Panel server by running the package installer.


4. Complete the installation of Microsoft FTP server as Parallels Plesk Panel component byrunning the def packagemng. exe utility in Parallels Plesk Panel.

For this, change directory to the %pl esk_bi n%directory. (By default, it is C: \ Pr ogr amFi l es\ Paral l el s \ Pl esk\ admi n\ bi n.) If Parallels Plesk Panel is installed in adifferent folder, all utilities are located at %pl esk_di r %\ admi n\ bi n. And then run thefollowing command:

defpackagemng.exe --fix --type=ftpserverThe Microsoft FTP service entry appears in the Parallels Plesk Panel components list.




Manual Upgrade

To upgrade the Microsoft FTP service component manually, follow these steps:

1.Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.

2. Obtain a Microsoft FTP upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Microsoft FTP service component by following the generalintegration procedure (on page 98). The upgraded Microsoft FTP service componententry appears in the Parallels Plesk Panel components list.




Installing and Upgrading Gene6 FTP Server

The Gene6 FTP server is not included in the Parallels Plesk Panel distribution package and


Supported versions

For the latest supported Gene6 FTP server application version, see your Parallels PleskPanel version release notes or the "Third-Party Software Supported by Parallels Plesk Panel"(on page 94) section in this guide.

Manual Installation

To install Gene6 FTP manually as Parallels Plesk Panel component, follow these steps:



This is necessary for the Gene6 FTP server that is being installed to properly registeritself in the system.

3. Obtain a Gene6 FTP server distribution package and install the application on theParallels Plesk Panel server by running the package installer.


4. Complete the installation of Gene6 FTP server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The Gene6 FTP server entry

appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Gene6 FTP component manually, follow these steps:


2. Obtain a Gene6 FTP upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of Gene6 FTP component by following the general integration

procedure (on page 98). The upgraded Gene6 FTP component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading Serv-U FTP Server

The Serv-U FTP server is not included in the Parallels Plesk Panel distribution package and


Supported versions

For the latest supported Serv-U FTP server application version, see your Parallels PleskPanel version release notes or the "Third-Party Software Supported by Parallels Plesk Panel"(on page 94) section in this guide.

Manual Installation

To install Serv-U FTP manually as Parallels Plesk Panel component, follow these steps:



This is necessary for the Serv-U FTP server that is being installed to properly registeritself in the system.

3. Obtain a Serv-U FTP server distribution package and install the application on theParallels Plesk Panel server by running the package installer.

4. Start the newly installed Serv-U FTP server application.

5. Configure the server to run as a Windows service by selecting the Run as Windows service option.

By default, the server does register as a service.

6. Complete the installation of Serv-U FTP server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The Serv-U FTP server entryappears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Serv-U FTP component manually, follow these steps:


2. Obtain a Serv-U FTP upgrade package and apply the upgrade to the existing installation.3. Complete the upgrade of Serv-U FTP component by following the general integration

procedure (on page 98). The upgraded Serv-U FTP component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading Web Statistics Applications

Only AWStats and Webalizer Web statistics application packages are included in the

Parallels Plesk Panel distribution package.

All other supported Web statistics applications can be installed as Parallels Plesk Panelcomponents by using manufacturer-supplied installation packages. After running an installerprogram, the newly installed Web statistics application must be integrated with ParallelsPlesk Panel by following the integration procedure (on page 98).

For some Web statistics applications, you need to additionally configure the application orsystem for the integration procedure to be successful.

This section describes installation and upgrade procedures for Web statistics applicationssupported by Parallels Plesk Panel.

In this section:

Installing and Upgrading Webalizer ..................................................................... 128 Installing and Upgrading AWStats ....................................................................... 129 Installing and Upgrading SmarterStats ................................................................ 130 Installing and Upgrading Urchin .......................................................................... 131

Installing and Upgrading Webalizer

The Webalizer Web statistics application is included in the Parallels Plesk Panel distributionpackage and can be automatically installed by one of the automatic installation methods. Formore information about the automatic installation methods, see "Automatic Installation ofParallels Plesk Panel Components" (on page 91). For more information about upgrademethods, see "Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported Webalizer version, see your Parallels Plesk Panel version releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Installing or upgrading Webalizer manually is not recommended. The build included in theParallels Plesk Panel distribution package cannot be upgraded. If you install Webalizer froman installation package produced by others or apply an upgrade package produced by othersto Webalizer that has been installed automatically by Parallels Plesk Panel, the Webalizerserver performance or its integration with Parallels Plesk Panel may be compromised.

If you want to upgrade to a later Webalizer version, do it by applying a Parallels Plesk Panelupgrade package that includes the newer version of Webalizer.




Installing and Upgrading AWStats

The SWStats Web statistics application is included in the Parallels Plesk Panel distribution

package and can be automatically installed by one of the automatic installation methods. Formore information about the automatic installation methods, see "Automatic Installation ofParallels Plesk Panel Components" (on page 91). For more information about upgrademethods, see "Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported SWStats version, see your Parallels Plesk Panel version releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Installing or upgrading SWStats manually is not recommended. Whether the build included inthe Parallels Plesk Panel distribution package can be manually upgraded by using themanufacturer-supplied software packages has not been tested. If you install AWStats from amanufacturer-supplied installation package or apply a manufacturer-supplied upgradepackage to AWStats that has been installed automatically by Parallels Plesk Panel, theapplication performance or its integration with Parallels Plesk Panel may be compromised.

If you want to upgrade to a later AWStats version, do it by applying a Parallels Plesk Panelupgrade package that includes the newer version of AWStats.




Installing and Upgrading SmarterStats

The SmarterStats Web statistics application is not included in the Parallels Plesk Panel

distribution package and cannot be installed automatically.

Supported versions

For the latest supported SmarterStats Web statistics application version, see your ParallelsPlesk Panel version release notes or the "Third-Party Software Supported by Parallels PleskPanel" (on page 94) section in this guide.

Manual Installation

To install SmarterStats manually as Parallels Plesk Panel component, follow these steps:

1. Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.2. Obtain a SmarterStats server distribution package and install the application on the


3. Configure the newly installed SmarterStats application: specify the administrator loginname, password and port number.

4. Complete the installation of the SmarterStats application as Parallels Plesk Panelcomponent by following the general integration procedure (on page 98). The newlyinstalled SmarterMail component entry appears inactive in the Parallels Plesk Panelcomponents list.

5. Activate the SmarterStats Web statistics component by clicking the entry and entering the

port number, administrator login name, and administrator password for the SmarterStatsapplication specified at the previous step.

The SmarterStats Web statistics component entry appears in the Parallels Plesk Panelcomponents list.

Note: When switching Parallels Plesk Panel to the SmarterStats Web statistics componentthat appears inactive in the components list, you will need to enter a valid port number, theadministrator login name, and administrator password for the entry before the switch can bemade. If you attempt to switch to SmarterStats that appears inactive in the components list,

you will be requested to enter the information.

Manual Upgrade

To upgrade the SmarterStats component manually, follow these steps:


2. Obtain a SmarterStats upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of SmarterStats component by following the general integrationprocedure (on page 98). The upgraded SmarterStats component entry appears in the

Parallels Plesk Panel components list.






Installing and Upgrading Server-Side Web ScriptingEngines

Perl, PHP 4, PHP 5, and Python scripting engine packages are included in the ParallelsPlesk Panel distribution package. Other supported scripting engines can be installed asParallels Plesk Panel components by using manufacturer-supplied installation packages. After running an installer program, the newly installed scripting engine must be integratedwith Parallels Plesk Panel by following the integration procedure (on page 98).

For some scripting engines, you need to additionally configure the engine or system for theintegration procedure to be successful.

This section describes installation and upgrade procedures for server-side Web scriptingengines supported by Parallels Plesk Panel.

In this section:

Installing and Upgrading Microsoft ASP .............................................................. 133 Installing and Upgrading ASP.NET 1.1 ............................................................... 134 Installing and Upgrading ASP.NET 2.0 ............................................................... 135 Installing and Upgrading Miva Merchant Empresa .............................................. 136 Installing and Upgrading Perl .............................................................................. 137 Installing and Upgrading PHP ............................................................................. 138 Installing and Upgrading Python ......................................................................... 141 Installing and Upgrading SSI ............................................................................... 142

Installing and Upgrading Apache Tomcat ........................................................... 143 Installing and Upgrading ColdFusion .................................................................. 144 Installing and Upgrading Microsoft FrontPage Server Extensions ...................... 146




Installing and Upgrading Microsoft ASP

The Microsoft ASP technology engine is a Windows component and cannot be installed

automatically.

Supported versions

For the latest supported Microsoft ASP version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manual Installation

To install Microsoft ASP manually as Parallels Plesk Panel component, follow these steps:


2. Obtain a Microsoft ASP distribution package and install the application on the ParallelsPlesk Panel server by running the package installer.


3. Complete the installation of Microsoft ASP technology engine as Parallels Plesk Panelcomponent by following the general integration procedure (on page 98). The Microsoft ASP component appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Microsoft ASP component manually, follow these steps:


2. Obtain a Microsoft ASP upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Microsoft ASP component by following the general integrationprocedure (on page 98). The upgraded Microsoft ASP component entry appears in theParallels Plesk Panel components list.

Note: When installed ASP component is upgraded automatically by Windows, no re-integration with Parallels Plesk Panel is required.




Installing and Upgrading ASP.NET 1.1

The Microsoft ASP.NET 1.1 technology engine is a Windows component and cannot be

installed automatically.

Supported versions

For the latest supported Microsoft ASP.NET 1.1 version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manual Installation

To install Microsoft ASP.NET 1.1 manually as Parallels Plesk Panel component, follow thesesteps:


2. Obtain a Microsoft ASP.NET 1.1 distribution package and install the application on theParallels Plesk Panel server by running the package installer.


3. Complete the installation of Microsoft ASP.NET 1.1 technology engine as Parallels PleskPanel component by following the general integration procedure (on page 98). TheMicrosoft ASP.NET 1.1 component entry appears in the Parallels Plesk Panelcomponents list.

Manual Upgrade

To upgrade the Microsoft ASP.NET 1.1 component manually, follow these steps:


2. Obtain a Microsoft ASP.NET 1.1 upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Microsoft ASP.NET 1.1 component by following the generalintegration procedure (on page 98). The upgraded Microsoft ASP.NET 1.1 component

entry appears in the Par allels Plesk Panel components list.

Note: When installed ASP.NET 1.1 component is upgraded automatically by Windows, nore-integration with Parallels Plesk Panel is required.






Installing and Upgrading Miva Merchant Empresa

The Miva Merchant Empresa engine is not included in the Parallels Plesk Panel distribution

package and cannot be installed automatically.

Supported versions

For the latest supported Miva Merchant Empresa version, see your Parallels Plesk Panelrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

To install Miva Merchant Empresa manually as Parallels Plesk Panel component, followthese steps:


2. Obtain a Miva Merchant Empresa distribution package and install the application on theParallels Plesk Panel server by running the package installer.

3. Start Parallels Plesk Panel Reconfigurator and use the Correct disk permissions option toautomatically set correct user permissions on the Miva Merchant Empresa installationfolders and files.

For help in completing this step, see "Using Parallels Plesk Panel Reconfigurator" (onpage 165).

Note: The security settings on the Miva Merchant Empresa installation folder and filesmust be configured to allow script execution on behalf of IIS user accounts. For moreinformation about IIS user account permissions, see "Windows Accounts Used by

Parallels Plesk Panel to Manage Hosted Windows Objects" (on page 18).4. Complete the installation of Miva Merchant Empresa engine as Parallels Plesk Panel

component by following the general integration procedure (on page 98). The newlyinstalled Miva Merchant Empresa component entry appears in the Parallels Plesk Panelcomponents list.

Manual Upgrade

To upgrade the Miva Merchant Empresa component manually, follow these steps:

1. Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.2. Obtain a Miva Merchant Empresa upgrade package and apply the upgrade to the existing

installation.

3. Complete the upgrade of Miva Merchant Empresa component by following the generalintegration procedure (on page 98). The upgraded Miva Merchant Empresa componententry appears in the Parallels Plesk Panel components list.




Installing and Upgrading Perl

The Perl engine is included in the Parallels Plesk Panel distribution package and can be

automatically installed by one of the automatic installation methods. For more informationabout the automatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 92). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported Perl version, see your Parallels Plesk Panel version release notes orthe "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide.

Manual Installation

To install Perl manually as Parallels Plesk Panel component, follow these steps:


2. Obtain a Perl distribution package and install the application on the Parallels Plesk Panelserver by running the package installer.


3. Complete the installation of Perl engine as Parallels Plesk Panel component by followingthe general integration procedure (on page 98). The Perl component entry appears in theParallels Plesk Panel components list.

Manual Upgrade

Caution: Several Parallels Plesk Panel components are Perl applications. When upgradingto a newer version of Perl, ensure that the currently installed Parallels Plesk Panelcomponents that depend on Perl engine are compatible with the Perl version.

To upgrade the Perl component manually, follow these steps:


2. Obtain a Perl upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of the Perl component by following the general integrationprocedure (on page 98). The upgraded Perl component entry appears in the ParallelsPlesk Panel components list.






Installing and Upgrading PHP 4

PHP 4 is included in the Parallels Plesk Panel distribution package and can be automatically

installed by one of the automatic installation methods. For more information about theautomatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 92). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported PHP 4 engine version, see your Parallels Plesk Panel release notesor the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide.

Manual Installation

To install PHP 4 manually as Parallels Plesk Panel component, follow these steps:

1. Log in to the Parallels Plesk Panel server as the administrator by using Remote Desktop.

2. Obtain a PHP 4 distribution package and install the application on a Parallels Plesk Panelserver by running the package installer.

The PHP 4 installation folder must be located in the %pl esk_di r %\ Addi t i onal folder,where %pl esk_di r %is the Parallels Plesk Panel installation folder.

3. Locate and copy the php. i ni file located in the PHP 4 installation folder (for example,C: \ Pr ogr am Fi l es\ Par al l el s\ Pl esk\ Addi t i onal \ Pl eskPHP4\ php. i ni ) to

the C: \ WI NDOWS folders on the system disk.4. Ensure that the ext ensi on_di r directive in the php. i ni file contain a valid full path to

folder where the loadable PHP extensions (modules) reside.

5. Complete the installation of PHP 4 engine as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The newly installed PHP 4component entry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the PHP4 component manually, follow these steps:1. Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.

2. Obtain a PHP4 upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of PHP4 component by following the general integrationprocedure (on page 98). The upgraded PHP4 component entry appears in the ParallelsPlesk Panel components list.




Installing and Upgrading PHP 5

PHP 5 is included in the Parallels Plesk Panel distribution package and can be automatically

installed by one of the automatic installation methods. For more information about theautomatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents" (on page 92). For more information about upgrade methods, see "ParallelsPlesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported PHP 5 engine version, see your Parallels Plesk Panel release notesor the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide.

Manual Installation

To install PHP 5 manually as Parallels Plesk Panel component, follow these steps:


2. Obtain a PHP 5 distribution package and install the application on a Parallels Plesk Panelserver by running the package installer.

The PHP 5 installation folder must be located in the %pl esk_di r %\ Addi t i onal folder,where %pl esk_di r %is the Parallels Plesk Panel installation folder.

3. Start registry editor.

4. Ensure that the HKEY_LOCAL_MACHI NE\ SOFTWARE\ PHP\ 5 registry key has the

I nFi l ePat h value set to to the full path to the PHP version installation folder (forexample, C: \ Pr ogr am Fi l es\ Par al l el s\ Pl esk\ Addi t i onal \ Pl eskPHP5).

5. Locate the php. i ni file located in the PHP 5 installation folder (for example,C: \ Pr ogr am Fi l es\ Par al l el s\ Pl esk\ Addi t i onal \ Pl eskPHP5\ php. i ni ).

6. Ensure that the ext ensi on_di r directive in the php. i ni file contain a valid full path tofolder where the loadable PHP extensions (modules) reside.

7. Complete the installation of PHP 5 engine as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The newly installed PHP 5component entry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the PHP5 component manually, follow these steps:


2. Obtain a PHP5 upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of PHP5 component by following the general integrationprocedure (on page 98). The upgraded PHP5 component entry appears in the ParallelsPlesk Panel components list.




Installing and Upgrading Python

The Python Web statistics application is included in the Parallels Plesk Panel distribution


Supported versions

For the latest supported Python version, see your Parallels Plesk Panel version releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Installing or upgrading Python manually is not recommended. The build included in the

Parallels Plesk Panel distribution package cannot be upgraded. If you install Python from aninstallation package produced by others or apply an upgrade package produced by others toPython that has been installed automatically by Parallels Plesk Panel, the Python serverperformance or its integration with Parallels Plesk Panel may be compromised.

If you want to upgrade to a later Python version, do it by applying a Parallels Plesk Panelupgrade package that includes the newer version of Python.




Installing and Upgrading SSI

The SSI engine is a Windows component and cannot be installed automatically.

Supported versions

For the latest supported Microsoft SSI version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manual Installation

To install Microsoft SSI manually as Parallels Plesk Panel component, follow these steps:


2. Obtain a Microsoft SSI distribution package and install the application on the ParallelsPlesk Panel server by running the package installer.


3. Complete the installation of Microsoft SSI technology engine as Parallels Plesk Panelcomponent by following the general integration procedure (on page 98). The MicrosoftSSI component appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the SSI component manually, follow these steps:


2. Obtain a SSI upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of SSI component by following the general integration procedure(on page 98). The upgraded SSI component entry appears in the Parallels Plesk Panelcomponents list.

Note: When SSI is upgraded automatically by Windows, no re-integration with ParallelsPlesk Panel is required.




Installing and Upgrading Apache Tomcat

The Apache Tomcat module is included in the Parallels Plesk Panel distribution package and

can be automatically installed by one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 92). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported Apache Tomcat version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Installing or upgrading Apache Tomcat manually is not recommended. The build included in

the Parallels Plesk Panel distribution package cannot be upgraded. If you install ApacheTomcat from an installation package produced by others or apply an upgrade packageproduced by others to Apache Tomcat that has been installed automatically by ParallelsPlesk Panel, the Apache Tomcat server performance or its integration with Parallels PleskPanel may be compromised.

If you want to upgrade to a later Apache Tomcat version, do it by applying a Parallels PleskPanel upgrade package that includes the newer version of Apache Tomcat.




Installing and Upgrading ColdFusion

The ColdFusion engine is not included in the Parallels Plesk Panel distribution package and


Warning: Please note that using ColdFusion engine might seriously compromise theParallels Plesk Panel server security. To increase safety of your Parallels Plesk Panel andthe server in whole, enable ColdFusion Sandbox Security feature. For more informationabout Sandbox Security, refer to ColdFusion documentation(http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=Security_4.html#1116021).

Supported versions

For the latest supported ColdFusion version, see your Parallels Plesk Panel release notes or

the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) section in thisguide.

Manual Installation

To install ColdFusion manually as Parallels Plesk Panel component, follow these steps:


2. Obtain a ColdFusion distribution package and install the application on the ParallelsPlesk Panel server by running the package installer.

When selecting Web servers and/or Web sites to configure for use with ColdFusion, enter

I nt er net I nf or mat i on Ser ver ( I I S) for Web server and Def aul t Web Si t e for IIS Web Site.

3. Start Parallels Plesk Panel Reconfigurator and use the Correct disk permissions option toautomatically set correct user permissions on the ColdFusion installation folders and files.

For help in completing this step, see "Using Parallels Plesk Panel Reconfigurator" (onpage 165).

Note: The security settings on the ColdFusion installation folder and files must beconfigured to allow script execution on behalf of IIS user accounts. For more informationabout IIS user account permissions, see "Windows Accounts Used by Parallels PleskPanel to Manage Hosted Windows Objects" (on page 18).

4. Log in to the ColdFusion Administrator and configure the ColdFusion server by followingthe ColdFusion Configuration Wizard.

5. Complete the installation of ColdFusion engine as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The newly installed ColdFusioncomponent entry appears in the Parallels Plesk Panel components list.

If you install ColdFusion 8 on 64-bit Windows before Parallels Plesk Panel, switch IIS to the32-bit mode first. To do this, follow these steps:

1. Log in to the Parallels Plesk Panel server as the administrator.

2. Click Start, click Run, type cmd, and then click OK.

http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=Security_4.html#1116021







3. Type the following command to enable the 32-bit mode:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 true

4. Obtain a ColdFusion 8 distribution package and install the application on the ParallelsPlesk Panel server by running the package installer.

During the installation confirm that ColdFusion will be working in the 32-bit mode.

5. Log in to the ColdFusion Administrator and configure the ColdFusion server byfollowing the ColdFusion Configuration Wizard.

6. After installation of Parallels Plesk Panel, complete the installation of ColdFusionengine as Parallels Plesk Panel component by following the general integrationprocedure (on page 98).

Installing ColdFusion 8 on 64-bit Windows after Parallels Plesk Panel does not require anyspecial actions.

Manual Upgrade

To upgrade the ColdFusion component manually, follow these steps:


2. Obtain a ColdFusion upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of ColdFusion component by following the general integrationprocedure (on page 98). The upgraded ColdFusion component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading Microsoft FrontPage Server Extensions

Microsoft FrontPage Server Extensions is a Windows component and cannot be installed

automatically.

Supported versions

For the latest supported Microsoft FrontPage Server Extensions version, see your ParallelsPlesk Panel version release notes or the "Third-Party Software Supported by Parallels PleskPanel" (on page 94) section in this guide.

Manual Installation

To install Microsoft FrontPage Server Extensions manually as Parallels Plesk Panelcomponent, follow these steps:


2. Obtain a Microsoft FrontPage Server Extensions distribution package and install theapplication on the Parallels Plesk Panel server by running the package installer.


3. Complete the installation of Microsoft FrontPage Server Extensions as Parallels PleskPanel component by following the general integration procedure (on page 98). MicrosoftFrontPage Server Extensions component appears in the Parallels Plesk Panelcomponents list.

Manual Upgrade

To upgrade the Microsoft FrontPage Server Extensions component manually, follow thesesteps:


2. Obtain a Microsoft FrontPage Server Extensions upgrade package and apply theupgrade to the existing installation.

3. Complete the upgrade of Microsoft FrontPage Server Extensions component by following

the general integration procedure (on page 98). The upgraded Microsoft FrontPageServer Extensions component entry appears in the Parallels Plesk Panel componentslist.

Note: When Microsoft FrontPage Server Extensions is upgraded automatically by Windows,no re-integration with Parallels Plesk Panel is required.




Installing and Upgrading Web Administration Tools

Several Web administration tool packages are included in the Parallels Plesk Panel

distribution package.

Installation of Web administration tools as Parallels Plesk Panel components by usingmanufacturer-supplied installation packages is not recommended.

This section describes installation and upgrade procedures for Web administration toolssupported by Parallels Plesk Panel.

In this section:

Installing and Upgrading phpMyAdmin ................................................................ 147

Installing and Upgrading ASP.NET Enterprise Manager ..................................... 148 Installing and Upgrading myLittleAdmin 2000 Lite .............................................. 149 Installing and Upgrading myLittleAdmin 2000 Full .............................................. 150 Installing and Upgrading myLittleAdmin 2005 ..................................................... 151

Installing and Upgrading phpMyAdmin

The phpMyAdmin Web administration tool is included in the Parallels Plesk Panel distributionpackage and can be automatically installed by one of the automatic installation methods. Formore information about the automatic installation methods, see "Automatic Installation ofParallels Plesk Panel Components" (on page 91). For more information about upgrademethods, see "Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported phpMyAdmin version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Installing or upgrading phpMyAdmin manually is not recommended. The build included in theParallels Plesk Panel distribution package is modified by Parallels and is thoroughly testedfor functional performance and compatibility with Parallels Plesk Panel. If you install

phpMyAdmin from an installation package produced by others, or if you apply an upgradepackage produced by others to phpMyAdmin that has been installed automatically byParallels Plesk Panel, the phpMyAdmin performance or its integration with Parallels PleskPanel may be compromised.

If you want to upgrade to a later phpMyAdmin version, do it by applying a Parallels PleskPanel upgrade package that includes the newer version of phpMyAdmin.

Note: If you must upgrade to a phpMyAdmin package that is not included in Parallels PleskPanel distribution package, contact Parallels Plesk Panel technical support for assistancewith the upgrade procedure.




Installing and Upgrading ASP.NET Enterprise Manager

The ASP.NET Enterprise manager is included in the Parallels Plesk Panel distribution

package and can be automatically installed by one of the automatic installation methods.Formore information about the automatic installation methods, see "Automatic Installation ofParallels Plesk Panel Components" (on page 91).

Supported versions

For the latest supported ASP.NET Enterprise manager version, see your Parallels PleskPanel version release notes or the "Third-Party Software Supported by Parallels Plesk Panel"(on page 94) section in this guide.

ASP.NET Enterprise manager can only be installed from the Parallels Plesk Paneldistribution package and cannot be upgraded. For more information about installing and

integrating Parallels Plesk Panel components included in Parallels Plesk Panel distributionpackage, see "Installing Parallels Plesk Panel Components Automatically After ParallelsPlesk Panel Has Been Installed".




Installing and Upgrading myLitt leAdmin 2000 Lite

myLittleAdmin 2000 Lite is included in the Parallels Plesk Panel distribution package and can

be automatically installed by using one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported myLittleAdmin 2000 Lite version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manually installing myLittleAdmin 2000 Lite is not recommended. myLittleAdmin should only

be installed automatically from the package included in the Parallels Plesk Panel distribution.

Manually upgrading myLittleAdmin 2000 Lite is not recommended. If you want to upgrade toa later myLittleAdmin 2000 Lite version, do it by applying a Parallels Plesk Panel upgradepackage that includes the newer version of myLittleAdmin 2000 Lite. For more informationabout upgrading Parallels Plesk Panel components included in Parallels Plesk Paneldistribution package, see "Upgrading Parallels Plesk Panel Components".

If you must upgrade to a version of myLittleAdmin 2000 Lite that is not included in a ParallelsPlesk Panel distribution package, follow these steps:

1. Obtain a ZIP distribution package for the desired myLittleAdmin 2000 Lite version.


3. Unzip the package into a directory on the server.

For example unzip the package into C: \ MLA_TEMP.

4. Make sure that myLittleAdmin 2000 Lite version included in Parallels Plesk Paneldistribution package is installed on the server.

If the installation is absent, install it by following instructions in the "Installing ParallelsPlesk Panel Components Automatically on Running Parallels Plesk Panel Servers"section.

5. Go to the C: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2000 directory anddelete the directory contents.

6. Move the contents of the C: \ MLA_TEMP directory (in which you unzipped the newermyLittleAdmin version installation files) to theC: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2000 directory.

7. Complete the upgrade of the component by following the general integration procedure(on page 98). The upgraded myLittleAdmin 2000 Lite component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading myLitt leAdmin 2000 Full

myLittleAdmin 2000 Full is included in the Parallels Plesk Panel distribution package and can

be automatically installed by using one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported myLittleAdmin 2000 Full version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manually installing myLittleAdmin 2000 Full is not recommended. myLittleAdmin should only

be installed automatically from the package included in the Parallels Plesk Panel distribution.

Manually upgrading myLittleAdmin 2000 Full is not recommended. If you want to upgrade toa later myLittleAdmin 2000 Full version, do it by applying a Parallels Plesk Panel upgradepackage that includes the newer version of myLittleAdmin 2000 Full. For more informationabout upgrading Parallels Plesk Panel components included in Parallels Plesk Paneldistribution package, see "Upgrading Parallels Plesk Panel Components".

If you must upgrade to a version of myLittleAdmin 2000 Full that is not included in a ParallelsPlesk Panel distribution package, follow these steps:

1. Obtain a ZIP distribution package for the desired myLittleAdmin 2000 Full version.




4. Make sure that myLittleAdmin 2000 Full version included in Parallels Plesk Paneldistribution package is installed on the server.


5. Go to the C: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2000Ful l directoryand delete the directory contents.

6. Move the contents of the C: \ MLA_TEMP directory (in which you unzipped the newermyLittleAdmin version installation files) to theC: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2000Ful l directory.

7. Complete the upgrade of the component by following the general integration procedure(on page 98). The upgraded myLittleAdmin 2000 Full component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading myLitt leAdmin 2005

myLittleAdmin 2005 is included in the Parallels Plesk Panel distribution package and can be

automatically installed by using one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported myLittleAdmin 2005 version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manually installing myLittleAdmin 2005 is not recommended. myLittleAdmin should only be

installed automatically from the package included in the Parallels Plesk Panel distribution.

Manually upgrading myLittleAdmin 2005 is not recommended. If you want to upgrade to alater myLittleAdmin 2005 version, do it by applying a Parallels Plesk Panel upgrade packagethat includes the newer version of myLittleAdmin 2005. For more information aboutupgrading Parallels Plesk Panel components included in Parallels Plesk Panel distributionpackage, see "Upgrading Parallels Plesk Panel Components".

If you must upgrade to a version of myLittleAdmin 2005 that is not included in a ParallelsPlesk Panel distribution package, follow these steps:

1. Obtain a ZIP distribution package for the desired myLittleAdmin 2005 version.




4. Make sure that myLittleAdmin 2005 version included in Parallels Plesk Panel distributionpackage is installed on the server.


5. Go to the C: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2005 directory anddelete the directory contents.

6. Move the contents of the C: \ MLA_TEMP directory (in which you unzipped the newermyLittleAdmin version installation files) to theC: \ I net pub\ vhost s\ sql admi n\ myLi t t l eAdmi n\ 2005 directory.

7. Complete the upgrade of the component by following the general integration procedure(on page 98). The upgraded myLittleAdmin 2005 component entry appears in theParallels Plesk Panel components list.




Installing and Upgrading Database Servers

MySQL and Microsoft SQL database server packages are included in the Parallels Plesk

Panel distribution package.

The database servers can also be installed as Parallels Plesk Panel components by usingmanufacturer-supplied installation packages. After running an installer program, the newlyinstalled database server server application must be integrated with Parallels Plesk Panel byfollowing the integration procedure (on page 98).

This section describes installation and upgrade procedures for database servers supportedby Parallels Plesk Panel.

In this section:

Installing and Upgrading Microsoft SQL Servers ................................................ 153 Installing and Upgrading MySQL Server ............................................................. 155




Installing and Upgrading Microsoft SQL Servers

Microsoft SQL Server is included in the Parallels Plesk Panel distribution package and can


Supported versions

Microsoft Data Engine (MSDE)



For the latest supported Microsoft SQL Server versions, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Manual Installation

To install Microsoft SQL Server manually as Parallels Plesk Panel component, follow thesesteps:


2. Obtain a Microsoft SQL Server distribution package and install the application on the



3. Complete the installation of Microsoft SQL Server as Parallels Plesk Panel component byfollowing the general integration procedure (on page 98). The Microsoft SQL Server entryappears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the Microsoft SQL Server component manually, follow these steps:


2. Obtain a Microsoft SQL Server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of Microsoft SQL Server component by following the generalintegration procedure (on page 98). The upgraded Microsoft SQL Server componententry appears in the Par allels Plesk Panel components list.




Warning: Manually upgrading from one Microsoft SQL server version to another (forexample, from MSDE to MS SQL 2000) is not recommended. The different versions of MSSQL server have different database structures. The databases that existed on the legacyserver will not be compatible with the upgraded version.




Installing and Upgrading MySQL Server

MySQL database server is included in the Parallels Plesk Panel distribution package and can

be automatically installed by one of the automatic installation methods. For more informationabout the automatic installation methods, see "Automatic Installation of Parallels Plesk PanelComponents". For more information about upgrade methods, see "Parallels Plesk PanelComponent Upgrade".

Supported versions

For the latest supported MySQL database server version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Warning: MySQL server up to v. 4.0 cannot be upgraded to v. 5.0 or later because the

MySQL server v.5.0 or later versions do not fully support backward compatibility with v. 4.0and earlier versions.

Manual Installation

To install MySQL database server manually as Parallels Plesk Panel component, followthese steps:


2. Obtain a MySQL database server distribution package and install the application on theParallels Plesk Panel server by running the package installer.


3. Complete the installation of MySQL database server as Parallels Plesk Panel componentby following the general integration procedure (on page 98). The MySQL componententry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade the MySQL database server component manually, follow these steps:


2. Obtain a MySQL database server upgrade package and apply the upgrade to the existinginstallation.

3. Complete the upgrade of MySQL database server component by following the generalintegration procedure (on page 98). The upgraded MySQL database server componententry appears in the Par allels Plesk Panel components list.




Installing and Upgrading Web Mail Solutions

Only Horde IMP Web mail solution is included in the Parallels Plesk Panel distribution

package.

All other supported Web mail solutions can be installed as Parallels Plesk Panel componentsby using manufacturer-supplied installation packages. After running an installer program, thenewly installed mail server application must be integrated with Parallels Plesk Panel byfollowing the integration procedure (on page 98).

For some Web mail solutions, you need to additionally configure the application or system forthe integration procedure to be successful.

The MailEnable, SmarterMail, and CommuniGate Web mail components that come as partsof the corresponding mail server distribution packages are installed along with the mailcomponents. You can switch Parallels Plesk Panel to one of these Web mail componentsonly if the corresponding mail server is selected as the current Parallels Plesk Panel mailcomponent. Such Web mail component is automatically disabled when Parallels Plesk Panelis switched to other mail component.

For example, If you have SmarterMail Web mail component enabled on your Parallels PleskPanel server when switching to a mail component other than SmarterMail, the Web mailcomponent will be disabled after the switching and no Web mail component will beautomatically enabled in its place. You need to enable another Web mail component toaccess mail on Parallels Plesk Panel server through a Web-based interface.

This section describes installation and upgrade procedures for Web mail software supportedby Parallels Plesk Panel.

In this section:

Installing and Upgrading Horde IMP ................................................................... 157 Installing and Upgrading MailEnable Web Client ................................................ 158 Installing and Upgrading SmarterMail Web Client ............................................... 159 Installing and Upgrading IceWarp Web Mail Client ............................................. 160 Installing and Upgrading CommuniGate Pro Web Client .................................... 161




Installing and Upgrading Horde IMP

The Horde IMP Web mail solution is included in the Parallels Plesk Panel distribution


Supported versions

For the latest supported Horde IMP version, see your Parallels Plesk Panel version releasenotes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94) sectionin this guide.

Installing or upgrading Horde IMP manually is not recommended. The build included in the

Parallels Plesk Panel distribution package cannot be upgraded. If you install Horde IMP froman installation package produced by others or apply an upgrade package produced by othersto Horde IMP that has been installed automatically by Parallels Plesk Panel, the Horde IMPperformance or its integration with Parallels Plesk Panel may be compromised.

If you want to upgrade to a later Horde IMP version, do it by applying a Parallels Plesk Panelupgrade package that includes the newer version of Horde IMP.




Installing and Upgrading MailEnable Web Client

Parallels Plesk Panel supports MailEnable Web Client that is installed as part of the

MailEnable Professional or MailEnable Enterprise mail components. The MailEnable WebClient component cannot be installed apart from the mail components. For information aboutinstalling the MailEnable Professional or MailEnable Enterprise mail components, see"Installing and Upgrading MailEnable Mail Server" (on page 100).

When the MailEnable Professional or MailEnable Enterprise mail component is installed, theMailEnable Web Client option is displayed in the list of Web mail components at Home > ServerComponents > Web Mail under Web Mail. The option is available only if MailEnable Professionalor MailEnable Enterprise mail server is selected as the current Parallels Plesk Panel mailcomponent. The option becomes unavailable when mail server other than MailEnableProfessional or MailEnable Enterprise is selected.

The MailEnable Web Client will be automatically disabled when Parallels Plesk Panel isswitched from MailEnable to other supported mail server.

Supported versions

For the latest supported MailEnable Web Client version, see your Parallels Plesk Panelrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

To enable MailEnable Web Client component on a Parallels Plesk Panel server, follow thesesteps:

1. Login to Parallels Parallels Plesk Panel Panel as the administrator.2. Go to Home > Server Components. The list of available Parallels Plesk Panel components is

displayed.

3. Make sure that a MailEnable Professional or MailEnable Enterprise mail server isenabled.

4. Click Web mail. The list of available Web mail components is displayed.

5. Select the MailEnable Web Client check box and click OK. The list of available ParallelsPlesk Panel components is displayed. The MailEnable Web Client entry is displayed inthe list as the currently active Web mail component.








Installing and Upgrading CommuniGate Pro Web Client

Parallels Plesk Panel supports CommuniGate Pro Web Client that is installed as part of the

CommuniGate Pro mail component. The CommuniGate Pro Web Client component cannotbe installed apart from the CommuniGate Pro mail component. For information aboutinstalling the CommuniGate Pro mail component, see "Installing and UpgradingCommuniGate Pro Mail Server" (on page 108).

When the CommuniGate Pro mail component is installed, the CommuniGate Pro Web Client option is displayed in the list of Web mail components at Home > Server Components > Web Mail under Web Mail. The option is available only if the CommuniGate Pro mail server is selectedas the current Parallels Plesk Panel mail component. The option becomes unavailable whenmail server other than CommuniGate Pro is selected.

The CommuniGate Pro Web Client will be automatically disabled when Parallels Plesk Panel

is switched from CommuniGate Pro to other supported mail server.

Supported versions

For the latest supported CommuniGate Pro Web Client version, see your Parallels PleskPanel release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

To enable CommuniGate Pro Web Client component on a Parallels Plesk Panel server,follow these steps:

1. Login to Parallels Parallels Plesk Panel Panel as the administrator.

2. Go to Home > Server Components. The list of available Parallels Plesk Panel components isdisplayed.

3. Make sure that the CommuniGate Pro mail component is enabled.

4. Click Web mail. The list of available Web mail components is displayed.

5. Select the CommuniGate Pro Web Client check box and click OK. The list of availableParallels Plesk Panel components is displayed. The CommuniGate Pro Web Client entryis displayed in the list as the currently active Web mail component.




Installing SpamAssassin Spam Filter

The SpamAssassin spam filter is included in the Parallels Plesk Panel distribution package

and can be automatically installed by one of the automatic installation methods. For moreinformation about the automatic installation methods, see "Automatic Installation of ParallelsPlesk Panel Components" (on page 91). For more information about upgrade methods, see"Parallels Plesk Panel Component Upgrade" (on page 93).

Supported versions

For the latest supported SpamAssassin spam filter version, see your Parallels Plesk Panelversion release notes or the "Third-Party Software Supported by Parallels Plesk Panel" (onpage 94) section in this guide.

Installing or upgrading SpamAssassin manually is not recommended because of potentialinter-module inconsistencies between SpamAssassin's and Perl's modules.

If you want to upgrade to a later version of SpamAssassin, do it by applying a Parallels PleskPanel upgrade package that includes the newer version of SpamAssassin.




Installing stunnel

The stunnel application is included in the Parallels Plesk Panel distribution package and can


Supported versions

For the latest supported stunnel application version, see your Parallels Plesk Panel versionrelease notes or the "Third-Party Software Supported by Parallels Plesk Panel" (on page 94)section in this guide.

Manual Installation

To install the stunnel application manually as a Parallels Plesk Panel component, followthese steps:


2. Obtain the stunnel distribution package and install the application on the Parallels PleskPanel server by running the package installer.


3. Complete the installation of stunnel as Parallels Plesk Panel component by following the

general integration procedure (on page 98). The stunnel component entry appears in thecomponents list in Parallels Plesk Panel.

Manual Upgrade

To upgrade the stunnel component manually, follow these steps:


2. Obtain a stunnel upgrade package and apply the upgrade to the existing installation.

3. Complete the upgrade of the stunnel component by following the general integrationprocedure (on page 98). The upgraded stunnel component entry appears in the ParallelsPlesk Panel components list.




Using Parallels Plesk Billing

You can use Parallels Plesk Billing with your Parallels Plesk Panel for Windows, only if you

also have at least one Parallels Plesk Panel for Linux/Unix server. Parallels Plesk Billing isnot included into the Parallels Plesk Panel for Windows distribution package. It is includedinto the Parallels Plesk Panel for Linux/Unix distribution package and can be installed on aParallels Plesk Panel for Linux/Unix server as a Parallels Plesk Panel component. ThenParallels Plesk Billing can be integrated with other Parallels Plesk Panel servers, includingParallels Plesk Panel for Windows servers. After integration with your Parallels Plesk Panelfor Windows server, Parallels Plesk Billing can be used for processing orders and paymentsof your customers.



Parallels Plesk Panel Reconfigurator is a stand-alone Windows application included inthe Parallels Plesk Panel distribution package. Parallels Plesk Panel Reconfigurator isused to automatically perform multiple coordinate changes in Parallels Plesk Panelserver configuration. For example, when you move large chunks of hosted content from

one disk to another, configuration settings for different software, domains, folders andfiles may have to be reset to conform to the changes. Similarly, when you changeParallels Plesk Panel server IP addresses, you need to make sure that configuration ofall affected domains and software is appropriately changed.

By using Parallels Plesk Panel Reconfigurator you can perform the following tasks:

Changing Parallels Plesk Panel server IP addresses. You may need to use thisfeature when, for instance, you are moving your Parallels Plesk Panel server to anew datacenter, and need to reconfigure the Parallels Plesk Panel server to run onnew IP addresses.

Moving the directory where virtual hosts reside to another location on the same or

another partition. You can use this feature to move the virtual hosts to a new, largervolume when disk space on the current partition is running out.

Moving the directory where Parallels Plesk Panel backup files are stored to anotherlocation on the same or another partition. You can use this feature when, forinstance, there is insufficient disk space on the current partition to house newbackup files, and you want to move them all to a new, larger volume.

Moving the directories that house mail content to another location on the same oranother partition. You can use this feature when there is insufficient amount of diskspace on the current partition to serve a larger amount of mailboxes, and you wishto move them all to a new larger volume.

Repairing Parallels Plesk Panel installation. This feature can be used to correct

various problems caused by misconfiguration of the Parallels Plesk Panel server,one of its services, or file and folder security settings. For example, you can correctmail delivery issues caused by the changes made to DNS server addresses orrestore system accounts used by Parallels Plesk Panel to manage the server.

Correcting disk user permissions. This feature can be used to reset securitysettings on files and folders on Parallels Plesk Panel server disks when a securitymisconfiguration occurs that causes security vulnerability or software malfunction.

Switching the database server engine used by Parallels Plesk Panel.

Check component and folder permissions. This feature can be used to check andfix permissions on files and folders while installing and configuring third-partyapplications (such as ColdFusion, MIVA, etc.) in Parallels Plesk Panel.

Changing the Web server engine used by your server .

C H A P T E R 7

Using Parallels Plesk Panel

Reconfigurator






Changing IP Addresses on Parallels Plesk

Panel ServerYou can switch from an existing IP address on your Parallels Plesk Panel server to anewly created IP address or to another existing address.

During life-time of a Parallels Plesk Panel server, you may need to replace IPaddresses used for hosting with other IP addresses. Replacing all old IP addresseswith new ones may be necessary when moving a Parallels Plesk Panel server onto anew network. More often, you may need to introduce more subtle changes in yourserver's IP address pool. For example, you may need to free up one or more IPaddresses currently used for hosting on the Parallels Plesk Panel server. This will allow

you to use the addresses for other purposes or to eliminate them from the server's IPpool altogether.

Every time you replace an IP address with a new one on a Parallels Plesk Panelserver, you need to reconfigure Parallels Plesk Panel and various Parallels Plesk Panelservices to use the new IP address instead of the replaced one.

You can switch from one IP address on a Parallels Plesk Panel server to another andautomatically reconfigure the Parallels Plesk Panel and all hosting services on theParallels Plesk Panel server to use the new address by using the Change Server IP Addresses feature.

Note: By using this feature, you can only replace one IP address with another. Youcannot migrate a group of select domains from one or more IP addresses to a new IPaddress.

To change from one IP address on a Parallels Plesk Panel server to another, followthese steps:

1. Start Parallels Plesk Panel Reconfigurator and select the Change Server IP Addresses option. The IP Addresses Reconfiguring window opens.

2. Under Select the IP addresses to be changed, select by using check boxes one or moreIP addresses that you want to change to other IP addresses.

To view the list of domains hosted on particular IP address, click the IP addressentry to highlight it. The list of hosted domains using the highlighted IP address isdisplayed in a window to the right.

3. Map each selected to an IP address of your choice.

1. To map a selected address, click on the selected address entry. The entry ishighlighted.

2. Select the address to map to:

To map to an existing IP address, select Existing Address option and thenselect an existing address entry. The entry information is displayed in theMapping Information column for the selected IP address entry under Select theIP addresses to be changed.






Changing Parallels Plesk Panel Backup

Data LocationBy using Parallels Plesk Panel Reconfigurator you can move the Parallels Plesk Panelbackup files storage directory to another location on the same or another partition. Usethis feature when disk space is insufficient on the current partition to house new backupfiles, and you want to move them all to a new, larger volume.

To change location of the backup files directory, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator and select the Change Plesk Backup Datalocation option.

2. Specify the destination directory name. If the directory does not exist, it will becreated.

3. Click Next. During this operation all Parallels Plesk Panel services will be restarted.

Changing Parallels Plesk Panel Mail DataLocation

You can move the directories that store mail content to another location on the same oranother partition. Use this option when disk space is insufficient on the current partitionto serve larger data volume or amount of mailboxes and you want to move all mailcontent to a new, larger volume.

To move the mail content directories to another location, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator and select the Change Plesk Mail Datalocation option.

2. Specify the destination directory name. If the directory does not exist, it will be

created.

3. Click Next. During this operation Parallels Plesk Panel mail and Parallels PleskPanel services will be restarted.



170 Using Parallels Plesk Panel Reconfigurator

Repairing Parallels Plesk Panel

InstallationBy using Parallels Plesk Panel Reconfigurator you can check and repair Parallels PleskPanel installation that is malfunctioning due to misconfiguration of one or more of itscomponents.

The following problems can be identified and corrected by using the Repair PleskInstallation option:

problems with mail delivery caused by user-made changes in DNS serveraddresses

misconfigurations of system user accounts or groups used by Parallels Plesk Panelto access system objects

Parallels Plesk Panel services malfunctions

misconfigurations in user access permissions for files and folders on Parallels PleskPanel disks and hosting folders

miscalculations of discspace usage by individual domains and subdomains

To check and repair Parallels Plesk Panel installation, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator and select the Repair Plesk installation option.

2. Select repair actions that you want to perform by using check boxes. See thefollowing table for explanation of each check and repair option.

3. Click Check. Parallels Plesk Panel Reconfigurator automatically performs thefollowing tasks:

corrects the problems with mail delivery caused by the changes made to DNSserver addresses

restores system accounts used by Parallels Plesk Panel to manage server

checks and corrects Parallels Plesk Panel settings and system account used to

run and manage various Parallels Plesk Panel services

resets security settings for files and folders

checks and corrects ownership of files and folders and recalculates disc spaceusage by individual domains and subdomains accordingly

Check & Repair options

Option Description

Plesk Mail Server DNS settings from network adapters are applied to Parallels Plesk Panelmail server; network name l ocal host is added to the relay list.






Plesk Virtual HostsSecurity

For each object, Reconfigurator first checks if the object's DACLcorresponds to the object's security rules contained in Parallels PleskPanel security files. (For detailed information about security rules, see"Security Metadata Files and Templates" (on page 24).) IfReconfigurator cannot resolve a SID, it removes all ACEs corresponding

to the SID from the DACL. If one or more SIDs specified by the securityrules are missing in the DACL or specific access rights in the ACEs donot match those determined by the security rules, Reconfiguratorupdates the existing DACL.To enable this, Reconfigurator recreates allmissing user accounts for which ACEs must be added to the DACL.Depending on the object type, Reconfigurator uses different accessrights matching criteria and DACL update methods.

For domain and subdomain root folders, after all unresolved SIDs' ACEsare removed from a DACL, Reconfigurator check if access rights definedin the existing DACL exactly match those defined by the security rules. Ifa mismatch is found (DACL contains SIDs that are not found in thesecurity rules, required SIDs are missing, or SID's access rights are

different), Reconfigurator compiles a new DACL based on the currentParallels Plesk Panel security rules and completely overwrites theexisting DACL.

For objects other than domain and subdomain root folders, after allunresolved SIDs' ACEs are removed from a DACL, Reconfigurator onlychecks if all access rights defined by the security rules are found in theDACL. If some access rights are missing from the DACL, Reconfiguratormerges the ACEs remaining in the existing DACL with the ACEs definedbased on the security rules.

Plesk Database Reconfigurator cleans up the Repository table of the Parallels PleskPanel internal database and checks application vaults' state.

Plesk Quotas Parallels Plesk Panel Reconfigurator checks that folders and files in adomain folder have proper ownership - are owned by to thecorresponding domain or subdomain user account or a web user of thecorresponding domain. (If they are owned by other accounts, ParallelsPlesk Panel may report wrong disk space usage by the correspondinghosing accounts).




Restoring Disk User Permissions

Maintaining proper user permissions on Windows objects on Parallels Plesk Paneldisks is necessary to ensure the maximum security of Parallels Plesk Panel serverswhile enabling full functionality of hosted content. Misconfiguration of object securitysettings on Parallels Plesk Panel server disks may result in hosted content malfunction.

By using Parallels Plesk Panel reconfigurator, you can restore disk security settingsbased on the security rules specified in the Di skSecur i t y. xml file and other xmlfiles found in the %pl esk_di r %\ et c\ Di skSecur i t y directory.

Note: You can change the disk security rules in the xml files found in the%pl esk_di r %\ et c\ Di skSecur i t y directory as desired before running the

Reconfigurator. For more information about Parallels Plesk Panel security policies andconfiguring security on Parallels Plesk Panel servers, see "Administering SecuritySettings on Windows Objects" (on page 20).

To restore the disk user permissions according to the Parallels Plesk Panel securitymetadata files, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator and select the Correct disk permissions option.

2. Using check boxes in the Volume column, select the drives for which you want torestore the user permissions.

3. Click Set to set the correct permissions for the selected drives. This operation maytake some time.

For information about the default user permissions on Parallels Plesk Panel serverdisks, see "Default User Permissions on Disks" (on page 15).




Switching Parallels Plesk Panel Database

Server EngineParallels Plesk Panel can use several different database engines to access theParallels Plesk Panel internal database. At any time you can change the databaselocation and select to use different database engine to access the database. In order toswitch from one database server to another you need to migrate the database to a newdatabase server and configure Parallels Plesk Panel to connect to the server to accessthe database. The following database servers are supported by Parallels Plesk Panel:

MySQL

Microsoft Jet

Microsoft SQL

You can use the Switch Database Provider option in Reconfigurator to switch betweendatabase servers to access Parallels Plesk Panel internal database. Reconfigurator willmigrate the Parallels Plesk Panel internal database to a new database server andconfigure Parallels Plesk Panel to access the database by means of the new databaseserver.

Two methods exist for switching between database servers: by using theReconfigurator GUI (on page 175) and by using the command-line interface (on page

176). This chapter describes both of these methods.

In this section:

Using GUI to Switch Between Database Servers ............................................... 175 Using Command-Line Interface to Switch Between Database Servers .............. 176




Using GUI to Switch Between Database Servers

You can migrate Parallels Plesk Panel internal database to new database engine and

configure Parallels Plesk Panel to access the database at the database server.

To switch between database servers through Reconfigurator GUI, follow these steps:

1. Run Parallels Plesk Panel Reconfigurator.

2. Select the Switch DB provider option.

3. Enter the supported database server engine type in the Server type field.

4. Enter the server address (IP address or host name) and, if different from default,port number in the corresponding fields.

(The field are available only if MySQL or MSSQL server type is entered.)

5. Enter the new server administrator's login and password.

Note: If you switch to MySQL database in Parallels Plesk Panel 8.2 or higher, notethe following:* if MySQL database was not used as a Parallels Plesk Panel database providerbefore, MySQL administrator's login is 'admi n' and password is 'set up'.* if MySQL database was already used as a Parallels Plesk Panel databaseprovider in the past, you should use MySQL administrator's login and passwordwhich were used before changing of the Parallels Plesk Panel database providerfrom MySQL to another server type.

6. Under Create a new database to locate data in, enter information about the new

Parallels Plesk Panel database that the data will be migrated to:

1. In the Database field, enter the new database name.

For Jet databases, you need to specify the name of the database file. Forexample,

psa_new. mdb

The new database will be created in the %pl esk_di r %\ admi n\ db directory, where the Parallels Plesk Panel installation directory.

For MySQL and MSSQL databases, you need to specify only the databasename on the server. For example:

psa_new

2. In the Database user name field, enter user name to be used by Parallels PleskPanel to access the migrated database.

3. In the Password and Confirm password fields, type the database user password.

Warning! By changing the database user password, you also change ParallelsPlesk Panel administrator's password for accessing Parallels Plesk Panel. ParallelsPlesk Panel administrator's password and Parallels Plesk Panel database userpassword are always the same (although user login names can be different).

To change Parallels Plesk Panel MySQL database user password, follow these steps:




1. Go to %Pl esk_di r %\ MySQL\ Dat a.

2. Open the my. i ni file and add to the [ Pl eskSQLSer ver ] section the followingline:

ski p- gr ant - t abl e

3. Go to Administrative Tools > Computer Management and start Parallels PleskPanel SQL server.

4. Go to command line and perform the following:

cd %Pl esk_di r %\ mysql \ bi n

mysql - P8306

mysql > use mysql

mysql > updat e user set passwor d=passwor d( ' <as your Pl eskadmi n passwor d>' ) where user ="admi n";

5. Go to %Pl esk_di r %\ MySQL\ Dat a.

6. Erase from the [ Pl eskSQLSer ver ] section of the my. i ni file the following line:

ski p- gr ant - t abl e

7. Restart Parallels Plesk Panel SQL server.

Using Command-Line Interface to Switch BetweenDatabase Servers

You can migrate Parallels Plesk Panel internal database to a new database server andconfigure Parallels Plesk Panel to access the database at the database server.

The command for switching the Parallels Plesk Panel database servers has thefollowing syntax:

reconfigurator --switch-plesk-database --new-provider=<provider name>--host=<host name> --db=<database name> --login=<database user login>--password=<database user password> [--password=<port number>] [--admin-login=<administrator login>] [--admin-password=<administrator password>]

See the following table for the command options descriptions.

Options

Option Parameter Description Comment

- - new- pr ovi der J et | MSSQL |MySQL

The newdatabase servertype





- - db <databasename>

name of theParallels Plesk

Panel databaseon the newdatabase server

For Jet databases, you need tospecify full path to a new database

to be created. To ensure thatproper user permissions areassigned to the database file,create the file in the the%pl esk_di r %\ admi n\ db directory, where %pl esk_di r %isthe Parallels Plesk Panelinstallation directory.

For example,

"- - db=c: \ Pr ogr amFi l es\ Para l l el s \ Pl esk\ admi n\ db\ psa_new. mdb"

For MySQL and MSSQLdatabases, you need to specifyonly the database name on theserver. For example:

" - - db=psa_new"

- - host <host name> database serverIP address orhost name

Jet databases are always local.

- - l ogi n <user login

name>

Parallels Plesk

Panel databaseuser name usedby Parallels PleskPanel

- - password <userpassword>

Parallels PleskPanel databaseuser name usedby Parallels PleskPanel

- -por t <port number> New databaseserver portnumber. This

parameter isoptional.

define port number if the newdatabase server uses a non-default port number

- - admi n- l ogi n <administratorlogin name>

Database serveradministratorlogin name. Thisparameter isoptional.

Define the server administratorcredentials if you want a newdatabase user created with theuser login name and password





- - admi n-passwor d

<administratorpassword>

Database serveradministrator

password. Thisparameter isoptional.

specified by the - - l ogi n and- - passwor d options. If the

options are omitted from thecommand, Parallels PleskPanel will be configured to usethe database user credentialsspecified by the - - l ogi n and- - passwor d options, no newuser will be created for thedatabase.

To switch between database servers through command-line interface, follow these

steps:

1. Log in Parallels Plesk Panel server as a user with administrator rights by usingRemote Desktop.

2. Start cmd. exe.

3. Change directory to the %pl esk_di r %\ admi n\ bi n\ folder (where %pl esk_di r %is the system variable defining the folder where Parallels Plesk Panel is installed).

4. Execute the server switch command.

For example, to migrate the Parallels Plesk Panel internal database to a newlocation accessible at c: \ Pr ogr am

Fi l es\ Par al l el s\ Pl esk\ admi n\ db\ psa3. mdb, make it accessible throughthe Jet database engine installed on the Parallels Plesk Panel server (local host),and instruct Parallels Plesk Panel to use an existing user credentials (login namedbadmi n and password dbadmi npass) to access the database, use the followingcommand:

reconfigurator --switch-plesk-database --new-provider=Jet --host=localhost “--db=c:\ProgramFiles\Parallels\Plesk\admin\db\psa3.mdb” --login=dbadmin -- password=dbadminpass

Warning! By changing the database user password, you also change Parallels PleskPanel administrator's password for accessing Parallels Plesk Panel. Parallels Plesk

Panel administrator's password and Parallels Plesk Panel database user password arealways the same (although user login names can be different).




Checking Component and Folder

PermissionsParallels Plesk Panel sets permissions to all server partitions to prevent users frompenetrating each other or accessing unknown third-party software. Due to this ParallelsPlesk Panel components or third-party applications used with Parallels Plesk Panel canhave insufficient permissions for proper operation. The Check component and folderpermissions option can be used to check and fix permissions on files and folders afterinstalling third-party applications on the Parallels Plesk Panel server. With this option,you do not have to scan the whole disk, but you can check and fix permissions just forone or several applications, or for a selected partition or directory.

To check and fix permissions for third-party applications, follow these steps:

1. Start Parallels Plesk Panel Reconfigurator and select the Check component and folderpermissions option.

2. Select one or several Parallels Plesk Panel components from the list or select thepartition where the third-party application is installed in the Path to check field.

3. Click Check.

View the progress at the bottom of the form. As soon as the check is complete andthe permissions are fixed, you are taken back to the main window of Parallels PleskPanel Reconfigurator.





Parallels Plesk Panel provides only limited tools to manage a Tomcat server from theGUI. This section describes additional Tomcat server management tasks that mayhave to be executed to restore proper Tomcat functioning.

In this chapter:

Changing Tomcat Java Connector Ports ............................................................ 181

Changing Tomcat Java Connector Ports

The default port numbers for Coyote and Warp connectors in Parallels Plesk Panel are9080 and 9008.

If you want Tomcat Java to work on other ports (e.g. 8090 and 8009), you shouldconnect to Parallels Plesk Panel database and add two parameters to the database asin the following SQL query example:

insert into misc (param,val) values ('coyote_connector_port', '8090');insert into misc (param,val) values ('warp_connector_port', '8009');

Alternatively, you can use the dbcl i ent . exe utility to add the information to theParallels Plesk Panel database. For information about using the dbcl i ent . exe utility,consult Parallels Plesk Panel for Windows Command Line Interface Reference.

Note: It is recommended that you change the Tomcat Java ports right after ParallelsPlesk Panel is installed on server, or prior to enabling the Tomcat Java service for yourdomains.

C H A P T E R 8

Managing Tomcat Service



You can monitor the status of your Parallels Plesk Panel server without logging in toParallels Plesk Panel. In order to do this, you need to access your server's OS desktopeither directly or by using the Remote Desktop feature.

Parallels Plesk Panel Services Monitor is loaded automatically every time ParallelsPlesk Panel starts. To manage the status of Parallels Plesk Panel services, open theParallels Plesk Panel Services Monitor by double clicking its icon in the system tray.The look of the icon depends on the state of crucial Parallels Plesk Panel services: the

icon means that all crucial Parallels Plesk Panel services are functioning, and theicon means that some crucial Parallels Plesk Panel services are stopped or notworking correctly.

Once you open the Parallels Plesk Panel Services Monitor, you can see the status of

all vital Parallels Plesk Panel services. The icon shows that a corresponding service

is working correctly, and the icon shows that the corresponding service is stoppedor is not working correctly.

To stop a service, select the service by using the corresponding check box and clickStop.

To restart a service, select the service by using the corresponding check box and clickRestart.

To start a service, select the service by using the corresponding check box and clickStart.

Note. You can use Select All and Clear All buttons to select or clear all available check

boxes.

To refresh the list of services and their respective statuses, click Refresh.

To remove all information about Parallels Plesk Panel sessions from Parallels PleskPanel database and disconnect all users from Parallels Plesk Panel, click DeleteSessions. This is useful when you need to restart Parallels Plesk Panel, but some usersare still connected to it, and you want to avoid possible data loss or files corruption.

Note. You can also start, stop, restart services and delete sessions by right-clicking theParallels Plesk Panel Services Monitor icon and selecting the required option from themenu.

To hide the Parallels Plesk Panel Services Monitor back in the system tray, click Hide.

C H A P T E R 9

Monitoring Server Status with Parallels

Plesk Panel Services Monitor



You specify your server's host name during your very first login to Parallels PleskPanel. If you want to change the host name later, you can do it through Parallels PleskPanel.

Note. Specifying an invalid host name will result in unpredictable Parallels Plesk Panelbehavior and server malfunction.

To change your server's host name, follow these steps:

1. Log in to Parallels Plesk Panel.


3. Click System Preferences.

4. Enter the new host name in the Full hostname field.

5. This should be a fully qualified host name, but without an ending dot (for example,host . exampl e. com).

6. Click OK.

C H A P T E R 1 0

Changing Your Server's Host Name



To create custom Parallels Plesk Panel title bar text, follow these steps:

1. Connect to the Parallels Plesk Panel database (psa).

2. Run the following query:

insert into misc(param, val) values('custom_title', 'My Custom Title')

Where 'My Custom Title' is the Parallels Plesk Panel custom title bar text you wantto set.

To change custom Parallels Plesk Panel title bar text, follow these steps:



update misc set val = 'New My Custom Title' where param='custom_title'

Where 'My Custom Title' is the Parallels Plesk Panel custom title bar text you wantto set.

To delete custom Parallels Plesk Panel title bar text, follow these steps:



delete from misc where param='custom_title'

Note: You can use the dbcl i ent . exe utility to add the information to the ParallelsPlesk Panel database. For information about using the dbcl i ent . exe utility, consultParallels Plesk Panel for Windows Command Line Interface Reference.

C H A P T E R 1 1

Customizing Parallels Plesk Panel Title

Bar Text



The link to Parallels support in your customer's Parallels Plesk Panel administrator'spanel can be customized so that your customer's support requests are sent to youinstead of Parallels support.

If you act as a reseller, you might provide a whole Parallels Plesk Panel server to yourcustomer so that your customer acquires access to the Parallels Plesk Panel server

administrator's panel. In this case you might want your customers contact you, notParallels, for support. By default, when a Parallels Plesk Panel server administratorclicks Home > Support button, they are redirected to the Parallels Plesk Panel OnlineServer Support form at the Parallels Web site, with a number of parametersautomatically collected and filled in, such as the Parallels Plesk Panel administrator'sname, company, e-mail, phone, product key number, operating system details,Parallels Plesk Panel version, and Parallels Plesk Panel build. You can customize thelink to the Parallels Plesk Panel support form, so that your customers' support requestswith the same automatically pre-collected parameters could be sent to you instead ofthe Parallels support team.

The Parallels Plesk Panel support form link location is defined by the suppor t _url

parameter in the psa. mi sc table of the Parallels Plesk Panel database. If thesuppor t _url parameter is absent or empty, the customer upon clicking the Home >Support button is redirected to Parallels support through the following URL:

' ht t ps: / / r egi st er . par al l el s. com/ suppor t / f or m. php?sv=' .ur l encode( ser i al i ze( $val ) )

where $val is an associative PHP array containing the following parameters:

f i r st Name, the Parallels Plesk Panel administrator's contact name;

company, the Parallels Plesk Panel administrator's company name;

emai l , the Parallels Plesk Panel administrator's e-mail address;

phone, the Parallels Plesk Panel administrator's phone number;

keyNumber , the Parallels Plesk Panel license number used on the server;

oper at i ngSystem, the operating system installed on the server;

PSAVersi on, the version number of the Parallels Plesk Panel software;

PSABui l d, the build number of the Parallels Plesk Panel software;

PSAI nst Type, the type of Parallels Plesk Panel software installation.

C H A P T E R 1 2

Customizing Link to Parallels Plesk

Panel Support



186 Customizing Link to Parallels Plesk Panel Support

By modifying the suppor t _url parameter in the psa. mi sc table of the ParallelsPlesk Panel database, you can perform the following tasks:

Configuring the Support button of your customer's Parallels Plesk Panel to open

the support form page on your web site with the above listed parameters pre-collected (see page 187);

Configuring the Support button of your customer's Parallels Plesk Panel to openthe compose e-mail form of your customer's mail client with your support e-mailaddress specified in the address line and the above listed parameters pre-collected (see page 189).

In this chapter:

Creating Link to Support Form on Your Site ....................................................... 187 Creating Link to Compose E-mail Message ........................................................ 189




Creating Link to Support Form on Your

SiteThis option allows you to modify the link to Parallels Plesk Panel support, so that byclicking the Home > Support button in the Parallels Plesk Panel administrator's panelyour customers are taken to the Parallels Plesk Panel support form on your web site.The customer's contact details and Parallels Plesk Panel server information will beautomatically collected and filled into the form. Make sure your Parallels Plesk Panelsupport page is properly configured to accept these pre-collected parameters.

You can customize the link to Parallels Plesk Panel support by specifying the URL ofthe Parallels Plesk Panel support form on your web site in the suppor t _url

parameter of the psa. mi sc table of the Parallels Plesk Panel database. The pre-collected information about your customer's Parallels Plesk Panel server will be addedto the specified URL in the following way:

' sv=' . ur l encode( ser i al i ze( $val ) )

where $val is an associative array of the following parameters:

f i r st Name, the Parallels Plesk Panel administrator's contact name;

company, the Parallels Plesk Panel administrator's company name;

emai l , the Parallels Plesk Panel administrator's e-mail address;

phone, the Parallels Plesk Panel administrator's phone number;

keyNumber , the Parallels Plesk Panel license number used on the server;

oper at i ngSystem, the operating system installed on the server;

PSAVersi on, the version number of the Parallels Plesk Panel software;

PSABui l d, the build number of the Parallels Plesk Panel software;

PSAI nst Type, the type of Parallels Plesk Panel software installation.

To ensure the Parallels Plesk Panel support page of your site is configured properly,consider the following:

Your Parallels Plesk Panel support page will accept the sv variable through theGET method. The value of this variable is a serialized associative array of pre-collected parameters.

You can get the array of parameters on your web site page in the following way:$params = unserialize($_GET['sv']);

You can address any parameter of this array in the following way:$params['firstName']$params['company']

...



188 Customizing Link to Parallels Plesk Panel Support

To make the Support button of the Parallels Plesk Panel administrator's panel open theParallels Plesk Panel support form on your web site, follow these steps:



If the suppor t _url parameter is absent, run:

insert into misc(param, val) values('support_url','https://example.com/support')

Where 'https://example.com/support' is the URL of the Parallels Plesk Panelsupport page on your web site.

If the suppor t _url parameter already exists, run:

update misc set val = 'https://example.com/support' where param ='support_url'

Where 'https://example.com/support' is the URL of the Parallels Plesk Panelsupport page on your web site.

Note: You can use the dbcl i ent . exe utility to add the information to the ParallelsPlesk Panel database. For information about using the dbcl i ent . exe utility, consultParallels Plesk Panel for Windows Command Line Interface Reference.




Creating Link to Compose E-mail

MessageThis option allows you to modify the link to Parallels Plesk Panel support, so that byclicking the Home > Support button in the Parallels Plesk Panel administrator's panelyour customers are offered to compose an e-mail with your support address alreadyspecified in the address line. The customer's contact details and Parallels Plesk Panelserver information will be automatically collected and included in the message body.

You can customize the link to Parallels Plesk Panel support by specifying your e-mailaddress in the suppor t _url parameter of the psa. mi sc table of the Parallels PleskPanel database.

To make the Support button of the Parallels Plesk Panel administrator's panel open thecompose e-mail page with your support e-mail address, follow these steps:



If the suppor t _url parameter is absent, run:

insert into misc(param, val) values('support_url','mailto:[email protected]')

Where '[email protected]' is the e-mail address where you want yourcustomers' support requests to be sent.

If the suppor t _url parameter already exists, run:

update misc set val = 'mailto:[email protected]' where param ='support_url'

Where '[email protected]' is the e-mail address where you want yourcustomers' support requests to be sent.

Note: You can use the dbcl i ent . exe utility to add the information to the Parallels

Plesk Panel database. For information about using the dbcl i ent . exe utility, consultParallels Plesk Panel for Windows Command Line Interface Reference.



RIPE recommends using YYYYMMDDNN format, where YYYY is year (four digits), MMis month (two digits), DD is day of month (two digits) and nn is version per day (twodigits).

To change DNS zone serial number format, follow these steps:



insert into misc(param, val) values('SOA_SERIAL_MODE', 'YYYYMMDDnn')

To revert back to old DNS zone serial number format, follow these steps:



delete from misc where param='SOA_SERIAL_MODE'

Note: you can use the dbcl i ent . exe utility to add the information to the ParallelsPlesk Panel database. For information about using the dbcl i ent . exe utility, consultParallels Plesk Panel for Windows Command Line Interface Reference.

C H A P T E R 1 3

Changing DNS Zone Serial Number

Format



You can restore your mail server functionality in cases when errors appear concerningthe mail server misconfiguration or its mismatching with the Parallels Plesk Panelinternal database. This purpose is served by an internal Parallels Plesk Panel utilitymchk. exe residing at %pl esk_di r %admi n\ bi n\ . The utility restores the mailserver configuration using the Parallels Plesk Panel database data.

Note: The utility restores only configuration of the mail server selected as default inHome > Server Components.

In general, mchk. exe matches the mail server configuration with Parallels Plesk Paneldatabase. In case when you execute mchk. exe - - al l - - f i x- al l , the utility resetsforcedly the mail server configuration the following way: it deletes all existingconfiguration files of the mail server (leaving its content) and then creates themaccordingly to Parallels Plesk Panel database.

Warning: Use - - f i x- al l option only if the mail server's configuration files are somuch corrupt that the mail server itself cannot work with them properly and executingmchk.exe with other options does not solve the problem.

Usage: mchk. exe [options]

Available options

Option Parameter Action Example

- - al l Checks andrestores server-wide mail settingsand mail settingsfor all domains

mchk. exe - - al l

- - f i x- al l Resets forcedly

server-wide anddomain's mailsettings

mchk. exe - - al l - -

f i x- al l

- - domai n - - domai n- name Checks andrestores mailsettings for aspecified domain

mchk. exe - - domai n -- domai n-name=exampl e. com

- - al l - domai ns Checks andrestores mailsettings for all

mchk. exe - - al l -domai ns

- - gl obal - Checks and mchk. exe - - gl obal -

C H A P T E R 1 4

Restoring Mail Configuration



192 Restoring Mail Configuration

set t i ngs restores onlyserver-wide mailsettings

set t i ngs

Note: This utility does not have any help reference, and executing it with argumentslike / ? will simply start restoring of mail configuration.





Microsoft SQL Server Desktop Engine (MSDE) is a database platform, a toned downversion of Microsoft SQL Server 2000 which is free for non-commercial use as well ascertain limited commercial use.

To access MSDE over a network, the database engine must be configured to usespecific network transports supported by SQL. The following network transports usedby SQL can be used by MSDE for network connections:

Named Pipes

TCP/IP

Multiprotocol

NWLink IPX/SPX

ApppleTalk

Banyan VINES

Use the Regkey method to enable one or more network transports to be used for

MSDE connections:

Warning: Serious problems might occur if you modify the registry incorrectly by usingRegistry Editor or by using another method. These problems might require that youreinstall your operating system. Modify the registry at your own risk.

For example, to enable use of the Named Pipes and TCP/IP protocols by using theRegkey method, follow these steps:

1. Login to the Windows Server as administrator.

2. Click Start, and then click Run.

3. In the Run dialog box, type r egedi t , and then click OK. This will start RegistryEditor.

4. Locate the HKEY_LOCAL_MACHI NE\ SOFTWARE\ Mi cr osof t \ MSSQLSERVER\MSSQLSERVER\ SuperSocket NetLi b\ Protocol Li st registry key. This key willhouse the network transport names MSDE is configured to use. Specify thefollowing value string for the key:

np, t cp

5. Quit Registry Editor.

C H A P T E R 1 6

Configuring MSDE Network Access



Parallels Plesk Panel can be configured to automatically download and install ParallelsPlesk Panel updates. For detailed information about configuring Parallels Plesk Panelto enable autoupdates, see the "Configuring Automatic Updates of Your Parallels PleskPanel" section in the Parallels Plesk Panel Administrator's guide.

Parallels Plesk Panel autoupdater will automatically connect to the Parallels PleskPanel update server, check for available updates, download new updates, and eitherinstall them automatically or display them in the list of available updates. You can viewthe list of available updates and select which updates to install if autoupdates are notenabled. If you do enable autoupdates, you can also set the desired periodicity of theautoupdater run sessions and configure notifications to be sent automatically to an e-mail address of your choice.

However, all these autoupdater features are only available in Parallels Plesk Panelsthat have been installed by using a Parallels Plesk Panel distribution package. Theautoupdater feature implementation in a Parallels Plesk Panel installed by using aVirtuozzo application template on a virtual private server (VPS) differs from the featureimplementation in a Parallels Plesk Panel installed from a distribution package byrunning an installer program.

As far as autoupdates are concerned, in an application template-installed ParallelsPlesk Panel you can only have them enabled or disabled. No other autoupdate controlis available. You can neither configure periodicity of the updates nor view a list ofavailable updates. This is because Parallels Plesk Panels installed from Virtuozzoapplication templates are only found on Virtuozzo-generated VPSs running on

hardware nodes housing multiple other VPSs. Because of potentially large number ofVPSs running on a single hardware node, the Parallels Plesk Panel user ability tocustomize Parallels Plesk Panel autoupdates on each VPS individually has to begreatly reduced to ensure that the total update-related workload on the hardware nodeis properly balanced over time. In particular, concurrent occurrence of updateprocesses on several VPSs residing on a single hardware node must be prevented.This goal is realized by using the vzt mpl upsvc service to manage autoupdates ofapplication-template installed Parallels Plesk Panels on VPSs running on Virtuozzohardware nodes.

C H A P T E R 1 7

Parallels Plesk Panel Autoupdates by

vztmplupsvc Service Using VirtuozzoUpdate Templates





User names and passwords of Parallels Plesk Panel users should comply with thefollowing rules of user names and passwords creation:

User names of Parallels Plesk Panel users should comply with the following rules:

A user name can include printed characters: letters, numbers, underscores ('_'),dots ('.'), and dashes ('-').

A user name must start with a letter or a number.

A user name must be more than 1 character long.

A user name length must not exceed 15 characters.

Passwords of Parallels Plesk Panel users should comply with the following rules:

A password can include only printed characters.

A password must not directly contain the user name.

A password length must not exceed 14 characters.

Minimal password length is 4 characters by default. This value can be changed

in the PLESK_MI N_PASSWORD_LENGTH parameter of the[ HKLM\ SOFTWARE\ PLESK\ PSA Conf i g\ Conf i g] key.

User names and passwords of mail users in Parallels Plesk Panel should comply withthe rules of user names and passwords creation described above as well as with therules of the mail server.

C H A P T E R 1 8

Rules for User Names and Passwords of

Parallels Plesk Panel Users



During installation of Parallels Plesk Panel several scheduled tasks are automaticallycreated. One of such tasks, stat i st i cs, generates statistics on the limits imposed ondomains, such as inbound and outbound traffic, the disk space occupied by webcontent, log files, databases, mailboxes, web applications, mailing list archives, andbackup files.

You can vary which data the stat i st i cs task should count, thus making the taskwork faster. To do this, run the stat i st i cs task with a necessary combination ofoptions specifying the parts of statistics you want to collect.

To run the statistics task with required options, follow these steps:

1. Log in the Parallels Plesk Panel server as a user with administrator rights by usingRemote Desktop.

2. Start cmd. exe.

3. Change directory to %pl esk_di r %\ admi n\ bi n (where %pl esk_di r %is thesystem variable defining the folder where Parallels Plesk Panel is installed).

4. Run the stat i s t i cs . exe task with required options. See the list of options andtheir descriptions in the tables below.

For example, to count statistics in the mode that will skip all FTP logs, you can usethe following command:

stati st i cs. exe - - ht t p- t r af f i c - - di sk- usage - - mai l box- usage - -mai l - t raf f i c - - not i f y - - updat e- act i ons

Main options

Each main option defines the part of statistics to be calculated. When only main options

are used, the specified statistics will be collected for all domains.

Option Description

- - mai l box- usage Disk usage will be calculated for all mail boxes.

- - di sk- usage Disk usage for domains and all mail boxes will be calculated.

- - ht t p- t r af f i c HTTP traffic will be calculated.

- - f t p- t r af f i c FTP traffic will be calculated.

- - mai l - t r af f i c Mail traffic will be calculated.

Note: Parallels Plesk Panel does not support trafficcalculation on hMail and CommunigatePro mail servers.

C H A P T E R 1 9

Customizing Statistics Calculation



Customizing Statistics Calculation 199

- - not i f y Clients traffic will be updates and expiration notifications will besent.

- - updat e- acti ons Action log will be rotated and action events will be launched.

- - al l This option is the combination of all previous options, thecomplete statistics will be collected.

none When no options are specified, the complete statistics will becollected, like in the case when the - - al l option is selected.

Addi tional opt ions

Additional options allow you to specify the set of domains for which the statistics will becalculated. Domain names or masks specified in these options should be separated by', ' or '; ' symbol. You may combine additional options and use them without main

options. If you use additional options without main ones, complete statistics will becalculated only for selected domains. Domains being specified directly have higherpriority then those being specified by masks, also 'skip' list has higher priority then'process' list.

Option Description

- - pr ocess- domai ns Only domains specified in this option will be processed.

- - pr ocess- domai n-mask

Only domains corresponding to the mask specified in this optionwill be processed.

When this options is used and there are no domainscorresponding to the specified mask, all the domains will beprocessed.

- - ski p- domai ns Domains specified by this option will not be processed.

- - ski p- domai n- mask Domains corresponding to the mask specified by this option willnot be processed.

- - si ngl e- not i f y The expiration notification will be sent only to the specifieddomain.

For information about implementation of permanently customized statistics calculation,consult the "Configuring Statistics" section of the Parallels Plesk Panel for Windows Administrator's Guide.





Configur ing APS Applications Catalog 201

[ l essused]

Vi deoDB

phpMyChatPl us

[ al l ]

j ooml a

Wor dPress

Dr upal

movabl et ype

Sugar CRM

Vi deoDB

phpMyChatPl us

3. Save the file.

To specify what applications and application categories should bepresented in the APS catalog:

1. On the server file system, go to the directory<par al l el s_pl esk_panel _ i nst al l at i on_di r ect or y>\ et c\ and create a text file named apscat al og_cat egor i es. conf .

2. Add the required entries to the f ile.

You should first add a top-level category name in brackets, like [Web]. Then, you

should add a name of a nested sub-category, for example, [Web/Blog]. After that,you can type the names of applications that belong to that category, one name perline.

Also, to be sure that no other applications (except for those that you specified) areshown in the server's APS Catalog and application vaults of other users, you canadd to the file the line ot her Appl i cat i onsPol i cy = hi de, and in the next line,add the line hi deLevel = admi n. If you want to hide other applications only fromyour customers, but not from your own application vault, then use the linehi deLevel = cl i ent .

The resulting text file should look like in the following example:

otherApplicationsPolicy = hide

hideLevel = admin

[Web]

[Web/Blog]

joomla

WordPress

Drupal

[Web/Gallery]

phpGallery



202 Configur ing APS Applications Catalog

VideoDB

3. Save the file.



By default, in IIS, Parallels Plesk Panel uses ISAPI to run PHP applications. You canalso use CGI or FastCGI. For better performance it is recommended to switch the PHPhandler type in IIS to FastCGI. The type of PHP handler is defined by the"PLESKCP_PHP_MODE" value of the HKEY_LOCAL_MACHI NE\ SOFTWARE\ PLESK\ PSAConf i g\ Conf i g key of Windows registry (isapi, cgi, or fastcgi).

To set FastCGI as PHP handler type, follow these steps:

1. Log in to the Parallels Plesk Panel server as the administrator using RemoteDesktop.

2. Make sure FastCGI component is installed on the Parallels Plesk Panel server. Fordetails refer to "Automatic Installation of Parallels Plesk Panel Components" (seepage 91) section.

3. Start Windows registry editor.

4. In the HKEY_LOCAL_MACHI NE\ SOFTWARE\ PLESK\ PSA Conf i g\ Conf i g key,set the "f ast cgi " value for the "PLESKCP_PHP_MODE" parameter.

Note: If the "PLESKCP_PHP_MODE" parameter is absent or set to "i sapi ", ISAPI isused as the PHP handler. If the "PLESKCP_PHP_MODE" parameters value is "cgi ",CGI is used.

5. Start Parallels Plesk Panel Reconfigurator and select the Repair Plesk Installation option. The Check & Repair window opens.

6. Select Plesk Services in the list and click Check.

To switch between PHP handler types, use Parallels Plesk Panel Reconfigurator in oneof the following ways:

1. Log in to the Parallels Plesk Panel server as the administrator by using RemoteDesktop.

2. Set the "PLESKCP_PHP_MODE" value in theHKEY_LOCAL_MACHI NE\ SOFTWARE\ PLESK\ PSA Conf i g\ Conf i g key ofWindows registry (isapi, cgi, or fastcgi).

3. Select the Repair Plesk Installation option of the Parallels Plesk PanelReconfigurator.

4. Select Plesk Services in the list and click Check.

or

C H A P T E R 2 1

Switching PHP Handler Type to FastCGI



204 Switching PHP Handler Type to FastCGI


2. Set the "PLESKCP_PHP_MODE" value in theHKEY_LOCAL_MACHI NE\ SOFTWARE\ PLESK\ PSA Conf i g\ Conf i g key of

Windows registry (isapi, cgi, or fastcgi).

3. Start cmd. exe and change directory to the %pl esk_di r %\ admi n\ bi n\ folder(where %pl esk_di r %is the Windows' system variable specifying the folderwhere Parallels Plesk Panel is installed).

4. Run the following command:

Reconf i gur ator . exe / check=Ser vi ces

or


2. Start cmd. exe and change directory to the %pl esk_di r %\ admi n\ bi n\ folder(where %pl esk_di r %is the Windows' system variable specifying the folderwhere Parallels Plesk Panel is installed).

3. Run the following command:

Reconf i gur at or . exe - - swi t ch- pl esk- web- ser ver - - new-pr ovi der =i i s - - php- handl er - t ype=<i sapi | f ast cgi | cgi > - -f orce



By default, the open relay option for the mail server is disabled in Parallels Plesk Panel.You can enable it by using the root . cont rol s . l ock file located inPRODUCT_DATA_D\ var directory. However we do not recommend enabling this optionbecause an open relay can make it possible for an unscrupulous senders to route largevolumes of spam.

To enable open relay, follow these steps:

1. Open the root . cont rol s . l ock file.

2. Remove the / ser ver / mai l . php3: r el ay_open line and save the file.

C H A P T E R 2 2

Using Open Relay Option for Your Mail

Server



DACL (Discretionary Access Control List)

Part of the security descriptor for an object. The DACL can be applied to a newlycreated object in order to restrict access to the object.

ACE (Access Control Entry)

An individual entry in an access control list (ACL). An access control entry (ACE)contains an SID and describes the access rights to a system resource by a specific

user or group of users. Each object has a set of all ACEs, which is used to determine

C H A P T E R 2 3

Glossary