Looking at the screen shots i would say the difference between the two are the limited menus look like the vrops standard edition licence was applied. Are you adding a licence key as part of your config?
After the deployment you would be in eval mode which would give you enterprise level licence which would explain what you have all the menu items
I think I give up...
So I deployed the appliance again, and the only thing I've done since, was run the "new instance" setup, then start the vROps service from /admin page. When service was up I got the startup wizard to configure ntp, ceip and license. I put in my ntp servers, disabled ceip, and went witht the eval License. So far, all OK.
Next, stopped the service from /admin page, rebooted VM and started the service again from /admin page. Dashboard actions test = all OK still.
License is a vCloud Suite Standard PLU, which includes vROps Advanced. When validating, it says "VMware vRealize Suite 2017 Standard for vRealize Operations", which seems right. vCloud Suite Standard means vSphere Enterprise Plus with vRealize Suite Standard (vCloud and vRealize Suite matches). And the vR Suite Standard contains vROps Advances, so full Dashboard management should be included (compared to vROps Standard).
So I added the License and Dashboard actions looks fine still.
Logged out and back in (as admin as before) - BANG! Dashboard actions are fucked!
So it seems my License is a problem maybe?
Yeah, it seems I've come to the same conclusion (see my other answer), but it should not be like this in my humble oppinion.
This is a vCloud Suite Standard License includes vRealize Suite Standard:
The vRealize Suite Standard includes vROps Advanced:
Do you agree with me that it should be vROps Advanced?
1 person found this helpful
And yes you should have vrops advanced. Try adding the vcloud suit licence into vrops that should fix the problem
Well, my "forum curse" keeps hitting me. Like many times before, I find a solution/reason after starting a forum thread. And it ends up being part of what you said sxnxr:
VMware KB2142364 - VMware vCloud Suite 7 Fulfillment
I've believed the vCloud Suite would be the same for all the latest versions, which seems not to be the case. This used to be a vCloud Suite Standard 6.0 earlier which was upgraded.
Well, what I thought was a reason, I'm now abit usure three sentences later. The KB says:
- vSphere ENT+ for vCloud Suite (per CPU)
- vRealize Suite STD 7.0 (per PLU)
- vRealize Automation STD 7.0 (per CPU)
So even though vRA isn't in the vRealize Suite Standard, we get a lic for that (and we do). We also should get a vRealize Suite Standard license; so why don't we get vROps Advanced then? Like my comparison from VMware shows above.
Strange we have a vRealize and not a vCloud License..
I'd like to note that I don't have direct access to the Licenses, but will get in touch with the right guy.
Good to know I'm not the only one who thinks we should have vROps ADV.
Everything look correct in the KB and all the screen shots. VCS standard gives you vrealise suite standard. vrealise suite standard gives you vrops advanced.
You just seem to have the wrong licence key. you need to get the VCS key and apply that to vrops
I agree. I talket to the license guy and we looked at the vmware portal. There where still vCloud Suite 6 Licenses that hadn't been converted (we are in an Upgrade phase to vSphere 6.5 etc). Pretending to upgrade the license we go from a vCloude Suite to separate licenses, no vCloud Suite license shows up when upgrading the licenses:
I think we will make a support case and ask why/demand correct licenses
Once you upgrade you will get the key as per your screenshot. The key will be the vRealize Suite 7 Standard
This is what i get when i add ours ( note we use advanced) It appends the for vrealize operations to the end when you validate it.
Your screen shot looks correct to me. VCS 6 upgraded gives you separate licences for each product. the vRealize Suite STD 7.0 key will work with vrops and vrli
I am not sure what your confusion is. This might help
Update - We ended up filing a support case with HPE (licenses bought from them etc). Still waiting on the output.