5.10 Handling Operating System Services and Applications

Portability Suite provides a mechanism for conversion jobs to handle Windows services (including special features for those related to Microsoft SQL Server and Microsoft Exchange Server software), Linux daemons, Solaris services, and virtualization enhancements (such as VMware Tools). In addition, when Windows HAL or kernel file replacements are required, you can view which ones were selected for update during a conversion job.

5.10.1 Handling the Startup Mode of Services (Windows Targets)

You can configure a job to modify the startup mode of selected Windows services after the conversion is complete. For example, if you don’t need a certain Windows service to continue running on a virtualized workload, you can configure your job to set that service’s target startup type to Disabled.

If you require a service to start upon another service’s request, set the startup type of the required service to Manual.

You can also configure the job to restore a service’s original startup type after the conversion is complete. For example, you might require a virus scanner to be disabled during the conversion, but its startup type to be restored after the conversion completes.

HINT:You can globally configure your startup mode preferences for selected Windows services in Portability Suite Server default options. See Target Service Defaults in your Configuration Guide.

To configure the post-conversion startup mode of Windows services:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click Windows Services (Target), then click an item in the Start Mode column.

  • In Wizard mode: In the wizard’s navigation pane, click Services, then click an item in the Target Mode column.

5.10.2 Handling Services During Live Transfer (Windows Source Workloads)

For jobs that are using the VSS File-based and VSS Block-based Live Transfer methods, Portability Suite provides a mechanism to stop selected services during the conversion. This ensures that data on your source is captured in a consistent state.

If your source workload is running Microsoft SQL Server or Microsoft Exchange Server software, you can configure your conversion job to automatically copy the database files of these servers. If you do not require the conversion to include the volume containing the databases, consider not stopping these services.

If your source workload includes I/O-intensive application services that might inhibit the ability of the file transfer process to keep up with the changes, consider stopping them during a Live Transfer conversion.

After the completion of the conversion, services that you select to stop during a Live Transfer conversion restart on the source automatically, unless you explicitly configure your conversion job to power off the source on completion.

HINT:You can globally configure your preferences for stopping selected Windows services during VSS File-based or VSS Block-based Live Transfer. See Source Service Defaults in your Configuration Guide.

To specify which Windows services to stop during a VSS-aware Live Transfer:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click Live Transfer Services (Source). To indicate that you want SQL Server and Exchange Server database files copied during the conversion, click Advanced.

  • In Wizard mode: In the wizard’s navigation pane, click Transfer Services.

5.10.3 Viewing Windows System Files Selected for Replacement During a Conversion

When converting Windows workloads with system files (such as a HAL or kernel files) that are incompatible with the target infrastructure, Portability Suite uses an appropriate file from its library and saves a backup copy of the source file (*.bak) on the target, in the same system directory.

You can view the HAL or kernel files that Portability Suite identifies as those requiring replacement:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click System Files.

  • In Wizard mode: Not available.

The following warnings might display at the bottom of the dialog box:

Driver Cache is empty

Indicates that you might need to place the necessary files into the local driver cache on the source Windows server (..\Windows\Driver Cache).

The driver cache contains a higher version

Portability Suite has a partial match with its matrix but the driver cache contains a higher version of one or more system files than what Portability Suite will use.

File <filename> will be replaced with lower version

Portability Suite has not found a match for the system files in its matrix. It will replace the system files with a version that is lower than what was discovered as the source machine's original system files.

File <filename> will be replaced with higher version

Portability Suite has not found a match for the system files in its matrix. It will replace the system files with a version that is higher than what was discovered as the source machine's original system files.

If warnings appear on the screen, click More Help (only available if warnings exist) to learn more.

See also the following Knowledge Base Articles:

  • Q20815: FAQ: Understanding the System Files Information screen

  • Q20817: INFO: How to Restore the Driver Cache on a source machine

5.10.4 Handling the Run Level of Daemons (Linux Targets)

You can configure a job to modify the run level of selected Linux daemons after the conversion is complete. Use the following numeric values:

0

Shutdown

1

Single-user mode

2

Unused (user-defined)

3

Full multi user-mode (no GUI)

4

Unused (user-defined)

5

Full multi-user mode with display manager (GUI)

6

Reboot

To configure the post-conversion run level of Linux daemons:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click Linux Daemons (Target), then click an item in the Run Level column.

  • In Wizard mode: In the wizard’s navigation pane, click Daemons, then click an item in the Target Run Level column.

5.10.5 Handling Services on Solaris Targets

You can select Solaris services for the system to enable or disable after the conversion is complete.

To enable or disable the required Solaris services:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click Solaris Services Configuration, then select or deselect the required service in the Enabled column.

  • In Wizard mode: Not available.

5.10.6 Handling Virtualization Enhancement Software

For V2X conversions, Portability Suite provides a mechanism to automatically uninstall virtualization enhancement software, such as VMware Tools.

When converting a workload on a VMware platform that has an earlier version of VMware Tools installed, Portability Suite identifies the presence of obsolete software and adds a dedicated VMware Tools Cleanup step in the conversion job.

You must provide administrator credentials to uninstall VMware Tools. The credentials provided must match the admin-level user account that was logged in during the installation of VMware Tools.

When the earlier version is uninstalled, Portability Suite proceeds with the installation of the new version of VMware Tools.

NOTE:If you are downgrading a virtual machine that has VMware Tools installed, or if you are converting a virtual machine to another VMware target that has an older version of VMware Tools, the installation of VMware Tools during the configuration of the target will fail.

To configure a job to remove or replace VMware Tools during the conversion:

  • In Advanced mode: In the Conversion Job window, under the Operating System and Application Configuration section, click Clean up VMware Tools.

  • In Wizard mode: In the wizard’s navigation pane, click VM Tools.

Depending on the target, Portability Suite identifies existing instances of VMware Tools and prompts to either replace or remove them, as applicable:

  • For non-VMware targets: The job configuration interface prompts you to uninstall VMware Tools. Provide the same admin-level credentials used to install the software. If the credentials are unknown, VMware Tools remains on the target machine after conversion.

  • For VMware targets: The job configuration interface prompts you to replace VMware Tools. Provide the same admin-level credentials used to install the obsolete version of VMware Tools. If the credentials are unknown, install the new version of VMware Tools manually after the conversion completes.