Please provide your feedback in this short Flings' survey.
Nov 15, 2022

The default root password is VM3dsc1! does not work. Also any password that i setup does not work. Any suggestions?

Nov 16, 2022

Login to the VMDSC appliance from the vCenter console. From there, you can type in VM3dsc1!, It will prompt you to change the password.

Nov 09, 2022

Does anyone have this automated? If so, please let me how you are doing this?

Thanks

Nov 09, 2022

There are a few options. I wrote a PowerShell module (PowerVMDSC) that you can install from the PowerShell Gallery. There are instructions in the fling documentation. Once you have PowerVMDSC up and running you can write a for each loop in a one line powershell script that processes a list of VMs in a csv file. This is how I've been automating testing in the lab.

There is also a bit of vRealize Orchestrator code downloadable from the flings website, it was written to pull configs out of vROPs and push them to VMDSC, but you could modify it however you want.

I may write an Ansible module, I've never written one from scratch but I need to for another project. I may write one for VMDSC as my training wheels since I know exactly what I need each module to do from an API perspective from writing the powershell module.

Nov 09, 2022

Thanks Heath. I will look into the for each loop

Nov 09, 2022

Has anyone run into this error in Postman when running GetVMID?

TypeError: Cannot read properties of undefined (reading 'vm')

It loos like the URL is being parsed correctly - the Parameters are instantiating as expected...

Nov 07, 2022

Hello,

I been testing the VMDSC solutions for a few weeks now. This a great solution. I have perform testing with this solution on vRealize Orchestrator and PowerVMDSC.

I would prefer to use Orchestrator for this rightsizing project that I am working on. Rightsizing works with Orchestrator with no issues. I have few questions that you can answer.

1. Can the VMDSC appliance connect to multiple vCenters or just one vCenter per VMDSC?
2. Will I need to deploy separate Orchestrator appliances per vCenter for the workflows to execute correctly for that vCenter? I have more than one vCenter that I will to apply this to.

Nov 14, 2022

Hello Antonio,

as for VMDSC, a single Orchestrator appliance can serve multiple vCenters. However after importing the VMDSC package, I had to clone the VMDSC Configuration (found in vRO under Assets -> Configuration) for every vCenter. Since every vCenter needs a unique VMDSC appliance and the VMDSC appliance has to be listed in the VMDSC configuration. After that I also had to clone the VMDSC workflows for every vCenter, because the workflows are tied to the VMDSC configuration for the respective vCenter.

Nov 15, 2022

Thanks Steven.

Are you importing the workflows into vROPs and using vROPs recommendation or making your own recommendation?
I want to see how everyone is rightsizing their VMs.

Thanks

Nov 15, 2022

Steven,

Did you have to create a new package also in VRO or add the configurations and workflows in the existing package?

Nov 09, 2022

There is a one to one relationship between a VMDSC appliance and a vCenter.

I'm not 100% sure on orchestrator, I feel like the answer is no. With vRA 7.x deployments I had one orchestrator appliance talking to multiple vCenters. Way back in the vCO days (2015) there were some issues with multiple vCenters and SSO but I don't think any of those issues impact vRO currently, but I no longer work with vRO every day so I can't say with 100% certainty.