_group 

_subaccts group is being created for each account that has subaccounts  any subaccount of a particular account becomes a member of

_subaccts group  NTFS permissions to particular subaccount home directory are given explicitly for this subaccount in addition to existing NTFS permissions for this directory 292 Windows Servers IIS Security Management Features:  The FTP account login is not used anymore as anonymous web access for all sites owned by the user. Instead of this, for each virtual host a separate account with random password is being created during virtual host creation procedure.  The password synchronization IIS feature which requries „LOCAL SYSTEM‟ identity for web application process is not used anymore. The reason for this is that this account and randomly generated password is registered in the metabase as anonymous for this particular virtual host.  An account is being added to HS_ACCTS, HS_IUSR_ACCTS and Parallels H-Sphere account group. Each anonymous login has the following format: _ where is Parallels H-Sphere FTP account title and is number of particular virtual web host owned by this Parallels H-Sphere account.  Now each IIS web application process is run under „NETWORK SERVICE‟ identity. There is a number of Parallels H-Sphere modules run in IIS web processes which should perform some privileged operations such as read/write files or register keys protected by NTFS permissions. That is why Parallels H-Sphere creates a special „HsISAPIAcct‟ account as a member of the „Local Administrators‟ group. This account is used by Parallels H-Sphere IIS modules to perform such privileged operations. In addition, its password is being regenerated each time IIS is started for security reason. Windows Servers 293 NTFS permissions There are permission schemes which are used for Windows 2000, Windows 2003, and for both platforms. Windows 2000 The following NTFS permissions are set for a user home directory:  Local Administrator group: FULL ACCESS  SYSTEM: FULL ACCESS  ASPNET account: READ ACCESS  _group local group: MODIFY,READ,WRITE,EXECUTE,LIST FOLDER CONTENT Windows 2003 The following NTFS permissions are set for a user home directory:  Local Administrator group: FULL ACCESS  SYSTEM: FULL ACCESS  NETWORK SERVICE: READ ACCESS  _group local group: MODIFY,READ,WRITE,EXECUTE,LIST FOLDER CONTENT The following permissions are added to bin directory:  NETWORK SERVICE: READ,EXECUTE,LIST FOLDER CONTENT Relevant to both platforms The following NTFS permissions are used for ODBC DSN registry key:  Local Administrator group: FULL ACCESS  SYSTEM: FULL ACCESS  _group local group: QUERY VALUE,SET VALUE,CREATE SUBKEY,ENUMERATE SUBKEYS,NOTIFY 294 Windows Servers FrontPage Server Extensions Management Notes The following changes were made to FPSE management as a part of a new scheme:  Anonymous access is assigned to Browser role for any FPSE enabled virtual host  _group local group is set as FPSE administrator for any FPSE enabled virtual host  HsAuth ISAPI filter is no more used for FPSE enabled virtual hosts ASP.NET Management Notes  The ASP.NET management operations, which enable and disable ASP.NET service for a particular virtual web host, are based on the .NET framework configuration file machine.config.  The following fragment is added to the machine.config file for a particular virtual host if ASP.NET is being disabled for this virtual host: ” allowOverride=”false”> >  When ASP.NET service is enabled for a particular virtual host, it is being removed from machine.config file, if found. Migration Notes  During the Winbox upgrade, all existing accounts will be automatically migrated to a new security scheme. This process migrates account settings, web settings, NTFS permissions for home directories and ODBC DSNs, ASP.NET settings, FPSE settings and can take significant time.  The migration procedure is performed once. If it‟s necessary for some reason to repeat the migration, the NewSecurity line should be removed from bininstall.history file.  Migration process can be monitored using migration log which can be found in the update.log log file of upgrade tool. Important: during the migration, IIS servers will be automatically restarted on Windows 2003. Windows Servers 295 Recovery Notes To perform server recovery (on page 483) or server to server movement, use the SetScrtNs.exe tool which is a new analogue of the SetScrt.exe tool. It has the same purpose as the older version, but sets the correct permissions for a new security scheme. Download SetScrtNs Tool: http://download.hsphere.parallels.com/shiv/WinBox/SetScrtNs20.exe Migrating Serv-U to MS-FTP Parallels H-Sphere Winbox 2.5 and up does not support Serv-U. Migrate Serv-U to MSFTP before updating Winbox to Parallels H-Sphere 2.5 and up from older version. To do this, perform the steps listed below. In this section: Step 1. Create a User Account and User FTP Accounts in IIS FTP ................... 296 Step 2. Reset NTFS Permissions ...................................................................... 298 Step 3. Recover Winbox quota .......................................................................... 299 Step 4. Reset Anonymous Access for All User Domains in IIS .......................... 300 296 Windows Servers Step 1. Create a User Account and User FTP Accounts in IIS FTP Before creating a user account and user FTP accounts, make sure IIS FTP is installed. Then perform the following: 1 Export all usernames and passwords for physical server from CP database to a file. For this: 1. Login to CP under root: su -l cpanel psql hsphere wwwuser 2. Run: select login, password from unix_user where hostid=??? Replace ??? with ID of the necessary Logical Server 2 Write down the result in the users.txt file in a folder [drive:]\hsphere\scripts\ (e.g. c:\hsphere\scripts\). The format of results is as follows: username pwd username pwd 3 Make the following alterations to the hsphere\scripts\conf.inc file: 1. Change ftpServer = “SERV-U” to ftpServer = “IIS” 2. Run regedit 3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Psoft\HSphere\Settings and set IIS FtpType 4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Psoft\HSphere\HsServULayer\Acce ss\, and delete the Users key. Then recreate the empty Users key. 5. Restart hssvc service in cmd window: net stop hssvc net start hssvc 6. restart hsphere service in cmd window: net stop hsphere net start hsphere 4 Create IIS Metabase backup. 5 Stop IIS: 1. Go to cmd 2. Run: iisreset/stop Windows Servers 297 6 Rename Hshome folder to 1Hshome (e.g. d:\1hshome) and create empty Hshome folder (e.g. d:\Hshome). If it is possible, create the backup of hshome folder. 7 Create createusersp.asp script in the Hsphere\scripts\ folder: <%@ LANGUAGE=JScript %> <% Server.ScriptTimeout = 600 inetSrv = Server.CreateObject(comRsrcManager) Server.Execute(“/cfg/set-config.asp”) fs = new ActiveXObject(“Scripting.FileSystemObject”); a = fs.OpenTextFile(Server.MapPath(“/cfg/users.txt”), 1, false); diskQuota = Server.CreateObject(“Microsoft.DiskQuota.1”) while (!a.AtEndOfLine) { record = a.ReadLine(); tokens = record.split(new RegExp(“[ \n\r\t]”)); user = tokens[0]; password = tokens[1]; errCode = 0 aOptions = new Array(useDedicatedUsersGroup) flags = new Array(1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384) options = 0 for (i = 0; i < aOptions.length; i ++) { if (aOptions[i] != 0) options |= flags[i] } errCode = inetSrv.CreateUser(user, usersHome + “\\” + user, “settler”, password, logPath, options) if (errCode != 0) Response.Write(“User: “ + user + “ failed
\n”) else Response.Write(“User: “ + user + “ = Ok
\n”) Response.Flush() } a.Close(); %> 8 Run in browser window http://Target_IP/cfg/createusersp.asp Then put an hsadmin login and password in authentication window 9 Delete empty Hshome folder, and rename 1Hshome to Hshome. Start IIS 10 Check if FTP accounts have been created for all users 298 Windows Servers Step 2. Reset NTFS Permissions 1 Download Recreation scripts from http://download.hsphere.parallels.com/shiv/WinBox/ReCreateAddScrip ts.zip in a zip archive and unpack them to a separate directory on the Winbox, for example recreation_scripts. 2 Set NTFS permission for Hshome folder: 3 Download the setscrt.exe utility from http://download.hsphere.parallels.com/shiv/WinBox/SetScrt.exe a Run it to set correct owner and NTFS permissions on user home directories: s etscrt [-owner] [-ntfs] > setscrt.log b Running the setscrt utility with the -owner and -ntfs options separately, will break the process in two: setscrt -owner > setscrt_owner.log setscrt -ntfs > setscrt_ntfs.log c Check the log files for report. 4 (skip this step, if your Parallels H-Sphere version is 2.5+) Reinstall ASP.NET for all accounts that have it enabled in CP a Get users and domains with installed ASP.NET from CP database. On this step, the scripts will be used in the recreation_scripts directory. b Log into the system database and run the following DB query to select the domain names with ASP.NET support enabled: select d.name,i.hostnum from parent_child p1,parent_child p2,parent_child p3,parent_child p4,domains d,iis_vhost i where i.host_id=??? and p1.child_id = i.id and p1.parent_id = p2.child_id and d.id = p2.child_id and p3.parent_id=p2.child_id and p4.parent_id=p3.child_id and p4.child_type=63; Replace ??? with the ID of the logical server you are recovering. c Copy the results of the query into a text file in the recreation_scripts directory and name it, for instance, aspnet.txt. d Enter the recreation_scripts directory and run the following command: aspnetprepare.bat %1 %2 %3 %4 > aspnet_links.txt where: - rem %1 - file name, e.g. aspnet.txt - rem %2 - Winbox IP - rem %3 - Parallels H-Sphere login used at Winbox installation - rem %4 - Parallels H-Sphere password used at Winbox installation e Open aspnet_links.txt and remove the first part leaving only the list of links. f Run the following command: WGET.EXE -i aspnet_links.txt This will recreate all ASP.NET resources on the Winbox. Windows Servers 299 Step 3. Recover Winbox quota 1 Log into the system database (on page 72) and run the following DB query to select the users and their space limit: select unix_user.login, quotas.size_mb from unix_user, parent_child, quotas where hostid=??? and parent_child.parent_id=unix_user.id and parent_child.child_id=quotas.id and parent_child.child_type=4001; Replace ??? with the ID of the logical server you are recovering. 2 Copy the results of the query into a text file in the recreation_scripts directory and name it, for instance, quotat.txt. 3 Enter the recreation_scripts directory and run the following command: Rquota.bat %1 %2 %3 %4 > quota.txt where: - rem %1 - file name, e.g. quota.txt - rem %2 - Winbox IP - rem %3 - Parallels H-Sphere login used at Winbox installation - rem %4 - Parallels H-Sphere password used at Winbox installation 4 Open quota.txt and remove the first part leaving only the list of links. 5 Recreate quota resource on the Winbox: WGET.EXE -i quota.txt 300 Windows Servers Step 4. Reset Anonymous Access for All User Domains in IIS 1 Create setun.js file with the help of Notepad with the following content: oldHome = new String(WScript.Arguments.item(0)); oldHome = oldHome.toLowerCase(); web = GetObject(“IIS://LocalHost/W3SVC”); allWeb = new Enumerator(web); var newDocRootPath, oldDocRootPath, stage = 0; for ( ; !allWeb.atEnd(); allWeb.moveNext()) { if (isNaN(parseInt(allWeb.item().name))) continue; docRoot = GetObject(“IIS://LocalHost/W3SVC/” + allWeb.item().name + “/ROOT”); docRoot.KeyType = “IIsWebVirtualDir”; docRoot.SetInfo(); oldDocRootPath = new String(docRoot.Path); oldDocRootPath = oldDocRootPath.toLowerCase(); WScript.Echo(“Site: “ + allWeb.item().name); if (oldDocRootPath.indexOf(oldHome.toLowerCase()) == -1) { WScript.Echo(“Site “ + allWeb.item().name + “ is not Parallels H-Sphere web site”); continue; } tokens = docRoot.Get(“Path”).split(new RegExp(“\\\\”)); username = tokens[tokens.length-2]; docRoot.Put(“AnonymousUserName”, username); docRoot.Put(“AnonymousPasswordSync”, 1); docRoot.SetInfo(); WScript.Echo(“Document root for “ + allWeb.item().name + “ web site has been changed to “ + newDocRootPath); } 2 Run in cmd window: cscript setun.js [path to Hshome] Example: cscript setun.js e:\hshome Note: anonymous access is reset only if domain properties path contains hshome folder and if domain is created by Parallels H-Sphere. 3 Restart IIS (on page 262). Go to cmd->iisreset 4 Go to hsphere.net\bin\. Open install.history file with the help of Notepad, select all the text, and delete it, save empty install.history file. 5 Run Parallels H-Sphere updater for Winbox. 6 If FTP subaccounts were created in Serv-U, recreate them via CP interface manually. Windows Servers 301 7 Open SOAP port 10125 for data communication between Control Panel and Windows server, in the hsphere.properties file on the Control Panel box. Preparing Servers for MS Exchange Hosting (Hosted Messaging and Collaboration 3.0) Note: This is the instruction for Hosted Messaging and Collaboration 3.0. Before you start using MS Exchange hosting, you need to prepare at least 2 servers, separately of Parallels H-Sphere, with the following software installed: 1 Server 1 (Primary Domain Controller): Windows 2003 SP1, Active Directory Domain Controller 2 Server 2 (MS Exchange Server): Windows 2003 SP1, MSSQL 2000 SP3, MS Exchange 2003 SP1, Hosted Messaging and Collaboration 3.0, WS Exchange Provider Adapter Namespace  To prepare Servers for MS Exchange Hosting: 1 2 3 4 Install Required Software on the Servers (on page 302) Deploy Hosted Messaging and Collaboration (on page 304) Install WS Exchange Provider Adapter Namespace (on page 315) Create Reseller Organization Unit (on page 316) In this section: Step 1. Install Required Software on the Servers .............................................. 302 Step 2. Deploy Hosted Messaging and Collaboration ........................................ 304 Step 3. Install WS Exchange Provider Adapter Namespace .............................. 315 Step 4. Create Reseller Organization Unit ......................................................... 316 302 Windows Servers Step 1. Install Required Software on the Servers  To install required software on the servers 1 Install Window 2003 SP1 on both servers with English language interface. 2 Install MDAC 2.8 on Server 2. 3 Install IIS and ASP.NET on Server 2: 1. On the taskbar, click Start, click Control Panel, select Add or Remove Programs, and then click Add/Remove Windows Components. 2. Select Application Server, and then click Details. 3. Select Internet Information Services (IIS), and then click Details. 4. Install the following components: Internet Information Services Manager, World Wide Web Services, Common Files, ASP.NET 5. Click OK, click OK again, and then click Next. 6. After the wizard completes, click Finish and close the Add or Remove Programs dialog box. 4 Install MSSQL Server 2000 on Server 2. 5 Install MSSQL Server 2000 SP3 on Server 2. 6 Enable Network DTC and COM+ Network Access 1. On the taskbar, click Start, open Control Panel, and then click Add or Remove Programs. 2. Click the Add/Remove Windows Components button. 3. Highlight Application Server, and then click Details. 4. Select EnableNetwork COM+ access. 5. Select EnableNetwork DTC access. Click OK. 6. Click Next. When the Windows Components Wizard completes, click Finish. 7 Enable Inbound and Outbound DTC Access on Server 2 1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services. 2. Click and expand Component Services, and then click and expand Computers. 3. Right-click My Computer, and then select Properties. 4. Select the MSDTC Tab. 5. Click the Security Configuration button. 6. Ensure that Network DTC Access is enabled. Then, ensure that the Allow Inbound and Allow Outbound options are selected in the Transaction Manager Communication section. Leave all other options as default. 7. Click OK to save the settings. Select Yes if you are prompted to restart the service. 8 Obtain Hosted Messaging and Collaboration 3.0 media. Windows Servers 303 9 Install Active Directory Domain Controller on Server 1 using the dcpromo.exe tool in Windows root directory. 10 Join Server 2 to installed domain. 11 Log on to Server 2 as a member of the Domain Administrators group. 12 Install MS Exchange server 2003 on Server 2. 13 Install MS Exchange server 2003 SP1 on Server 2. 304 Windows Servers Step 2. Deploy Hosted Messaging and Collaboration  To deploy Hosted Messaging and Collaboration 1 Log on to Server 2 as a member of the Domain Administrators group. 2 Install the MPS (Microsoft Provisioning Service) deployment tool. 1. Quit all running programs. 2. Open command prompt, and change the directory to SolutionMedia\Service Provisioning\Deployment Tool. 3. To install the Deployment Tool on Server 2, run the following from the command prompt: cscript initdeploymenttool.wsf. Note: If you are not installing from CD, you will be prompted to enter a path to the root directory of the solution media source files. 4. When prompted for the server name for configuration files, enter Error! Hyperlink reference not valid. 2 name>, and then click OK. 5. When prompted for the server name for installation files, enter Error! Hyperlink reference not valid. 2 name>, and then click OK. 6. In the confirm configuration dialog box, click Yes if the settings are correct, or click No to cancel. 7. In Do you want to install the deployment tool to the local computer? dialog box, click Yes. A shortcut for the Deployment Tool will be added to the desktop of Server 2. 3 Install the MPF (Microsoft Provisioning Framework) Engine and Database 1. Run the MPS Deployment Tool, and then click the Servers tab. 2. Under SQL Servers, click Add. 3. Enter ,and then click OK. 4. Under MPS Servers, click Add. 5. Enter the name of the MPF Engine server as , and then click OK. 6. In the Requirements Status pane, expand the Active Directory component, rightclick Native Mode, and then select User input on the contextual menu that appears. In the Active Directory Native Mode dialog box, click OK. 7. Under the Active Directory component, right-click List Object Mode, and then select User Input on the contextual menu that appears. The Active Directory/list Object Mode dialog box appears and prompts you as to whether or not you want to proceed. Click OK. 8. In the Requirements Status pane, right-click the MPF Engine component, select Install on Server, and then click . 9. The icon next to the MPF Engine component changes to a silver disk to indicate that you have scheduled the installation of this component. Windows Servers 305 Note: Because of inherent dependencies, when you configure the MPF Engine to be installed on Server 2, other core MPS components are also installed on Server 2, and the MPFServiceAcct is scheduled to be created in Active Directory. 10. In the Requirements Status pane, right-click the MPF Config Database component, select Install on SQL Server, and then click . 11. Repeat step 3.10 for each of the MPF database components:  Resource Manager Database  MPF Audit Database  MPF Transaction Database 12. In the Requirements Status pane, right-click the Windows-based Hosting component, and then select Install this Group to install all the components. The Install This Group dialog box will display the list of items to be installed and actions to be performed. Click OK. 13. Click Start Deployment to start the installation of the MPF Engine, databases, and namespaces/providers on the server. 14. Monitor the deployment session on the Install Details tab. 15. When the deployment is complete, on the Action History tab, click View Details to review events. 16. Close the Provisioning Deployment Tool. Note: When deployment completes, you will see that the following Namespace Initialization procedures are displayed with a red X, and the Install Details pane displays an unable to create the credential error. Managed Helpers:InitializeNamespaceSecurity Managed Web Hosting:InitializeNamespaceSecurity Managed Sharepoint Hosting:InitializeNamespaceSecurity This is an expected error. 4 Verify the MPFClientAccts Group on Server 2 1. Click Start, point to AllPrograms, point to AdministrativeTools, and then click Computer Management. 2. Expand Local Users and Groups, and then click Groups. 3. Double-click Distributed COM Users, and then click the Members tab. 4. Verify that the \MPFClientAccts group is member of Distributed COM Users group. Click OK. 5. Click OK to close the Distributed COM Users Properties dialog box. 5 Add MPFServiceAccts to the Local Administrators Group 1. On the taskbar, click Start, click All Programs, click Administrative Tools, and then click Computer Management. 2. Expand Local Users and Groups, and then click Groups. 3. Double-click the Administrators group. 4. Click Add, and then enter MPFServiceAccts. Select the Check Names check box to make sure that the name resolves, and then click OK. 306 Windows Servers 5. Click OK to close the Administrator Properties window. 6 Reboot Server 2 7 Initialize Namespaces 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, expand the Namespace Initialization component. Right-click Managed Helpers:InitializeADforHosting, and then select User Input. 3. When prompted for the name of the hosting organization, accept the default of Hosting, and then click OK. 4. Right-click Managed Helpers:InitializeADforHosting, and then select Execute Initialization Procedure. 5. In the Confirm Operation dialog box, click Yes. 6. Right-click Managed Helpers:InitializeNamespaceSecurity, and then select Execute Initialization Procedure. 7. In the Confirm Operation dialog box, click 8. When the deployment completes, close the MPS Deployment Tool. 8 Install the Plans Database 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, right-click Plans Database, select Install on Server, and then select . 3. Click Start Deployment. 4. When deployment completes, close the MPS Deployment Tool. 5. Run the MPS Deployment Tool. 6. In the Requirements Status pane, expand Namespace Initialization. 7. Right-click Managed Helpers: InitializePlanDatabase, and then select Execute Initialization Procedure. 8. In the Confirm Operation dialog box, click Yes. 9. When deployment completes, close the MPS Deployment Tool. 9 Install the MPS Web Services on Server 2 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, right-click Web Service, select Install on Server, and then select . 3. Below Web Service, right-click , and then select User Input. 4. In the New Virtual Directory box, enter MPSWS, and then click OK. Note: After you assign the Web service and input the virtual directory name, the MPF Client will automatically be assigned for installation on Server 2 5. Click Start Deployment. 6. When the deployment completes, click OK, and then quit the MPS Deployment Tool. 10 Install Resource Manager Web Client on Server 2 Windows Servers 307 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, right-click Resource Manager Web Client, select Install on Server, and then select . 3. Below Web Service, right-click , and then select User Input. 4. In the New Virtual Directory box, enter ResourceManagerWebClient, and then click OK. 5. Click Start Deployment. 6. When the deployment completes, click OK, and then quit the MPS Deployment Tool. 11 Initialize Hosted Exchange Provisioning Namespaces 1. Run the MPS Deployment Tool. 2. Expand Namespace Initialization. 3. Right-click Hosted Exchange: InitializeHostedExchange, and then select Execute Initialization Procedure. At the Confirm Operation dialog box, click Yes. 12 Configure the MPFServiceAccts Group As Exchange Full Administrator 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard. 3. Click Next, click Add, click Browse, select MPFServiceAccts from the list, and then click OK. 4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK. 13 Configure the Microsoft Provisioning System Server for Hosted Exchange 1. Run the MPS Provisioning Deployment Tool. 2. Under Microsoft Exchange, right-click Delegate Exchange Administration, then select Force State. At the Force State dialog box, select the Verified radio button and click OK. 3. Under Microsoft Exchange, right-click Disable Domain RUS, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes. 4. Under Microsoft Exchange, right-click Secure All Address Lists, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes. 5. Under Microsoft Exchange, right-click Native Mode, then select Install. The Confirm Operation dialog box appears and prompts you as to whether or not you want to proceed with an action that has an immediate effect. Click Yes. Check the log information at the bottom of the Configuration Wizard screen to verify that the configuration was successfully set. 308 Windows Servers 14 Configure the MPSExchangeAccts Group As Exchange Full Administrator 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard. 3. Click Next, click Add, click Browse, select MPSExchangeAccts from the list, and then click OK. 4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK. 15 Configure the All Address Lists Container 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, click the Recipients node, expand the tree. 3. Right-click the All Address Lists and select Properties. 4. Click the Security tab, click Advanced, and then click Add under Permissions. 5. In the Name text box, type MPSExchangeAccts, and then click OK. 6. In the Apply onto list, select This object and subcontainers. 7. In the Permissions list, click Full Control. 8. Click OK three times. 16 Add the MPSExchangeAccts Group to Local Administrators Group 17 Create Mailbox Stores for Hosted Exchange 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, expand Servers, then expand , and then expand First Storage Group. 3. Create any appropriate mailbox stores will be used as a Business Mailstores. 18 Initialize Resource Management 1. Launch Internet Explorer, and go to http://localhost/ResourceManagerWebClient/QueryResources.aspx. 2. When prompted for Username and Password, log in as \Administrator. 3. Enter in the Preferred Domain Controller text box. Click Submit. 4. In the left pane, click Exchange Resource Manager. Then, select the Business Mailstores tab. 5. Add Business Mailstore resources. Important: The value should always be set to 1 for Business mail stores 6. In the left pane, click Exchange Resource Manager. Then, select the Public Stores tab. 7. Under Publicstores, click Add New Resource. Windows Servers 309 8. Add Public Store resources 9. In the left pane, click Exchange Resource Manager, and then, select the OAB Servers tab. 10. Under OAB Servers, click Add New Resource. 11. Add OAB Server resources. 19 Install the Hosted Exchange Offline Address Book (OAB) and Update Batch Application (on page 310) 20 Deploy the MPS Sample Web Client 1. Run SetupMPSSampleWeb.msi from the Windows-based Hosting distribution media in the \Samples\Provisioning\MPSSampleWeb directory. 2. On the MPPSSampleWeb Setup Wizard Welcome page, click Next. 3. On the Select Installation Address page, accept the default Virtual Directory (MPSSampleWeb) and Port (80), and then click Next. 4. On the Confirm Installation page, click Next. 5. On the Installation Complete page, click Close. 6. Open the Internet Information Services (IIS) Manager, and then expand the default Web site. 7. Right-click MPSSampleWeb, and then select Properties. 8. Click the Directory Security tab, and then, under Authentication and access control, click Edit. 9. Clear the Enable atupMPSSampleWeb.msi from the Windows-based Hosting distribution media in the \Samples\Provisioning\MPSSampleWeb directory. 10. Ensure that the Integrated Windows Authentication check box is cleared. 11. Select the Basic authentication check box, and then, in the warning dialog box, click Yes. 12. Enter a backslash “\” in the default domain field. 13. Click OK, and then click OK again. 14. Close the IIS Manager window. 15. Edit the Web.Config file in the root directory of the MPS Sample Web Client (usually \inetpub\wwwroot\MPSSampleWeb). Set the following preferredDC and DefaultNamingContext key values to your preferred domain controller and default naming context. For example: ”/> 21 Disable the EventSink: 1. Go to C:\Program Files\Microsoft Hosting\Provisioning\MPSWS\ and open file web.config. 2. Find the string and change value to 0 () 3. Save changes. 310 Windows Servers It will allow creating Exchange Recipient Policy for new SMTP domains. In this section: Installing the Hosted Exchange Offline Address Book (OAB) Update Batch Application 310 Installing the Hosted Exchange Offline Address Book (OAB) Update Batch Application The Hosted Exchange OAB Update batch application runs on a daily schedule in order to rebuild OAB for organizations that have had membership modifications.  To install and configure it to run as a scheduled job, do the following: 1 Install the Hosted Exchange OAB Update Batch Application (on page 311) 2 Configure Security for the Hosted Exchange OAB Update Batch Application Registry Keys (on page 312) 3 Configure Security Access for the Applications‟ Local File Resources (on page 313) 4 Configure Option Settings for the Hosted Exchange OAB Update Batch Application (on page 313) 5 Execute the Hosted Exchange OAB Update Batch Application (on page 314) 6 Create a Scheduled Task for the Hosted Exchange OAB Update Batch Application (on page 314) In this section: Step 1. Install the Hosted Exchange OAB Update Batch Application ................. 311 Step 2. Configure Security for the Hosted Exchange OAB Update Batch Application Registry Keys Step 3. Configure Security Access For the Applications Local File Resources .. 313 Step 4. Configure Option Settings for the Hosted Exchange OAB Update Batch Application 313 Step 5. Execute the Hosted Exchange OAB Update Batch Application ............. 314 Step 6. Create a Scheduled Task for the Hosted Exchange OAB Update Batch Application 314 Windows Servers 311 Step 1. Install the Hosted Exchange OAB Update Batch Application 1 Log on to Server2(Exchange) using an account that is a member of the Domain Administrators group. 2 From a command prompt in the Service Provisioning\MPS\Install folder, run the ExchangeOABUpdate.msi file. You must specify a password as follows: msiexec.exe /i ExchangeOABUpdate.msi OABUSERPW=password where password meets your Active Directory security requirements. 3 On the License Agreement page, select I accept the terms in the license agreement, and then click Next. 4 On the Customer Information page, enter the User Name and Organization, and then click Next. 5 On the Setup Type page, select Complete, and then click Next. 6 Click Install. 7 Click Finish to complete the installation and close the Installation Wizard. 8 Log on to Server1(DC) using an account that is a member of the Domain Administrators group. 9 On the taskbar, click Start, point to Administrative Tools, and then click Active Directory Users and Computers. 10 Expand fabrikam.com, and then select Users. 11 In the right pane, locate and right-click the MPFClientAccts user object, and then select Properties. 12 In the Properties dialog box, select the Members tab. 13 Click Add, type MPSOABUpdateAccts and then click Check Names. Verify that MPSOABUpdateAccts is underlined, and then click OK. 14 Click OK to close the Properties dialog box. Note: By default, the MPSOabUpdateAcct is the only account that can execute the HEOabUpdate.exe application. If you want other users to be able to run the application, you must add them to the MpsOabUpdateAccts group. After adding users to the MpsOabUpdateAccts group, you muse restart the Microsoft Provisioning Framework (MPF) engine for the changes to take effect. 312 Windows Servers Step 2. Configure Security for the Hosted Exchange OAB Update Batch Application Registry Keys In the following procedures you will configure security access for the applications registry keys, local resources, and MPF procedures. WARNING: Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be resolved. Before editing the registry, back up any valuable data.  To configure security access for the Hosted Exchange OAB Update Batch Application registry keys: 1 Log onto Server2(Exchange) using an account that is a member of the Domain Administrators group 2 Start Registry Editor (regedit). 3 Navigate to the HKEY_LOCAL_MACHINE\Software\Microsoft\Provisioning\He OabUpdate key. 4 Click the Edit menu and select Permissions. 5 In the Permissions for HeOabUpdate dialog box, click Add. 6 Type MpsOabUpdateAccts and click Check Names to verify that the group exists. 7 Click OK. 8 Click Advanced. 9 Select MPSOabUpdateAccts in the permissions entries list and click Edit. 10 In the Apply onto list, ensure that this key and subkeys is selected. 11 In the Permissions list, leave the default values selected, and then select the Allow check box for the Set Value and Create Subkey permissions. 12 Click OK three times. 13 Close Registry Editor. Windows Servers 313 Step 3. Configure Security Access For the Applications Local File Resources  To configure security access for the Hosted Exchange OAB Update Batch Application local resources 1 Open File Explorer and navigate to :\Program Files\Microsoft Hosting\Provisioning. 2 Right-click the Exchange OAB Update directory and select Properties. 3 Select the Security tab and click Add. 4 Type MpsOabUpdateAccts and click Check Names to verify that the group exists. Click OK. 5 Ensure that the Allow check box for the Modify permission is selected. 6 Click OK. Step 4. Configure Option Settings for the Hosted Exchange OAB Update Batch Application In this procedure, you will edit the applications configuration file to change settings to appropriate values for your deployment.  To configure optional settings for the Hosted Exchange OAB Update Batch Application: 1 Remove the read-only attribute from :\Program Files\Microsoft Hosting\Provisioning\Exchange OAB Update\HeOabUpdate.exe.config, and then open the file. 2 Set the preferredDomainController value to the fully qualified domain name (FQDN) of your preferred domain controller as in the following example: Note: AD01.fabrikam.com is full computer name of Server1(Domain controller) 3 Save the file after making your changes 314 Windows Servers Step 5. Execute the Hosted Exchange OAB Update Batch Application In the following procedure you execute the Hosted Exchange OAB Update batch application from the command line.  To execute Hosted Exchange OAB Update from a command line: 1 Open a command prompt and navigate to :\Program Files\Microsoft Hosting\Provisioning\ Exchange OAB Update. 2 Type the following, and press Enter: HeOabUpdate.exe 3 Close the command prompt when the application has finished processing. Step 6. Create a Scheduled Task for the Hosted Exchange OAB Update Batch Application In the following procedures you will create a scheduled task for the application.  To create a scheduled task to run Hosted Exchange OAB Update daily 1 2 3 4 5 Point to Settings, and then click Control Panel. Double-click Scheduled Tasks. Double-click Add Scheduled Task. In the Scheduled Task Wizard, click Next. Click Browse, and then select :\Program Files\Microsoft Hosting\Provisioning\Exchange OAB Update\HeOabUpdate.exe. 6 Click Open. 7 Select the Daily option, and then click Next. 8 Set Start Time to 6:00 AM. 9 Click Next. 10 Enter the Fabrikam\MPSOabUpdateAcct user name and the password for this account. Click Next. Where Fabrikam is active directory domain name Note: Task Scheduler does not verify that the password you enter for the MPSOabUpdateAcct matches the password set for the user in Active Directory. If you enter an incorrect password, the task will fail when it runs at its scheduled time. 11 Click Finish. Windows Servers 315 Step 3. Install WS Exchange Provider Adapter Namespace WS Exchange Provider Adapter Namespace (WS stands for “Web service”) provides communication between Parallels H-Sphere and MS Exchange provider via HTTP in order to manage MS Exchange hosting in Parallels H- Sphere CP. 1 Download WS Exchange Provider Adapter Namespace installation: http://hsphere.parallels.com/download/wsexchangeprovider.msi . 2 Run the downloaded MSI file and follow the installation instructions. 316 Windows Servers Step 4. Create Reseller Organization Unit Create reseller organization unit under which Parallels H-Sphere users signed up for MS Exhange plans will be hosted. On Server 2: 1 2 3 4 5 6 In Internet Explorer, go to http://localhost/MPSSampleWeb When prompted, log on as Domain Administrator. Leave the Current Reseller and Current Customer fields empty. Select the General tab. In the left-hand pane, click Create a Reseller Organization. Enter information about the organization in the appropriate boxes on the Create Reseller Org page 7 Click Submit Request. 8 When the request completes, you can review the XML response at the bottom of the page. After that, you can proceed to configuring Microsoft Provisioning Framework in admin CP. This is described in MS Exchange section of Parallels H-Sphere Service Administrator Guide. That‟s how the organization unit may look like when it is created and used for Parallels H-Sphere hosting: Windows Servers 317 318 Windows Servers In the above screenshot, Organization1 is the reseller organization unit, and its organization units like exchange are Parallels H-Sphere user accounts with emails and distribution lists. Preparing Servers for MS Exchange Hosting (Hosted Messaging and Collaboration 3.5) Before you start using MS Exchange hosting, you need to prepare at least 2 servers, separately of Parallels H-Sphere, with the following software installed: 1 Server 1 (Primary Domain Controller): Windows 2003 SP1, Active Directory Domain Controller 2 Server 2 (MS Exchange Server): Windows 2003 SP1, MSSQL 2000 SP3, MS Exchange 2003 SP1, Hosted Messaging and Collaboration 3.5, WS Exchange Provider Adapter Namespace  To prepare Servers for MS Exchange Hosting: 1 Install Required Software on the Servers (on page 319) 2 Deploy Hosted Messaging and Collaboration (on page 321) 3 Install WS Exchange Provider Adapter Namespace (on page 327) 4 Create Reseller Organization Unit (on page 328) In this section: Step 1. Install Required Software on the Servers .............................................. 319 Step 2. Deploy Hosted Messaging and Collaboration ........................................ 321 Step 3. Install WS Exchange Provider Adapter Namespace .............................. 327 Step 4. Create Reseller Organization Unit ......................................................... 328 Windows Servers 319 Step 1. Install Required Software on the Servers 1 Install Window 2003 SP1 on both servers with English language interface. 2 Install MSXML4 from http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b -b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en on Server 2. 3 Install IIS (WWW, FTP, SMTP, NNNT) and ASP.NET on Server 2: 1. On the taskbar, click Start, click Control Panel, select Add or Remove Programs, and then click Add/Remove Windows Components. 2. Select Application Server, and then click Details. 3. Select Internet Information Services (IIS), and then click Details. 4. Install the following components: Internet Information Services Manager, World Wide Web Services, Common Files, ASP.NET 5. Click OK, click OK again, and then click Next. 6. After the wizard completes, click Finish and close the Add or Remove Programs dialog box. 4 Install MSSQL Server 2000 on Server 2. 5 Install MSSQL Server 2000 SP4 on Server 2. 6 Enable Network DTC and COM+ Network Access 1. On the taskbar, click Start, open Control Panel, and then click Add or Remove Programs. 2. Click the Add/Remove Windows Components button. 3. Highlight Application Server, and then click Details. 4. Select EnableNetwork COM+ access. 5. Select EnableNetwork DTC access. Click OK. 6. Click Next. When the Windows Components Wizard completes, click Finish. 7 Enable Inbound and Outbound DTC Access on Server 2 1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services. 2. Click and expand Component Services, and then click and expand Computers. 3. Right-click My Computer, and then select Properties. 4. Select the MSDTC Tab. 5. Click the Security Configuration button. 6. Ensure that Network DTC Access is enabled. Then, ensure that the Allow Inbound and Allow Outbound options are selected in the Transaction Manager Communication section. Leave all other options as default. 7. Click OK to save the settings. Select Yes if you are prompted to restart the service. 8 Obtain Hosted Messaging and Collaboration 3.5 media. 320 Windows Servers 9 Install Active Directory Domain Controller on Server 1 using the dcpromo.exe tool in Windows root directory. 10 Join Server 2 to installed domain (first configure a Server2 to use of new DNS on server1). 11 Log on to Server 2 as a member of the Domain Administrators group. 12 Install MS Exchange server 2003 on Server 2. 13 Install MS Exchange server 2003 SP1 on Server 2. Windows Servers 321 Step 2. Deploy Hosted Messaging and Collaboration 1 Log on to Server 2 as a member of the Domain Administrators group. 2 Install the MPS (Microsoft Provisioning Service) deployment tool. 1. Quit all running programs. 2. Open command prompt, and change the directory to Service Provisioning\DeploymentTool 3. To install the Deployment Tool on Server 2, run the following from the command prompt: Deployment Tool.msi Note: If you are not installing from CD, you will be prompted to enter a path to the root directory of the solution media source files. 4. When prompted for the server name for configuration files, enter Error! Hyperlink reference not valid. 2 name>, and then click OK. 5. When prompted for the server name for installation files, enter Error! Hyperlink reference not valid. 2 name>, and then click OK. 6. In the confirm configuration dialog box, click Yes if the settings are correct, or click No to cancel. 7. In the Do you want to install the deployment tool to the local computer? dialog box, click Yes. A shortcut for the Deployment Tool will be added to the desktop of Server 2. 8. Restart winbox after MPS (Microsoft Provisioning Service) deployment tool has been installed. 3 Create an MPS SQL Service Account for MPS Interaction with SQL based Servers Procedure DWSPV.11: To create a SQL service account on the domain controller 1. Log on to \\Server1 using an account that is a member of the domain administrators group. 2. On the taskbar, click Start, point to Administrative Tools, and then click Active Directory Users and Computers. 3. Expand fabrikam.com (domain). 4. Right-click Users, point to New, and then click User. 5. In the New Object-User dialog box, type MPSSQLService as the First name and the User logon name, and then click Next. 6. In the next New Object - User dialog box, clear the User must change password at next logon check box. Enter the password (twice), and then select Password never expires. 7. Click Next. Verify the information you have entered, and then click Finish. 4 Add MPSSQLService to the Local Administrators Group Procedure DWSPV.12: To add MPSSQLService to the local administrators group 1. Log on to \\Server2 as a member of the domain administrators group. 322 Windows Servers 2. On the taskbar, click Start, point to All Programs, then to Administrative Tools, and then click Computer Management. 3. Expand Local Users and Groups, and then click Groups. 4. Double-click Administrators. 5. Click Add, and then type MPSSQLService. Click Check Names to make sure that the name resolves, and then click OK. 6. Click OK to close the Administrator Properties window. 5 Install the MPF (Microsoft Provisioning Framework) Engin e and Database Procedure DWSPV.20: To deploy the Core Platform 1. Log on to \\server2 as a member of the enterprise administrators group. Set your screen resolution to 1024 x 768 to properly display the Provisioning Deployment Tool interface when you start it. 2. On the \\server2 desktop, double-click the shortcut to the MPS Deployment Tool. 3. Click the Servers tab, and then, under SQL Servers, click Add. 4. In the Add SQL Server dialog box, type , and then click OK. 5. Under MPS Servers, click Add. 6. In the Add Server dialog box, type the name of the MPF Engine server as , and then click OK. 7. In the Requirements Status pane, expand Core Platform, expand Initialize Active Directory, right-click Native Mode, and then select Confirm irreversible Native Mode conversion. In the Active Directory /Native Mode dialog box, click OK. Right-click Native Mode and then select Install. 8. Under the Initialize Active Directory component, right-click List Object Mode, and then select Install. 9. In the Requirements Status pane, expand Core MPF Install, right-click the MPF Engine component, select Install on Server, and then click . The icon next to the MPF Engine component changes to a silver disk to indicate that you have scheduled the installation of this component. 10. In the Requirements Status pane,under Core MPF Install, expand MPF Config Database. Right-click SQL not assigned, select Install on SQL Instance, and then click . 11. Repeat step 10 for each of the MPF database components:  Resource Manager Database  MPF Audit Database  MPF Transaction Database 12. In the Requirements Status pane, under Core MPF Install, right-click the MPF Audit and Recovery component, point to Install on Server, and then click Add New Server. 13. Right-click the MPF Audit and Recovery component, point to Install on Server, and then click Add New Server. Windows Servers 323 14. In the Requirements Status pane, right-click Core Platform, and select Install all in this group. 15. If prompted with the Confirm Install on Dependents dialog box, review the list of actions to be performed, and click OK. 16. Click Start Deployment to start the installation of the MPF Engine, databases, and namespaces/providers on the server. 17. Monitor the deployment session on the Install Details tab. 18. When the deployment is complete, on the Action History tab, click View Details to review events. 19. Close the Provisioning Deployment Tool. 6 Install the Plans Database Procedure DWSPV.21: To deploy the Hosting Platform 1. In the MPS Deployment Tool, in the Requirements Status pane, expand Hosting Platform, expand Hosted PlansDatabase, then expand Plans Database. 2. Right-click Server not assigned, click Install on Server, then click . 3. Under Plans Database, right-click and click Select SQL instance. 4. In the Select SQL Server dialog box, type and then click OK. 5. In the Requirements Status pane, below Hosting Platform, expand Initialize Default Services. 6. Right-click Initialize Active Directory for Hosting, then select Set procedure parameters. 7. When prompted for the name of the hosting organization, accept the default of Hosting and then click OK. 8. In the Requirements Status pane, right-click Hosting Platform, and select Install all in this group. 9. Click Start Deployment to start the installation of the Plans Database and Hosting Platform Service Components. 10. Monitor the deployment session on the Install Details tab. 7 Install the MPS Web Services on Server 2 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, right-click Web Service, select Install on Server, and then select . 3. Under Business Web Service->, right-click on the New Virtual Directory box, enter MPSWS, and then click OK. Note: After you assign the Web service and input the virtual directory name, the MPF Client will automatically be assigned for installation on Server 2. 4. Click Start Deployment. 5. When the deployment completes, click OK, and then quit the MPS Deployment Tool. 8 Install Resource Manager Web Client on Server 2 1. Run the MPS Deployment Tool. 324 Windows Servers 2. In the Requirements Status pane, right-click Web Services->Resource Manager Web Client, select Install on Server, and then select . 3. In the New Virtual Directory box, enter ResourceManagerWebClient, and then click OK. 4. Click Start Deployment. 5. When the deployment completes, click OK, and then quit the MPS Deployment Tool. 9 Initialize Hosted Exchange Provisioning Namespaces 1. Run the MPS Deployment Tool. 2. In the Requirements Status pane, expand Hosted Exchange. 3. Expand Exchange Platform. 4. Right-click Hosted Exchange Namespace, and then click Execute. Initialize Hosted Exchange Namespace. Make sure to check if Exchange organization is being set correctly. 5. Click Start Deployment. 10 Configure the MPFServiceAccts Group As Exchange Full Administrator 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard. 3. Click Next, click Add, click Browse, select MPFServiceAccts from the list, and then click OK. 4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK. 5. Initialize Hosted Exchange Provisioning Platform. 6. In this procedure you will initialize your environment for Hosted Exchange provisioning. 11 Configure the Microsoft Provisioning System Server for Hosted Exchange Procedure DP.3: To initialize Hosted Exchange provisioning namespaces 1. Log on to as a member of the Domain Administrators group. 2. Run the MPS Deployment Tool. 3. Expand Hosted Exchange. 4. Expand Exchange Platform. 5. Right-click Native Mode, and then click “Confirm irreversible Native Mode conversion”. 6. At the Microsoft Exchange/Native Mode dialog box, click OK. 7. Right-click Exchange Platform, and then select Install all in this group. 8. Click Start Deployment. Windows Servers 325 Check the log information at the bottom of the Configuration Wizard screen to verify that the configuration was successfully set. 12 Configure the MPSExchangeAccts Group As Exchange Full Administrator 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, right-click the top node where the name of your Exchange organization is displayed, and then click Delegate control to start the wizard. 3. Click Next, click Add, click Browse, select MPSExchangeAccts from the list, and then click OK. 4. On the drop-down menu, click Exchange Full Administrator, click OK, click Next, and then click Finish. If prompted with a security dialog box, click OK. 13 Configure the All Address Lists Container 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, click the Recipients node, expand the tree. 3. Right-click the All Address Lists and select Properties. 4. Click the Security tab, click Advanced, and then click Add under Permissions. 5. In the Name text box, type MPSExchangeAccts, and then click OK. 6. In the Apply onto list, select This object and subcontainers. 7. In the Permissions list, click Full Control. 8. Click OK three times. 14 Add the MPSExchangeAccts Group to Local Administrators Group 15 Create Mailbox Stores for Hosted Exchange (only fro enterprise exchange) 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. 2. In the console tree, expand Servers, then expand , and then expand First Storage Group. 3. Create any appropriate mailbox stores will be used as a Business Mailstores. 16 Initialize Resource Management 1. Restat IIS on server2 2. Launch Internet Explorer, and go to http://localhost/ResourceManagerWebClient/QueryResources.as px. 3. When prompted for Username and Password, log in as \Administrator. 4. Enter in the Preferred Domain Controller text box. Click Submit. 5. In the left pane, click Exchange Resource Manager. Then, select the Business Mailstores tab. 326 Windows Servers 6. Add Business Mailstore resources. 7. Important: The value should always be set to 1 for Business mail stores 8. In the left pane, click Exchange Resource Manager. Then, select the Public Stores tab. 9. Under Publicstores, click Add New Resource. 10. Add Public Store resources (Server and Public Store names you can find in Exchange System Manager). 11. In the left pane, click Exchange Resource Manager, and then, select the OAB Servers tab. 12. Under OAB Servers, click Add New Resource. 13. Add OAB Server resources. 17 Install the Hosted Exchange Offline Address Book (OAB) Update Batch Application (on page 310) 18 Deploy the MPS Sample Web Client 1. Run SetupMPSSampleWeb.msi from the Windows-based Hosting distribution media in the \Samples\Provisioning\MPSSampleWeb directory. 2. On the MPPSSampleWeb Setup Wizard Welcome page, click Next. 3. On the Select Installation Address page, accept the default Virtual Directory (MPSSampleWeb) and Port (80), and then click Next. 4. On the Confirm Installation page, click Next. 5. On the Installation Complete page, click Close. 6. Open the Internet Information Services (IIS) Manager, and then expand the default Web site. 7. Right-click MPSSampleWeb, and then select Properties. 8. Click the Directory Security tab, and then, under Authentication and access control, click Edit. 9. Clear the Enable anonymous access check box. 10. Ensure that the Integrated Windows Authentication check box is cleared. 11. Select the Basic authentication check box, and then, in the warning dialog box, click Yes. 12. Enter a backslash “\” in the default domain field. 13. Click OK, and then click OK again. 14. Close the IIS Manager window. 15. Edit the Web.Config file in the root directory of the MPS Sample Web Client (usually \inetpub\wwwroot\MPSSampleWeb). Set the following preferredDC and DefaultNamingContext key values to your preferred domain controller and default naming context. For example: ”/> example test.ts.com Value=”DC=test,DC=ts,DC=com” Windows Servers 327 19 Disable the EventSink: 1. Go to C:\Program Files\Microsoft Hosting\Provisioning\MPSWS\ and open file web.config. 2. Find the string and change value to 0 () 3. Save changes. It will allow creating Exchange Recipient Policy for new SMTP domains. Step 3. Install WS Exchange Provider Adapter Namespace WS Exchange Provider Adapter Namespace (WS stands for “Web service”) provides communication between Parallels H-Sphere and MS Exchange provider via HTTP in order to manage MS Exchange hosting in Parallels H-Sphere CP. 1 Download WS Exchange Provider Adapter Namespace installation: http://hsphere.parallels.com/downloads/wsexchangeprovider.msi . 2 Run the downloaded MSI file and follow the installation instructions. 328 Windows Servers Step 4. Create Reseller Organization Unit Create reseller organization unit under which Parallels H-Sphere users signed up for MS Exhange plans will be hosted. On Server 2: 1 2 3 4 5 6 In Internet Explorer, go to http://localhost/MPSSampleWeb When prompted, log on as Domain Administrator. Leave the Current Reseller and Current Customer fields empty. Select the General tab. In the left-hand pane, click Create a Reseller Organization. Enter information about the organization in the appropriate boxes on the Create Reseller Org page 7 Click Submit Request. 8 When the request completes, you can review the XML response at the bottom of the page. After that, you can proceed to configuring Microsoft Provisioning Framework in admin CP. This is described in MS Exchange section of Parallels H-Sphere Service Administrator Guide. That‟s how the organization unit may look like when it is created and used for Parallels H-Sphere hosting: Windows Servers 329 In the above screenshot, Organization1 is the reseller organization unit, and its organization units like exchange are Parallels H-Sphere user accounts with emails and distribution lists. 330 Windows Servers Calculating Winbox Traffic In Parallels H-Spherethe system writes winbox traffic data to XML logfiles:  YYYY-MM-DD.web.xml - http traffic,  YYYY-MM-DD.ftpg.xml - guest ftp traffic,  YYYY-MM-DD.ftpa.xml - anonymous ftp traffic. Example: 7782 39060 15 8 3493 38549 8 2 These xml files are saved to the C:\HSphere.NET\data\services\traffic\ directory. Once a day TrafficLoader (on page 38) parses these files using SOAP and writes statistic data into the translog table of the Parallels H-Sphere system database. After that these files are deleted and created anew on the next day. Windows Servers 331 Creating Mail Plan on MPS Server This document is an example of how to create a new Mail Plan on MPS Server (Server2, i.e MS Exchange Server ).  To create mail plan on MPS Server: 1 Remove the read-only attribute and then edit :\Program Files\Microsoft Hosting\Provisioning\Samples\Hosted Exchange Namespace\CreateMailboxPlan.XML. The following example shows the XML in the shipped version of this file: PopMail POP3 Mail HeBusiness HeConsumer OWA Outlook Web Access Disabled 1 IMAP IMAP Access Disabled 1 POP POP Access Enabled 0 MailboxSize Mailbox size in kilobytes 10000 kb 332 Windows Servers AD01.fabrikam.com 2 Edit the element as follows: SimpleMail 3 Edit the element this way: Basic POP3 Mailbox 4 Edit the value, where AD01.fabrikam.com is the full name of Active Directory domain controller server. 5 The edited file should now look like the following: SimpleMail Basic POP3 Mailbox HeBusiness HeConsumer OWA Outlook Web Access Disabled 1 IMAP IMAP Access Disabled 1 POP POP Access Enabled 0 MailboxSize Windows Servers 333 Mailbox size in kilobytes 10000 kb AD01.fabrikam.com 6 Save the edited file in the in the :\Program Files\Microsoft Hosting\Provisioning\Samples\Hosted Exchange Namespace\ directory as CreateSimpleMailPlan.xml. 7 From a command prompt in the :\Program Files\Microsoft Hosting\Provisioning\Samples\Hosted Exchange Namespace\ directory, execute provtest CreateSimpleMailPlan.XML (ProvTest.exe is located in C:\Program Files\Microsoft Provisioning\Tools). You now have a mailbox plan called SimpleMail, which enables a 10 MB mailbox for use by POP3 clients. This plan will show up as available to add to new organizations. Also you can edit other features like MailboxSize. By default, MPS sets mailbox size using the following scheme: - Mailbox size in kilobytes (equivalent to ProhibitSendQuota) - the default one is 90 percent of size - the default one is 500 percent of size So if you create a mailbox with the size of 100Mb, the parameters will be as follows:  Warning Quota - 90MB  Prohibit Send Quota - 100MB  Prohibit Send And Receive Quota - 500MB. Note: if the size of mailbox is ~2GB (maximum), the parameter will have the maximum possible value (not 5x2GB). Read more about Mailbox store prohibit send and receive limits of mailboxes at Microsoft documentation: http://technet.microsoft.com/en-us/library/79f14549-6c7b4073-8628-b93654f3659e.aspx. CHAPTER 19 Microsoft SQL Server Microsoft SQL, like other commercial third party products, is purchased and installed separately from Parallels H-Sphere. Microsoft SQL Server is a fully Web-enabled database with the ability to query the database through a browser and rich Extensible Markup Language (XML) support. In addition, Microsoft SQL Server holds benchmark records for scalability and reliability, both of which are crucial for the success of an enterprise database. For extensive coverage of Microsoft SQL Server, please refer to http://www.microsoft.com/sql/default.asp. In this chapter: Installing Microsoft SQL 2000 Server ................................................................ 335 Installing Microsoft SQL 2005 Server ................................................................ 336 Moving MS SQL Databases Across Servers ..................................................... 337 Moving MS SQL Databases to a New Location ................................................. 338 Microsoft SQL Server 335 Installing Microsoft SQL 2000 Server This document explains how to install MS SQL database software and integrate it with the Parallels H-Sphere system. Parallels H-Sphere supports both Microsoft SQL 7.0 and Microsoft SQL 2000 servers. MS SQL server can be installed on an Parallels H-Sphere Windows server. This means, the server must have Parallels H-Sphere Windows software installed and be added to the Parallels H-Sphere configuration.  To install MS SQL server: 1 Buy a License package. 2 Install MS SQL server following the directions of the installation wizard. 3 Configure Parallels H-Sphere connection settings to work with MS SQL server.  If you already have MS SQL server and are installing Parallels H-Sphere, follow Parallels H-Sphere Winbox Installation Guide.  If Parallels H-Sphere was installed earlier and you are adding MS SQL server to it, set the following three values for MS SQL Server variables in the /script/conf.inc file on the Windows server:  mssqlServer = IP of the MS SQL server if it works through TCP/IP or the server name if MS SQL uses pipe connection.  mssqlHSLogin = a login with system adminitrator privileges for the MS SQL server. You can create this login by means of MS SQL Enterprise Manager. If there is any login registered earlier with the same privileges, you can use it, too.  mssqlHSPasswd = password for this login. 4 Go to SQL Server Properties -> Security and choose SQL Server Authentication and Windows Authentication to allow Parallels HSphere and your customers to access MS SQL server remotely. 336 Microsoft SQL Server Installing Microsoft SQL 2005 Server This document explains how to install MS SQL database software and integrate it with the Parallels H-Sphere system. Parallels H-Sphere 2.5.0 and higher supports Microsoft SQL Server 2005 (http://www.microsoft.com/technet/prodtechnol/sql/2005/default.mspx). MS SQL server can be installed on Parallels H-Sphere Windows server. This means the server must have Parallels H-Sphere Windows software installed and be added to the Parallels H-Sphere configuration. To add MS SQL 2005 to winbox with Parallels H-Sphere installed: 1 Install ASP.NET 2.0 and check the version of ASP.NET. RootVer must be 2.0.XXXX, not 1.1.XXXX in the registry HKLM/Software/Microsoft/ASP.NET. If RootVer is 1.1.XXXX:  Go to C:\Windows\Microsoft.NET\Framework\v2.0.5xx\ through command line  Run from command line: aspnet_regiis -r  Restart IIS : iisreset /restart 2 Install MS SQL server following the directions of the installation wizard. If you installed SQL 2005, you should also install SQL Server Management Studio Express. 3 In SQL Server Managment Studio Express create login with system administrator privileges for the MS SQL server. As a rule, login „sa‟ is used. 4 Configure Parallels H-Sphere connection settings to work with MS SQL server: Note: Parallels H-Sphere 3.0 + uses Windows authentication method to connect to MSSQL server. Therefore MSSQL server should be installed locally on the same server with Parallels H- Sphere. Go to /hsphere.net/bin/hsphere.config file and make sure the NAME_OF_YOUR_SQL_SERVER is set correctly in: prop name=”server” value=”NAME_OF_YOUR_SQL_SERVER” description=”MSSQL server name or IP” 5 Go to SQLServer Properties -> Security. Chose SQL Server Authentication and Windows Authentication to allow Parallels HSphere and your customers to access MS SQL server remotely. Microsoft SQL Server 337 6 Make sure that MS SQL server IP set as a logical server IP in the E.Manager menu is set in Start -> Programs -> MSSQL 2005 Server -> Configuration Tools -> SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP(enabled) -> Properties -> IP Addresses tab. Make sure this IP is there with Active and Enabled set to Yes. 7 In your CP add MS SQL server group to the physical winboxes with MS SQL installed. 8 Add logical MS SQL servers in CP and add IP addresses for it. 9 On winboxes run the following commands: net stop hsphere net start hsphere 10 Turn on MS SQL servers in the user‟s Plan Edit Wizard. After that, try creating MS SQL databases from user‟s CP. Moving MS SQL Databases Across Servers  To move the databases from one MS SQL server to another: 1 Install the new MS SQL server, keeping the same path to databases as for the old server. That means, databases on the new server should be located on the same disc and necessarily in the same directory as for the old server. For example, on the old server data is located on d:\mssql\data\, so the data on the new server should be located in the same directory. 2 Stop the new MS SQL server. 3 Copy all MS SQL database files including the “master” database which keeps all logins information and other necessary information. Important: All database files should be put into the same directory as for the old server. 4 Start the new MS SQL server. 5 Change the MS SQL logical server IP to the new MS SQL server IP in the Control Panel. 6 All resellers should reconfigure MS SQL server aliases to use the new IP for the MS SQL server. 338 Microsoft SQL Server Moving MS SQL Databases to a New Location This document describes how to change the location of the data and log files for any MS SQL database. There are two ways to move MS SQL databases: Method 1 (preferable) 1 Create new MS SQL data location (E:\MSSQL\data\) 2 Stop MS SQL server 3 Move all databases to a new location (move *.mdf and *.ldf files) 4 Create junction link between old and new MS SQL data folders. This can be done with Sysinternals Junction (http://download.hsphere.parallels.com/shiv/WinBox/linkmagic.exe ) or any other utility of this kind 5 Start MS SQL server In case you have some databases with different from default locations: 1 Detach these databases 2 Copy these databases from old location to a new location 3 Attach these databases from a new location Method 2 1 Go to MS SQL Enterprise Manager 2 Choose the MS SQL server Properties option. For this, go to Expand SQL Server Group > MS SQL server Microsoft SQL Server 339 340 Microsoft SQL Server 3 On the Database Settings tab, change New database location and set the path to:  Default data directory, i.e. a new logical disk (E:\MSSQL\DATA\)  Default log directory (E:\MSSQL\DATA\) Microsoft SQL Server 341 4 Create the following folder E:\MSSQL\DATA\ 5 Set the same NTFS permissions as in the folder [drive]:\Program Files\Microsoft SQL\Server\MSSQL\DATA (the path where DB‟s are located). 6 Go to MS SQL Enterprise Manager > Databases and right click on the Necessary database > All tasks > Detach Database with the option Update statistics prior detach. Make sure to check database and database log files locations before detaching a database. 342 Microsoft SQL Server 7 Go to [drive]:\Program Files\Microsoft SQL Server\MSSQL\DATA and copy Detached DB files (*.mdf and *.ldf) to a new folder E:\MSSQL\DATA\ 8 Go to MS SQL Enterprise Manager > Databases and right click Databases > Attach Database. 9 Put the path to the necessary database (E:\MSSQL\DATA\) and select hsadmin in Specify database owner field. Microsoft SQL Server 10 Re databases. eat steps 6-8 for the rest of All necessary information can be found in MS SQL documentation (http://www.microsoft.com/sql/default.mspx). 343 CHAPTER 20 Virtual Private Servers Parallels H-Sphere VPS feature integrates virtual private server hosting into H-Sphere. Install H-Sphere VPS software on a separate physical box and add this box to your HSphere cluster. This software is then identified as a logical VPS server and run by a number of packages that may vary depending on your operating system Once installation is performed and VPS hosting is configured in H-Sphere, users who signup to VPS plans get a virtual server in their use and a user CP interface from which to configure servers. The number of virtual servers per your physical box is limited by the amount of system resources consumed by them and hardware parameters of the VPS host server. Since Parallels H-Sphere virtual private servers are logically separate boxes, their network interfaces must be configured identically to separate boxes in your Parallels HSphere cluster. Even though the main server has only one physical network adapter, the kernel emulates separate logical network adapters for each virtual private server. Hence, it is NOT correct to treat VPS IPs as aliases to the main server IP. Interaction with the main server. Logically separate, the main server and virtual private servers don‟t communicate with each other directly or interact any differently from regular servers. Virtual private servers don‟t know anything about their „parent‟, they don‟t even know about their virtual nature! Configuring IPs. VPS IPs are set up automatically and are registered in the settings of the virtual private servers, not the main server. DON‟T configure virtual private server IPs in the main server settings. Adding or Changing IPs. VPS IPs or netmasks can be added or changed only through the Control Panel. This can‟t be done by editing the settings of the virtual private servers. VPS Gateway. Virtual private servers should use the gateway of the main server only if they belong to its subnet. If placed in different subnets, they must be given different gateways. Configuration Parameters The default VPS configuration file is /hsphere/local/config/vserver/vps.cfg. WARNING: 1. Do not change location of the configuration file! 2. It is strongly recommended not to make changes to the configuration file manually! If you need to set parameters to the configuration file, run VPS configuration (on page 348) script (/hsphere/shared/scripts/vps-configure.pl). Virtual Private Servers See also configuration parameters (on page 375) set in the VPS configuration file. Template configuration files are located in $HSINSTALLPKG (Default: /hsphere/local/config/vserver//) where : RH73 - Red Hat Linux release 7.3 RHES3 - Red Hat Enterprise Linux ES release 3 RHAS3 - Red Hat Enterprise Linux AS release 3 RHWS3 - Red Hat Enterprise Linux WS release 3 WBEL3 - White Box Enterprise Linux release 3 CentOS3 - CentOS release 3 rpm_base.cfg - base and core of Linux rpm_development-tools.cfg - Development Tools rpm_dns-server.cfg - DNS Name Server rpm_ftp-server.cfg - FTP Server rpm_kernel-vps.cfg - kernel emulator for VPS rpm_mail-server.cfg - Mail Server rpm_mysql-server.cfg - MySQL Database rpm_news-server.cfg - News Server rpm_perl-full.cfg - Perl programing language modules rpm_pgsql-server.cfg - Postgresql SQL Database rpm_quota.cfg - quota tools for VPS rpm_samba-server.cfg - Windows File Server rpm_system-tools.cfg - System Tools rpm_web-server.cfg - Web Server VPS box configuration files located in $VPSCONFIGS (Default: /hsphere/local/config/vserver/): vps.cfg - the main configuration file for all Virtual Private Servers. vps.cfg.bak - the main configuration file backup. vps.cfg.default - default configuration for all Virtual Private Servers. vps.list - the list of all known VPS and the list of Virtual Private Servers scheduled for removal. In this chapter: VPS Scripts ....................................................................................................... 346 Backing Up VPS Content .................................................................................. 372 Adding VPS Network Gateways ........................................................................ 373 345 346 Virtual Private Servers Parallels H-Sphere VPS Configuration Parameters ........................................... 375 VPS Templates ................................................................................................. 381 VPS Limits......................................................................................................... 388 Changing VPS Solution ..................................................................................... 391 Configuring VPS Host ....................................................................................... 394 Customizing Operating System Distributive URLs ............................................. 398 VPS Scripts Parallels H-Sphere VPS is a set of scripts that serve as the backend for advanced VPS management via Parallels H-Sphere CP but they can also run from the command-line mode. The latter is the subject of this section. All VPS scripts are located in the $VPSSCRIPTS directory (Default: /hsphere/shared/scripts). Cron scripts are located in the $VPSSCRIPTS/cron (Default: /hsphere/shared/scripts/cron). In this section: Perl Modules Used by VPS Scripts.................................................................... 347 VPS Configuration ............................................................................................. 348 Create VPS ....................................................................................................... 349 Migrate VPS ...................................................................................................... 351 Delete VPS........................................................................................................ 352 VPS Cron Scripts .............................................................................................. 353 VPS Configuration Scripts ................................................................................. 357 View List of Installed VPS‟s ............................................................................... 360 Install/Uninstall Additional Packages ................................................................. 361 Check VPS Files for Changes ........................................................................... 363 VPS IP Migration Tool ....................................................................................... 365 VPS Network Configuration Tools ..................................................................... 366 Device Management ......................................................................................... 369 Virtual Private Servers 347 Perl Modules Used by VPS Scripts Note: We provide the hsphere-vps package only for: Red Hat Linux 7.3 with Perl 5.6.1 installed. Red Hat Enterprise Linux release 3, CentOS 3.x, White Box Enterprise Linux release 3 with Perl 5.8.0 installed. If you wish to install this package with other versions of Perl, you need to build your own Parallels H-Sphere VPS binaries. Perl modules: Red Hat Linux 7.3: Perl v5.6.1 modules are installed in [/usr/lib/perl5/site_perl/5.6.1/VServer/] Red Hat Enterprise Linux release 3, CentOS 3.x, White Box Enterprise Linux release 3: Perl v5.8.0 modules are installed in [/usr/lib/perl5/site_perl/5.8.0/VServer] Addon.pm Admin.pm Net.pm Util.pm Vars.pm Vrpm.pm 348 Virtual Private Servers VPS Configuration Enter the $VPSSCRIPTS directory (Default: /hsphere/shared/scripts) to run the vps_configure.pl script. SYNTAX: ./vps-configure.pl [-d|-r|-h] OPTIONS:  defaults|-d load default settings  restore|-r restore settings you made before  help|-h display this help message Run vps_configure.pl: # /hsphere/shared/scripts/vps-configure.pl Do you really want to reconfigure your VPSs [y/n]? Kernel: 2.4.21-freevps-1.2-1hugemem FreeVPS patch build: 1080548030 Base FreeVPS tools package: freevps-tools-1.2-1 Parallels H-Sphere VPS scripts package: hsphere-vps-1.2-1 RedHat release: RH73 To perform basic configuration for all virtual servers, run the scipt and follow the instructions step by step (on page 394). Virtual Private Servers 349 Create VPS To create new Virtual Private Server, run the vps-post-config.pl script: ./vps-post-config.pl VPS_HOST_NAME And put the following parameters to STDIN: IP=ADDRESS:MASK:HDEV - IP to be assigned to this VPS and allowed on network interface HDEV on your VPS box; DLIMIT=XXXX - Disk limit in Mb; MLIMIT=XXXX - Memory Limit in Mb; PLIMIT=XXXX - Limit on the number of running processes; FILELIMIT=XXXX - Number of opened files limit; TCPLIMIT=XXXX - TCP sockets limit; ROOTPWD=**** - User root password; CTRL+D - Press Ctrl+d to stop data input. Example: Create a VPS with the following configuration: Hostname: 231.tst IP address: 192.168.112.231, mask: 255.255.255.0 Disk limit: 3000Mb Memory limit: 512Mb Limit on the number of running processes: 1000 Root password: 1 [root@vps scripts]# ./vps-post-config.pl 231.tst IP=192.168.112.231:255.255.255.0[press Enter] DLIMIT=3000[press Enter] MLIMIT=512[press Enter] PLIMIT=1000[press Enter] ROOTPWD=1[press Enter] [press Ctrl+d] (end of data input) vps-post-config.pl creates the $HSVPSFILES/231.tst/231.tst.in file (Default: /hsphere/local/config/vserver/cp/231.tst/231.tst.in) with the input parameters, and registers VPS in the list of known vservers: $VPSCONFIGS/vps.list (Default: /hsphere/local/config/vserver/vps.list) Check the list of VPSs: [root@vps scripts]# cat /hsphere/local/config/vserver/vps.list You would get something like this: 350 Virtual Private Servers DELETE=”” VSERVERS=”3:231.tst” Format: DELETE=”HOSTNAME1 HOSTNAME2 HOSTNAME3” - the list of VPSs scheduled for deletion, separated with whitespaces; VSERVERS=”CONTEXT_ID1:HOSTNAME1 CONTEXT_ID2:HOSTNAME2” - the list of known VPSs, separated with whitespaces; CONTEXT_ID is a virtual server ID Virtual Private Servers 351 Migrate VPS VPS migration is performed by the vps-migrate.pl script that moves VPS(s) to another host. This script uses:   OpenSSH client:  for secure copying (scp remote file copy program)  for executing commands on a remote machine tar archiving utility. To perform a migration, access to remote servers and logging into them automatically without entering the password each time is required from the “source” box. So, the access keys should be copied from the “source” box into the destination box. If such keys are not uploaded, the script does it for you (use the—put-ssh-key option). Preparation: 1 Suspend the VPS server on the “source” box. 2 Configure the destination machine to be VPS server host:  Install all required packages (FreeVPS kernel, FreeVPS tools, Parallels HSphere VPS scripts).  Complete all configuration tasks. Actions performed by the script:  The remote host VPS servers configuration is loaded and checked  Platform compatibility is checked for the VPS box and the destination host. For example, a VPS under Enterprise Linux can‟t be moved to a host under RedHat Linux release 7.3.  The script checks whether a VPS with the same name as the migrated one exists on the destination box  Available free disk space on the destination host VPS home partition is checked as Free_space > VPS_disk_usage*1.5  The script checks if the VPS server virtual context number exists on the destination box:  if the migrated VPS server virtual context does not exist on the destination box, the VPS is created with this context  if it does exist, the first free virtual context is used for the migrated VPS  Network interface which all the virtual network interfaces were attached to is checked. If a network interface does not exist on the destination host, new one is used, and the VPS network is reconfigured to be used to assign virtual network interfaces.  VPS home is archived using the tar utility filtered through gzip  MD5SUM for the source file is compared with that of the file copied to the remote host  VPS traffic data is migrated to the destination box  Post-migration: 352 Virtual Private Servers  configuration quota check) is restored within 3 minutes by the crpn/vpscron-fix.pl cron  Migrated VPS is suspended on the destination box, and should be resumed via Parallels H-Sphere or manually. For help, run: # ./vps-migrate.pl—help vps-migrate.pl # Moves VPS(s) to another host. Usage: vps-migrate.pl—host= [--user=] --vps=v|--all [--put-ssh-key] [--help]  host # - host (DNS name/IP address) to migrate VPS(s) to.  user # - username to be used to log into the host. # If username is not specified, the name of the user executing the script will be taken.  vps  all  put-ssh-key # Generate and upload public SSH keys to remote box.  help # - VPS to be migrated. # Migrate all known VPSs. # Print this help information. Delete VPS vps-delete.pl SYNTAX: ./vps-delete.pl VPS_HOST_NAME 1 It removes existing VPS [VPS_HOST_NAME], all its configuration files, removes [VPS_HOST_NAME] from the list of known VPS. 2 If [VPS_HOST_NAME] is being created by cron at the moment, [vps-delete.pl] posts deletion request for VPS (sets the DELETE parameter in the vps.list file) 3 All deletion requests are processed by vps-cron-delete.pl cron every 4 minutes. Virtual Private Servers 353 VPS Cron Scripts These are VPS scripts scheduled in cron on the host server: */5 * * * * /hsphere/shared/scripts/cron/vps-cron.pl >/dev/null 2>&1 59 */1 * * * /hsphere/shared/scripts/cron/vps-cron-traf.pl >/dev/null 2>&1 */4 * * * * /hsphere/shared/scripts/cron/vps-cron-delete.pl >/dev/null 2>&1 */3 * * * * /hsphere/shared/scripts/cron/vps-cron-fix.pl >/dev/null 2>&1 vps-cron.pl The $VPSSCRIPTS/cron/vps-cron.pl script (Default: /hsphere/shared/scripts/cron/vps-cron.pl) runs every 5 minutes. It is used to install and configure new Virtual Private Servers. The script works as follows: 1 It checks the list of known vservers and takes each VPS and processes requested tasks from the $HSVPSFILES/VPS_NAME/VPS_NAME.in file (Default: .../cp/VPS_NAME/VPS_NAME.in). 2 If the requested task is successfully done, it creates a note in the $HSVPSFILES/VPS_NAME/VPS_NAME.out file (Default: .../cp/VPS_NAME/VPS_NAME.out) 3 If all of the requested tasks are done, it creates the DONE file: $HSVPSFILES/VPS_NAME/VPS_NAME.done (Default: .../cp/VPS_NAME/VPS_NAME.done), and deletes the request file: $HSVPSFILES/VPS_NAME/VPS_NAME.in (Default: .../cp/VPS_NAME/VPS_NAME.in). 4 It creates the FLAG file: $STATCRONPID (Default: /var/log/hsphere/vps_cron.pid) with its own PID, to prevent executing another copy of it. 5 It creates all configuration files required for VPSs: $VPSCONFIGS/VPS_NAME.conf (Default: /hsphere/local/config/vserver/VPS_NAME.conf) $VPSCONFIGS/VPS_NAME.sh (Default: /hsphere/local/config/vserver/VPS_NAME.sh) 6 It installs basic Linux RH7.3 packages and additional packages if configured, creates services, set limits, assigns IPs, and finally, starts VPS. vps-cron-traf.pl Processes VPS network traffic statistics. Creates files with VPS daily traffic statistics: /hsphere/local/var/statistic/DD.MM.YYYY.vps.txt vps-cron-delete.pl 354 Virtual Private Servers This cron script that runs every 4 minutes deletes VPS server(s) scheduled for removing. VPS server is scheduled for removing if it cannot be deleted immediately after the removing request was sent, e.g. when other tasks need to be finished first. Names of the VPS servers(s) scheduled for removing are listed delimited with whitespace in the DELETE parameter of the /hsphere/local/config/vserver/vps.list configuration file. Example: # cat /hsphere/local/config/vserver/vps.list DELETE=”vps1.psoft vps2.psoft” VDU=”” VSERVERS=”3:230.psoft 4:vps1.psoft 5:test.test 6:vps2.psoft 7:vps4.psoft 8:vps5.psoft 9:vps6.psoft 10:vps3.psoft 11:vps7.psoft 12:vps9.psoft 13:blabla.test.tst 14:vps11.psoft 15:vps12.psoft 16:vps13.psoft 17:vps-rh73-blank.psoft 18:vps14.psoft 21:newacc.test.tst 22:jumbo.jumbo23:vps200.hs.test 24:vps203.hs.test 25:vps207.hs.test 26:vps212.hs.test 27:myvps.test 28:my-server.test 29:krambambuli.test” vps-cron-fix.pl This script fixes some VPS(s) configuration: limits, usage, etc. For instance, it can fix VPS server(s) configuration that was “lost” when you upgraded the FreeVPS kernel after the host system (physical box) reboot. Fixed parameters:  VPS server virtual context recreated  VPS root directory (new root for the created virtual context) set  VPS server files context fixed   VPS server inside user/group quotas for all filesystems configured in /etc/fstab checked VPS disk usage calculated  all limits restored The script runs as a cron job and is configured to fix corrupted configuration every 3 minutes. The script also checks and fixes VPS servers(s) daily. If needed, you can run the script manually. Use—vps to fix a particular VPS and -f|-force to forcefully fix a virtual server(s) even if its(their) configuration is uncorrupted. Virtual Private Servers 355 IMPORTANT: It is recommended that you stop/suspend VPS server(s) before the fix. For help, run: # vps-cron-fix.pl—help vps-cron-fix.pl # Script for checking and fixing VPS(s) configuration: limits, usage, etc. # The script is configured to check (and to fix if needed) VPS(s) configuration every 3 minutes (run as a cron job). # VPS(s) are fixed daily anyway. Usage: vps-cron-fix.pl [--vps=|-v ] [--force|-f]  v|--vps # Fixes particular VPS. # If not set - script will fix all known VPS servers.  f|--force  help # Run script by force (even if it was run today already). # Print this help information. vps-cron-net-reconfig.pl (VPS Network Reconfiguration Cron) Location: $VPSSCRIPTS/cron/vps-cron-net-reconfig.pl (by default /hsphere/shared/scripts/cron/vps-cron-net-reconfig.pl) This script runs every 5 minutes as cron to reconfigure virtual servers‟ network (on page 366). If subnet configuration is changed, it reconfigures all affected virtual servers‟ configuration. If subnet default gateway or mask is changed, it reconfigures and restarts network for each virtual server. If network interface is changed on a virtual server, it restarts this virtual server. Usage: vps-cron-net-reconfig.pl [--vps=] [--force]  vps # Process particular VPS. # If not set - script will process all registered virtual servers.  force # Run script by force—help # Print this help information. Examples: vps-cron-net-reconfig.pl—vps=vps.test—force # Process VPS server vps.test forcefully, even if the reconfig flag is not set vps-cron-net-reconfig.pl—vps=vps.test # Process VPS server vps.test if the reconfig flag is set vps-cron-net-reconfig.pl—force # Process all registered virtual servers, even if reconfigure flag is not set 356 Virtual Private Servers vps-cron-net-reconfig.pl # Process all registered VPS server(s) if the reconfig flag is set Virtual Private Servers VPS Configuration Scripts ./vps-addip.pl VPS_HOST_NAME IP:MASK Assigns new IP address to the VPS_HOST_NAME virtual server. ./vps-rmip.pl VPS_HOST_NAME IP[:MASK] Removes IP from VPS_HOST_NAME. ./vps-dlimit-set VPS_HOST_NAME DISK_LIMIT_VALUE Sets disk usage limit for VPS_HOST_NAME to DISK_LIMIT_VALUE, in Mb. ./vps-dlimit-get VPS_HOST_NAME Returns disk limit and disk usage for VPS_HOST_NAME. ./vps-mlimit-set VPS_HOST_NAME MEMORY_LIMIT_VALUE Sets memory limit for the VPS_HOST_NAME server to MEMORY_LIMIT_VALUE, in Mb ./vps-mlimit-get VPS_HOST_NAME Returns memory limit and memory usage for VPS_HOST_NAME ./vps-plimit-set VPS_HOST_NAME PROCESS_LIMIT_VALUE Sets limit on the number of processes running on VPS_HOST_NAME to PROCESS_LIMIT_VALUE, in Mb ./vps-plimit-get VPS_HOST_NAME Returns the limit on and the number of processes running on VPS_HOST_NAME ./vps-flimit-get VPS_HOST_NAME Returns file handlers limit, and the number of opened at this moment files VPS_HOST_NAME ./vps-flimit-set VPS_HOST_NAME Sets file handlers limit for VPS_HOST_NAME 357 358 Virtual Private Servers ./vps-tcplimit-get VPS_HOST_NAME Returns the limit on socket connections and the number of established connections for VPS VPS_HOST_NAME ./vps-tcplimit-set VPS_HOST_NAME Sets limit for established socket connections for VPS VPS_HOST_NAME ./vps-dev-speed.pl Tools to get|set the speed of virtual network interface. Note: Virtual network interface speed must be divisible by 64000. Usage: vps-eth-speed.pl VPS_NAME [--dev=|-d ] --get|--set For more information, please run: vps-dev-speed.pl—help ./vps-dev-speed-set VPS_NAME [--dev=|-d ] Sets work speed to Kb/sec for virtual network interface on Virtual Private Server VPS_NAME Note: Virtual network interface speed ( value) must be divisible by 64000. If—dev=|-d option not specified, value will be set to all registered virtual network interfaces on VPS VPS_NAME ./vps-dev-speed-get VPS_NAME [--dev=|-d ] Returns work speed for virtual network interface on Virtual Private Server VPS_NAME Note: If—dev=|-d option not specified, returns speed for all virtual network interfaces registered on VPS VPS_NAME, in the following format: VDEV0 SPEED0 VDEV1 SPEED1 ... ./vps-start.pl [VPS_HOST_NAME | [-a|--all]] Virtual Private Servers 359 Turns on VPS_HOST_NAME, or all known stopped VPS servers if the -a|--all option is specified. ./vps-stop.pl [VPS_HOST_NAME | [-a|--all]] Turns off VPS_HOST_NAME, or all known running VPS servers if the -a|--all option is specified. ./vps-suspend.pl [VPS_HOST_NAME | [-a|--all]] Suspends (turns off and sets ONBOOT=no) vserver [VPS_HOST_NAME], or all known VPS servers if the -a|--all option is specified. ./vps-resume.pl [VPS_HOST_NAME | [-a|--all]] Resumes (turns on and sets ONBOOT=yes) vserver [VPS_HOST_NAME], or all known VPS servers if the -a|--all option is specified. ./vps-rootpwd.pl VPS_HOST_NAME To set new password for user root, send it to STDIN. ./vps-du.pl Returns disk usage for all known VPSs on the host server in the format required by Parallels H-Sphere Control Panel. ./vps-get-config.pl VPS_HOST_NAME Returns all VPS configuration parameters in the format required by Parallels H-Sphere Control Panel. 360 Virtual Private Servers View List of Installed VPS’s The ./vps-list.pl script returns brief information about all VPS installed on the host server, installed VPS packages, values of configuration variables. Example: # ./vps-list.pl Kernel release: 2.4.21-freevps-1.3-22smp FreeVPS kernel patch build: 0 [19691231] FreeVPS tools release: 1.3-9 Parallels H-Sphere VPS release: 1.3-6.4 [20050426] Linux release: CentOS release 3.3 (final) [CentOS3] Free disk space on VPS home [/home/hsphere/local/vservers]: 9346 Mb Virtual Private Servers found on the host: --------------------------------------------------------------------------------------------------- ID NAME STATUS VDEV:HDEV:IP/MASK+|-(UP|DOWN) DISK (Mb) MEMORY (Mb) SWAP PROCESSES CPU (%) TRAFFIC -----------------------------------------------------------------(Mb)------------s—h—used-----(Mb) 5 vps1.psoft run. eth0:eth0:10.0.0.2/24- 0 1707.6 0 0.8 0.5 0 5 0 0 0 0.0 6 vps2.psoft run. eth0:eth0:160.79.224.138/24+ 0 425.0 0 2.2 1.4 0 8 0 0 0 0.0 Display all settings for VPSs on this host [y/n]? Virtual Private Servers 361 Install/Uninstall Additional Packages To install an additional template or package into completely created virtual server use vps-pkg-inst.pl script. Run # ./vps-pkg-inst.pl—help to get help on the script options: vps-pkg-inst.pl # Install template or single package into Virtual Private Server(s) Usage: vps-pkg-inst.pl—vps=|--all—package=|-template=