To install RightLink on a running Windows instance so that you can bundle it and create a RightLink-enabled version of that image.
NOTE: Although the steps provided below for bundling an instance may still be valid in some scenarios, we encourage you to explore using the Instance Provisioner to bundle existing instances. See Create New Instance with the Instance Provisioner for additional information.
In order to have a running instance where you can view real-time monitoring data inside the RightScale Dashboard and run RightScript and/or Chef recipes, you must use a RightScale-enabled image with RightLink installed. Once you have a RightLink-enabled image, you can create a MultiCloud Image (MCI) and use it in ServerTemplates to define servers and launch Windows instances on Amazon EC2, Rackpsace, or CloudStack.
This tutorial only applies to users who are interested in creating custom RightLink-enabled images of their own. If possible, RightScale recommends that you use our own Windows RightImages. However, if you need to use a base AMI from Amazon or even one of your own and you want to make the image RightScale-friendly, you can follow this tutorial to add RightLink to the existing image and create a new RightLink-enabled version of that image. You can use the new RightLink-enabled image to build a MultiCloud Image (MCI) and use with ServerTemplates.
Do not forget to tag the MultiCloud Image! Any MCI that points to custom images that have RightLink installed must be tagged appropriately to successfully operate with the RightScale management platform. See the last step in this article for more information.
Launch an instance using one of Amazon's Windows AMIs or your own custom Windows image that you have developed yourself. If you are using one of Amazon's base Windows AMIs, we recommend using their latest AMIs.
Important! This tutorial will not work if you use one of Amazon's v1.07 AMIs.
Important! Be sure to use an EC2 Security Group with port 3389 open to any port so that you can create a Remote Desktop Connection to the instance.
Before you can create a Remote Desktop Connection to the running Windows instance you must first wait for the instance to be assigned its initial password.
Note: Once the instance is listed as "Operational" you might have to wait around 10-20 minutes before the password becomes visible. You will not be able to establish a remote desktop connection until a password becomes available. To check on the initial password once it is operational:
Clicking "Show Value" will prompt you to enter your RightScale user password, after which the initial password should become exposed.
There are two different ways to create a Remote Desktop Connection.
Note: This may only work with certain browsers and environments (Internet Explorer etc). If you are not using a workstation that qualifies, then you will want to proceed with the 'Local Remote Desktop Connection' section listed below.
When viewing the show page for the running Windows instance, click the RDP action button.
Click Connect when you get the warning message.
Note: Screenshot and directions below are only for the built in Windows RDP client. If using your own RDP client in your own environment these instructions will obviously vary.
Once the instance becomes operational, go to the instance's Info tab and take note of the "Initial password" which you will later use to remotely login into the instance. (The password is located inside the first and last parentheses.)
On your local machine, use the instance's Public DNS Name or Public IP address to establish a remote desktop connection to the instance. Click Connect to connect to the instance.
Note: If you get a certificate error message, you can still continue to connect to the instance.
Next, you will need to log into the instance with the following credentials:
Password: ("Initial password" from the instance's Info tab. Only enter the characters that are enclosed within the parentheses as mentioned previously.)
Be sure to save your login credentials.
Several prerequisites must be downloaded and installed before you bundle the instance.
Note: Unfortunately, due to the restrictive security settings that are built into a Windows server, it is easier to download the below files locally and upload the files to an S3 bucket, after which we can download them to the Windows instance. Download the below installation files on your local computer and upload the installer files to an S3 bucket and set its permissions to 'public-read'. Obtain the link for each file from the S3 browser (Clouds > AWS Global > S3 Browser). You will need to use that link to download the installation files to your Windows instance instead.
To allow your S3 bucket download permissions in Internet Explorer, open an I.E. browser window on the Windows instance and follow these directions:
Save and apply the changes. Refresh the browser window and you should be able to download these files using the link to the file in your S3 bucket. Alternatively, you can also allow all downloads from the Options > Internet Options > Security tab if you wish as well in order to download these files directly to the instance.
Copy the below link and paste it into a browser window on your workstation, then upload the installer file to the aforementioned S3 bucket that we created earlier:
More information here, for reference
Download the file from your S3 bucket (e.g., https://<your-bucket>.s3.amazonaws.com/dotnetfx35.exe), then run the installer file on the instance and follow the wizard to let it complete.
In order to install RightLink on your instance, you must have PowerShell installed. Navigate to the following link and find the PowerShell installer that is specific for your Windows instance:
Download the necessary installation file to your local workstation, then re-host it in the aforementioned S3 bucket created earlier. Download the file from your S3 bucket (e.g., https://<your-bucket>.s3.amazonaws.com/kb968930.exe), then run the installer file on the instance and follow the wizard to let it complete. At the conclusion of the installation, you will be prompted to reboot the instance. Click 'Restart Now' and the instance will be rebooted. After a couple minutes, refresh the RDP window or re-establish an RDP connection and now the PowerShell installation is complete.
Note: Powershell may already be installed on your Amazon Windows instance, so it may be unnecessary to install this update as it may not apply here.
If using an image that does not have EC2Config pre-installed, you will want to download and install it from here:
The first step is to download the RightLink installation package to the Windows instance.
Browse RightScale's mirror for the latest RightLink packages to find the appropriate RightLink installer file. You must choose the distribution package that's most appropriate for your purposes, based upon your instance's architecture (64-bit only).
64-bit: Rightscale_Windows_x64_5.8.13.msi (19.5MB)
Although we recommend using the latest available RightLink package, it may not be available for your particular release. The most recently published packages can be found in the "latest" RightLink packages directory. If you do not find a suitable package in one of the "latest" directories, you can also browse for a different version from one of the archived directories.
For Windows 2008, you cannot download the RightLink installer file from the RightScale mirror directly to the Windows instance. Similar to the PowerShell installation process above, you will need to use an S3 bucket and your local computer to download the RightLink installer to. Download the appropriate RightLink installer file based on the chosen architecture (x64) to your local computer. Upload the file to the same S3 bucket where you uploaded the PowerShell and .NET 3.5 installers, and change the file's permissions to be 'public-read'. Open an I.E. browser window on the running instance and enter the URL to the RightLink installer file in your S3 bucket (e.g., http://<your-bucket>.s3.amazonaws.com/Rightscale_Windows_x64_5.8.13.msi). Save the file to the Windows instance.
Run the executable file on your new Windows instance and complete the RightLink Setup process.
Note: If you do not have PowerShell 2.0 installed on the instance, you will not be able to install RightLink.
To verify that RightLink was installed successfully, you can check the server's programs:
Go to the running instance's Info tab and click the Bundle action button, which may be located under the More Actions budtton.
You will be redirected to the main "Info" page for your newly created AMI.
Note: You will still need to wait for the image's state to become "available" before you can use it to launch an instance. It may take 15-30 minutes before your image becomes available. Refresh the AMI Info page to monitor the state if desired.
In order to properly use the RightScale-enabled image with ServerTemplates, you should create a MultiCloud Image (MCI) that references the new image. See Create a New MultiCloud Image. The MCI can then be added to any local (HEAD) ServerTemplates in your account. If you need to make that image available in a different AWS region, follow the Replicate an Image to different AWS regions.
Once you have created the MCI, you will need to add the following tag to the MCI so that RightScale will be able to identify the created image as a RightLink-enabled image:
Congratulations! You now have an MCI that points to a RightLink-enabled image for launching Windows instances. Just like any other instance that's launched using one of our v5 RightImages (which are RightLink-enabled by default), you will be able to see monitoring graphs and execute scripts inside the RightScale Dashboard.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.