Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
|Table of Contents|
Long Term Support
Stable, tested ServerTemplate assets
The "Base" ServerTemplate is specifically designed for developing custom ServerTemplates that include best practices for deploying Windows servers with the RightScale management platform.
Note: Some versions are not available in all clouds. Check the ServerTemplate's Images tab for details.
For Windows servers, the root filesystem (C:\) is located on a mounted volume (if volumes are supported). In the example screenshot below, an EBS volume is used as the root filesystem for an EC2 instance. Note: The instance's AWS ID (i-904c37c9) is used in the nickname of the volume.
The 'SYS Set Windows Automatic Updates Policy' and 'SYS Install All Windows Updates' scripts control whether or not Automatic Windows Updates will be applied to a running server, as well as how the updates will be applied. Some updates require the server to be rebooted in order to complete the update. In such cases, you can use the WINDOWS_UPDATES_REBOOT_SETTING input to either allow is disallow an automatic reboot of the instance. By default, servers will NOT be rebooted so that you can pick a more convenient time to reboot the server in order to minimize the affect on your application and its users. See Base ServerTemplate for Windows (v13.5 LTS) - Runbook for details.
Use the 'SYS Install Microsoft update by KB number' script and the KB_ARTICLE_NUMBER and WINDOWS_UPDATES_REBOOT_SETTING inputs to selectively pick which KB updates to apply to the server. See Base ServerTemplate for Windows (v13.5 LTS) - Runbook for details.
Use the 'SYS Activate Windows with KMS server' script with the KMS_HOST and KMS_PORT inputs to use a Microsoft Key Management Server (KMS) to activate volume licensed Microsoft products like a Windows 2008 Server. See Base ServerTemplate for Windows (v13.5 LTS) - Runbook for details.
The 'SYS Monitoring install Windows' script is used to enable the instance for real-time monitoring by the RightScale management platform. DO NOT CHANGE the values for the SKETCHY and SERVER_UUID inputs because they are used to properly connect the instance to RightScale's Monitoring system so that you can view real-time monitoring graphs (under the Monitoring tabs) in the dashboard and set up alerts for automation. If the script is executed successfully, you will see the following machine tag on the instance.
|Glossary | 用語 | 용어||Site Map | Site Help||Community||Corporate Site||Get Support||Dashboard Login|
|Doc Feedback||Product Feedback||Resources||MultiCloud Marketplace||Forums|
© 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.