Recent as of April 6, 2021, 9:00am CST
APRIL 6, 2021
The following instructions are intended for customers of the following Orion Platform versions, which are known to be affected by the SUNBURST malware and are considered a Category 3 from the CISA recommended categorizations classification at https://cyber.dhs.gov/ed/21-01/#supplemental-guidance:
If you’re not considered a Category 3 by the CISA criteria, but plan to upgrade to the latest version of the Orion Platform, along with the latest versions of the Windows and SQL Server systems, please follow our normal upgrade documentation available in your Customer Portal at https://customerportal.solarwinds.com or at https://www.solarwinds.com/securityadvisory/faq#question10 to upgrade to the latest version of the Orion Platform from your current version. These instructions are designed for those who are starting a new Orion Platform environment but who cannot use the existing Orion database due to malicious activity associated with the SUNBURST attack.
These instructions and scripts are designed to help an Orion administrator configure a new Orion system built on the latest version of the Orion Platform (version 2020.2.5) but still utilizing data from the existing Orion database to help “bootstrap” the new Orion Platform instance to behave like the old Orion Platform instance.
These instructions are designed to help you to ensure your new Orion Platform instance is configured as similarly to the old system as possible. These instructions assume you will have access to the existing Orion database. Note, the Orion database does not need a network connection, nor does the new Orion instance need a network connection to the old Orion database. The administrator would be benefitted most if they’re able to transfer files between the old Orion database SQL Server and a server with connectivity to the new SQL Server to which the new Orion instance will connect. This file transfer could, for example, be facilitated via a USB drive to copy SQL scripts and output CSV files from one environment to the other.
For more information on setting up a new Orion instance, please visit: https://support.solarwinds.com/SuccessCenter/s/article/Use-PowerShell-and-SQL-scripts-to-discover-configuration-data-on-your-existing-Orion-database-server-when-migrating?language=en_US
Please check back to this page regularly as we continue to add steps and dates for transferring data and configurations for each of the Orion modules, or Subscribe to this RSS Feed to be notified when we update this page (note: you will need to cut and paste the "Subscribe to this RSS feed" URL into an RSS Feed Reader, e.g., Outlook's RSS Subscriptions, to monitor updates).
Basic recommendations:
Please follow the instructions carefully for each feature you want to migrate from the old Orion Platform instance to the new instance.
Step 1: Install a fresh Orion Platform instance per the installation guide with all the modules you’re licensed to use.
Step 2: Conduct basic discovery and import of your Orion Nodes.
SELECT [E].[EngineID], [E].[ServerName] AS [PollingEngineName] FROM [Engines] [E] |
SELECT [N].[IP_Address] FROM [dbo].[Nodes] [N] JOIN [Engines] [E] ON [E].[EngineID] = [N].[EngineID] WHERE [N].[DynamicIP] = 0 AND [E].[EngineID] = <enter ID Here>
|
Directions to import configurations for the following Orion Platform products will be provided soon – check back on this page for updates: