Anonymize RVTools

While Dr Migrate’s AVS Express SaaS instance deletes all ingested RVTools data after generating the PowerPoint proposal, some organizations may prefer to anonymize their RVTools files before uploading them to Dr Migrate.

Automated RVTools Anonymizer

Dr Migrate provides a simple executable that locally anonymizes an RVTools file by masking sensitive data columns. It also removes any non-essential columns for the assessment. Internet access is not required to run the package as all processing is performed on the local machine.

1. Download the RVTools Anonymizer here

2. Launch the anonymizer and select the target RVTools file.

1. Once completed, the anonymized file will be located in the same directory as the source file named ‘filename_anonymized’.

Source Code Request

In the event an organization wishes to inspect the source code of the package, please request via: support@altra.cloud

Checksum

The checksum of the packaged is: a32afa9566114ac5764a618d70e72f2880f9d481633cc76a24e53d02efcc00d8

Manually Anonymizing an RVTools File

Alternatively, you are also able to manually anonymize an RVTools file, however this is not recommended, as it is easy to make mistakes and these may impact the accuracy of the report.

Step 1 - Removing Unused Columns

Delete all the sheets and columns except for the below:

vInfo	vHost	vPartition	vMetaData
VM	Host	VM	RVTools version
Powerstate	Datacenter	Capacity MiB
CPUs	# CPU	Consumed MiB
In use MiB	Cores per CPU	Disk
Memory
Template
SRM Placeholder
OS according to the configuration file
OS according to the VMware Tools

Step 2 - Masking Sensitive Columns

You may want to additionally mask columns that could be considered sensitive, such as:

• VM (appears in vInfo & vPartition)
• Host (appears in vHost)

It is not recommended to mask the Datacenter column as this appears in the PowerPoint AVS Express report.

Mask both VM & Host with respect to the following guidelines:

1. Each unique VM name in vInfo should have a corresponding unique masked name.

• For example VM_1, VM_2, VM_3, etc.

1. Since the column ‘VM’ appears in both the vInfo and vPartition sheets, the masked names should match between the sheets as they did before the masking.

• For example if the first VM was called ‘Example_VM_Name’ in vInfo and has now been masked to VM_1, every occurrence of ‘Example_VM_Name’ in vPartition should be replaced with VM_1, and so on for all VM names.
• Please note: Since vPartition contains multiple rows per VM whereas vInfo contains 1 row per VM, it is recommended to use an Excel VLOOKUP to do something like this.

1. Each unique Host name in vHost should have a corresponding unique masked name.

• For example Host_1, Host_2, Host_3, etc.