Blog

University Technology is aware of the recently announced Apple Mac OS security issue called "Rootpipe" affecting Mac OS X versions 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite). We are closely monitoring this issue and more details will be forthcoming about our response plan at the end of this week.

Last Wednesday, Apple released a major update to the latest version of Mac OS, version 10.10 (Yosemite). In addition to correcting several issues with Yosemite that had caused many organizations, including Drew, to recommend against upgrading, this latest update also included fixes for several security issues. The full extent of those issues were disclosed on Thursday by the independent researcher who originally discovered the vulnerability, including that the issue exists in prior versions of Mac OS starting with 10.7 (Lion) and onward. As Apple has indicated that they do not intend to fix the issue in prior releases of Mac OS X, it will be necessary for all Macs to be upgraded to Yosemite including the 10.10.3 update released last week in order to eliminate the vulnerability.

University Technology is in the process of developing a plan to upgrade University-managed Macs to this release. While we do encourage you to upgrade any personally owned Macs to the 10.10.3 release at your own discretion, we ask that you do not do so on University managed Macs for now and instead wait for further information from UT which will be forthcoming at the end of the week.

Change in Service Center Support Model

It has been just over a month since we made the change to professional staff answering Service Center phone calls. In our first month full time staff answered 173 calls. Our most experienced student assistants answer lunchtime, evening and overflow calls. These students answered 25 overflow calls during the 9-12 and 1-5 shifts this month. This means that, in our first month, 87.4% of calls were answered by full time staff. We will continue to work toward a goal of 90%.

For those of you who have called the Service Center since January 26, we hope that you have experienced a higher level of service than ever before. It is our hope that calls will be resolved more quickly, often during the initial call, and that those questions requiring further investigation or expertise from another area in University Technology are routed efficiently so that resolution time is reduced.

The next time you have a technology question or problem, please call the UT Service Center at 973-408-4357 (or HELP from your Drew phone) or fill out a support request. We hope you’ll be pleased with the changes!

University Technology relies on an issue tracking system located at help.drew.edu to manage all technology-related questions, problems, and issues for the Drew Community. Help.drew.edu is the backbone of all technology support at Drew, and is therefore crucial to the success of the User Services Revitalization.This system allows us to keep track of issues, to communicate with users, and to ensure that questions and issues are assigned to the appropriate group or individual to ensure efficient resolution.

To this end, University Technology encourages you to fill out a support request or call the Service Center for any technology questions or issues. UT staff will create a support ticket for any requests that come in via phone, email, or other means, in order to ensure that it is documented and tracked through resolution.

When a ticket has been created, you will receive an email alert with the ticket project and number (for example, GNRL-1234) in the subject line. As work on your question continues, subsequent emails will be generated from the ticket, giving you updates or asking for further information. Reading and responding to these emails as appropriate will ensure that your question is resolved as quickly as possible. When the issue or question is resolved, a final email is sent to close the ticket.

If you would like to check on your open tickets, you can access them anytime at help.drew.edu. All status updates, questions for you and any other comments on the ticket are available at any time, as well as the opportunity to send a message to UT about the ticket.

The UT ticketing system is supported by Rian Spivak, whom you may know as our Hardware Support Specialist. In recent years, administration of this system as been added to his job responsibilities, and he has received extensive training in the system. Rian is constantly researching and implementing improvements to the system behind the scenes, and we hope that you notice these improvements on the customer service side as well.

Should you have any questions, comments, or suggestions about UT’s Change in Service Center Support Model or the help.drew.edu Ticketing System, please don’t hesitate to contact Gamin Bartle, Senior Director of Instructional Technology and User Services (gbartle@drew.edu).

Last Friday, Lenovo announced and published an advisory warning consumers that software known as SuperFish had been included on certain consumer-grade computers shipped by Lenovo between September 2014 and February 2015. SuperFish delivers advertising to users while web browsing and has also been found to present a security risk. In response to consumer feedback, Lenovo has discontinued the practice and provided a removal tool for users of affected Lenovo products. The United States Computer Emergency Readiness Team (US-CERT) has also published an advisory.

Lenovo computers purchased by UT for university use or computers recommended to students through the laptop program are NOT affected and none have included SuperFish. SuperFish was distributed with Lenovo’s consumer-grade line of notebook computers only and was not shipped with any of the enterprise-grade ThinkPad line of computers that Drew provides. If you have purchased a Lenovo laptop for yourself or your department has purchased Lenovo products outside of normal channels, we recommend that you consult Lenovo’s advisory to see if your computer is affected and follow the provided instructions for removing the SuperFish software.

For more information on the Lenovo SuperFish vulnerability, please see the following sites:

It has been just over two months since we announced the University Technology reorganization and I stepped into the role of Interim CIO. In that time, we have launched four important revitalization initiatives to enhance technology service to the community. I'd like to take a few minutes of your time to review the significant progress so far and what's still to come. Many of these changes are informed by the results of the Employee Technology Survey conducted this fall. We intend to issue a student oriented survey this spring, and both of these surveys will serve a vital role in our planning process going forward. I'd like to thank Gamin Bartle for leading the effort to administer this survey and Mike Richichi for writing the report, which you may read here.

As you read through the summaries of the work accomplished, they may strike you as different than a typical technology announcement. We are not pitching new tools that you can use with a lot of new features. That is deliberate. The four revitalization initiatives are focusing on the fundamental services that UT provides, reevaluating How and Why we deliver these services and not just What services we offer. The underlying motivation of each of these four initiatives is to either improve customer service or to eliminate unneeded complexity and reduce costs, freeing up resources for more important pursuits. Ensuring that the basic services are performing as effectively and efficiently as possible will put us in a better position to meet the evolving needs of Drew going forward.

So what is it that we have been doing for the past two months?

User Services Revitalization - Starting January 26, we made the most significant change to our customer service model since the beginning of the computer initiative. Calls to the University Technology Service Center during business hours are now answered by members of the UT professional staff. Student assistants will continue to answer Service Center calls during evening and lunch hours and also serve as overflow operators for periods of unexpected high call volumes. By putting experienced staff on the front-line, we are able to resolve more incidents during the initial call. Full-time staff are also able to provide continuity and take a more active role in ensuring that an incident which requires additional research or engaging other areas of UT is resolved quickly and efficiently. If you haven't used the Service Center recently, I encourage you to do so. The number is 973-408-4357 (or HELP from your Drew phone). Read more about the User Services Revitalization here.

Computing Experience Revitalization- UT's Operations team has been working to improve the most basic service any IT department provides, the computer on your desk. An important first milestone in this project has been to change the way your network drives work. By moving off of the Novell file servers to standard Windows servers, we are going to reduce software licensing costs and reduce complexity, but more importantly this change is a prerequisite for what will be coming later in the spring. We will be announcing new desktop management software for PCs which will automate keeping your computer healthy and up to date with patches and the current versions of Drew supported software. In addition, as more people rely upon the CloudPC service to access Windows-only Drew software from Macs and other devices, we have decided to invest in CloudPC and will be announcing a change to the more industry standard Citrix platform for CloudPC later this spring. Read more about the Computing Experience Revitalization here.

Infrastructure Revitalization- UT is making a significant investment to bolster wireless network coverage in the student residence halls to meet current demand. This past week, based upon an engineer's site survey conducted in the Fall, we installed new wireless access points throughout the Tolley and Brown residence halls. This represents the highest density wireless deployment we have on-campus, with a dedicated access point installed per every two bedrooms. This deployment will serve as a model for other buildings on campus. Based upon a follow-up site survey, we will plan for wireless improvements in all student residence halls, with the bulk of the work to commence this Summer.

The campus telephone system will also be revamped. Drew's current phone system was installed in the late 1980s, is costly to operate, and lacks some basic expected calling features like Caller ID for off-campus calls. This January, work began in the installation of a new telephone system. The basic equipment is on-site and being configured. The first roll out of new phones will be to the 22 Madison building, which is not currently on Drew's phone system. Read more about the Infrastructure Revitalization here.

Administrative Systems Revitalization- The Enterprise Applications team has been meeting with the major users of Banner to set priorities for changes and new functionality in the coming months. An initial priority for this Revitalization project has been to focus on the Finance area, in particular budget manager reporting. Working with the Finance team, new processes have been developed for managing and reporting on restricted funds which will be rolled out in the coming months.

In addition, UT has been able to acquire an easier to use web-based reporting tool which will supplement the existing Argos reports. Training for IBM Cognos for UT staff and a group of functional users was delivered in December and we are currently in the process of setting up a production installation of Cognos. Expect more information on Cognos in the coming months. Read more about the Administrative Systems Revitalization here.

I would like to acknowledge the dedicated and talented UT staff who have responded to the call for change with professionalism and skill. Thanks to their efforts, significant progress has been made in a very short time period and there is much more to come. I would also like to thank Mike Groener and President Baenninger for their support of these initiatives. I am eager to hear your feedback on this or any other technology related concerns. Please feel free to reach out to me directly at elarsson@drew.edu with your feedback.

Project Description

To improve the efficiency and customer service of Enterprise Application we have begun to meet with functional user departments to assess their ongoing needs and utilization of banner and related software systems. These will include determining new banner work flows, use of banner document management and implementing new reporting tools with Cognos.

An initial priority has been to meet with finance to develop accurate restricted funds reports for the budget managers.

Milestone

We have already met with a couple departments and meetings with additional departments have been scheduled, and in some cases rescheduled due to weather related school closings.

After detailed analysis several meetings have been held with Finance and advancement services and an action plan has been developed to provide more accurate restricted fund reports within the first quarter of this year.

Coming Next

We are working with University Technology Operations to develop a roll-out plan for the production Cognos reporting server

Enterprise Applications will be reaching out to more functional user departments to schedule review meetings

New space on uknow.drew.edu for tracking your functional software business process documentation.

Project Description

Work on the Infrastructure Revitalization has already begun and includes an evaluation of and improvement of WiFi coverage in the student residence halls and replacement of the aging campus telephone system.

Milestone

A great deal of planning and preparation has been done on the improvement of WiFi coverage in the student residence halls. This process has included collecting data from student reports of WiFi issues, extensive WiFi signal testing, and bringing in outside consultants to review and refine placement of new WiFi Access Points (APs). The first residence halls that will see these improvements are Tolley and Brown.

On Tuesday, Wednesday and Thursday of this week, technicians will be installing additional APs throughout Tolley and Brown, focusing on dorm rooms to ensure good WiFi coverage for everyone. This is being done in coordination with Residence Life so that students will have advanced notice of when installers will need access to each room.

Coming Soon

This work is the foundation for further WiFi improvements in other residence halls on campus. University Technology will use student feedback and results from further signal strength testing as we plan and design the next installations.

Project Description

To lay the technical groundwork for future development with the Computing Experience Revitalization initiative, we have begun the migration of user data from Novell file servers to Windows file servers. This data includes personal drives (U: F:), organizational drives (O:, P:, G:), course-related drives (T:, R:, K:), and applications (M:). Drew computers now log in mounting the drives through Windows instead of via the Novell Client. A new web-based interface for accessing files off-campus has been launched, MyFiles.

Our team is also underway in the implementation of a Citrix environment to replace CloudPC's current vWorkspace installation, updating our back-end technology supporting Macs on campus, and updating our development environment of TreeHouse in preparation of its relaunch.

Milestone

Beginning January 21st, computers were switched to using a Windows script to mount network drives instead of the Novell Client. Starting that weekend and continuing every weekend through February 14th, volumes are being migrated over to the new file servers. More information and a full schedule can be found here.MyFiles has been released, with a formal launch to follow shortly.

Coming Next

Once the Citrix environment is ready, we will be launching an improved CloudPC for the university. After the file migration is complete, the team will work to develop an improved computing model taking advantage of SCCM and Casper to ensure an optimal computing experience, keeping in mind both existing computers already out there and new computers. An updated version of TreeHouse using the latest version of the underlying software (Luminis) will begin testing soon, after which will follow a redesign for the relaunch.

Project Description

As part of a User Services Revitalization initiative, calls to the Service Center during business hours will be answered by full-time staff starting at the end of January. The team will also be reviewing and formalizing support processes with the goal of improving response and resolution times as well as better handling of service requests that involve multiple areas of UT. As they always have, our students will continue to play a vital role in customer support.

Milestone

On January 26, 2015, University Technology full-time staff began answering Service Center calls during business hours. Experienced student assistants are covering the phones between 12:00 pm and 1:00 pm, as well as during evening hours (5:00 pm - 10:00 pm).

Coming Next

University Technology will present the results of our Drew Employee Customer Satisfaction Survey, which was conducted late last year. 130 members of the Drew Community responded to the survey, and the feedback is informative and actionable. User Services is working on plans for responding to the information, comments, and suggestions gathered from the survey. We thank everyone who participated for taking the time to supply valuable responses to inform this revitalization.

On Monday evening, March 11th, we will be putting the new network switch in Brothers College into production as the first step in upgrading our campus network infrastructure. We ran into problems during our previous attempt in January and switched back to the old equipment while we did some additional testing to work around the issue. This is the largest change we've made to the network infrastructure in a decade. We expect that it will take a few hours to swap out the switch and reconnect everything. Our intention is to make sure that nearly all public-facing services continue to operate, with only a few exceptions, and barring unforeseen problems. We will be posting updates to the CNS Facebook and Twitter feeds during the work.

The following buildings will have no network connectivity (wired or wireless) on the evening of Monday 11th: Brothers College, Hall of Science, Davies, Faulkner, Gilbert, Hannon, Lewis, Sitterly, Smith and Sycamore.

During the day on Monday, we will take steps to host Internet-facing services (Moodle, Library, faculty/staff GroupWise email, the web site, etc.) on servers in Pepin and the Learning Center so that they remain operational while we work. At 6:30 PM, there will be a very brief internet outage as we re-route our internet connection from Brothers to Learning Center.A second, brief internet outage will occur at the end of the evening when we switch the internet connection back to Brothers.

At 7pm, we are going to start to disconnect equipment and the buildings connected to Brothers College. At that point, the buildings listed above will be off the network for the evening.

Once Brothers is back up and running, we will be carefully monitoring for problems that might be caused by the change in configuration. We will announce a schedule for replacing the switch in the Learning Center, which will give us the full benefit of the network upgrade in the near future. Given the scope of this change to the backbone of the network, we may need to schedule additional work in order to make configuration changes should unexpected complications arise.

We will be updating this entry, adding additional details.

Just a little background . . .

We ran into an unexpected problem during the January attempt, which lead to additional disruptions to some services. Around 2am, we made a decision to put the old switch back into use, so that services were largely restored to normal by 5am. However, the old switch is actually sitting next to the new one - we don't have to physically remove it from the rack and install the new one this time (that alone took two hours last time). This time, it's simply a matter of unhooking the old switch, plugging it in, and testing. While we did find the cause of the major problem that came up in January, and we've done additional testing, it is still possible that unexpected issues will come up - we can't completely duplicate the production network (equipment, connections, configuration, network traffic, and so forth). Once we're done, we still to have to schedule the Learning Center switch replacement. We'd originally hoped to do BC over January and LC during this coming week. If this upgrade goes well, we will be looking at the calender to try to find the least disruptive time possible to do that. If things are working well, we will be more conservative about the LC replacement schedule. If the BC switch is working well, but some of the configuration changes needed are causing problems between BC and LC (which would be very disruptive), we might adopt a more aggressive schedule for replacing the Learning Center switch if we believe it will solve the issue.

What we're doing

We're replacing our 10-year-old Cisco Catalyst 6500 swiches in Brothers College and the Learning Center with new data center switches from Brocade. Nearly all of the network traffic on campus passes through one or both. Once it's complete, we'll not only have new, faster switches, but also a faster data connection between the BC and LC (10 gigabits per second of traffic, instead of a pair of 1 gigabit per second connections). In addition, the computer systems room in Pepin, where we have some important systems, will no longer pass traffic through a smaller switch in Pepin, but instead pass network traffic directly to either LC or BC. We're also going to patch the Pepin switches to the rest of the network in a way that will allow that west side of campus to remain connected to the internet and more campus systems if Learning Center loses power and emergency power. Doing this ahead of the Learning Center upgrade will also make that upgrade substantially less disruptive.

On Thursday evening, January 17th, we are planning to replace the network switch in Brothers College as the first step in upgrading our campus network infrastructure. This is the largest change we've made to the network infrastructure in a decade. We expect (barring complications) that it will take a few hours to swap out the switch and reconnect everything. Our intention is to make sure that nearly all public-facing services continue to operate, with only a few exceptions (the largest is that student email will be shut down while we are doing the work). We will be posting updates to the CNS Facebook and Twitter feeds during the work.

The following buildings will have no network connectivity (wired or wireless) on the evening of January 17th: Brothers College, Hall of Science, Davies, Faulkner, Gilbert, Hannon, Lewis, Sitterly, Smith and Sycamore. Student email will be down for the evening,

During the day on Thursday, we will take steps to host Internet-facing services (Moodle, Library, faculty/staff GroupWise email, the web site, etc.) on servers in Pepin and the Learning Center so that they remain operational while we work. At 6:30 PM, there will be a very brief internet outage as we re-route our internet connection from Brothers to Learning Center.A second, brief internet outage will occur at the end of the evening when we switch the internet connection back to Brothers.

At 7pm, we are going to start to disconnect equipment and the buildings connected to Brothers College. At that point, the buildings listed above will be off the network for the evening.

Once Brothers is back up and running, we will be carefully monitoring for problems that might be caused by the change in configuration. We will announce a schedule for replacing the switch in the Learning Center, which will give us the full benefit of the network upgrade in the near future. Given the scope of this change to the backbone of the network, we may need to schedule additional work in order to make configuration changes should unexpected complications arise.

We will be updating this entry, adding additional details.

Just a little background . . .

We're replacing our 10-year-old Cisco Catalyst 6500 swiches in Brothers College and the Learning Center with new data center switches from Brocade. Nearly all of the network traffic on campus passes through one or both. Once it's complete, we'll not only have new, faster switches, but also a faster data connection between the BC and LC (10 gigabits per second of traffic, instead of a pair of 1 gigabit per second connections). In addition, the computer systems room in Pepin, where we have some important systems, will no longer pass traffic through a smaller switch in Pepin, but instead pass network traffic directly to either LC or BC. We're also going to patch the Pepin switches to the rest of the network in a way that will allow that west side of campus to remain connected to the internet and more campus systems if Learning Center loses power and emergency power. Doing this ahead of the Learning Center upgrade will also make that upgrade substantially less disruptive.

On the morning of *Tuesday, December 4th*, Drew passwords, when used with Drew web applications will become case-sensitive (distinguishing between upper- and lower-case letters). This is a change - in the past, no matter what mix of upper- and lower-case letters you picked, they were treated as equivalent when using your uLogin account with Drew-hosted web applications.
*We recommend that* *[everyone set or review their password security questions |https://cas.drew.edu/pwm/private/SetupResponses?forwardURL=http://www.drew.edu/accounts/\]**ahead of time, so you can reset your password if there is a problem.*
* *
*Q:* Will this change the way I log into my computer on- or off-campus?
*A:* _No. This only has an effect on uLogin passwords when used with web applications. Network (uLogin) passwords, when used to authenticate to a computer, have been case-sensitive for years. This has actually been a source of confusion for customers in the past, and we are now eliminating it._
* *
*Q:* I've had problems with the password self-service feature on Treehouse in the past. Will I be able to change or reset my password?
*A:* _If you know the answers to your security questions, yes. One of the primary reasons for this change is to fix a problem with the self-service password feature caused by the inconsistent handling of mixed-case password between different systems. It was actually preventing users from being able to update their passwords because the password change utility was using case sensitivity, but the initial web session login hadn't. If you used an all lower-case version of a mixed-case password when presented with the Drew web login screen, your password change would then fail._
_ __ _
*Q:* I don't understand what you mean by "case sensitivity".
*A:* _Here's an example. Currently, if your password is "33dawwnPrarrie", you'd need to type that in exactly that way in order to log into a campus workstation. Our web-based applications were using a specific method to test the passwords that was case insensitive - so "33dawwnprarrie" would be treated the same as "33dawwnPrarrie"._
On the morning of *Tuesday, December 4th*, Drew passwords, when used with Drew web applications will become case-sensitive (distinguishing between upper- and lower-case letters). This is a change - in the past, no matter what mix of upper- and lower-case letters you picked, they were treated as equivalent when using your uLogin account with Drew-hosted web applications.

*We recommend that* *[everyone set or review their password security questions |https://cas.drew.edu/pwm/private/SetupResponses?forwardURL=http://www.drew.edu/accounts/\]**ahead of time, so you can reset your password if there is a problem.*
* *

*Q:* Will this change the way I log into my computer on- or off-campus?
*A:* _No. This only has an effect on uLogin passwords when used with web applications. Network (uLogin) passwords, when used to authenticate to a computer, have been case-sensitive for years. This has actually been a source of confusion for customers in the past, and we are now eliminating it._

* *
*Q:* I've had problems with the password self-service feature on Treehouse in the past. Will I be able to change or reset my password?
*A:* _If you know the answers to your security questions, yes. One of the primary reasons for this change is to fix a problem with the self-service password feature caused by the inconsistent handling of mixed-case password between different systems. It was actually preventing users from being able to update their passwords because the password change utility was using case sensitivity, but the initial web session login hadn't. If you used an all lower-case version of a mixed-case password when presented with the Drew web login screen, your password change would then fail._
_ __ _

*Q:* I don't understand what you mean by "case sensitivity".
*A:* _Here's an example. Currently, if your password is "33dawwnPrarrie", you'd need to type that in exactly that way in order to log into a campus workstation. Our web-based applications were using a specific method to test the passwords that was case insensitive - so "33dawwnprarrie" would be treated the same as "33dawwnPrarrie"._

This is an important reminder - the F-Prot antivirus software, formally distributed with Drew-issued Windows PCs - is no longer supported and no longer getting updates. With each passing day, it is increasingly out-of-date. This poses a very real risk to your personal data, and University data to which you have access. You need to install F-Secure as soon as possible. A significant number of computers do not have F-Secure at this time.
You should install F-Secure via the Application Explorer folder on your Drew-issued Windows computer. Browse to "Install Software" and then "Utilities" and look for an icon named "Install F-Secure Antivirus". If you have F-Prot installed, this will remove it and install the new package.

If the installation does not run, or you are having problems with the Application Explorer, you need to contact the CNS Helpdesk at 3205 or send an email describing the problem to helpdesk@drew.edu.

This year's new computer models (Macintosh and Thinkpad models with Windows 7) already have F-Secure, and very recently reimaged computers may as well. The easiest way to determine if F-Secure is installed on a Windows system is to Windows Start button, select "All Programs" and see if there is a folder titled "F-Secure Anti-Virus for Workstations". It may appear at the end of the list. If F-Secure is not there, and F-Prot is listed, you need to install F-Secure.

This is an important reminder - the F-Prot antivirus software, formally distributed with Drew-issued Windows PCs - is no longer supported and no longer getting updates. With each passing day, it is increasingly out-of-date. This poses a very real risk to your personal data, and University data to which you have access. You need to install F-Secure as soon as possible. A significant number of computers do not have F-Secure at this time.
You should install F-Secure via the Application Explorer folder on your Drew-issued Windows computer. Browse to "Install Software" and then "Utilities" and look for an icon named "Install F-Secure Antivirus". If you have F-Prot installed, this will remove it and install the new package.

If the installation does not run, or you are having problems with the Application Explorer, you need to contact the CNS Helpdesk at 3205 or send an email describing the problem to helpdesk@drew.edu.

This year's new computer models (Macintosh and Thinkpad models with Windows 7) already have F-Secure, and very recently reimaged computers may as well. The easiest way to determine if F-Secure is installed on a Windows system is to Windows Start button, select "All Programs" and see if there is a folder titled "F-Secure Anti-Virus for Workstations". It may appear at the end of the list. If F-Secure is not there, and F-Prot is listed, you need to install F-Secure.

This weekend CNS staff spent time doing additional troubleshooting and testing of our virtual server and storage environment. After further analysis and testing, including replacing equipment in some servers, we were able to determine that a network switch in our storage environment was the source of the problem. As a troubleshooting measure, we have removed the defective switch from the storage configuration, and at this time are seeing indicators of greatly improved performance and stability. The next few days will be an indicator of whether the situation is in fact improved.

The issue is that our storage network is now in a less than fully redundant configuration, and we eventually need to replace the device. However, before we do that we must attempt to determine if the switch itself is defective, one of its interface modules, or if there was an error in the switch configuration or our storage topology. However, this testing can now be done in a controlled environment, and the switch restored when we're confident the underlying issue is resolved.

We again must thank everyone for their patience and consideration. Although we were able to avoid major downtime, we did have several outage events that were disruptive, and for that we apologize. The nature of this problem, however, was complicated and subtle, and much of our troubleshooting involved downing systems, making a change, and waiting for another failure. We hope those situations are no longer necessary and we can move forward.