View Only
  • 1.  vCenter PowerCLI language

    Posted Mar 06, 2012 01:39 PM


    When I query the network settings of a VM I get a non-english output (Netzwerkadapter) :smileyshocked::

    [vSphere PowerCLI] C:\sdk> Get-NetworkAdapter -vm vm_name

    Name                 Type       NetworkName  MacAddress         WakeOnLan
    ----                 ----       -----------  ----------         ---------
    Netzwerkadapter 1    e1000      Virtual M... 00:50:56:33:00:fd       True

    The OS of the powerCLI is English including regional settings. Is the vCenter language responsible for the non-english output? How can I change it to english.

    I do need an english output (network adapter) because a script is parsing the output.

    Thank you!



  • 2.  RE: vCenter PowerCLI language

    Posted Mar 06, 2012 01:41 PM

    thread moved to VMware vSphere™ PowerCLI Community

  • 3.  RE: vCenter PowerCLI language

    Posted Mar 06, 2012 01:54 PM

    Take a look at this discussion some objects properties are in current language instead of English. It will probably solve you problem.

    Regards, Robert

  • 4.  RE: vCenter PowerCLI language

    Posted Mar 06, 2012 01:51 PM

    What language settings do you have on the Vcenter to which you connect ?

  • 5.  RE: vCenter PowerCLI language
    Best Answer

    Posted Mar 06, 2012 01:54 PM

    Hi, rossisuchtdasglueck,

    It seems to be the locale of the vSphere that you're seeing. Your admins will have to change that on the server if you need a different locale set.

    There is a workaround you might be able to use. When the connection is initiated, you can change the server's default locale to EN-US to receive English results until your admins change the VC locale. (there was a similar problem a couple of days ago, see this thread From that thread:

    To check what your default locale when talking to the server is:

    Connect-VIServer xx.xx.xx.xx

    $si = get-view ServiceInstance

    $sm = Get-View $si.Content.SessionManager


    You can set it to en-US only immidiately after connecting (It appears that setlLocale works only when executed immediately after connect-viserver):

    Connect-VIServer xx.xx.xx.xx

    #don’t run any other cmdlets between the Connect-VIServer and the SetLocale below

    $si = get-view ServiceInstance

    $sm = Get-View $si.Content.SessionManager


    Hope this helps,


  • 6.  RE: vCenter PowerCLI language

    Posted Mar 06, 2012 02:33 PM

    Thank you very much for the quick help. Issue resolved!