User manual NOVELL PLATESPIN PORTABILITY SUITE 8.1 CONFIGURATION

[. . . ] novdocx (en) 13 May 2009 AUTHORIZED DOCUMENTATION Configuration Guide Novell® 8. 1 August 3, 2009 PlateSpin® Portability Suite www. novell. com PlateSpin Portability Suite 8. 1 Configuration Guide novdocx (en) 13 May 2009 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. [. . . ] A local administrator is implicitly part of this group. Portability Suite Power Users: Have access to most features and functions of the application with some limitations, such as restrictions in the capability to modify system settings related to licensing and security. Portability Suite Operators: Have access to a limited subset of system features and functions, sufficient to maintain day-to-day operation. Configuring Portability Suite and Your Network Environment 15 novdocx (en) 13 May 2009 When a user attempts to connect to a Portability Suite Server, the credentials provided through the Portability Suite Client are validated by IIS. If the user is not a member of one of the Portability Suite roles, connection is refused. If the user is a local administrator on the Portability Suite Server host, that account is implicitly regarded as a Portability Suite Administrator. The following is a list of permissions for each role. Table 2-1 Portability Suite Roles and Permission Details Role Details Administrators Power Users Operators Licensing: Add, delete licenses; transfer workload licenses Machines: Discover, undiscover Machines: Delete virtual machine Machines: View, refresh, export Machines: Import Machines: Export Portability Suite Networks: Add, delete Jobs: Create new job Jobs: View, abort, change start time Workload Protection: Protect workload, cancel protection yes yes yes yes yes yes yes yes yes yes no yes no yes yes yes no yes yes yes yes yes yes yes no yes yes yes no yes no no no yes no yes no no yes no yes no yes no no yes no yes no no Workload Protection: View, start synchronization in existing yes schedules Imaging: Protect image, cancel synchronization schedule Imaging: View, start synchronization in existing contracts yes yes Imaging: Consolidate increments, apply increments to base, yes delete increments, install/delete image servers Block-based Transfer Components: Install, upgrade, remove Device Drivers: View Device Drivers: Upload, delete Portability Suite Server access: View Web services, download client software Portability Suite Server settings: Edit settings that control user activity logging and SMTP notifications Portability Suite Server settings: Edit all server settings except those that control user activity logging and SMTP notifications Run Diagnostics: Generate detailed diagnostic reports on jobs. Post-conversion Actions: Add, update, delete yes yes yes yes yes yes yes yes yes yes yes no 16 PlateSpin Portability Suite 8. 1 Configuration Guide novdocx (en) 13 May 2009 2. 1. 2 Assigning Portability Suite Roles to Windows Users To allow specific Windows domain or local users to carry out specific Portability Suite operations according to designated role, add the required Windows domain or user account to the applicable Windows local group (Portability Suite Administrators, Portability Suite Power Users, or Portability Suite Operators) on the Portability Suite Server host. For more information, see your Windows documentation. 2. 2 Setting Up User Activity Logging By default, Portability Suite records all user activities in a log file, PortabilitySuite. UserActivityLogging. log, located on your Portability Suite Server host, in the following directory: . . \PlateSpin Portability Suite Server\logs. The format of an individual log entry is: date|Category|description|user|details1|details2 The Category element describes the functional area applicable to a particular action; for example, Security, Inventory (discovery operations), LicenseManagement, or Migration (workload portability operations). Elements details1 and details2 depend on the Category and provide additional information if applicable. Below is an example of a log entry recording the login action of a user with the domain account MyDomain\John. Smith. 2008-09-02 14:14:47|Security|User logged in|MyDomain\John. Smith When the size of a log file reaches a specified value, it is rolled over to a new file with a sequential number appended to the name: PortabilitySuite. UserActivityLogging. log. 1 PortabilitySuite. UserActivityLogging. log. 2 PortabilitySuite. UserActivityLogging. log. 3 When the number of log files reaches a specified value, the system starts overwriting the oldest file each time a rollover is performed. To enable or disable user activity logging, and to specify log file size and rollover options: 1 In Portability Suite Client, click Tools > Options. 3 Specify the required options, then click OK. Configuring Portability Suite and Your Network Environment 17 novdocx (en) 13 May 2009 2. 3 Network Communication Prerequisites Machines that you plan to designate as migration sources or targets, such as production workloads and virtual machine servers, must have certain prerequisite software components installed and specific ports for transport layer protocols open. The following sections summarize these requirements. Section 2. 3. 1, "Network Communication Prerequisites for Discovery, " on page 18 Section 2. 3. 2, "Network Communication Prerequisites for Workload Migration and Protection, " on page 19 2. 3. 1 Network Communication Prerequisites for Discovery The following are software, network, and firewall requirements that systems in your environment must meet for the discovery and inventory process. For information about the actual discovery procedures, see "Discovering Source Workloads and Migration Targets" in your User Guide. Table 2-2 Network Communication Prerequisites for Discovery Operations System Prerequisites Portability Suite Server Microsoft* Windows* Server 2008 and Windows Vista* sources Open port 80 (HTTP). Required to maintain communication among Portability Suite Server, sources, and targets. Built-in Administrator or domain admin account credentials (mere membership in the local Administrators group is insufficient). On Vista, the account must be enabled (it is disabled by default). The Remote Registry service enabled (disabled on Vista by default). Firewall configured with these Inbound Rules enabled and set to Allow: File and Printer Sharing (Echo Request - ICMPv4In) File and Printer Sharing (Echo Request - ICMPv6In) File and Printer Sharing (NB-Datagram-In) File and Printer Sharing (NB-Name-In) File and Printer Sharing (NB-Session-In) File and Printer Sharing (SMB-In) File and Printer Sharing (Spooler Service - RPC) File and Printer Sharing (Spooler Service - RPC-EPMAP) NOTE: The firewall settings above are configured using the Windows Firewall with Advanced Security utility (wf. msc). You can achieve the same result by using the basic Windows Firewall utility (firewall. cpl): select the File and Printer Sharing item in the list of exceptions. 18 PlateSpin Portability Suite 8. 1 Configuration Guide novdocx (en) 13 May 2009 System Prerequisites All supported Windows sources prior to Windows Server 2008 and Windows Vista Windows Management Instrumentation (WMI) installed Open ports 135/445 (TCP) for DCOM/RPC Windows NT* Server does not include WMI as part of the default installation. [. . . ] Maximum number of files for rollover: When the number of log files reaches the specified value, the system starts overwriting the oldest file each time a rollover is performed. Configuring Portability Suite and Your Network Environment 25 novdocx (en) 13 May 2009 2. 6. 4 Default Job Values Use this tab to specify default migration job values specific to the target virtualization platform. To access this dialog box in the Portability Suite Client, click Tools > Options. Target Container Name and Path Details: These variables control naming conventions for target paths and containers. Expand a variable set and click a variable to edit its value. Job Conversion Defaults: Use this area to set defaults that affect all migration jobs. [. . . ]