locked
Confusion with Cloud Service Properties RRS feed

  • Question

  • I have a cloud service setup for several VMs to be able to communicate with one another. When I look at the Cloud Service properties via the management portal, it shows attributes that are not displayed when I get the properties via Powershell. In particular...the management portal displays "Deployment Name" and "Deployment Label" but these attributes are not displayed when viewing the service via Powershell. I would like to change the value of these properties...how would I do it?
    Thursday, April 30, 2015 9:01 PM

Answers

  • Hi,

    Thank you for posting here.
        

    Set-AzureService does not change service name.It only changes deployment name and description. These properties are just kind of Meta-Data associated with the hosted service deployment. You cannot change cloud service name (**cloudservice**.cloudapp.net) by any means. You can only create or delete cloud service.

    And, not you can't change VM's name via Azure PowerShell cmdlets, but you can do this by remote power shell to the targeted VM. Please note that renaming a Windows machine always requires restart!

    For information on how to use Remote Power Shell on Azure VM, please check out this article.

    http://fabriccontroller.net/blog/posts/using-remote-powershell-with-windows-azure-virtual-machines/

    http://azure.microsoft.com/en-in/documentation/articles/cloud-services-how-to-manage/

    Regards.

    Friday, May 1, 2015 4:50 AM

All replies

  • Hi,

    Thank you for posting here.
        

    Set-AzureService does not change service name.It only changes deployment name and description. These properties are just kind of Meta-Data associated with the hosted service deployment. You cannot change cloud service name (**cloudservice**.cloudapp.net) by any means. You can only create or delete cloud service.

    And, not you can't change VM's name via Azure PowerShell cmdlets, but you can do this by remote power shell to the targeted VM. Please note that renaming a Windows machine always requires restart!

    For information on how to use Remote Power Shell on Azure VM, please check out this article.

    http://fabriccontroller.net/blog/posts/using-remote-powershell-with-windows-azure-virtual-machines/

    http://azure.microsoft.com/en-in/documentation/articles/cloud-services-how-to-manage/

    Regards.

    Friday, May 1, 2015 4:50 AM
  • I appreciate the reply but your response is a copied response that I have seen posted on other threads and really does not address the questions I posed.
    Friday, May 1, 2015 4:59 AM
  • Hi;

    Apologies for the misinformation. In retrospect one cannot change the Deployment Name and ID generically. You will have to delete every instance and rename them, also an important feature is Name Availability one needs to make sure that the Name Change variable needs to be available in our Domain name Service.

    If you could let us know what is it that you are trying to achieve with the name change perhaps i could research and provide you with an alternative.

     

    • Proposed as answer by Shreya Hajela Friday, May 1, 2015 7:44 AM
    Friday, May 1, 2015 7:44 AM
  • I was just trying to change the Deployment Name and Deployment Label values to something that makes more sense because the current values are the name of the first VM I deployed into the cloud service.
    Friday, May 1, 2015 1:01 PM