Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all 180329 articles
Browse latest View live

Connect-VIServer fails to connect with passed credentials inside scripts but connects when manually typed

$
0
0

I have 4 vCenters.  The first 3 are all Windows vCenter installations.  I am able to connect to them via scripts with this method.

Connect-VIServer IP/DNS_Name -User administrator@vsphere.local -Password P@ssw0rd -Force

 

The 4th vCenter instance is a VCSA deployment and it will not accept this method in a script.  I've also tried the credential store method.

Two of the Windows vCenter instances are behind firewalls as is the VCSA instance I'm having issues with.  I've worked with our Cisco guru to insure that communication is not the issue.

I can consistently pass the above command manually via the cli and it connects to the VCSA every time, but when ran via a script, it consistently fails to connect to the VCSA.

 

VCSA Version

----------------

6.0.0 Update 3b build 5318203

 

 

PowerCLI Version

----------------

   VMware PowerCLI 6.5 Release 1 build 4624819

---------------

Component Versions

---------------

   VMware Cis Core PowerCLI Component 6.5 build 4624453

   VMware VimAutomation Core PowerCLI Component 6.5 build 4624450

   VMWare ImageBuilder PowerCLI Component 6.5 build 4561891

   VMWare AutoDeploy PowerCLI Component 6.5 build 4561891

   VMware Vds PowerCLI Component 6.5 build 4624695

   VMware Cloud PowerCLI Component 6.5 build 4624821

   VMware HA PowerCLI Component 6.0 build 4525225

   VMware HorizonView PowerCLI Component 7.0.2 build 4596620

   VMware Licensing PowerCLI Component 6.5 build 4624822

   VMware PCloud PowerCLI Component 6.5 build 4624825

   VMware Storage PowerCLI Component 6.5 build 4624820

   VMware vROps PowerCLI Component 6.5 build 4624824

   VMware vSphere Update Manager PowerCLI 6.5 build 4540462


Trying to install PowerCLI 10 on Windows 7 and failing ... please help!

$
0
0

Hi all,

 

I need your help.

 

I'm trying to install PowerCLI 10 on Windows 7 and failing, repeatedly.  No matter what I do, I always end-up with a 6.5.* version:

 

After running my script (below), I'm still on version 6.5.*:

 

PS C:\Users> Get-PowerCLIVersion

 

PowerCLI Version

----------------

   VMware PowerCLI 6.5.1 build 5377412

---------------

Component Versions

---------------

   VMware Cis Core PowerCLI Component 6.5 build 6870462

   VMware VimAutomation Core PowerCLI Component 6.5 build 6234650

 

 

PS C:\Users> Get-Module -Name VMware.* | Select-Object -Property Name,Version

 

Name                          Version     

----                          -------     

VMware.VimAutomation.Cis.Core 6.5.3.6870462

VMware.VimAutomation.Common   6.5.1.5335010

VMware.VimAutomation.Core     6.5.2.6234650

VMware.VimAutomation.Sdk      1.0.0.5334677

 

 

Here is my script: it kept not working, so I kept adding (things I did not understand) to it:

 

# Set execution policy:

set-executionpolicy unrestricted

 

# The VMware.PowerCLI module is a NuGet repository.

# So, we need to install NuGet before trying the install:

Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force

 

# Close and reopen PowerShell.  Why? Is this really necessary?

 

# Confirm version -- WHY is it not version 10? 

Get-PowerCLIVersion

 

# why?

Install-Module –Name PowerShellGet –Force  -AllowClobber

 

# Install PowerCLI 10:

Install-Module -Name VMware.PowerCLI -Scope CurrentUser

 

# Confirm version -- WHY is it not version 10?

Get-PowerCLIVersion

Get-Module -Name VMware.* | Select-Object -Property Name,Version

 

# Update PowerCLI:

Update-Module VMware.PowerCLI

 

# Confirm version -- WHY is it not version 10?

Get-PowerCLIVersion

Get-Module -Name VMware.* | Select-Object -Property Name,Version

 

# Try this:

Save-Module -Name VMware.PowerCLI -Path .

Install-Module -Name VMware.PowerCLI

 

# Confirm version -- WHY is it not version 10?

Get-PowerCLIVersion

Get-Module -Name VMware.* | Select-Object -Property Name,Version

 

Please get rid of unnecessary modal dialogs (like Defragmenting Disk etc.) --- PLEASE VOTE

$
0
0

It's very annoying that VMware Workstation keeps me from accessing and working in one VM while I'm administering another VM.

 

These modal dialogs, like Virtual Machine Settings, Virtual Machine Settings > Defragmenting Disk, Virtual Machine Settings > Compacting Disk, Snapshot Manager, Snapshot Manager > Cleaning Up Disk Files should not block the whole Workstation window.

 

Instead, they should only block the corresponding VM.

 

Please, VMware, with the next release (v13), get rid of these modal dialog boxes and alter them so they, for example, replace the corresponding VM's console display when opened. Then they'll only block the corresponding VM but not all the others.

 

 

Current situation:

Workstation modal dialog.png

 

 

Desired situation:

Virtual Machine Settings

Workstation VM Settings.png

 

Snapshot Manager

Workstation Snapshot Manager.png

com.vmware.vapi.std.errors.invalid_argument error

$
0
0

Hello Expert,

 

When I call rest api to create a disk for vm, the api response with an error body:

 

2018-04-17T13:47:42.539Z+08:00 ▶ INFO  >> e8da8850209f method: POST, path: rest/vcenter/vm/vm-xxxxx/hardware/disk, headers: map[content-type:application/json accept:application/json vmware-api-session-id:xxxxxxxxx], body: {"spec":{"type":"SCSI","ide":{"primary":true,"master":true},"scsi":{"bus":0,"unit":0},"sata":{"bus":0,"unit":0},"backing":{"type":""},"new_vmdk":{"name":"Hard disk 2","capacity":1073741824}}}

2018-04-17T13:47:42.945Z+08:00 ▶ ERRO  << e8da8850209f status: 400, response: {"type":"com.vmware.vapi.std.errors.invalid_argument","value":{"messages":[{"args":["com.vmware.vcenter.vm.hardware.disk.create_spec","sata"],"default_message":"Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata","id":"vapi.data.structure.union.extra"}]}}

 

For your convenience of view, the request json body:

{

    "spec": {

        "backing": {

            "type": ""

        },

        "ide": {

            "master": true,

            "primary": true

        },

        "new_vmdk": {

            "capacity": 1073741824,

            "name": "Hard disk 2"

        },

        "sata": {

            "bus": 0,

            "unit": 0

        },

        "scsi": {

            "bus": 0,

            "unit": 0

        },

        "type": "SCSI"

    }

}

 

response:

{

    "type": "com.vmware.vapi.std.errors.invalid_argument",

    "value": {

        "messages": [

            {

                "args": [

                    "com.vmware.vcenter.vm.hardware.disk.create_spec",

                    "sata"

                ],

                "default_message": "Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata",

                "id": "vapi.data.structure.union.extra"

            }

        ]

    }

}

 

 

What's wrong with my calling to the api? I also tried type: "IDE", reporting sata too, or type: "SATA", reporting "scsi"

 

Thanks for any advice.

only 1G on 10GB ports

$
0
0

Hi,

 

I have problem because on server I have 1x1Gb port to MGMT vsphere and connect to "internet". And 2x10Gb to iSCSI storage but works as 1Gb. Ports show on vmware, switch and storage as 10Gb/s.

 

Whoever had such a problem like this  ?

I enable Traffic Shaping, but does not working.

vSphere5.1からvSphere6への移行に必要な調査について

$
0
0

社内のvSphere 5.1環境を6.0 U3aへ移行するため、調査をしていますが質問させてください。

 

■現在の環境

vCenter

 5.1b(Windows Server 2008R2の物理サーバーにOracle11gを外部DBとして構築)

ESXi

 5.1 Update2 Build 1612806(4台のクラスタが一基、2台のクラスタが一基、ノンクラスタが4台)

Data Protection

 5.5.9.4が各ホストに一台ずつ、4台が存在

VM

 仮想マシンバージョン7から9が合計で140台

ストレージ

 iSCSIのストレージが5台、VMFS3、VMFS5が混在

スイッチ

 Power ConnectやCatalystなどL2、L3スイッチが10台ほど

 

◆ターゲットバージョン

vCenter

 VCSA 6.0 U3a

ESXi

 6.0U3a

Data Protection

 6.1.7

 

◆今回問い合わせさせて頂く前に済んでいるアクション

1.アップグレードが出来るバージョンかどうか->ESXiは可能、vCenter、Data Protectionは新規構築が推奨、仮想マシンバージョンはアップ不要

2.ライセンス的にバージョンアップが可能かどうか->可能

3.サーバーハードウェア、ストレージのvSphere6対応状況確認->ハードウェアレベルでは対応状況問題なし

 

◆聞きたいこと

移行・バージョンアップについて、考慮しなければいけない点がどれくらいあるのかつかめていない。

ハードウェアの要件やバージョンアップ方法の他に、調査しなければいけない点を教えてほしい。

vshpare 6.7 install plugin

$
0
0

Hi All

 

hope anyone could help on this one , we are trying to install a plugin on the vshpare 6.7 without any success

i could find this link which points that the flex and web client are going to be deprecated

 

Goodbye vSphere Client for Windows (C#) – Hello HTML5 - VMware vSphere Blog

but they are still available on the UI

 

when trying to install the plugin with the api calling the RegisterExtension function ( available on the VimService)

 

i could find some related logs on the VC

 

[2018-02-26T10:10:21.229+02:00] [WARN ] session-init-pool-8          70000091 100006 200004 com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin version mismatch for com.MyPlugin.plugin between the plugin registration info (3.0)

and the version specified in plugin-package.xml (4.1). The registration version will be used but you should keep them in sync. 

 

Line 114806: [2018-02-26T10:10:21.265+02:00] [INFO ] plugin-validation1            com.vmware.vise.extensionfw.impl.OsgiUsageValidationService       Started validating com.MyPlugin.plugin:3.0

Line 114829: [2018-02-26T10:10:21.266+02:00] [INFO ] plugin-validation1            com.vmware.vise.extensionfw.impl.OsgiUsageValidationService       Finished validating com.MyPlugin.plugin:3.0

 

[2018-02-26T11:00:03.427+02:00] [WARN ] data-service-pool-794        70000674 100003 200006 c.v.vsphere.client.vcextension.impl.ManagedByPropertyProvider     ManagedObjectReference: type = VirtualMachine, value = vm-82, serverGuid = 4f57e45b-f53c-4c2b-8b6a-b64d72af7c15 specifies a managedBy relation to an extension with the key com.MyPlugin.plugin but no such extension is registered

 

does anyone has experienced the same issue when trying to install plugins on 6.7 ?

anyone knows it installing plugins on 6.7 is available ?

 

thanks

Updating to windows 10 creators fall edition 1709 fails

$
0
0

Windows 10 1709 creators fall update: Failed in Safe_OS Phase

 

I have the following Symptom:

A Guest machine running windows 10 creators edition 1703 is failing to update to windows 10 creators edition 1709.

On update it downloads , installs, and reboots to rollback to the old 1703 edition. Then it continues to update again and again every few days, and rollback. 

I ahve found this happens from system update as well as from a standalone USB created from microsofts MediaCreationTool.

 

When using the standalone USB the following message  comes:

 

0x80070570   0x2000C

"Installation Failed in Safe_OS Phase with an error during APPLY_IMAGE operation"

 

I have spent the best part of a Saturday trying to resolve this isssue:

I tried the following, testing an upgrade each time

1. Tidied up temp files

2.  turned the following services to automatic and rebooted

     BITS, Windows Update Service, Cryptographic Service)

    

Then I changed to the standalone USB  and after continued failure did the following, testing an upgrade each time

3.  Expanded the virtual disk disk, so there is now over 60GB free (beforehand it was ~20GB)

4.  Converted disk from split_sparse 2GB  (growable) to  split flat 2GB  (preallaocated,3)

5.  Set Graphics accelerater  to off in VM setting

 

Is there anything else that I should do ? Any ideas ?

 

Dan

 

 

Host:

   intel cpu  (I thought I might have to remove mcupdate_genuineIntel.dll from the update image, however there is no install.wim in sources of the update image so I can't easily)

   Windows 10 creators fall edition 1709 PRO 64 bit

   vmware 14.1.1 workstation pro build 16299

Guest

   windows creators 1703, UK version PRO 64 bit

   HW version 11

 

p.s:

On my Apple MAC laptop, Under parallels Pro on a elCapitan Mac-OS host, updating 1703 to 1709 works perfectly right from the start


VMDK and FLAT-VMDK

$
0
0

Hi

 

I know the difference between a .vmdk- and a flat.vmdk-file.
But why does a ESX-Host use flat-files and VM-Workstation does not?

Why these different ways to handle VM-disks?

 

Thank you in advance!

 

M.

ESXi 6.5 VSAN crash 6 host

$
0
0

Hello guys,

 

We have 6 servers Lenovo x3650 M5 united in VSAN cluster.

 

Time to time, all server in cluster down in purple screen, image attach bellow.

 

Any ideas? We don't have vmware support on this case, plz help!

 

Same error: "exception 14 vmnic5" on all host.

VMware vCenter 6.0 VM gets hanged

$
0
0

Hi ,

There are two VMs for which I am facing issue. The VM gets frozen out and I cannot perform any action, it reconnects automatically. But meanwhile its hanged the impact is that services are affected and I am not able to fetch data.

 

VM details:

OS: Windows 2K8 R2 Standard Edition

Role:  MsSql Database and Application server.

com.vmware.vapi.std.errors.invalid_argument error

$
0
0

Hello Expert,

 

When I call rest api to create a disk for vm, the api response with an error body:

 

2018-04-17T13:47:42.539Z+08:00 ▶ INFO  >> e8da8850209f method: POST, path: rest/vcenter/vm/vm-xxxxx/hardware/disk, headers: map[content-type:application/json accept:application/json vmware-api-session-id:xxxxxxxxx], body: {"spec":{"type":"SCSI","ide":{"primary":true,"master":true},"scsi":{"bus":0,"unit":0},"sata":{"bus":0,"unit":0},"backing":{"type":""},"new_vmdk":{"name":"Hard disk 2","capacity":1073741824}}}

2018-04-17T13:47:42.945Z+08:00 ▶ ERRO  << e8da8850209f status: 400, response: {"type":"com.vmware.vapi.std.errors.invalid_argument","value":{"messages":[{"args":["com.vmware.vcenter.vm.hardware.disk.create_spec","sata"],"default_message":"Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata","id":"vapi.data.structure.union.extra"}]}}

 

For your convenience of view, the request json body:

{

    "spec": {

        "backing": {

            "type": ""

        },

        "ide": {

            "master": true,

            "primary": true

        },

        "new_vmdk": {

            "capacity": 1073741824,

            "name": "Hard disk 2"

        },

        "sata": {

            "bus": 0,

            "unit": 0

        },

        "scsi": {

            "bus": 0,

            "unit": 0

        },

        "type": "SCSI"

    }

}

 

response:

{

    "type": "com.vmware.vapi.std.errors.invalid_argument",

    "value": {

        "messages": [

            {

                "args": [

                    "com.vmware.vcenter.vm.hardware.disk.create_spec",

                    "sata"

                ],

                "default_message": "Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata",

                "id": "vapi.data.structure.union.extra"

            }

        ]

    }

}

 

 

What's wrong with my calling to the api? I also tried type: "IDE", reporting sata too, or type: "SATA", reporting "scsi"

 

Thanks for any advice.

Method "HostImageConfigGetAcceptance" in PowerCLI

$
0
0

Hello Community,

 

I am looking for a way to get the Value from the Method HostImageConfigGetAcceptance in PowerCLI as in Managed Object Browser.

 

Unfortunately I was unable to get the value from VMHost's ExtensionData but I am sure there's a way I don't know yet ^.^

ExtensionData.ConfigManager.ImageConfigManager.HostImageConfigManager

 

many thanks and kind regards,

Dex

com.vmware.vapi.std.errors.invalid_argument error

$
0
0

Hello Expert,

 

When I call rest api to create a disk for vm, the api response with an error body:

 

2018-04-17T13:47:42.539Z+08:00 ▶ INFO  >> e8da8850209f method: POST, path: rest/vcenter/vm/vm-xxxxx/hardware/disk, headers: map[content-type:application/json accept:application/json vmware-api-session-id:xxxxxxxxx], body: {"spec":{"type":"SCSI","ide":{"primary":true,"master":true},"scsi":{"bus":0,"unit":0},"sata":{"bus":0,"unit":0},"backing":{"type":""},"new_vmdk":{"name":"Hard disk 2","capacity":1073741824}}}

2018-04-17T13:47:42.945Z+08:00 ▶ ERRO  << e8da8850209f status: 400, response: {"type":"com.vmware.vapi.std.errors.invalid_argument","value":{"messages":[{"args":["com.vmware.vcenter.vm.hardware.disk.create_spec","sata"],"default_message":"Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata","id":"vapi.data.structure.union.extra"}]}}

 

For your convenience of view, the request json body:

{

    "spec": {

        "backing": {

            "type": ""

        },

        "ide": {

            "master": true,

            "primary": true

        },

        "new_vmdk": {

            "capacity": 1073741824,

            "name": "Hard disk 2"

        },

        "sata": {

            "bus": 0,

            "unit": 0

        },

        "scsi": {

            "bus": 0,

            "unit": 0

        },

        "type": "SCSI"

    }

}

 

response:

{

    "type": "com.vmware.vapi.std.errors.invalid_argument",

    "value": {

        "messages": [

            {

                "args": [

                    "com.vmware.vcenter.vm.hardware.disk.create_spec",

                    "sata"

                ],

                "default_message": "Structure com.vmware.vcenter.vm.hardware.disk.create_spec has a union with a field not allowed for this case: sata",

                "id": "vapi.data.structure.union.extra"

            }

        ]

    }

}

 

 

What's wrong with my calling to the api? I also tried type: "IDE", reporting sata too, or type: "SATA", reporting "scsi"

 

Thanks for any advice.

Upgraded to PowerCLI to 6.5 gettings used to the changes, any idea what the equivelent of "Connect-VIServer" is

$
0
0

Upgraded to PowerCLI to 6.5 getting used to the changes, any idea what the equivalent of "Connect-VIServer" and what the syntax would be...

 

For example I currently connect into the infrastructure with ....

 

"Connect-VIServer -Server myserver.domain.internal -User user@myserver.domain.internal -Password MyPassword

 

I need to make all my old scripts work

 

Thanks in advance.


Can you share an example of an OSR report?

$
0
0

Hi,

 

Is there an example/demo report that you can share?

 

Thanks

M

Backslash key \ on Console translates to #

$
0
0

Just created my first W2016 Server on VSphere Web Client Version 6.5.0.13000 Build 7515524 - How on earth do you get a backslash '\' when using the console? All I get is a '#'

How im can deploy ovf using pówercli ?

$
0
0

Dear Members

 

How im can deploy ovf using powercli ?

 

Thanks

Almir

Cluster Error: vMotion not supported by host

$
0
0

Hi!

 

I have a strange error:

When I try to vmotion a running VM from one cluster to another (Compute and Storage vMotion) the following errors are displayed:

The "Destination" host 'hostname' does not support vMotion.

com.vmware.vim.vpxd.vmcheck.vmotionNotSupportedByHost

 

The "Source" host 'hostname' does not support vMotion.

com.vmware.vim.vpxd.vmcheck.vmotionNotSupportedByHost

 

If the VM is powered off, it can be migrated.

Between the hosts of a cluster, a live migration is working well.

 

I'm sure that I have migrated VMs in the past sucessfully. The only thing I have done in the past was the update from VCSA 5.5 U3b to VCSA 6.0 U3.

I have tried all the suggestions from KB1003734 but nothing seems to be wrong. VMotion and DRS work perfectly, only to another cluster fails.

Understanding and troubleshooting vMotion (1003734) | VMware KB

 

Does anyone has an idea?

Otherwise I will have to open an official support request.

Provisioning error, any idea ?

$
0
0

Hi Guys I am new to VRA administration..

 

would anyone know what this error is ?

 

The following component requests failed: Machine. Request failed: xxxMAchine: sendEBSMessage19(workflow=720664c1-4634-4bf9-ae0a-e5b2bee5f86e) Error in state VMPSMasterWorkflow32.MachineProvisioned phase PRE event (queue = 5a506c8e-5039-45c0-8f5c-66fc08493644): Extensibility consumer error(20999) - The remote workflow 'MachineProvisioned' / 'RFC' execution failed! The 'Create complete RFC - Provisioned' workflow execution failed! RFC created notification sending - commissioning xxxMAchine - failed Please check Send RFC created notification workflow: czchowsint5143 id: 720664c1-4634-4bf9-ae0a-e5b2bee5f86e I/O error on POST request for "https://vra7server:443/SAAS/t/vsphere.local/auth/oauthtoken": java.security.cert.CertificateException: Untrusted certificate chain.; nested exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Untrusted certificate chain. (Workflow:Get email address for username (CAFE) / Get email (item1)#12758) (Workflow:Execute GSN workflow / Execute WF (item1)#8)...

 

Regards,

 

ETR

Viewing all 180329 articles
Browse latest View live