The main reason for extending the WiFi network into my Dads backyard and throughout the house was to ensure surrounding wireless security cameras receive great reception due to a recent Coyote problem, and we have 4 cats. They even need to be locked in the house every night. My dad has a mechanical mind and installed 8 foot fencing. I have a technical mind and wanted to have the highest powered WiFi coverage throughout every inch of our property. Neighboring interference? I’ll choose to out-muscle the interference or go around it if possible. All it took for me was a cousin with ties to a company throwing away good network equipment, prior network wiring skills, and a $60 1000 ft spool of CAT6 UTP 23AWG ethernet cable. Amazing how low prices are today time comparatively. To do a job like this would easily run into the multi-hundreds, however due to the reason for this and free equipment provided (although not 802.11ac) it was all worth it.
Let’s Encrypt is a new open source certificate authority that promises to provide free SSL certificates in a standardized, API accessible and non-commercial way. If you’ve installed SSL certificates in the past, you’re probably familiar with the process of signing up for a certificate with some paid for provider and then going through the manual process of swapping certificate requests and completed requests.
Let’s Encrypt is based on set of open service APIs that can be implemented on any platform and create certificates for Web servers including IIS. This seems like a fabulous idea, given that securing your site if you have any sort of authenticated access is an absolute requirement. It’s not so much the money that’s a problem since basic SSL certificates these days even from paid providers are relatively cheap (I use Cloudflare both for DNS and free SSL certificates), but the fact that you can completely automate the process of SSL creation and management is a huge win. This has both upsides and downsides actually and I’ll talk about that at the end of the article. To be clear – I’m not a network admin and I don’t have extensive experience managing certificates on a large number of sites so in this post I cover a few basic scenarios that I deal with in my own sites hosted on my own hosted servers.
Amazon Linux 2016 AMI is now available!
This content was taken from the official AWS Blog but since you’re already here, might as well enjoy yourself and if you can think of something you’re thankful for in 5 seconds or less, go ahead and help my site stay up by clicking on an ad. If you don’t, there’ll be even more!
The Amazon Linux AMI is a supported and maintained Linux image provided by Amazon Web Services for use on Amazon Elastic Compute Cloud (Amazon EC2). It is designed to provide a stable, secure, and high performance execution environment for applications running on Amazon EC2. It supports the latest EC2 instance type features and includes packages that enable easy integration with AWS. Amazon Web Services provides ongoing security and maintenance updates to all instances running the Amazon Linux AMI. The Amazon Linux AMI is provided at no additional charge to Amazon EC2 users.
We offer new major versions of the Amazon Linux AMI after a public testing phase that includes one or more Release Candidates. The Release Candidates are announced in the EC2 forum and we welcome feedback on them.
Launching 2016.09 Today (9/27/2016)
Today we launching the 2016.09 Amazon Linux AMI, which is supported in all regions and on all current-generation EC2 instance types. The Amazon Linux AMI supports both HVM and PV modes, as well as both EBS-backed and Instance Store-backed AMIs.
In fact you can adjust the amount of memory assigned to a virtual machine while it’s running, even if you haven’t enabled Dynamic Memory. This works for both generation 1 and generation 2 virtual machines.
Additionally some of the new features for Hyper-V include an update in the management tool which now allowing to manage all generations of Hyper-V …. So basically you can manage all of those hyper-v hosts – Hyper-V 2008, 2012, 2012 R2 or 2016 – with the same console….
So the lab setup was pretty simple:
This time I used my desktop system with VMware Workstation installed, but you can also use ESXi and configure the requirements (via web client).
Physical Box (running desktop OS …. Windows 8.1) > VMware Workstation VM running Server 2016 TP4 (named “2016TP4MAIN” ) with Intel VT-x activated > Server 2016 TP4 Hyper-V VM which we will be testing the hot-add or hot-remove memory.