...
Audit verifies whether the source and destination machines comply with the requirements listed in /wiki/spaces/VDOC/pages/310706978. You can run the Audit check from the Administrative Console by clicking Run Audit before you find applications on the source machine, or from the CLI by executing https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/314212459/virtaaudit?search_id=2f59b815-88d1-49ed-acca-e579a401ca5a.
For each pre-requisite, the Audit Report will indicate findings as follows:
...
Open the Audit Report in the appliance
ctrack/logfolder, orClick the Audit Report tab in the Appliance Logs tab in the Administrative Console.
...
Running Audit from the Administrative Console
Double-click the VirtaMove Administrative Console shortcut on your desktop.
Create a container:
Click Application on the Menu bar
Click "Create Empty VAA"
Click the Tether tab
Enter the source machine's information.
Click Run Audit.
To check the output, click the Appliance Logs tab and then click the Audit Report tab.
...
Requirement | Description | ||
Registry key value | If the registry key value If Additionally, if RemoteAccessEnabled is disabled on the source machine, attempts to connect from the destination machine to the source machine and list COM+ applications on the source machine will result in an error. | ||
Membership in the Distributed COM Users Group | The account used to perform the export (the account specified in the tether credentials) must be a member of the Distributed COM Users group on the source machine. Otherwise, the export will fail. | ||
Configure your firewall to allow DCOM connections | You may need to configure your firewall to allow DCOM connections. For information, see: | ||
| For Windows Server 2003 Source Machines To ensure that VirtaMove can access COM/COM+ components related to your application, the Application Server Role must be installed and the following key must be enabled (set to 1) on the source server:
A reboot is not required after you change the value of this key. For Windows Server 2008 and Higher Source Machines For Windows Server 2008 and higher source machines, the |
...
| Code Block |
|---|
Failed to intercept OS calls. Sanity test failed. Cannot dock. |
For more information, see Antivirus.
Domain Controller
This section indicates whether the source machine is a domain controller, a server that responds to authentication requests and verifies users on a Windows domain.
...
A firewall comparison tool is available if you want to compare firewall rule differences or troubleshoot firewall issues between the source and destination. See Comparing Firewall Rules Group Policies between Source and Destination for more information.
Group Policies
...
The group policy section in the audit report indicates whether group policy information was successfully collected from the source and destination machines. If the audit was successful, then you can perform a group policy comparison using the Group Policy Comparison tool from the Administrative Console. https://virtamove.atlassian.net/wiki/spaces/VE/pages/309297809/Group+Policy+Comparison+Tool?search_id=8befec8f-bb8f-4f46-ac1d-6efb11f17c83 from the Administrative Console. If the audit was not successful, the audit report will indicate why group policy information could not be collected.
...
If Web Deploy 3.0 was installed on the source server and you subsequently installed Web Deploy 3.5 or higher in order to successfully migrate your application after the source and destination machines are connected via VirtaMove Source Agent, you will need to run
...
on the destination server so that the destination server will recognize the new installation of Web Deploy on the source server. It indicates whether Web Deployment Agent is installed and started.
...
VirtaMove Source Agent communicates through TCP port number 9665 by default. You can configure the port number to a different number if required. See https://virtamove.atlassian.net/wiki/spaces/VDOC/pages/311263870/VirtaMove+Source+Agent?search_id=ad789219-0efd-43c1-83fa-db74b84f128b for more information.
If the Audit Report indicates that a required port is closed, makes sure that external nodes between the destination machine and the source machine also permit communication across these ports (port 445, 9665, etc.). For example, if you are migrating across a cloud managed by to an Amazon Web Services (AWS) managed cloud server, make sure that AWS also has these ports opened.
...
Remote Access must be enabled to accept COM requests , and may be required for DCOM.
To enable remote access, the registry key values Com+Enabled and RemoteAccessEnabled must be set to 1 in the HKLM\SOFTWARE\Microsoft\COM3 registry key on the source machine. The Remote Access enabled value is used in the COMPlus check. Enable the key as follows:
...