Since approximately 3am US EST this morning, teams have been working to restore a fleet of Windows server and workstations which were impacted by the CrowdStrike Anti-Virus bug.
- IT has restored operations to all impacted Windows Servers. - Product teams have confirmed all our applications (including WMC, SignuApp, and IRIS) are operating successfully.
# Steps to Resolve
For remote users with their own Windows laptops or desktop PCs, you may need to follow the instructions below to recover access to your computer:
*****
These instructions will walk you through the necessary steps to remediate your access issues due to the CrowdStrike Outage issues.
**Note, you might need to go through more than one of the options listed.
Please follow the options in the order given.
ISSUE: Blank or Black Screen
## FIRST OPTION
1. Hold down the power button for 10 seconds to turn off your device.
2. Press the power button again to turn on your device.
3. On the first sign that Windows has started (for example, some devices show the manufacturer's logo when restarting) hold down the power button for 10 seconds to turn off your device.
4. Press the power button again to turn on your device.
5. When Windows restarts, hold down the power button for 10 seconds to turn off your device.
6. Press the power button again to turn on your device.
7. When presented with Windows logon screen, if you can sign-in, do so. **Note, if this does not resolve your issue, please proceed to Second Option***
## SECOND OPTION
1. If Step 7 reboots your device or takes you to the following screen, click on "See advanced repair option"
2. Click on Troubleshoot from "Choose an option" menu
3. Choose "Advanced Options" from "Troubleshoot' menu
4. Choose "Startup Settings" from "Advanced options" menu
5. You will need to input the BitLocker key at this stage. When entering the BitLocker key, please note the following a. MOST IMPORTANT – you will only have about 10 seconds to start entering the BitLocker key once you get to the prompt, if you wait too long the device will reboot, so be ready please b. You do not need to enter the " – " in between each set of 6-digits, Windows will enter that automatically c. For most devices the Bitlocker key is: 159995-481888-409277-662277-503976-035112-345939-176297 d. If that key doesn't work, please email crowdstrike_outage@theagora.com for assistance. e. Once you have entered the code, there is NO need to press enter, if the code is correct you will get passed to the "Startup Setting" menu (step 6). If the code is incorrect, you will be prompted to enter the code again. f. Even if you enter the code correctly the first time, you might need to enter a second time.
6. From the "Startup Setting" menu click "Restart". After your device restarts you will be presented with the following menu, press the number 5 key to select "Enable Safe Mode with Networking"
7. Sign into Windows using the following credentials" a. Username – IT b. Password – R3liabl3TacoTruck! c. *Note: For in office workstations enter the username as: .\IT d. If those credentials do not work, please email crowdstrike_outage@theagora.com for assistance.
8. Once logged in, you will need to navigate to the following file path a. C:\Windows\System32\drivers\Crowdstrike b. Locate the file starting with "C-00000291-…*sys*" and delete it. c. To do the above, open File Explorer, in the file path type in C:\Windows\System32\drivers\Crowdstrike
9. Reboot the device and you should be good sign-in when back at the logon screen
10. For assistance with any of these steps, email crowdstrike_outage@theagora.com and provide as much detail as possible about which step failed.
14West Technologies Support
Jul 19, 2024 - 12:49 EDT
Update - Summary CrowdStrike is aware of reports of crashes on Windows hosts related to the Falcon Sensor.
Details Symptoms include hosts experiencing a bugcheck\blue screen error related to the Falcon Sensor. This issue is not impacting Mac- or Linux-based hosts Channel file "C-00000291*.sys" with timestamp of 0527 UTC or later is the reverted (good) version.
Current Action CrowdStrike Engineering has identified a content deployment related to this issue and reverted those changes. If hosts are still crashing and unable to stay online to receive the Channel File Changes, the following steps can be used to workaround this issue:
Workaround Steps for individual hosts: Reboot the host to give it an opportunity to download the reverted channel file. If the host crashes again, then: Boot Windows into Safe Mode or the Windows Recovery Environment - https://support.microsoft.com/en-us/windows/start-your-pc-in-safe-mode-in-windows-92c27cff-db89-8644-1ce4-b3e5e56fe234 Navigate to the C:\Windows\System32\drivers\CrowdStrike directory Locate the file matching “C-00000291*.sys”, and delete it. Boot the host normally.
Note: Bitlocker-encrypted hosts may require a recovery key. Contact Miles Palmer for you Bitlocker Recovery Key - milespalmer@theagora.com
Jul 19, 2024 - 08:25 EDT
Investigating - Is the ability to take or process orders affected? NO
Are Customers able to access their products? YES
The Issue All Windows Systems (servers and workstations) using CrowdStrike Anti-Virus received an automated update this morning which caused them to crash.
The Impact Affected Windows servers or workstations are stuck in a reboot-loop, requiring manual intervention to fix.
Workaround The teams are actively assessing and quickly remediating any crashed Windows servers or user-workstations to bring them back online.
Next Update Regular updates to follow every 2-hours as the issue is being addressed.
We will be replacing the Horizon certificate. During this time Horizon will not allow connections or apps to launch. Posted on
Jul 24, 2024 - 11:13 EDT
The IRIS system is scheduled for system maintenance to begin on Sunday, 7/28 at 8:00 a.m. US time, and will last for approximately 3 hours. During the maintenance window there is no expected downtime; however the system may experience some delays processing sign-ups. Reminders will be sent 60 mins before maintenance begins, at the start of maintenance, and then finally when maintenance is complete.
Thanks, The IRIS team Posted on
Jul 28, 2024 - 04:50 EDT
Completed -
The scheduled maintenance has been completed.
Jul 22, 18:00 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 22, 16:00 EDT
Scheduled -
Please be advised that on Monday, July 22nd, starting at 4:00 PM EDT, IRIS will undergo some scheduled maintenance work on the Mailing stats component.
During this maintenance window, Mailing stats will not be updated in IRIS. The process may run for up to 2 hours.
Impact: Mailing Stats: Mailing stats updates will be paused during this maintenance period. IRIS Pages: There should be no impact on any IRIS pages. All other functionalities should remain fully operational.
We appreciate your understanding and patience as we perform this necessary maintenance. Reminders will be sent 60 mins before maintenance begins, at the start of maintenance, and then finally when maintenance is complete.
Completed -
The scheduled maintenance has been completed.
Jul 19, 00:00 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 18, 20:00 EDT
Scheduled -
On Thursday July 18th from 8 PM to Midnight local time the Mt Vernon area office networks will be unavailable as we upgrade equipment.
Network access from any building including access to any computers on the office networks and Internet access from the office network will be unavailable. This will not impact applications in the Baltimore Data Centers. This will NOT affect any customer facing systems, and access to major systems such as IRIS, Advantage and WMC will not be affected.
This upgrade will both increase our capacity and save us money on our yearly equipment renewal.
Contact John Huber with any questions or concerns jhuber@theagora.com 443-280-0840.
Jul 11, 08:47 EDT
Resolved -
After implementing a network fix to resolve a post-migration latency issue between Hasura and Advantage on-prem databases, error rates have returned to normal for all Hasura and PIE endpoints.
Jul 16, 15:27 EDT
Investigating -
We are experiencing an intermittent error with Hasura REST calls that could effect authentication on a small number of attempts, which will resolve upon retry.
We are exploring fixes to reduce the error rate, and are working with the vendor to find a path to full mitigation.
Jul 15, 16:22 EDT
Resolved -
Blueshift reported some possible delayed campaigns today between 10:51 am EDT and 12:16 pm EDT. This affected the following campaign types: One-Time/Recurring Campaigns, Segment-Triggered Campaigns, and Event-Triggered Campaigns. Blueshift implemented a fix at 12:16 pm EDT.
Jul 16, 13:03 EDT
After monitoring over the weekend, we can officially call this migration complete and successful. For the specific items that we knew would be delayed, please see the list of updates below.
WMC - All orders that WMC has sent to PIE and then sent to Advantage Omnistream (OSM) have processed and are fully caught up.
-All SignupApp data is fully caught up
Blueshift - Blueshift is fully caught up and all transaction processing have been running successfully on the hour all weekend.
Reporting - All connection resets were successful - Batch Orders & Daily reports are caught up but the D&A Team are going to run a full Production refresh this morning to shake out any loose ends. - All reports previously mentioned that were scheduled to be refreshed on Tuesday, are ahead of schedule and caught up. *Please allow time for the Prod refresh this morning, but if you are seeing any discrepancies in the afternoon, please submit a ticket to the D&A team and they will take a look.*
Thanks, 14West Technologies Team
Jul 15, 11:07 EDT
Verifying -
Hi,
We are happy to report that the planned Advantage migration from AWS to On Premises (TierPoint) has completed. It took approximately 7 hours and 18 minutes. We will monitor things over the next 24 hours before fully Resolving this planned Maintenance.
As a reminder, nothing will change with how you access Advantage. You will access web-based Advantage Production the same way you do today- through the Advantage Production tile in OneLogin.
Please also remember that while the systems are coming back up and recovering, there will be some delays for the specific items listed below:
WMC - There will be a processing delay of all orders as WMC and PIE process order held in queue.
-SignupApp and PIE are up and data is currently being processed
Blueshift - Will experience delayed updates to list, subscription/AMB, and product transactions.
Reporting - Any new data sourced from Advantage will be delayed until ADV is online and replicating. This includes a brief delay in Batch Orders reporting during the downtime. Daily reports are expected to be caught up on schedule Saturday. - New Stitch costs will be delayed until Tuesday following new server connection. - The following reports are expected to be refreshed by Tuesday following new server connection: o Adverse Events_NMH o Auto Renew Notification Analysis o AutoDelivery Cancel Reasons o Future and Past Installments o Inventory Management o MMP Commissions Dashboard o TCC TEL Outbound Performance o Unapplied Credits
We wanted to provide an update on progress. We are halfway through our migration punch list and the Advantage database backup and restore are taking longer than expected. We are looking at a new completion time of 12:30am, instead of our originally estimated 10pm.
We will provide another progress update once the migration has completed, or if anything changes with our newly estimated time.
Thanks, 14West Technologies Team
Jul 12, 23:02 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:02 EDT
Scheduled -
Hi,
As previously communicated, our Advantage Production migration from AWS to On Premises has begun and is expected to take up to 4 hours.
Please refer to emails sent on Wednesday, June 26th and Tuesday, July 9th titled: "IMPORTANT || Advantage PRODUCTION migration from AWS to On-Prem (TierPoint)" for a list of detailed impacts.
We will provide another update once the migration has completed.