Why you shouldn’t use .local in your Active Directory domain name.


Saving this link for another day. The topic of what gTLD to give your internal AD domain comes up all too often.

Share MS doesn’t have a more up to date page about this. Bonus points if it also talks about their experiences with how best to naming things with Azure and its various identity services.

Source: Why you shouldn’t use .local in your Active Directory domain name.

Adding your vCenter Web Client as a search provider in Chrome


Most browsers these days offer a function that allows you to add other search engines to them. This function allows you to quickly search for stuff directly from your web browsers search field instead of having to open up the site directly, type in what you want and press enter.

In this article I’m going to show describe how to add your vCenter 6.5U1 HTML5 client as a custom search engine in Google Chrome.

This will allow you to search for vCenter objects directly from Chrome without first opening the HTML5 Web Client.

What you need

  • Access to an HTML5 vCenter Web Client (vCenter 6.5U1 on the VCSA was used to write this.)
  • Google Chrome (Chrome 60 was used at the time this was written)

Find your vCenter Web Client Search URL

  • Browse to your HTML5 vCenter Web Client and sign in. Its usually something like ​https://{FQDN}/ui` where {FQDN} is the URL for your vCenter Web Client.
  • From the banner at the top of the page, click on `Menu` and select `Search`.
  • Enter the name of a VM you want to search for and press `Search`.
  • Copy the URL from the address bar in Chrome. In this example we have something like this. I’ve replaced https://{FQDN}/ui/#?extensionId=vsphere.core.search.domainView&query={SEARCHTERM}&searchType=simple

Add a custom search provider to Chrome


  • Open a new Chrome tab or Window, enter your keyword and the object name you want to search for.
  • Chrome will return the vCenter Web Client search page with the term you entered.
  • $profit.