Batch Script Error Leads to System32 Deletion and Server Failure

Despite passing tests and managerial approval, the script caused an unforeseen disaster.

In this edition, we feature a reader, pseudonymously named Pascal, who worked for a company that recently implemented its initial Exchange server, supporting approximately 600 mailboxes.

Pascal recounted that the IT manager emphasized the importance of maintaining the Information Store’s performance, proposing a weekly offline defragmentation.

Finding this prudent, Pascal developed a batch script to halt the Information Store, execute eseutil /d for database compaction, remove temporary files, and restart the service.

After successful testing, which effectively reduced the Store’s size, the script was scheduled for execution on Friday evening, allowing the team to depart for the weekend.

However, shortly after the weekend began, Pascal received numerous alerts indicating that Exchange services had ceased functioning.

He promptly returned to the office, discovering that the Windows NT 4 server was unresponsive, with minimal functionality and Exchange services halted.

Pascal identified the issue: his script included the DEL *.* command without specifying a target directory. Executed from the System32 folder, it initiated file deletion within that critical directory.

The script erroneously deleted most System32 files, effectively disabling Windows NT 4 and rendering the server irreparable. A complete rebuild and restoration were necessary, consuming the entire weekend.

Reflecting on the incident, Pascal acknowledges it as a low point, though financially beneficial due to overtime compensation. Notably, his career remained intact despite the mishap.

Source link