3

I have created VM which needs to download some files from Azure File Storage. I am looking for a way to automate this and I am trying the Azure VM Run command Script.

The first step CmdKey is all working fine but the next step which is:

net use Z: \\my123storageaccount.file.core.windows.net\databases /u:AZURE\my123storageaccount sskhgkghgkuytiytru...==

is failing with these messages.

When I login to that VM and run the command in PowerShell window it works without any error.

One thing that might help is the storage account name in the error is trimming the first letter the one I have. For instance, if it's called MyStorageAccount in the error it is saying yStorageAccount.file.core.windows.net

any help

CivFan
  • 13,560
  • 9
  • 41
  • 58
Mohsen Kokabi
  • 31
  • 4

4 Answers4

1

For me, the issue was that, according to the Azure docs, "scripts run as System on Windows." So when you login as your normal user, that user doesn't have the credentials saved, and can't view the mounted drive contents.

To workaround this, you can use psexec (from the PSTools package) to run as your regular user. For example:

psexec.exe \\your-ip -u your-user -p your-pass cmdkey /add:...
psexec.exe \\your-ip -u your-user -p your-pass net use Z: \my123storageaccount.file.core.windows.net\databases /u:AZURE\my123storageaccount sskhgkghgkuytiytru...==

Note: Due to voodoo black magic, you have to use the form of psexec.exe \\your-ip rather than just psexec.exe as System user, or risk upsetting Billy Goates.

CivFan
  • 13,560
  • 9
  • 41
  • 58
0

You can copy files like this. The powershell commands can be copied from Azure, using 'connect' from the context menu of the share in the Azure portal. If this doesn't work could be connectivity or may be SMB related 

$buildSource = 'M:\build\'

$acctKey = ConvertTo-SecureString -String "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -AsPlainText -Force
$credential = New-Object System.Management.Automation.PSCredential -ArgumentList 
"Azure\wserverBuild", $acctKey
New-PSDrive -Name M -PSProvider FileSystem -Root "\\wserverBuild.file.core.windows.net\build" -Credential $credential -Persist

Copy-Item  'M:\build\' -Destination 'C:build' -Recurse
Tim Tharratt
  • 1,251
  • 1
  • 10
  • 18
  • Hi Tim I am g4tting this New-PSDrive -Name M -PSProvider FileSystem -Root "\\mystorageaccount.file.core.windows.net\databases" -Credential $credential New-PSDrive : Illegal characters in path. – Mohsen Kokabi Aug 17 '18 at 08:21
  • it's possible you have have spurious characters in your code. If you use the cut paste method from the portal it should work. – Tim Tharratt Aug 17 '18 at 10:17
0

Update

On my side, I can download some files from Azure File Storage with Azure VM run command script.

The main steps are as follows:

  • Copy the script from my storage account-files-connect.

  • Paste the script to Azure virtual machine-run command-RunPowerShellScript-PowerShellScript.

enter image description here

According to this doc, Running a command requires the Microsoft.Compute/virtualMachines/runCommand/action permission, which the Contributor role and higher have. Please check this one your side.

Also, check the Azure VM Agent when logging into the Azure VM, look for a process name WindowsAzureGuestAgent.exe from Task Manager.

References: Azure Virtual Machine Agent overview

Nancy
  • 26,865
  • 3
  • 18
  • 34
  • I found the script from storage account and it works if I RDP to the VM but it doesn't work when I try it in **Run Command Script**. – Mohsen Kokabi Aug 17 '18 at 10:59
  • I also use this script from the portal, and can you share your Run Command Script? – Nancy Aug 17 '18 at 11:07
  • @MohsenKokabi Any update? Could you restart your VM or update the VM agent on your side? – Nancy Aug 20 '18 at 09:52
0

if you go to the storage account -> files you can copy the powershell commands you need to map the drive.

enter image description here

Tim Tharratt
  • 1,251
  • 1
  • 10
  • 18
  • Thank Nancy, yes this is where I get the command and it works when I RDP to the VM but if I try it in **Run Command Script** it gives error. – Mohsen Kokabi Aug 17 '18 at 11:00