Azure ASRDeployment v3.52 unable to profile hyper-V servers

Question

Azure ASRDeployment v3.52 unable to profile hyper-V servers

Dowell, Keith 0

I have generated a txt file vm list using the ASRD tool to. This tool created a list of VMs in a text file. That made a long list of VMs as an example below:

Hyp-Server1\App-Server

But then when I run the profiling command It runs for a second and then stops leaving the following messave

2025-08-25T08:16:57.4988690-07:00	Info:	Trace Session Started
08/25/2025 08:16:57:
08/25/2025 08:16:57:Input passed from command line and default values from configuration file: 
FileVersion: 5.24.916.7
ServerName: HyperV
UserName: domain\****
Operation: StartProfiling
Virtualization: HyperV
InputVmFileName: C:\temp\VMList5.txt
Directory: C:\temp\Profiling_Data
NoOfDaysToProfile: 0.0416666666666667
UserInput: Default
Geo: 
SubscriptionId: 
OfferDurableId: 
OfferPurchasedRegion: 
StartDateLocalTime: 1/1/0001 12:00:00 AM
EndDateLocalTime: 1/1/0001 12:00:00 AM
NoOfHoursToCompleteIR: 0
Compression: 0
NormalizedFile: 
DesiredRPOInMin: 0
DesiredBandwidthInMbps: 0
DesiredRPOList: 
PercentileForBandwidthList: 
PercentileForRPOGivenBandwidthList: 
PercentileRPOToShow: 0
NumberOfBandwidthValuesForIR: 0
PercentileBandwidth: 0
WriteIOPSPercentile: 0
ReadWriteIOPSPercentile: 0
DataChurnPercentile: 0
SnapshotDataChurnPercentile: 0
BandwidthAdjustmentFactor: 0
GrowthFactor: 0
StorageAccountName: 
StorageAccountEnvironment: AzureCloud
CandidateServer: 
IsManagedDisk: Any
IsLargeDisk: Any
VMLIST: ut-frb, 

08/25/2025 08:16:57:Performing prerequisite checks...
08/25/2025 08:16:57:The special character: \ is invalid in a VM:HYP-FBR\UT-FRB. Remove the special characters from VMName list.
08/25/2025 08:16:57:
2025-08-25T08:16:57.6238701-07:00	Info:	Trace Session Ended

Please note I just edited to remove username and full server names but all the context is here. I also ran this with only 1 server in the textfile for testing.

so the ASRDeployment tool seems to generate a list that it can't use....

1 answer

Your answer

Answer 1

Siva shunmugam Nadessin 575 Microsoft External Staff Moderator

Hello Dowell, Keith,

It looks like you're running into an issue with profiling your Hyper-V servers using the ASRDeployment tool. The error message you received indicates that there are invalid special characters in the VM name format. Specifically, the backslash () character in the VM name is causing the tool to reject the input.

Here's what you can try to resolve the issue:

Edit the VM List: Make sure your VM list text file (C:\temp\VMList5.txt) follows the correct format. The standard format should be HostName\VMName on each line, but if you're encountering issues, consider checking for any extraneous characters or formatting errors.

For instance, instead of:

Hyp-Server1\App-Server

You might want to test with just the App-Server name or ensure that the names don't contain characters that are not acceptable.

Remove Special Characters: If your VM names contain special characters (other than the backslash), try renaming the VMs if possible, or remove those characters from the text file and see if that helps.
Test with a Single Entry: Since you mentioned that you tried with a single server for testing, ensure the VM name is exactly as it is in Hyper-V without any special characters (i.e., just App-Server).
Confirm VM Connectivity: Make sure that the Hyper-V host is accessible and that the VMs are running when you execute the profiling command.
Check Permissions: Ensure that the user you are using to run the tool has administrative access on both the Hyper-V host and the VMs you are trying to profile.

Reference Document:

https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-deployment-planner-run?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#get-the-vm-list-for-profiling-hyper-v-vms

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-deployment-planner-run?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#profile-vmware-virtual-machines

Please click Accept Answer and upvote if the above was helpful.

Dowell, Keith 0 Reputation points

2025-08-26T12:28:37.74+00:00

this answer was taken from your AI, I know because it has an issue detecting \ and marked two parantheses (), this is not an answer.
Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-27T02:55:20.73+00:00

Hello Dowell, Keith,

The answer was validated before it was posted, but since you have issue in special character \ kindly look into below resolution and see if it helps.

Replace entries like DOMAIN\VMName with just VMName since \ (backward slash) apart from - & . is treated as special character for example

HYP-FBR\UT-FRB

With just

UT-FRB

To specify domain context in the Azure Site Recovery Deployment Planner (ASRD tool)— especially when profiling Hyper-V virtual machines—You can use -Server parameter to specify the domain and -VMListFile parameter to specify the Virtual machines.

Reference document:

Run the Deployment Planner for VMware disaster recovery with Azure Site Recovery - Azure Site Recovery | Azure Docs

Still facing the issue then share the ASRD command you are using for us to investigate further, If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.

Dowell, Keith 0

thanks for the reply. I have tried this. I get the following response.
I ran the following syntax - with minor changes to protect sensitive info.

ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization Hyper-V -Server Hyp-Server.contoso.local -Directory "C:\temp\Profiling_Data" -VMListFile "C:\temp\VMList5.txt"  -NoOfMinutesToProfile 60 -User Contoso\server.admin

The process ends immediatley and I find the response in the logs:

VMLIST: app-pou, dc-pou, it-pou, sql-pou,

06:21:23:Performing prerequisite checks...
08/27/2025 06:21:24:Finding all clustered nodes
08/27/2025 06:21:24:Saved Physical Disk Volume Details to C:\temp\Profiling_Data\PhysicalVolumeDetail.xml)
08/27/2025 06:21:24:Successfully Got HostList for all Clusters
08/27/2025 06:21:24:Finding VMs along with their VHDs....
08/27/2025 06:21:24:Exiting Method FillMapOfVMToVhd()
08/27/2025 06:21:24:Finding VHDs that dont need to be profiled
08/27/2025 06:21:24:Prerequisite checks completed.
08/27/2025 06:21:24:
Total number of profiling virtual machines: 0.
08/27/2025 06:21:24:Exiting.
08/27/2025 06:21:24:
2025-08-27T06:21:24.5082670-07:00	Info:	Trace Session Ended

Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-27T15:06:09.96+00:00

Hello Dowell, Keith,

As you can see the total number of profiling virtual machines is 0 which indicates the virtual machines are not detecting. Kindly check the virtual machines are valid and also it is available in the domain Hyp-Server.contoso.local.

Also ensure the VMs you're trying to profile are running and accessible from the Hyper-V host.

When specifying the VM names in VMList5.txt mention each VM in new line as below

app-pou

dc-pou

it-pou

sql-pou

If the issue still persist try with only one VM and check if it works and narrow down the error.

If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily.
Dowell, Keith 0 Reputation points

2025-08-27T19:56:11.14+00:00

I already do have them broken down line by line. tried with just their core names and also with the local domain called out e.g., app-pou.contoso.local

They are all VMs on the hyper-v server refereneced as well. I have tried only 1 VM on multiple Hyper-Vs doesn't seem to matter here.
Dowell, Keith 0 Reputation points

2025-08-28T12:53:14.32+00:00

I am beginning to think it may also be a connection issue with the Hyper-V's if I put in a junk username for the connection it gives me the same prereq checks. I expected an error stating bad username but I never got one. When looking at the Hyper-V Security logs I do not see any connection attempt being made or failing there.

Share via

Azure ASRDeployment v3.52 unable to profile hyper-V servers

1 answer

Your answer