About Dynamic Drop-Down List “Name” and “Value”

This post was originally published on this site

Hi,

 

I have two question about that.

 

First question ; I created two dynamic dropdown custom property called via external source ( With vRealize ORchestrator );

 

My vRO action code is ;

….

….

return [“Production,”Development”];

….

….

 

But, I want to write “Name” and “Values” different like picture below . Is that possible ?

 

return [{“name” : “Production”, “value” : “PROD”}] –> this is not working…

 

My second question is ;

 

When I click the first dropdown, second drowdown values are coming but i want to first values set as default. Because i’ll hide second dropdown and values should be set as default without user selection.

 

Thanks.

Videos flickering

Hello, Greetings, Can any expert here please tell me what is the hardware and Vmware settings needed on ESX 5.1 to be able to play videos on  windows servers 2008 and 2012R2. The videos are flickering currently.

Esxi upgrade from 5.5 to 6.0U3 HPE custom offline bundle VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip requires VSAN?

This post was originally published on this site

Hello all,

 

I am trying to upgrade one of my HPDL 380 G7 servers from Esxi Ver 5.5 to Esxi ver 6.0U3 using the esxcli and the VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip.

 

I SSH into box and run

 

#esxcli software vib update -d “/vmfs/volumes/mydatastore/VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip”

 

I receive the following about VSAN being required??

[DependencyError]

VIB VMware_bootbank_esx-base_6.0.0-3.79.6921384 requires vsan >= 6.0.0-3.79, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_esx-base_6.0.0-3.79.6921384 requires vsan << 6.0.0-3.80, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

 

Can anyone provide any insight on how I can resolve this error and get my Dl380 G7 server to upgrade to esxi 6.0U3?

 

Much appreciated

Esxi upgrade from 5.5 to 6.0U3 HPE custom offline bundle VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip requires VSAN?

Hello all,

 

I am trying to upgrade one of my HPDL 380 G7 servers from Esxi Ver 5.5 to Esxi ver 6.0U3 using the esxcli and the VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip.

 

I SSH into box and run

 

#esxcli software vib update -d “/vmfs/volumes/mydatastore/VMware-ESXi-6.0.0-Update3-6921384-HPE-600.10.2.0.23-Feb2018-depot.zip”

 

I receive the following about VSAN being required??

[DependencyError]

VIB VMware_bootbank_esx-base_6.0.0-3.79.6921384 requires vsan >= 6.0.0-3.79, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_esx-base_6.0.0-3.79.6921384 requires vsan << 6.0.0-3.80, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

 

Can anyone provide any insight on how I can resolve this error and get my Dl380 G7 server to upgrade to esxi 6.0U3?

 

Much appreciated

Cannot Open Web Or Remote Console

This post was originally published on this site

Dear all,

I recently upgraded my lab server to ESXi 6.7. Everything worked fine until I tried to access my virtual machines using VMRC (Remote Console)

If I open VMRC trough Chrome or Firefox, It shows an authentication screen and it doesn’t matter what I enter on it. never authenticates.

With browser console, it fails to connect to virtual machine console

And with new window browser console, it shows only the vmware logo page

I do not have this issue with Microsoft Edge or with Opera browsers.

Do you have any idea what it is happening?

Thank you for your attention.

Anyone see the KB article that was posted in early May related to: API calls blocked if Basic Admin account authentication

This post was originally published on this site

Look at this article: https://support.air-watch.com/articles/360003873834 Seems starting with console 9.3+, if you are using an AW basic account for API calls in any tie-in component (i.e. SEG V2, ACC, VIDM, Content Gateway), when the basic password expires, it will now start blocking api calls.

This is a big change and a huge headache. Their solution…use an AD account with a non-expiring password.

vRA 7.4 – Custom Forms Data Grid

This post was originally published on this site

Hello!

 

I am playing around with the Data Grid in the New Custom forms Designer – more precisely with the “disks” Grid. What I found so far:

 

  • Adding the Grid to the Forms I got this Error:

 

Schema fields [[is_clone, initial_location, volumeId, id, label, custom_properties, userCreated, storage_reservation_policy, capacity]] should match the default value fields [[is_clone, initial_location, volumeId, id, label, userCreated, storage_reservation_policy, capacity]].

 

Cause: there is no “custom_properties” Field in the Grid Layout

 

Solution: Look at the “Default” Value and remove the “custom_properties,” from the Header and the “,” bevor the capacity – in my case before the “80”:

 

is_clone,initial_location,volumeId,id,label,custom_properties,userCreated,storage_reservation_policy,capacity

true,,0,1525072814859,Hard disk 1,,false,,80

 

is_clone,initial_location,volumeId,id,label,custom_properties,userCreated,storage_reservation_policy,capacity

true,,0,1525072814859,Hard disk 1,,false,80

 

  • Using the “disks” Grid “breaks” any approval Policies based on Storage Size

 

Cause: If you add more disks to the Grid the Value of “Storage (GB)” will not be incremented

 

Solution: Well… its more a workaround since I have not found a way to pass the Values of a Data Grid to an vRO Action. I created a vRO Action which fills the “disks” Grid based on Values in the Custom Form (the size of the template base disks are Hardcoded):

 

  • If you use an external vRO Action for the Grid Values the Return type of the Action must be “Array/Properties”. In my Case the Action was not found if I use this return Type.

 

Cause: Bug?

 

Workaround: I changed the Return Type to “Array/String” and the Action was found in vRA. After I changed the Values Binding in the Custom Form, Saved the Blueprint and corrected the Return Type of the Action to Array/Properties.

Slow looping through vCenter objects since upgrade from vRO 7.2 to 7.4

This post was originally published on this site

Since I upgraded our vRO standalone installation from vRO 7.2 to 7.4 we have performance issues while executing code which looping though a large number of vCenter objects (like vm oder vmFolder objects).

 

I`m using following code:

 

var ret = VcPlugin.getAllVirtualMachines();

var time = new Date();

var start = time.getTime();

var i = 0;

var allVmNames = [];

for each(var vm in ret) {

      allVmNames.push(vm.name);

      if ((++i % 1000) == 0){

           System.log (“inserts: ” + i);

      }

}

var time = new Date();

var end = time.getTime();

 

               System.log (“Start:     ” + start);

               System.log (“End:      ” + end);

System.log (“Difference: ” + (end – start));

 

    

 

 

Result vRO 7.2:

2018-05-04 07:18:54.980] [I] Ergebnis: 5557

[2018-05-04 07:19:35.745] [I] inserts: 1000

[2018-05-04 07:20:37.296] [I] inserts: 2000

[2018-05-04 07:21:36.996] [I] inserts: 3000

[2018-05-04 07:22:36.400] [I] inserts: 4000

[2018-05-04 07:23:37.950] [I] inserts: 5000

[2018-05-04 07:24:11.751] [I] Start:     1525411134982

[2018-05-04 07:24:11.757] [I] Ende:      1525411451749

[2018-05-04 07:24:11.760] [I] Differenz: 316767

 

Result vRO 7.4:

[2018-05-04 07:18:13.604] [I] Ergebnis: 5557

[2018-05-04 07:18:13.644] [I] inserts: 1000

[2018-05-04 07:18:13.682] [I] inserts: 2000

[2018-05-04 07:18:13.705] [I] inserts: 3000

[2018-05-04 07:18:13.729] [I] inserts: 4000

[2018-05-04 07:18:13.747] [I] inserts: 5000

[2018-05-04 07:18:13.758] [I] Start:     1525411093614

[2018-05-04 07:18:13.760] [I] Ende:      1525411093756

[2018-05-04 07:18:13.762] [I] Differenz: 142

 

As you can see the execution time is in vRO 7.4 is much longer than in 7.2.

 

Does anyone see the same behavier after the updrage?