Don’t leave your keys in the lock

MS Azure has announced a nifty tool that spots secret information in Github related to Azure keys.

via Managing Azure Secrets on GitHub Repositories | Blog | Microsoft Azure

Advertisements

Looking to get started coding?

Have a read of the knowledge Ashley McNamara has distilled via ashleymcnamara/learn_to_code: Resources for budding developers

Technet landing page for Windows Event Forwarding information.

Probably more information about Windows Event Forwarding (WEF) than you will ever need.

via Windows Event Forwarding – TechNet Articles – United States (English) – TechNet Wiki

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

• Follow the steps described [here](https://support.google.com/chrome/answer/95426?visit_id=1-636408548555398702-3960116703&p=settings_omnibox&rd=1) to add custom search engine to Chrome.
• Enter the following information:
  • Search Engine: A meaningful name/label for the search config
  • Keyword: The keyword you want to use in chrome to tell it to search your VC
  • URL: Enter the URL you copied in the step above. Replace `{FQDN}` with the URL for your vCenter Web Client and replace `{SEARCHTERM}` with `%s`

Testing

• 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.

mpp files stored in SharePoint open read only in Project Client | Microsoft Office Sharepoint

Yay. I needed to write up a quick project plan for an upcoming engagement. I refuse to do project plans in Excel on principle.

Installed Project 2013 on my Windows 10 VM. Applied pending Windows update. Created plan. Saved to SharePoint Online. Closed Project.

Went and did something else.

Came back to make adjustments to the plan. Everytime I opened the plan from SP in Project it would open as read-only.

This is a known issue and the KB below will help you.

Ill drop Project 2016 on there tomorrow and see if its O365 integration is any saner. In the meantime the patch below worked around the problem.

https://support.microsoft.com/en-us/kb/3114843

Source: mpp files stored in SharePoint open read only in Project Client | Microsoft Office Sharepoint

IPv6 Best Current Practices | APNIC

APNIC has a list of documents and information regarding Best Practices for IPv6 deployments in various types of environments.

FYI, I dislike the term ‘Best Practice’ because in IT solutions are almost never “one size fits all”. I’ll generally refer to Recommended Practices.