daphnissov's Accepted Solutions

Without knowing more about how you've set up your tenant, it's difficult to give precise recommendations. Generally speaking, though, you can create only a single Windows 2012 blueprint and have that accessible to each of your business groups simply by setting up an entitlement that allows them to provision from that. If, for example, a user is a member of multiple business groups, they'll see two copies of that catalog item with a gray label underneath the title that names the business group to which it applies. You can further reduce sprawl by having a drop-down list in the presentation form (if you so wish) that allows a user to set any of your five clusters. And in vRA 7.3 with component profiles, you can create an image profile that allows a user to pick 2012 or 2016 without dedicating a blueprint to each. So best case scenario is you only have one blueprint for all six business groups for all five clusters and for both Windows operating systems.

Yes, fortunately now nested ESXi 6.5 does provide guest customization via a Linux-type specification. The networking information only gets applied to the first vmkernel interface (so as to provide management capabilities), but from there you can customize it to your liking. lamw wrote a blog post that covered this feature back in October, so I highly recommend you give it a read and also follow the link as it contains the two edits you'll need to make in your template. Of specific interest in your case is removal of the system UUID inside esx.conf.

PowerShell comes to mind first. If you want to export the active alerts, use Get-OMAlert and pipe it to Export-CSV. If you want alert definitions, use Get-OMAlertDefinition and pipe it to the same.

I don't think there's a state that gets you further along that what you have now. One workaround you might try is to begin your vRO workflow with a long sleep statement which will allow enough time for your software components to run. Alternatively, instead of using software components for operations which are fairly simple, you could have the guest agent run a script. Check the custom properties for reference material on that.

Hi, Eric. I dealt with this conundrum recently so can shed some light. You can still get this behavior although you give up flexibility when it comes to services. In vRA 7.x, the approval policy type to look for is "Service Catalog - Catalog Item Request - Virtual Machine" as seen in the below screenshot. The conditions for which an approval can be built are as follows. Once you've created that, a couple things I've noticed: This type of approval policy can only be applied to an individual blueprint level (even if composite). It cannot be applied to a service. In your Entitlements, the only way to link this Approval Policy is to change the filter from "Show applicable" to "Show all" as you can see here. Once done, however, the approvals do work as intended. I wish that vRA were smart enough to apply any sort of approval policy to a service (thereby having it propagate to children blueprints) and be intelligent enough to only apply to objects/types for which it is applicable. But the "Show all" switch just seems to be a plain old bug.

That's all well and good, but what I'm saying is you can already do that without having to add any custom properties or mess with the deployment. Look at my screenshot below. You can see I've clicked on the vSphere machine item (not the deployment) and can adjust CPU and memory because I've set minimum and maximum allowable values in the blueprint. It could be left wide open as well. This all comes out of the box. There are no custom properties needed to achieve what you see.

In the Scope for a new notification, you'll have to pick and choose which objects are still the responsibility of your operations team. As they change hands, you'll have to adjust your notifications accordingly.

First, this really isn't a vRealize Automation issue and belongs in the vROps forum. Secondly, there's not going to be any good solution for you without using a combination of the EpOps agents in-guest, or the management packs from Blue Medora. If you have an Advanced license, you can use the Endpoint Operations agents. By default, recent versions of vROps have the SQL plug-in embedded for the EpOps agents, so when you deploy to a system with MSSQL the agent can, after configuration, collect on certain metrics. But to do what you want in the best way really requires an Enterprise license, and Blue Medora pack for SQL is really excellent although not free.

What is your use case? Why are you looking for this behavior? In short, like nmshadey​ says, this really isn't possible normally as vRA executes these machine provisioning workflows under the context of the service account.