A dozen or so VMs exist on my network. Everything from my virtual router (PFSense of course), a Plex server, a Nextcloud server, as well as some world domination experiments. Muaahhhh ha ha! Up until the last few months, they have run on a VMware cluster consisting of a pair of Dell Poweredge 2950s that I had absolutely maxed out with 32GB of RAM each and 4 of the best Xeons I could find for that socket. Needless to say these were power hungry beasts, also, outdated.
In this post, I'll show you how to store the keys in a Google Cloud Storage Bucket instead of statically in the code. This will allow you to update your certificate authentication with Let's Encrypt without deploying a new version of your app (thank goodness), and is a great first step towards automating this process entirely.
I didn't find a guide that brought this all together on the web, so here it is. We are going to be adding a module to our app that will be returning the correct text for the Let's Encrypt validation, using express middleware to direct the route correctly, and having a lot of fun!
Here is a quick walkthrough to configure logs on Amazon Linux, including IAM role creation.
Let's start with the IAM policy that the role will consume. Go to IAM > Policies > Create Policies, and select 'Create Your Own Policy'
I was listening to the Packet Pushers Show 349 'Future of Networking with Mark Townsley' today, and they talked an awful lot about IPv6. My opinion on IPv6 in the enterprise up to now has been that it is really just a useless way to complicate LAN networking, and not ready for widespread enterprise use on the WAN. It still isn't 100% supported everywhere, no one in enterprise knows it, you almost certainly need to run dual stack or have NAT gateways, and it doesn't solve any of the problems I run into every day. Now, I think most of those points are still valid, though less so than even just a few years ago, but Mark made a point towards the end of the show that really got me thinking...
We discovered a problem while creating a new user in our on-prem Exchange 2013 ECP. I amused myself in resolving the issue and have decided to inflict it upon the world.
On trying to create a user, the following error appeared...
This script will take a google user export, find mailboxes matching the email addresses in Exchange, and disable the mailboxes. Make sure you are not letting Google AD Sync synchronize until you are done with this process.
I have been working on archiving and removing a a little over 3000 Exchange Mailboxes that had been sitting since my client's move to Google Apps. Obviously, I didn't want to manually go through and export and disable all of the mailboxes, so I made a quick and dirty script which I thought I would share here. Emphasis on quick and dirty here. :)
Windows Server 2016 has a lot of things disabled out of the box as to improve responsiveness and reliability. One of those things is Windows Photo Viewer. In this quick tutorial, I'll show you how to enable it. Now as you read through this, you might be wondering if there is a way to enable the Photo Viewer with Windows add / remove features or some built-in utility like that, but as much as I searched, I could not find a way to do it from within Windows Server 2016. So this method uses a donor OS.
My workstation came with the
abhorred beloved Windows 10, beset with ads from the Windows store, invasive data mining software (in my opinion) known as Cortana, and annoying pop-ups questioning if you REALLY want to use a browser other than Edge as the default. I have to be honest, Windows 10 seemed great when it first released, but with every update, it seemed to get more and more controlling, invasive, and resource hungry. I really don't see Windows 10 as a business/workstation OS.