Invoke-AzVMRunCommand returns a string output i want to have list of objects , is there anyway to get that .
I am using below cmdlets to fetch the output :
$out = Invoke-AzVMRunCommand -ResourceGroupName "Test" -VMName "PraveenTestVM7" -CommandId runpowershellscript -ScriptPath C:\Users\praveen.mittapalli\Desktop\RawDiskScript.ps1 -Verbose
$finaloutput = $out.Value[0].Message
The $finaloutput is a string but i need a list of object is there anyway to get that or convert it
Hi you can try this as mentioned below using cs convertor to get it in usable format :
Remote script :
Get-Disk | Where-Object PartitionStyle -EQ 'RAW' | ConvertTo-Csv
Invoke script :
$out = Invoke-AzVMRunCommand -ResourceGroupName "Test" -VMName "TestVM" -CommandId runpowershellscript -ScriptPath C:\Users\Desktop\RawDiskScript.ps1 -Verbose
$s=$out.Value[0].Message
$x=$s | ConvertFrom-Csv
$x | Export-Csv -Path C:\Users\Desktop\testrawdisk.csv -NoTypeInformation
why you need convert something From csv if on the next line you will export it back to the csv?
That's because without convertto-csv the output comes in string format which is a list of object in string format , by doing so i get it in a readable format and can convert it back to object in my invoke script
i'm not saing anything about converto-csv but about convertfrom-csv
you can just execute
$out.Value[0].Message | out-file C:\Users\Desktop\testrawdisk.csv and got exact the same output
No, there isn't. The data are deserialized before being returned. The same is true for any cmdlet/script that's run on another machine.
Hi，
A string actually is an object of string class. What do you want $finaloutput to be like?
Best Regards，
Ian
the expected output is a list of azure vm disks objects but i am getting it in a string format hence not a viable format to output it in a csv ot html file
for getting azure vm disk information you have other prefferable ways like this
Hi thanks for your response i already knew this azure level disk report, but in my case i need OS level raw disks hence i am using invoke cmdlet
16 people are following this question.
