Below is a summary of features, updates, and changes in regards to RackConnect. Keep this page bookmarked for updates made periodically to RackConnect.

April 9, 2013

• Support for ASA software versions greater than 8.3
• Support for ASA X series firewalls

January 15, 2013

• Support for Cloud Networks
• Automated quality control for each new RackConnect customer configuration. RackConnect will automatically create two cloud servers (via a test account which the customer will NOT be billed for) and perform several quality assurance checks before removing the servers and marking the configuration complete.
• The AutoNAT feature is now available

November 19, 2012

• Support for Windows Server 2012

November 13, 2012

• Changed the order of operations for cloud server builds for customers at the managed service level so that the server builds, RackConnect automation runs, and then managed cloud automation runs. Managed cloud customers who run their own post-build automation should trigger their automation to start based on the completion of the managed cloud automation rather than RackConnect. For more information, consult How to Programmatically Determine the RackConnect Automation Status of Your Cloud Servers.

October 9, 2012

• Network device configuration save and sync performance improvements

October 3, 2012

• Customers will be notified when a cloud server is unprocessable due to being built in a region that does not match the region in which their dedicated environment is deployed.

• You may now use the Cloud Servers API to query the RackConnect Automation Status of your Cloud Servers. Instructions are posted here.

August 13, 2012

• Performance improvements for F5 packet filter changes 

August 1, 2012

• Support for Next Generation Cloud Servers

July 02, 2012

• Customer API call to retrieve automation status 

• Customer API call to retrieve automation status details 

• Customer API call to retrieve gateway IP 

May 08, 2012

• Add Network Policies which allow communication between Cloud accounts belonging to the same RackConnect Configuration 

• Improve overall automation performance

Known Issues

Pre-9/6 Windows Managed Cloud Server Snapshots Failing RackConnect

Description: Windows Managed Cloud Server Snapshots fail RackConnect automation

Cause: The agent is not able to correctly set the private IP when IPv6 is disabled, leading to an instance that does not have proper connectivity and thus fails RackConnect automation.

Affects: Snapshots created from Next-Gen Managed Windows Servers where the Cloud Server from which the image is based was spun up before 9/6/12

Workaround: Re-enable IPv6 on the base image before creating snapshots. See http://support.microsoft.com/kb/929852 for instructions.