locked
CloudDeployment Folder RRS feed

  • Question

  • Is it safe to delete C:\CloudDeployment folder once you have the stack fully deployed? With all the PaaS services installed, there is not much disk space left in CloudBuilder.vhdx and it slowly fills to capacity over time. Would like to gain that additional space back if it can be reclaimed.

    John V. Casella

    Friday, January 6, 2017 4:15 PM

Answers

  • Hi John,

    This is not a recommended practice as there are many scripts that are relied on in that folder.

    Thanks,

    Charlie

    • Proposed as answer by DanielSavage [MSFT] Monday, January 9, 2017 7:32 PM
    • Marked as answer by Blueroy Monday, January 9, 2017 7:51 PM
    Friday, January 6, 2017 7:36 PM
  • Hi John,

    To increase the size of a CloudBuilder.vhdx
    - Boot back into hard Disk OS
    - Open Hyper-V Manager and select "Edit Disk"
    - Browse to Clouldbuilder.vhdx and Next
    - Choose 'Expand' and Next
    - Type the size you want in GB and Next
    - Boot back into the Clouldbuilder.vhdx

    Also - DON'T DELETE the CloudDeployment folder.
    I just deleted my CloudDeployment folder, rebooted and now all the VMs are gone.

    Thanks,


    Gary Gallanes

    Monday, January 9, 2017 11:12 PM
  • But also make sure space is not filling up by WinRM logs, its a known issue. Clear that folder on the host and all your fabric VM's by executing this script on your Host

    # Retrieves all fabric VMs plus Host $CompArr = (get-vm | where notes -notmatch '[a-z]').Name + ($env:computername) Invoke-Command -computername $CompArr {

    $computername = $env:computername cd c:\winrm .\stop-logging.ps1 logman stop "NetTrace-AzureStack-$computername`$" -ets rd logs -Force -Recurse -Confirm:$false md logs

    if ($computername -eq 'mas-xrp01'){
    logman stop keyvault
    logman stop fabriccounters
          rd c:\cpiservices\diagnostics -Force -Recurse -Confirm:$false
          rd c:\crpservices\diagnostics -Force -Recurse -Confirm:$false
          rd c:\frpservices\diagnostics -Force -Recurse -Confirm:$false
    }

    } # end invoke-command



    Cheers,

    Ruud
    Twitter:    Blog: www.ruudborst.nl  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.





    • Marked as answer by Blueroy Tuesday, January 10, 2017 4:25 PM
    • Edited by Ruud BorstMVP Monday, January 16, 2017 7:06 PM
    Tuesday, January 10, 2017 2:20 PM

All replies

  • Hi John,

    This is not a recommended practice as there are many scripts that are relied on in that folder.

    Thanks,

    Charlie

    • Proposed as answer by DanielSavage [MSFT] Monday, January 9, 2017 7:32 PM
    • Marked as answer by Blueroy Monday, January 9, 2017 7:51 PM
    Friday, January 6, 2017 7:36 PM
  • That's what I figured. Thought I would ask. Is there a way to expand Cloudbuilder.vhdx?

    John V. Casella

    Friday, January 6, 2017 7:45 PM
  • Hi John,

    To increase the size of a CloudBuilder.vhdx
    - Boot back into hard Disk OS
    - Open Hyper-V Manager and select "Edit Disk"
    - Browse to Clouldbuilder.vhdx and Next
    - Choose 'Expand' and Next
    - Type the size you want in GB and Next
    - Boot back into the Clouldbuilder.vhdx

    Also - DON'T DELETE the CloudDeployment folder.
    I just deleted my CloudDeployment folder, rebooted and now all the VMs are gone.

    Thanks,


    Gary Gallanes

    Monday, January 9, 2017 11:12 PM
  • Of course! Simple enough. Not sure why I didn't think of that! :) Thanks.

    John V. Casella

    Tuesday, January 10, 2017 2:00 PM
  • But also make sure space is not filling up by WinRM logs, its a known issue. Clear that folder on the host and all your fabric VM's by executing this script on your Host

    # Retrieves all fabric VMs plus Host $CompArr = (get-vm | where notes -notmatch '[a-z]').Name + ($env:computername) Invoke-Command -computername $CompArr {

    $computername = $env:computername cd c:\winrm .\stop-logging.ps1 logman stop "NetTrace-AzureStack-$computername`$" -ets rd logs -Force -Recurse -Confirm:$false md logs

    if ($computername -eq 'mas-xrp01'){
    logman stop keyvault
    logman stop fabriccounters
          rd c:\cpiservices\diagnostics -Force -Recurse -Confirm:$false
          rd c:\crpservices\diagnostics -Force -Recurse -Confirm:$false
          rd c:\frpservices\diagnostics -Force -Recurse -Confirm:$false
    }

    } # end invoke-command



    Cheers,

    Ruud
    Twitter:    Blog: www.ruudborst.nl  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.





    • Marked as answer by Blueroy Tuesday, January 10, 2017 4:25 PM
    • Edited by Ruud BorstMVP Monday, January 16, 2017 7:06 PM
    Tuesday, January 10, 2017 2:20 PM
  • Yes, I noticed the WinRM folder filling up and had been clearing that. Thanks for the script. I can definitely use it!

    John V. Casella

    Tuesday, January 10, 2017 4:25 PM
  • Azure Stack TP3 has been released on March 1, 2017.

    If you are experiencing any issues with the TP2 release, please download and redeploy using the latest Azure Stack POC deployment package

    Please see the updated deployment documentation:

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script

    And updated Azure Stack Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

    If you experience any issues with TP3 release, feel free to contact us.

    https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/

    Wednesday, March 1, 2017 7:16 PM