In this blog post, we use two AWS Systems Manager documents, AWSEC2-CloneInstanceAndUpgradeWindows and AWSEC2 -CloneInstanceAndUpgradeSQLServer, to help you automate the upgrade process for your fleet of Windows Server 2008 R2 and SQL Server 2008 with SP4 or SQL Server 2008 R2 instances in your AWS environments. When the automation steps are complete, an AWS AMI is created. This approach gives you flexibility on how you can move forward with your upgraded servers.
Do not install the Tanium Client on the same host as a Tanium Core Platform server. Managing Tanium Core Platform servers as endpoints requires significantly more complex access restrictions in Tanium. Tanium users with management rights over Tanium Core Platform servers might be able to circumvent access restrictions within Tanium or inadvertently deploy actions that interfere with Tanium functionality. If you choose to install the client on Tanium Core Platform server machines, you must carefully restrict access to computer groups that include Tanium Core Platform servers, such as All Computers, All Servers, and All Windows. You cannot install the client on a Tanium Appliance, and you cannot use Tanium Client Management to install the client on the Tanium Module Server.
When it's time to restore files from your backups, the Instant Restore feature can very quickly convert a full system backup to a VMware or Hyper-V virtual machine for the easiest possible access. Acronis claims an RTO (recovery time objective) of as little as 15 seconds; we tested this by recovering a Windows Server 2012 R2 system backup as a Hyper-V virtual machine. The conversion took 68 seconds, and while the first boot on virtual hardware was comparatively slow, we were sitting at a functional desktop around five minutes later. That's some way short of the claimed RTO, but getting an entire Windows server fully back in action in under 7 minutes is good enough for us. 2b1af7f3a8