SkyCoop's Posts

Do you have a sample payload you used for creating the directory? Not sure what goes in the directoryConfig object. { "directoryConfig": {}, "directoryType": "ActiveDirectory", "vidmAdminPasswor... See more...
Do you have a sample payload you used for creating the directory? Not sure what goes in the directoryConfig object. { "directoryConfig": {}, "directoryType": "ActiveDirectory", "vidmAdminPassword": "some-password", "vidmAdminUser": "configadmin", "vidmHost": "vidm.corp.local, "vidmTenant": "default", "vidmVersion": "3.3.5" }
How are you retrieving the SubTenantId when you say "you can lookup the subtenant then via the bound id" for the vRO action?
You can use pre-requested to fail the workflow, but you have to have the custom property - In addition to using the PRE lifecycle phase, you also need to add the following custom property: Ext... See more...
You can use pre-requested to fail the workflow, but you have to have the custom property - In addition to using the PRE lifecycle phase, you also need to add the following custom property: Extensibility.Lifecycle.Error.Event.VMPSMasterWorkflow32.Requested = Destroy With the exception of BuildingMachine, MachineProvisioned, and RegisterMachine, the property needs to be added for any lifecycle state: Extensibility.Lifecycle.Error.Event.VMPSMasterWorkflow32.{state} = Destroy Might actually be Disposing instead of Destroy. I wouldn't use Requested for the subscription as I've seen random machines fail in the vRO portion but a VM gets spun up in vCenter, while vRA isn't aware of it. Safer to use the Building Machine state, typically fits most use cases that Requested would work for anyway.
Take a look at the release notes, drop down relationship - as currently implemented in previous versions, is not the same. You need to create an action in vRO and reference that in the properties... See more...
Take a look at the release notes, drop down relationship - as currently implemented in previous versions, is not the same. You need to create an action in vRO and reference that in the properties of the drop down list. <From the release notes> In vRealize Automation 7.0, the property definitions no longer use the attributes. You must recreate the property definition or configure the property definition to use a vRealize Orchestrator script action rather than the embedded control types or attributes. Workaround: Migrate the control type or attributes to vRealize Automation 7.0 using a script action. In vRealize Orchestrator, create a script action that returns the property values. The action must return a simple type. For example, return strings, integers, or other supported types. The action can take the other properties on which it depends as an input parameter. For information about creating script actions, see the vRealize Orchestrator documentation. In vRealize Automation, configure the product definition. a. Select Administration > Property Dictionary > Property Definitions                     b. Select the property definition and click Edit                     c. From the the Display advice drop-down menu, select Dropdown                     d. From the Values drop-down menu, select External Values                     e. Select the script action.                     f. Click OK                     g. Configure the Input Parameters that are included in the script action. To preserve the existing relationship, bind the parameter to the other property.                     h. Click OK
I don't believe you are actually searching Customization Specs, you are seeing residual specs you typed in previously in some form that used the same backend name.
Did you disable the loopback on the IaaS server to include the VIP name for the tier you are installing?
Check the release notes: VMware vRealize Automation 6.2.1 Release Notes , not sure if this is what you are experiencing? After upgrading to PSC 6.0, a 400 Request error appears when you access ... See more...
Check the release notes: VMware vRealize Automation 6.2.1 Release Notes , not sure if this is what you are experiencing? After upgrading to PSC 6.0, a 400 Request error appears when you access the default tenant URL, https://FQDN_VA/vcac, because port 7444 is no longer valid in SSO registration in the vRealize Virtual Appliance* The error message, Trying to access remote SSO on host vra-va-hostname.domain.name and port 7444, but the returned host is vra-va-hostname.domain.name and port 443 appears on the Virtual Appliance when you try to re-register the Virtual Appliance to the upgraded PSC 6.0.
It came back in 6.2, I think it was 6.1 that wouldn't allow you to define this in the property dictionary.
Is the proxy agent running under a service account that is a local administrator? Can you see the cluster in the Fabric Group? Until you add it to the fabric group, it won't appear in compute res... See more...
Is the proxy agent running under a service account that is a local administrator? Can you see the cluster in the Fabric Group? Until you add it to the fabric group, it won't appear in compute resources. When you do a distributed install, the Web components use Windows Authentication, the manager service does not. The proxy agent is old legacy SOAP communication done to the manager service, so I would guess that the VMPS2 directory (haven't looked) in IIS Manager, shows as anonymous is enabled or should show as anonymous for a non-distributed install?
Is the certificate on the Load balancer a SAN or Wildcard cert and the same one that is installed on the appliances / IAAS hosts?
The health monitors rely on services being up before passing traffic to a particular node, the services can't start until the traffic is being passed to the first node that is starting up.  I typ... See more...
The health monitors rely on services being up before passing traffic to a particular node, the services can't start until the traffic is being passed to the first node that is starting up.  I typically put in a record in the hosts file on both the virtual appliance and the IAAS web nodes that point to the VIP name to the local IP, then the stack can start up with the health monitoring left in place. If you do this on the virtual appliance, make sure you put the hosts entry outside of the VAMI GENERATED (or something like that) comments, as this is rebuilt each time the appliance restarts. -just saw the certificates are loaded on the load balancer - I don't do that, just pass the traffic through. (Think it is layer4-performance in F5 terms)
When you did the install, what name did you specify for he virtual appliance (when you configured the vRA Settings -> Hostname)? And assume you specified the same name when you did the IAAS insta... See more...
When you did the install, what name did you specify for he virtual appliance (when you configured the vRA Settings -> Hostname)? And assume you specified the same name when you did the IAAS install? Your new certificate, does the name match the name you used for the subject name (or included in the SAN if you are doing that)?
Playing with this now, check the following for some help - the templates are Apache Velocity based (according to the bottom link below) VMware KB: Examples for customizing email templates in VMw... See more...
Playing with this now, check the following for some help - the templates are Apache Velocity based (according to the bottom link below) VMware KB: Examples for customizing email templates in VMware vRealize Automation http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2088805 Enhancing User Experience: Customization of vRealize Automation 6.2.x Email Notifications | VMware vSphere Blog - VMware…
Can you put a screen shot of all the properties you have configured for the AD Cleanup Plugin? I believe the workflow occurs on the DEM worker, can the DEM worker access your domain controller(s)... See more...
Can you put a screen shot of all the properties you have configured for the AD Cleanup Plugin? I believe the workflow occurs on the DEM worker, can the DEM worker access your domain controller(s)?
When you imported the PEM certificate in vRA 6.2, did you include the entire chain? Could be that the intermediate or root certificate authority certificate was not included so the chain of trust... See more...
When you imported the PEM certificate in vRA 6.2, did you include the entire chain? Could be that the intermediate or root certificate authority certificate was not included so the chain of trust could not be validated. Login to vRA 6.2, click on the icon that shows the certificate (varies to what browser you are using), and click on the Certificate Chain tab once you can view the cert. Validate that it has all of the chain listed, and not just the end certificate.
FQDN of the appliance and IaaS box, do they match what you put in when specifying the URL for the Web Server, Manager Service, Virtual Appliance? Anything in the Windows event logs? Did you tr... See more...
FQDN of the appliance and IaaS box, do they match what you put in when specifying the URL for the Web Server, Manager Service, Virtual Appliance? Anything in the Windows event logs? Did you try and shutdown the Windows box, reboot the virtual appliance and power on the Windows server after the CPU calms down on the VA (or when the services are registered)?
As people have already said, a catalog item can only be along to one service, but based on what you said below... Probably use reservation policies, create a Linux and Windows Policy, assign t... See more...
As people have already said, a catalog item can only be along to one service, but based on what you said below... Probably use reservation policies, create a Linux and Windows Policy, assign them to the appropriate cluster reservation and blueprints so that windows only go to window's reservations, and linux only to linux reservations. You can entitle catalog items, you don't have to entitle the entire service. Doing the service makes it easier to manage, as any new catalog item you create and assign to the service, all groups entitled to that service can use the new catalog item. If you have groups that need drop down boxes, and groups that don't, you could associate the custom properties at the business group, set to prompt user, and define them in the property dictionary. Then only groups that have the properties defined would get prompted for those additional data points.
Is this a distributed install? Load balancers in play?
From the manual - format is bad, but page 11 of the IaaS Configuration for Virtual Platforms PDF Order of Precedence for Custom Properties When the same property exists in more than one sou... See more...
From the manual - format is bad, but page 11 of the IaaS Configuration for Virtual Platforms PDF Order of Precedence for Custom Properties When the same property exists in more than one source, a specific order is followed when applying properties to the machine. You can add custom properties that apply to provisioned machines to the following elements: n A reservation, to apply the custom properties to all machines provisioned from that reservation n A business group, to apply the custom properties to all machines provisioned by business group members n A global or local blueprint, to apply the custom properties to all machines provisioned from the blueprint n Build profiles, which can be incorporated into any global or local blueprint, to apply the custom properties to all machines provisioned from the blueprint n A machine request, if you are a business group manager, to apply the custom properties to the machine being provisioned The full order of precedence for custom properties is that any property value specified in a source later in the list overrides values for the same property specified in sources earlier in the list. The order is shown in the following list: 1 Build profile 2 Blueprint 3 Business group 4 Compute resource 5 Reservations 6 Endpoint 7 Runtime Any runtime property takes higher precedence and overrides a property from any source. A custom property is marked as runtime if the following conditions exist: n The property is marked as Prompt User, which specifies that the user must supply a value for it when requesting a machine. This requires that the machine requestor customize individual characteristics of each machine, or gives them the option of doing so when a default value is provided for the required property. n A business group manager is requesting a machine and the property appears in the custom properties list on the Properties tab of the Confirm Machine Request page. Custom properties in reservations and business groups may be applied to many machines so they should be used carefully. Their use is typically limited to purposes related to their sources, such as resource management, line of business accounting, and so on. Specifying the characteristics of the machine to be provisioned is generally done by adding properties to blueprints and build profiles. Each blueprint of any type can optionally incorporate one or more build profiles and thereby inherit the custom properties in those profiles. Build profiles are especially useful for applying common sets of properties for specific purposes to a wide range of blueprints. For example, your site might want to add a second disk to, customize Microsoft Remote Desktop Protocol behavior for, and enable Active Directory cleanup for a wide variety of machines. If a build profile with the necessary properties is created, it can be incorporated into all of your blueprints, local or global. When creating and managing build profiles, a fabric administrator can load a number of predefined property sets to add several related properties all at once, instead of one by one.
To update a property from vRO, vCAC 6.1 - Update a Custom Property from vCO - Realize.net To update an array of properties from vRO (this builds on the previous post) - vCAC 6.1 - Generic Blue... See more...
To update a property from vRO, vCAC 6.1 - Update a Custom Property from vCO - Realize.net To update an array of properties from vRO (this builds on the previous post) - vCAC 6.1 - Generic Blueprint With vCO - Realize.net Those posts don't meet your use case, but shows you how to update properties from vRO, which hopefully helps out? You will find somethings can't be updated in the BuildingMachine state, or rather can be updated, but will be ignored. Network Profiles is one that comes to mind, updating VirtualMachine.Network0.ProfileName in building machine occurs after the IP information has already been allocated during the request.