Also a little off topic, but I'm really shocked that your administrators didn't do anything before this to protect the network. Granted, it's a pain, but when these holes became public knoledge, every server should have been upgraded, and every client should have had their browser upgraded. I know that some companies don't see the benifit of dedicating resources to this, but as they've now seen, the penalty for non compliance is pretty large.

As far as the Exchange servers, they could have bee set up beforehand to strip off the offending attachments.

As for your question, I'd send an email and a "net send" to a couple people.

But as in most cases, the real solution is prevention. Not that it's your responsibility, but being an NT sys admin, it seems negligent that steps wern't taken to protect things before this.

Rich

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.