In Part 1 we deployed the vCenter Orchestrator virtual appliance. Now in part 2 we are going to configure vCO, such as SSO integration, vCenter and SSL certificates amongst other items.
vCenter Orchestrator (vCO) is a product which allows you to create tasks and automated workflows which and be run directly within vSphere Web Client or the vCenter Orchestrator Client.
There are a number of pre-made workflows to get your started, and the number of tasks you can perform is quite amazing. Any task that can be performed in vCenter can be automated through vCO, and thats just the start. Add some Active Directory integration, API's and other 3rd party plugin's makes this a pretty neat toolkit.
Workflows can be anything from simple workflows that contain a single task to say create a virtual machine, to complicated workflows containing many tasks that might build an entire solution and integrate with 3rd party plugins.
One of the best things about vCO is it's included with vCenter Server and it's free!
If you are in the unfortunate position in which you or someone else has forgotten the vCenter SSO v5.1 admin@System-Domain password, then you may have a problem. Particularly if there are no other users delegated as SSO administrators.
However the aim of this blog post is to help you in resetting the admin@System-Domain password in SSO 5.1 only (it is much easier in 5.5)!.
First and foremost it's worth pointing out this is completed unsupported by VMware. VMware's advise and supported method is to reinstall SSO.
However you do have 2 other possible options I have presented below.
The default pathing policy for a LUN can be changed (for example from Fixed to Round Robin). This can be a LUN on an iSCSI or FC array (or FCoE for that matter).
When I refer to pathing policy I'm refering to what you may have seen if you've ever clicked manage path's on a VMFS datastore and see it set to Fixed, Round Robin (RR) or Most Recently Used (MRU).
In this example I will be changing the default pathing policy for an EqualLogic array from Fixed to Round Robin.
Before I get into how to change the multi-pathing policy, it's important to understand the below 3 plugins (NMP, SATP and PSP):
Since the release of VMware Horizon View 5.2 Feature Pack 1, it has been possible to access View virtual desktops simply via a HTML5 browser, without the need for the View Client.
Now in Horizon View 5.3 Feature Pack 1, this ability now has an improved feature set and really makes this a viable alternative in some cases to the full VMware View Client. It is particularly useful if you need to get access to a desktop quickly where the View client is not installed or cannot be installed, such as working remotely on a non company owned device.
Some of the improvements to functionality are:
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.